Difference between revisions of "201605 C-CDA on FHIR Connectathon Proposal"
| Line 29: | Line 29: | ||
===Document Creator=== | ===Document Creator=== | ||
<!-- Provide a description of the capabilities this role will have within the connectathon --> | <!-- Provide a description of the capabilities this role will have within the connectathon --> | ||
| − | Creates a C-CDA on FHIR document (Bundle containing a Composition and supporting resources) using whatever means are appropriate, including manual creation, assembling documents from other resources, transforming C-CDA R2.1 XML documents (CDA -> FHIR transform), etc. | + | Creates a C-CDA on FHIR document (Bundle containing a Composition and supporting resources) using whatever means are appropriate, including manual creation, assembling documents from other resources, transforming C-CDA R2.1 XML documents (CDA -> FHIR transform), etc. and submits that document to a FHIR server. |
===Document Consumer=== | ===Document Consumer=== | ||
Revision as of 22:17, 5 February 2016
C-CDA on FHIR
This track will test the exchange of Clinical Documents (using document Bundle resources containing a Composition and other supporting resources) that conform to the profiles of the in-progress C-CDA on FHIR Implementation Guide.
Submitting WG/Project/Implementer Group
Justification
The Structured Documents Work Group is creating an Implementation Guide with a set of profiles (using the StructureDefinition resource) that represent Consolidated CDA documents using FHIR, and the work needs the kind of active testing and review that only a Connectathon can provide. Also, it has been a long time since a FHIR Connectathon has had a document track, and the Composition resource has changed significantly during that time so even the base resource could stand some more live testing.
Proposed Track Lead
- Rick Geimer
- Email: rick dot geimer at lantanagroup dot com
- Skype: rgeimer
Expected participants
- Lantana Consulting Group
- TBD
Roles
Document Creator
Creates a C-CDA on FHIR document (Bundle containing a Composition and supporting resources) using whatever means are appropriate, including manual creation, assembling documents from other resources, transforming C-CDA R2.1 XML documents (CDA -> FHIR transform), etc. and submits that document to a FHIR server.
Document Consumer
Receives a C-CDA on FHIR document and does one or more of the following: a) validates the document against the C-CDA on FHIR profiles, b) displays the document in a browser using a supplied display stylesheet, and c) extracts discrete resources from the document for some other purpose.
Scenarios
TBD
