Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

FHIR Mapping

This is a suggestion on how to map OpenMRS TestOrder object into FHIR TBD.

Fields which didn't match into FHIR representation are marked on red. Keyword extension means that FHIR Extension has to be used to synchronize this field.
Fields which partially match into FHIR representation are marked on orange.

Fields from parent classes are omitted.

OpenMRS order documentation - Order Entry API.



OpenMRS TestOrder class extends Order class.

OpenMRS classOpenMRS fieldDB fieldFHIR fieldDetails
TestOrderspecimenSource : Concepttest_order.specimen_sourcespecimen : Reference(Specimen)
TestOrderlaterality : Lateralitytest_order.laterality

bodySite : CodeableConcept

FHIR: "Codes describing anatomical locations. May include laterality."

OpenMRS: "Has to be one of: LEFT, RIGHT, BILATERAL"
TestOrderclinicalHistory : Stringtest_order.clinical_historyrelevantHistory : Reference(Provenance)
TestOrder

frequency : OrderFrequency

numberOfRepeats : Integer

order.instructions

occurenceTiming : TimingSee table FHIR Timing class


FHIR Timing class - description

OpenMRS class

OpenMRS field

DB field

FHIR field

Details

OrderFrequencyfrequencyPerDay : Doubleorder.instructions

repeat.frequency : integer

repeat.period : decimal

repeat.periodUnit : UnitsOfTime

frequencyPerDay = frequency / (period * periodUnit), where period=1, periodUnit=d

if there's a period, periodUnit is required

TestOrdernumberOfRepeats : Integerorder.instructionsrepeat.count : integer
  • No labels