This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

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

From HL7Wiki
Jump to navigation Jump to search
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
The '''Creation of a Set of RIMBAA Whitepapers''' project was established to manage the process of creating a set of whitepapers.  
 
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 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.
+
*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==
 
==Scope==
Line 6: Line 6:
  
 
==Planning==
 
==Planning==
*[[Software Implementation of CDA]], September 2012
+
*[[Software Implementation of CDA]]
**Sept 2013: for RE-approval
+
**May 2016, stable pending new (features) of tools, up for re-approval in May 2017
 
+
*[[Implementation Guidance for the IVL TS data type]]
Candidate topics:
+
**Sept 2014: will need additional review, won't need maintenance once finished
*Persisting FHIR Resources.
+
**Sept 2015: stable, doesn't need review
**There are three approaches that have already been taken for persisting FHIR resources.
+
*[[FHIR Server Design]]
**#Just each resource by itself with links
+
**Sept 2015: create starter version based on Brian P's presentation
**#Enough of a them linked together to be equivalent to a clinical statement or what we previously referred to as a SMIRF
+
*[[FHIR-v2 Mapping Guidance]]
**#Entire CDA like documents that contain many clinical statements within them.
+
**Sept 2015: thoughts on the mapping process, v2 messages to/from REST FHIR, and v2 messages to/from FHIR Messages
**The experiences of persisting FHIR resources in any of the “clusters” above in the various “NoSQL” databases such as MongoDB (Ewout), CouchDB (Gordon), ?? (PHI), XML (Van Der Zel).
 
*v2-v3 migration / mapping, inclusive of recommendations as to how one should 'enrich' current v2 interface to ensure ease of transformability.
 

Latest revision as of 10:27, 30 March 2017

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