Configuring Order Entry

Owned by Darius Jazayeri
Jul 06, 2017
1 min read

To use the Order Entry API, you need to configure certain pieces of metadata, described here.

Order Frequencies

You must add rows to the order_frequency table. These frequencies must be represented by concepts, but can also have additional information allowing them to be machine-interpreted. See OrderFrequency.java.

At present there is no UI for managing order frequencies, so you must populate them via the orderfrequency REST resource, via the Java API, or via SQL.

Drug Routes

Set the Advanced Setting order.drugRoutesConceptUuid to be the UUID of a concept set containing routes.

Drug Dosing Units

Set the Advanced Setting order.drugDispensingUnitsConceptUuid to be the UUID of a concept set containing dosing units.

Drug Dispensing Units

Set the Advanced Setting order.drugDispensingUnitsConceptUuid to be the UUID of a concept set containing dispensing units. This set will typically be similar to the Dosing Units set, but might also include concepts that represent packages, bottles, etc.

Duration Units

Set the Advanced Setting order.durationUnitsConceptUuid to be the UUID of a concept containing duration units.

The concepts in this set must have a SAME-AS mapping to a SNOMED-CT concept source with a code for one of the durations listed in the Duration.java class. (Currently: seconds, minutes, hours, days, weeks, months, years.)

Test Specimen Sources

Set the Advanced Setting order.testSpecimenSourcesConceptUuid to be the UUID of a concept containing possible specimen sources for lab tests