@ampath/esm-dha-workflow-app 4.0.0-next.34 → 4.0.0-next.340

package/src/case-summary/components/case-summary-printable.utils.ts

@@ -0,0 +1,51 @@
+import { formatDate, parseDate } from '@openmrs/esm-framework';
+import { type CaseSummaryLabInterpretation } from '../types/case-summary.types';
+
+export const EMPTY_VALUE = '—';
+
+export function formatDateSafe(value?: string): string {
+  return value ? formatDate(parseDate(value), { time: false }) : EMPTY_VALUE;
+}
+
+/**
+ * Human label for a lab interpretation. `interpretation` is only ever present
+ * on the wire when the result is abnormal — `NORMAL` and unassessable results
+ * omit the field entirely (see `CaseSummaryLabInterpretation`) — so every
+ * value this can be called with is a real flag to render.
+ */
+export function interpretationLabel(interpretation: CaseSummaryLabInterpretation): string {
+  switch (interpretation) {
+    case 'LOW':
+      return 'Low';
+    case 'HIGH':
+      return 'High';
+    case 'CRITICALLY_LOW':
+      return 'Critically low';
+    case 'CRITICALLY_HIGH':
+      return 'Critically high';
+    case 'OFF_SCALE_LOW':
+      return 'Off-scale low';
+    case 'OFF_SCALE_HIGH':
+      return 'Off-scale high';
+  }
+}
+
+/** Carbon tag tone for a lab interpretation — red for critical/off-scale, magenta for a plain high/low. */
+export function interpretationTagType(interpretation: CaseSummaryLabInterpretation): 'red' | 'magenta' {
+  return interpretation === 'LOW' || interpretation === 'HIGH' ? 'magenta' : 'red';
+}
+
+/**
+ * Splits a SOAP note section's prose into its component sentences for
+ * display as a scannable list rather than one dense paragraph. The
+ * server-generated text is sentence-terminated prose (`"Chief Complaint:
+ * HEADACHE. Onset: MODERATE."`), so splitting after `". "` recovers the
+ * original field-level lines without needing the raw fields.
+ */
+export function splitSoapSentences(text?: string): Array<string> {
+  if (!text) return [];
+  return text
+    .split(/(?<=[.!?])\s+/)
+    .map((sentence) => sentence.trim())
+    .filter(Boolean);
+}

package/src/case-summary/types/case-summary.types.ts

@@ -0,0 +1,152 @@
+/**
+ * Types for the patient Case Summary.
+ *
+ * Mirrors the `hie-saf` package's `GET /case-summary` response verbatim
+ * (`packages/hie-saf/src/case-summary/types/index.ts`) — this endpoint now
+ * does the AMRS join server-side, so there is nothing left to assemble here.
+ * See `packages/hie-saf/docs/case-summary-endpoint.md` for the full contract.
+ */
+
+export type CaseSummaryVisit = {
+  uuid: string;
+  display?: string;
+  visitType?: string;
+  startDatetime?: string;
+  stopDatetime?: string;
+};
+
+export type CaseSummaryDemographics = {
+  name: string;
+  birthDate?: string;
+  gender?: string;
+  age?: string;
+  patientId?: string;
+  nationalId?: string;
+  crNumber?: string;
+};
+
+export type CaseSummaryAllergy = {
+  substance: string;
+  criticality?: string;
+  reaction?: string;
+};
+
+export type CaseSummaryCondition = {
+  code?: string;
+  description: string;
+  certainty?: string;
+  /** Present only for a rank-1 diagnosis. */
+  primary?: true;
+  onsetDate?: string;
+};
+
+/** Keyed, not an array of `{label, value}` pairs — display labels belong here in the view, via `VITAL_ROWS`. */
+export type CaseSummaryVitals = {
+  temperature?: string;
+  bloodPressure?: string;
+  pulse?: string;
+  respiratoryRate?: string;
+  spo2?: string;
+  height?: string;
+  weight?: string;
+  bmi?: string;
+  tewScore?: string;
+};
+
+export type CaseSummaryMedication = {
+  date?: string;
+  drug: string;
+  dose?: string;
+  route?: string;
+  frequency?: string;
+  duration?: string;
+  instructions?: string;
+};
+
+/**
+ * One encounter's non-vital obs. Kept in the type for parity with the wire
+ * contract, but deliberately not rendered by `CaseSummaryPrintable` — see the
+ * note there. The SOAP note is the intended replacement for this section.
+ */
+export type CaseSummaryClinicalNote = {
+  encounterUuid: string;
+  encounterType?: string;
+  datetime?: string;
+  fields: Array<{ label: string; value: string }>;
+};
+
+/** Present only when there is something to say — `'--'`/`NORMAL` are never sent. */
+export type CaseSummaryLabInterpretation =
+  | 'LOW'
+  | 'HIGH'
+  | 'CRITICALLY_LOW'
+  | 'CRITICALLY_HIGH'
+  | 'OFF_SCALE_LOW'
+  | 'OFF_SCALE_HIGH';
+
+export type CaseSummaryLabResult = {
+  test: string;
+  /** Immediate parent panel name when nested; absent at root. */
+  panel?: string;
+  value: string;
+  units?: string;
+  datetime?: string;
+  range?: string;
+  interpretation?: CaseSummaryLabInterpretation;
+};
+
+export type CaseSummaryLabOrder = {
+  uuid: string;
+  test: string;
+  orderNumber?: string;
+  orderedDate?: string;
+  /** Present only when no in-window result was found. */
+  pending?: true;
+  /** OpenMRS `order_action` — e.g. `NEW`, `RENEW`, `DISCONTINUE`. */
+  action?: string;
+  /** OpenMRS's own fulfiller workflow status — e.g. `RECEIVED`, `COMPLETED`, `EXCEPTION`. */
+  fulfillerStatus?: string;
+  results: Array<CaseSummaryLabResult>;
+};
+
+export type CaseSummaryInpatientDetails = {
+  admissionDate?: string;
+  ward?: string;
+  doctor?: string;
+  status?: string;
+  dischargeDate?: string;
+};
+
+/**
+ * A SOAP note assembled server-side from everything else in this response —
+ * narrative text, not a new source of clinical data. Deterministic and
+ * template-based, not model-generated. Each section is absent when nothing
+ * categorised into it.
+ */
+export type CaseSummarySoapNote = {
+  subjective?: string;
+  objective?: string;
+  assessment?: string;
+  plan?: string;
+};
+
+export type CaseSummaryResponse = {
+  /** Anchor visit; the merged span when several same-day visits were folded in. */
+  visit: CaseSummaryVisit;
+  /** All folded-in visit uuids, anchor first. Length > 1 ⇒ the view says "N visits combined". */
+  visitUuids: Array<string>;
+  demographics: CaseSummaryDemographics;
+  allergies: Array<CaseSummaryAllergy>;
+  /** Active diagnoses. */
+  conditions: Array<CaseSummaryCondition>;
+  vitals: CaseSummaryVitals;
+  /** Active drug orders only — inactive ones are filtered server-side. */
+  medications: Array<CaseSummaryMedication>;
+  clinicalNotes: Array<CaseSummaryClinicalNote>;
+  labOrders: Array<CaseSummaryLabOrder>;
+  /** Present only when orders existed but the lab results query failed. */
+  labResultsUnavailable?: true;
+  /** Present only for a visit with an ADT encounter — absent entirely for outpatient. */
+  inpatientDetails?: CaseSummaryInpatientDetails;
+  soapNote: CaseSummarySoapNote;
+};

package/src/claims/claims.component.scss

@@ -0,0 +1,70 @@
+// Stack the claim fields with clear spacing between them.
+.claimFields {
+  display: flex;
+  flex-direction: column;
+  gap: 1rem;
+}
+
+.preExistingInterventionsHeader {
+  display: flex;
+  flex-direction: column;
+  gap: 0.25rem;
+}
+
+.tableWrapper {
+  overflow-x: auto;
+}
+
+.field {
+  position: relative;
+}
+
+// Interventions field with its eligibility / preauth tags: field on its own row,
+// tags wrapping neatly below with breathing room.
+.interventionRow {
+  display: flex;
+  flex-wrap: wrap;
+  align-items: center;
+  gap: 0.5rem 0.75rem;
+
+  .field {
+    flex: 1 1 100%;
+  }
+}
+
+// Keep the eligibility spinner inline (Carbon defaults it to full width) so it
+// sits on the same row as the Needs Preauth tag.
+.checkingEligibility {
+  width: auto;
+  min-width: 0;
+}
+
+// A small spinner sitting inside the ComboBox's input row, just left of its chevron.
+//
+// The field is the containing block and the input is the last thing in it, so anchoring
+// to the bottom puts the spinner on the input row whatever the label above does — it
+// stays put if the label wraps to two lines, which it does in a narrow panel. 0.75rem up
+// from that edge centres a 1rem spinner on the 2.5rem row.
+//
+// z-index because the list-box paints its own background and border over anything sharing
+// its space; without it the spinner sits behind the field it is meant to be inside.
+.fieldSpinner {
+  position: absolute;
+  inset-inline-end: 2.5rem;
+  inset-block-end: 0.75rem;
+  z-index: 1;
+  width: 1rem;
+  height: 1rem;
+}
+
+// The spinner floats over the input, so the placeholder underneath has to stop short of
+// it — 2.5rem to clear the chevron, 1rem for the spinner, and a little air. Without this
+// the loading text ran under the spinner and the field read as garbled. Only applied
+// while the spinner is actually there.
+.field:has(.fieldSpinner) {
+  :global(.cds--text-input),
+  :global(.cds--list-box__field input) {
+    padding-inline-end: 4.25rem;
+    text-overflow: ellipsis;
+  }
+}