medplum / medplum / 26245060159

92%

main: 92%

push

github

React and Provider App components for Meds Ordering (#8999)

* feat: meds order form improvements

Signed-off-by: Oleg Rocklin <oleg@medplum.com>

* [autofix.ci] apply automated fixes

* fix: condition lookup fix

Signed-off-by: Oleg Rocklin <oleg@medplum.com>

* feat: order set prescribing support

Signed-off-by: Oleg Rocklin <oleg@medplum.com>

* fix: address PR comments and refactor dark mode

Signed-off-by: Oleg Rocklin <oleg@medplum.com>

* [autofix.ci] apply automated fixes

* fix: use of fhir ops vs bot ids for refs

Signed-off-by: Oleg Rocklin <oleg@medplum.com>

* fix: ci errors

Signed-off-by: Oleg Rocklin <oleg@medplum.com>

* fix: linter errors fix

Signed-off-by: Oleg Rocklin <oleg@medplum.com>

* [autofix.ci] apply automated fixes

* feat(meds-order-set): migrate useMedicationOrderSet to $order-set-url FHIR custom operation

Closes the API asymmetry flagged in PR #8999 Claude review: useMedicationOrderSet
no longer takes a botIdentifier and calls executeBot directly. Now POSTs to a
project-scoped $order-set-url custom FHIR operation on PlanDefinition, mirroring
the $order-medication pattern from the prior commit. Bot binding moves to deploy
time via OperationDefinition + operationDefinition-implementation extension.

- @medplum/core: add MedicationOrderSetRequest/Response, helpers
  (medicationOrderSetRequestToParameters / parametersToMedicationOrderSetResponse),
  isMedicationOrderSetResponse type guard, INVALID_MEDICATION_ORDER_SET_RESPONSE
  constant, and round-trip + missing-launchUrl coverage.
- @medplum/react-hooks: rewrite useMedicationOrderSet — no botIdentifier arg,
  no vendorOrderSetIdField (operation locks the param name); POSTs Parameters
  to PlanDefinition/\$order-set-url and decodes the response. Public surface
  ({ url, loading, error, refresh }) unchanged. 11/11 tests.
- @medplum/scriptsure-react: collapse useScriptSureOrderSet to a 4-line
  forwarder that maps scriptSureOrdersetId → vendorOrderSetId; mark
  SCRIPTSURE_... (continued)

21429 of 24150 branches covered (88.73%)

Branch coverage included in aggregate %.

257 of 267 new or added lines in 8 files covered. (96.25%)

35208 of 37392 relevant lines covered (94.16%)

23574.19 hits per line