This wiki has undergone a migration to Confluence found Here
Difference between revisions of "AID three year plan"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 6: | Line 6: | ||
*#*Document/describe (for all possible cell transitions) how those steps could be supported/achieved. | *#*Document/describe (for all possible cell transitions) how those steps could be supported/achieved. | ||
*#*We focus on Patterns for Application Development. Guidance, no normative outcomes. | *#*We focus on Patterns for Application Development. Guidance, no normative outcomes. | ||
| − | *#* | + | *#*Promote creation and usage of toolkits |
*#*Outreach to RIMBAA implementers (especially those not present at RIMBAA meetings); publish reviews of existing RIMBAA implementations | *#*Outreach to RIMBAA implementers (especially those not present at RIMBAA meetings); publish reviews of existing RIMBAA implementations | ||
*#Education - for newbies to RIMBAA | *#Education - for newbies to RIMBAA | ||
*#Standard Improvement | *#Standard Improvement | ||
*#*Identify issues in HL7 standards during the implementation process | *#*Identify issues in HL7 standards during the implementation process | ||
| − | |||
*#*Identify issues caused by the ‘interoperability mindset’ of the RIM | *#*Identify issues caused by the ‘interoperability mindset’ of the RIM | ||
*#*V3 constructs: Context Conduction, Update Mode, Object Versioning | *#*V3 constructs: Context Conduction, Update Mode, Object Versioning | ||
| − | |||
==Three year plan== | ==Three year plan== | ||
*Project: create set of whitepapers (#550) | *Project: create set of whitepapers (#550) | ||
| − | *Last updated 2010-10-04 | + | *Created: September 2009. Last updated 2010-10-04 |
*Best practices whitepapers: | *Best practices whitepapers: | ||
**Implementation of CDA in software, October 2010 | **Implementation of CDA in software, October 2010 | ||
| Line 29: | Line 27: | ||
*Project: reference implementation (#549) | *Project: reference implementation (#549) | ||
**Document design/decision process of the Java RIMBAA reference implementation, Sept 2010 | **Document design/decision process of the Java RIMBAA reference implementation, Sept 2010 | ||
| − | **20100517: During the Rio WGM this project was abandoned because we don't have the resources to support and maintain the reference implementation. | + | **20100517: During the Rio WGM this (non-approved) project was abandoned because we don't have the resources to support and maintain the reference implementation. |
Revision as of 13:00, 4 October 2010
- See [1] for Three-year-Plans as collected by the TSC.
- Goals of the RIMBAA WG:
- Marketing - Public exposure of successes (of v3 implementability and the RIM itself)
- Sharing of experiences and solutions
- Document/describe (for all possible cell transitions) how those steps could be supported/achieved.
- We focus on Patterns for Application Development. Guidance, no normative outcomes.
- Promote creation and usage of toolkits
- Outreach to RIMBAA implementers (especially those not present at RIMBAA meetings); publish reviews of existing RIMBAA implementations
- Education - for newbies to RIMBAA
- Standard Improvement
- Identify issues in HL7 standards during the implementation process
- Identify issues caused by the ‘interoperability mindset’ of the RIM
- V3 constructs: Context Conduction, Update Mode, Object Versioning
Three year plan
- Project: create set of whitepapers (#550)
- Created: September 2009. Last updated 2010-10-04
- Best practices whitepapers:
- Implementation of CDA in software, October 2010
- Code generation, February 2011
- LDM/PDM approaches, May 2011
- Outreach to RIMBAA implementers to get hold of experiences/best practices.
Old projects
The following projects have been completed or aborted:
- Project: reference implementation (#549)
- Document design/decision process of the Java RIMBAA reference implementation, Sept 2010
- 20100517: During the Rio WGM this (non-approved) project was abandoned because we don't have the resources to support and maintain the reference implementation.
