Yes, agree with the @ibacher and @mseaton … for Dose Unit you will want to be submitting to "dosageInstructions[0].doseAndRate[0].doseQuantity.code, where code would be a coded reference to the unit (likely the uuid or snowmed code of the unit).
If you look at the MedicationRequest object returned when viewing a prescription, you’ll see how these elements like the dose unit, route, and frequency are defined:
In each of these cases, though you’ll be displaying the “unit” or “display” fields to the user, you’ll need to submit the “code” back to the server so that a proper match is made.
A current potential missing step is that there should be an endpoint for you to to request all the valid dose units, routes, and frequencies to use to render those drop downs (with the “unit” or “display” being the display text of the dropdown, and the “code” being the underlying value). If you don’t already know these endpoint, it would likely be worth looking at the code for the Drug Orders ESM (or perhaps talk to whoever is working on it… @samuel34 @grace?) as they will have a need for the same endpoints there.
There is a REST endpoint provided by the REST module to get this information this that is used in the 2.0 Order Entry OWA:
ws/rest/v1/orderentryconfig?v=custom:(uuid,display)
… but I’m not sure if is what we intend/want to use going forward, or if we’ve developed a FHIR equivalent? (@ibacher ?)
