Skip to main content

OrderReconciliation

ComplexInpatient flow<co-order-reconciliation>

OrderReconciliation reviews every active order when a patient changes level of care, so orders that are not allowed on the new unit are stopped or changed before the transfer.

import { OrderReconciliation } from 'health-components';

Examples​

Showcase​

Storybook

All Reviewed​

Storybook

Usage​

<OrderReconciliation from="icu" to="medsurg" orders={activeOrders} />

When to use​

  • ICU to step-down or floor, floor to ICU, and to or from procedures.

When not to use​

  • Home medicine decisions: MedReconciliation.

Variants and states​

VariantWhat it is
groupedOrders grouped by type: medications, drips, nursing, labs.
not allowedRed line; Continue is removed.
stoppedStruck through.
incompleteRelease button counts what is left.
readOnlyLocked.

Clinical values​

Every number goes through the clinical value rules: tabular digits, unit always shown, fixed precision per measure (temperature 0.1 °C, potassium 0.1 mmol/L, creatinine 0.01 mg/dL, heart rate whole bpm), the reference range in the tooltip and H, L, H! or L! flags. Doses drop trailing zeros and keep a leading zero (0.5 mg, 5 mg).

Accessibility​

  • Arrow between levels is also read as "to".

Do and don't​

  • Do: Mark unit rules with notAllowedOn from the unit policy.
  • Don't: Silently drop drips at transfer.

Props​

PropTypeDefaultDescription
orders *TransferOrder[]—Array of { type, name, dose, unit, detail, action, notAllowedOn: level[] }: the starting orders (uncontrolled); required
ordersValueTransferOrder[]uncontrolledThe orders (controlled); pair with onOrdersChange
onOrdersChange(orders: TransferOrder[]) => voidnoneCalled with the new orders when an action changes
from *LevelOfCare—Level of care the patient leaves; required
to *LevelOfCare—Level of care the patient goes to; required
patientstringnonePatient name and context
readOnlybooleanfalseView only
onRelease(orders: TransferOrder[]) => voidnoneCalled by Release Orders with the orders (enabled once every order is reviewed)
rangeContextRangeContextId'inpatient' when no global context is setWhich shared reference range flags use; the lab range on a result still wins

Also accepts native attributes, including defaultChecked, defaultValue, autoFocus, plus className and event handlers on the root element.

Angular, Vue and HTML​

Register the elements once (Angular guide), then use <co-order-reconciliation>. Attributes take strings; arrays and objects are set as properties (Angular [prop], Vue :prop) or as JSON attributes. Callbacks are DOM events with the value in event.detail.

Angular template
<co-order-reconciliation from="…" to="…" [orders]="orders" (co-orders-change)="onOrdersChange($event.detail)"></co-order-reconciliation>
KindNameDescription
property / JSON attributeordersArray of { type, name, dose, unit, detail, action, notAllowedOn: level[] }: the starting orders (uncontrolled); required
property / JSON attributeorders-value / ordersValueThe orders (controlled); pair with onOrdersChange; default uncontrolled
attributefromLevel of care the patient leaves; required
attributetoLevel of care the patient goes to; required
attributepatientPatient name and context; default none
attributeread-only / readOnlyView only; default false
attributerange-context / rangeContextWhich shared reference range flags use; the lab range on a result still wins; default 'inpatient' when no global context is set
attributedefault-checked / defaultChecked
property / JSON attributedefault-value / defaultValue
attributeauto-focus / autoFocus
eventco-orders-changeCalled with the new orders when an action changes; default none (React: onOrdersChange)
eventco-releaseCalled by Release Orders with the orders (enabled once every order is reviewed); default none (React: onRelease)