Difference between revisions of "Creation of a Set of AID Whitepapers"

From HL7Wiki
Jump to navigation Jump to search
Line 7: Line 7:
 
==Planning==
 
==Planning==
 
*[[Software Implementation of CDA]]
 
*[[Software Implementation of CDA]]
**Sept 2014: updating, re-approval in January 2015
+
**May 2015, stable pending new (features) of tools, up for re-approval in May 2016
 
*[[Persisting FHIR Resources]],  
 
*[[Persisting FHIR Resources]],  
 
**Sept 2014: Andy will create skeleton verson before meeting in January 2015
 
**Sept 2014: Andy will create skeleton verson before meeting in January 2015
 +
**sept 2015: probably a topic that's covered by [[FHIR Server Design]], should we fold this whitepaper into the new one?
 
*[[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
 
+
**Sept 2015: stable, doesn't need review
Candidate topics:
+
*[[FHIR Server Design]]
*v2-v3 migration / mapping, inclusive of recommendations as to how one should 'enrich' current v2 interface to ensure ease of transformability.
+
**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

Revision as of 15:43, 6 October 2015

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