Description: This workflow describes the process that the Shared Health Record will go through to save an inbound encounter.
Sponsor: SHR community
Last Modified: 12th March 2015
A Shared Health Record should support receiving of clinical document using an XDS.b interface. The document that is receives are expected to be IHE profiled CDA templates.
Another option for an interface into the SHR was to parse the document at the IL and pass the document in object form to the SHR for storage using a custom interface. We decided against doing this as the cons out weighed the pros. The pros and cons of this approach are listed below:
title SHR Internal save encounter workflow participant IL participant SHR Interface as INT participant Document registry as REG participant SHR Document store as DS participant SHR Discrete data storage as DDS IL->+INT:  Send clinical document INT->+REG:  Register document metadata REG->-INT:  Acknowledgement INT->+DS:  Forward clinical document DS->DS:  Store document as-is DS->-INT:  Acknowledgement INT->+DDS:  Send clinical document DDS->DDS:  Parse and extract understood discrete data from the document DDS->DDS:  Persist understood discrete data DDS->-INT:  Acknowledgement INT->-IL:  Acknowledgement that document was stored
For a more detailed design of how this can be implemented in the OpenMRS SHR reference application see: OpenMRS as the SHR design document.
|1||Send clinical document||XDS.b provide and register|
|2||Register document metadata||XDS.b specified transaction|
|4||Forward clinical document||Internal system function|
|5||Store document as-is|
|7||Send clinical document||Internal system function|
|8||Parse and extract understood discrete data from the document|
|9||Persist understood discrete data|
|11||Acknowledgement that document was stored||XDS.b provide and register response|