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
Line 6: Line 6:
  
 
==Planning==
 
==Planning==
*[[Software Implementation of CDA]], October 2010
+
*[[Software Implementation of CDA]], September 2012
**Nov 2011: for RE-approval
+
**Sept 2013: for RE-approval
*[[RIM Based Persistence]], September 2011
 
**Nov 2011: for initial approval
 
*LDM/PDM approaches, May 2012
 
  
 
Candidate topics:
 
Candidate topics:
 +
*Persisting FHIR Resources.
 +
**There are three approaches that have already been taken for persisting FHIR resources.
 +
**#Just each resource by itself with links
 +
**#Enough of a them linked together to be equivalent to a clinical statement or what we previously referred to as a SMIRF
 +
**#Entire CDA like documents that contain many clinical statements within them.
 +
**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.
 
*v2-v3 migration / mapping, inclusive of recommendations as to how one should 'enrich' current v2 interface to ensure ease of transformability.

Revision as of 07:35, 20 September 2012

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.

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

Candidate topics:

  • Persisting FHIR Resources.
    • There are three approaches that have already been taken for persisting FHIR resources.
      1. Just each resource by itself with links
      2. Enough of a them linked together to be equivalent to a clinical statement or what we previously referred to as a SMIRF
      3. Entire CDA like documents that contain many clinical statements within them.
    • 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.