This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Services for RIMBAA"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
|||
| Line 8: | Line 8: | ||
==See also== | ==See also== | ||
*Related blogpost by Keith: [http://motorcycleguy.blogspot.com/2010/07/virtual-medical-records-hl7-models-and.html]. | *Related blogpost by Keith: [http://motorcycleguy.blogspot.com/2010/07/virtual-medical-records-hl7-models-and.html]. | ||
| + | |||
| + | ==Some notes/thoughts== | ||
| + | *vMR as Content Model? | ||
| + | *Templates on e.g. Care Record as Content Model? | ||
| + | *Existing HL7 interactions as Interface? | ||
| + | *CRUD/REST as Interface? | ||
| + | *Use SAIF! | ||
| + | *Align/connect/traceability with SOA Ontology project? | ||
| + | *Align/connect/traceability with EHR-IM for Content Model? | ||
Revision as of 08:38, 16 July 2010
The Services for RIMBAA project is a joint effort by the SOA WG and the RIMBAA WG. The project was agreed upon during the May 2010 WGM.
Scope and Aim of the project
Status of the project
- A draft project plan has been created during the May 2010 WGM.
See also
- Related blogpost by Keith: [1].
Some notes/thoughts
- vMR as Content Model?
- Templates on e.g. Care Record as Content Model?
- Existing HL7 interactions as Interface?
- CRUD/REST as Interface?
- Use SAIF!
- Align/connect/traceability with SOA Ontology project?
- Align/connect/traceability with EHR-IM for Content Model?
