This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Creation of a Set of AID Whitepapers"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 8: | Line 8: | ||
*[[Software Implementation of CDA]] | *[[Software Implementation of CDA]] | ||
**May 2015, stable pending new (features) of tools, up for re-approval in May 2016 | **May 2015, stable pending new (features) of tools, up for re-approval in May 2016 | ||
| − | |||
| − | |||
| − | |||
*[[Implementation Guidance for the IVL TS data type]] | *[[Implementation Guidance for the IVL TS data type]] | ||
**Sept 2014: will need additional review, won't need maintenance once finished | **Sept 2014: will need additional review, won't need maintenance once finished | ||
Revision as of 12:25, 14 April 2016
The Creation of a Set of RIMBAA Whitepapers project was established to manage the process of creating a set of whitepapers.
- Note: This is project #550 and #951 in the Project Insight tool. Project approved by FTSD on its call of 2010-10-19. Project approved by TSC on its call on 2010-11-08.
Scope
This is a long running (maintenance type) project to create a set of whitepapers with the consensus based findings of the RIMBAA WG as to what the v3 implementation best practices (or: v3 implementation patterns) are.
Planning
- Software Implementation of CDA
- May 2015, stable pending new (features) of tools, up for re-approval in May 2016
- Implementation Guidance for the IVL TS data type
- Sept 2014: will need additional review, won't need maintenance once finished
- Sept 2015: stable, doesn't need review
- FHIR Server Design
- Sept 2015: create starter version based on Brian P's presentation
- FHIR-v2 Mapping Guidance
- Sept 2015: thoughts on the mapping process, v2 messages to/from REST FHIR, and v2 messages to/from FHIR Messages
