TestOrder synchronization

FHIR Mapping

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

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.

OpenMRS Order documentation - Order Entry API.

OpenMRS TestOrder class extends Order class.

OpenMRS class	OpenMRS field	DB field	FHIR field	Details

OpenMRS class	OpenMRS field	DB field	FHIR field	Details
TestOrder	specimenSource : Concept	test_order.specimen_source	specimen : Reference(Specimen)	-
TestOrder	clinicalHistory : String	test_order.clinical_history	relevantHistory : Reference(Provenance)	-
TestOrder	frequency : OrderFrequency	test_order.frequency	extension - Order Frequency Extension
Order	careSetting : CareSetting	orders.care_setting	extension - CareSetting FHIR Extension
Order	concept : Concept	orders.concept_id : integer	extension - Order Concept Extension
TestOrder	laterality : Laterality	test_order.laterality	extension - Laterality Extension	FHIR: "Codes describing anatomical locations. May include laterality." OpenMRS: "Has to be one of: LEFT, RIGHT, BILATERAL"
TestOrder	clinicalHistory : String	test_order.clinical_history	extension - Clinical History Extension
TestOrder	patient : Patient	orders.patient_id	subject : Reference
Order	encounter : Encounter	orders.encounter_id	context : Reference
Order	orderer : Provider	orders.orderer	recorder : Reference
Order	urgency : Urgency	orders.urgency	priority : ProcedureRequestPriority
Order	action : Action	orders.order_action	status : ProcedureRequestStatus