This wiki has undergone a migration to Confluence found Here
Difference between revisions of "AID Activities"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
Line 1: | Line 1: | ||
The AID HL7 "User Group", in order to fulfill its [[AID Mission and Charter|Mission and Charter]] is involved in the following activities: | The AID HL7 "User Group", in order to fulfill its [[AID Mission and Charter|Mission and Charter]] is involved in the following activities: | ||
#Facilitate the exchange of implementation experiences | #Facilitate the exchange of implementation experiences | ||
− | ##We accomplish this by organizing regular face-to-face meetings for the exchange of implementation experiences and architectural approaches between users of the HL7 standards. | + | ##We accomplish this by organizing regular face-to-face meetings for the exchange of implementation experiences and architectural approaches between users of the HL7 standards. We focus on Patterns for Application Development. Guidance, no normative outcomes. |
##*AID meets 3 times a year during the HL7 WGMs (i.e. meetings that are focused on HL7 standards development), and at so-called out-of-cycle meetings. We aim to geographically cover those areas where most of the HL7 users can be found. | ##*AID meets 3 times a year during the HL7 WGMs (i.e. meetings that are focused on HL7 standards development), and at so-called out-of-cycle meetings. We aim to geographically cover those areas where most of the HL7 users can be found. | ||
##*Any aspects related to the review of HL7 standards, and the creation of whitepapers is done at WGMs, and out-of-cycles are exclusively focused on the exchange of ideas/practices. | ##*Any aspects related to the review of HL7 standards, and the creation of whitepapers is done at WGMs, and out-of-cycles are exclusively focused on the exchange of ideas/practices. | ||
Line 13: | Line 13: | ||
#We provide feedback from the implementation community into the standards development process, to ensure that HL7 standards are easy to implement. | #We provide feedback from the implementation community into the standards development process, to ensure that HL7 standards are easy to implement. | ||
#*How (SMART) will we do this? We get ad-hoc comments during various presentations, but we'll need some structured way of 'havesting' feedback from the implementation community | #*How (SMART) will we do this? We get ad-hoc comments during various presentations, but we'll need some structured way of 'havesting' feedback from the implementation community | ||
+ | #Marketing - Public exposure of successes (of HL7 implementatations) | ||
+ | #Provide Education - related to software implementation |
Revision as of 20:44, 22 January 2014
The AID HL7 "User Group", in order to fulfill its Mission and Charter is involved in the following activities:
- Facilitate the exchange of implementation experiences
- We accomplish this by organizing regular face-to-face meetings for the exchange of implementation experiences and architectural approaches between users of the HL7 standards. We focus on Patterns for Application Development. Guidance, no normative outcomes.
- AID meets 3 times a year during the HL7 WGMs (i.e. meetings that are focused on HL7 standards development), and at so-called out-of-cycle meetings. We aim to geographically cover those areas where most of the HL7 users can be found.
- Any aspects related to the review of HL7 standards, and the creation of whitepapers is done at WGMs, and out-of-cycles are exclusively focused on the exchange of ideas/practices.
- See List of Scheduled Meetings
- We facilitate the exchange of questions and answers by means of an e-mail list and/or discussion forum
- We have a project to create a series of best practices documents that document the architectural and software implementation approaches.
- See List of Whitepapers and (project plan:) Creation of a Set of AID Whitepapers
- We accomplish this by organizing regular face-to-face meetings for the exchange of implementation experiences and architectural approaches between users of the HL7 standards. We focus on Patterns for Application Development. Guidance, no normative outcomes.
- We identify and support third parties in the design, development and maintenance of software toolkits that support the development of software applications that support or use one or more HL7 standards.
- How (SMART) will we do this?
- This is a joing activity with the Tooling Committee.
- We provide feedback from the implementation community into the standards development process, to ensure that HL7 standards are easy to implement.
- How (SMART) will we do this? We get ad-hoc comments during various presentations, but we'll need some structured way of 'havesting' feedback from the implementation community
- Marketing - Public exposure of successes (of HL7 implementatations)
- Provide Education - related to software implementation