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]], September 2012 | *[[Software Implementation of CDA]], September 2012 | ||
**Sept 2013: for RE-approval | **Sept 2013: for RE-approval | ||
− | + | *[[Persisting FHIR Resources]], January? 2013 | |
− | |||
− | *Persisting FHIR Resources | ||
**There are three approaches that have already been taken for persisting FHIR resources. | **There are three approaches that have already been taken for persisting FHIR resources. | ||
**#Just each resource by itself with links | **#Just each resource by itself with links | ||
Line 16: | Line 14: | ||
**#Entire CDA like documents that contain many clinical statements within them. | **#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). | **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). | ||
+ | |||
+ | Candidate topics: | ||
*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:40, 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
- Software Implementation of CDA, September 2012
- Sept 2013: for RE-approval
- Persisting FHIR Resources, January? 2013
- 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).
- There are three approaches that have already been taken for persisting FHIR resources.
Candidate topics:
- v2-v3 migration / mapping, inclusive of recommendations as to how one should 'enrich' current v2 interface to ensure ease of transformability.