Skip to content

Health Patient Chart And Visits

The patient chart is the clinical home page for a patient. It should behave like an OpenMRS-style chart: patient header, identifiers, flags, active visits, recent clinical widgets, and quick actions that open chart-scoped forms.

Patient Identity

Patients are parties first. Health adds a patient clinical profile, MRN, identifiers, privacy level, protection flags, and chart state.

DataOwner
Name, phone, demographicsParties
Patient MRN and identifiersHealth patient profile and identifier types
Privacy level and protection flagsHealth governance
User loginAdministration access, only where the patient is also a system user

Patient Header

The chart header should show:

  • patient name
  • primary MRN
  • party number
  • patient status
  • sex and date of birth where available
  • phone/contact summary
  • identifiers such as national ID, clinic number, insurance number, or program ID
  • protection flags and privacy warnings
  • active visit count

Chart Widgets

Widgets are patient-scoped summaries. View-more links open the owning workspace filtered to the patient.

WidgetTypical contentView-more destination
Clinical snapshotCounts and trends for active visits, orders, forms, notes, lab, pharmacy, charges, and flags.Patient registry/chart or dashboard.
Active visitsOpen encounters and care context.Visits and OPD flow.
Visit historyClosed or historical encounters.Visits and OPD flow.
Open ordersReleased or pending clinical orders.Clinical Orders.
Clinical formsRecent submitted forms and amendment state.Clinical Forms.
Clinical notesDraft, signed, and amended notes.Clinical Notes.
Lab resultsRecent results, validation state, critical markers.Laboratory.
ImagingStudies, reports, status, modality.Imaging.
PharmacyMedication orders, dispenses, administrations, returns, controlled-drug traceability.Dispensing and Administration.
Visit chargesREADY, POSTED, credited, and paid charge traces.Visit Charges.
Claims and coverageCoverage, claim state, remittance, denial/appeal readiness.Claims and Remittance.
Privacy and auditBreak-glass, consent, access, disclosure, and sensitive access review.Consent and Privacy.

Chart Actions

Quick actions should stay on the chart and open forms with patient and encounter context already prefilled.

ActionExpected behavior
New visitOpens encounter or OPD visit form for the current patient and branch.
OrderOpens clinical order form with patient, visit, provider, and location context.
FormOpens published clinical form chooser, then the selected form submission.
NoteOpens clinical note form with patient and encounter context.
ObservationOpens observation entry with patient and encounter context.
ChargeOpens visit-charge trace or billing handoff where the user has permission.

Do not route away from the chart just to create a chart-scoped action unless the action is intentionally a full workspace process.

Visits And Business Units

Visits are controlled by facility and department business-unit context.

ContextMeaning
Facility business unitClinic, health centre, or branch where care is delivered.
Department business unitOPD, lab, pharmacy, ward, theatre, or specialty unit where applicable.
Operational locationRoom, ward, bed, counter, lab station, theatre, or service point.
Business dayThe posting day and teller/day-control context for billable activity.
Fiscal periodThe GL posting window used when Billing, Payments, Stock, or POS post financial effects.

Before a Health branch goes live, the branch must have fiscal periods, open business day readiness, approved currency usage, and teller/payment setup where cashier collection is expected.

Encounter Flow

  1. Register patient or select an existing patient.
  2. Start appointment, OPD queue, or admission.
  3. Open encounter with facility, provider, and location.
  4. Capture triage and observations.
  5. Add notes, forms, diagnoses, allergies, and orders.
  6. Generate visit charges where configured.
  7. Close the encounter only when clinical and billing readiness checks pass.

Detail Dialogs

Encounter, order, lab, pharmacy, imaging, claim, and charge detail dialogs should show the patient name and MRN, not only record IDs. Internal IDs should remain hidden unless they are required for debugging.

Pinkapple ERP by Stat Solutions Network