This wiki has undergone a migration to Confluence found Here
Persisting FHIR Resources
Revision as of 13:43, 21 September 2012 by Rene spronk (talk | contribs) (Created page with "category:RIMBAA WhitepaperCategory:HowTo '''This whitepaper is one of a series of whitepapers created by the RIMBAA Work Group. The wh...")
This whitepaper is one of a series of whitepapers created by the RIMBAA Work Group. The whitepaper is based on actual HL7 version 3 implementation experiences and aims to document a best practice or an implementation pattern.
Summary
- From discussions during the September 2012 WGM
- 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.
(potential) authors/contributors
- Eve Marcelina Rubillos emfrubillos@gmail.com
- I would want to volunteer in writing or creating this whitepaper. I am quite new to FHIR, it has only been a little over a month since I have been joining conference calls whenever my time permits, thus, I would prefer working with a team.
- david hay david.hay25@gmail.com
- I'm happy to be a reviewer / contributor - especially in the noSql space - but there are better qualified lead authors out there..
- alex.zupan@tbsgroup.com alex.zupan@tbsgroup.com
- Alex can provide info on our O-R (Hibernate) approach, starting from the class diagram down to the physical db model (tested on Oracle and MySql).
- Charles McCay charlie@ramseysystems.co.uk
- I may be able to offer some example content from the semantichealthnet project
