Have you implemented OpenMRS? Please participate in the Implementation Site Survey. If you already have, thank you!
Child pages
  • Non-FHIR resource list for Sync
Skip to end of metadata
Go to start of metadata

Some data ( mostly OpenMRS specific metadata) cannot be mapped to FHIR resources - it will have to be pushed/pulled using other means - rest representations. Sync 2.0 Children will transmit these instances using the OpenMRS REST API.

Sync will need a separate client for sending the metadata - the default will be the client using the REST API. However it should be possible for implementers to inject their own implementation of the interface that will use different protocols.

Based on the data Sync wishes to push/retrieve, it should have an instance of the appropriate client (FHIR/REST). A facade should should be added that is responsible for figuring out the client to use and then using it to retrieve or push the object.

REST Client

The Sync module will maintain a REST client, which will be responsible for converting objects to their OpenMRS representations

Non-FHIR resource list

NoEntityNotesNot required to Sync
3Concept (and related classes)  
5HL7 metadata  

  • No labels