Appearance
Health Setup
Health setup prepares the clinical foundation before users start patient care. It should be done after the tenant has parties, business units, operational locations, items, billing items, payment channels, and user roles configured.
Setup Sequence
- Activate the Health service for the company and assign the Healthcare permission profile.
- Create the clinic, branch, ward, lab, pharmacy, theatre, or service-centre business units.
- Maintain operational locations for OPD rooms, wards, beds, lab stations, pharmacy counters, theatres, stores, and cashier points.
- Apply a starter profile where available, such as the Uganda clinic starter.
- Review clinical terminology, forms, order sets, payer defaults, and visit-charge defaults.
- Bind order-set lines to tenant lab profiles, medication profiles, imaging profiles, procedure profiles, stock items, billing items, and pricing.
- Configure Health roles through Administration -> Access -> Roles.
- Create users only after selecting or creating their individual party record.
Service And Permission Profile
Health should appear as Health Services under the service selector. If it appears under another service name, the company-service record or seed binding is wrong and should be corrected before users start live work.
The Healthcare permission profile controls the Health menu. Provider clinical credentials are Health records, but they do not replace system roles. A clinician who signs notes, releases orders, or validates results still needs the relevant Pinkapple role permissions.
Recommended seeded Health roles include Health Administrator, Clinician, Nurse, Lab Technician, Lab Manager, Pharmacist, Pharmacy Assistant, Radiology User, Theatre User, Inpatient Ward User, Claims Officer, Privacy Officer, HMIS Reporting Officer, Interoperability Administrator, and Health Cashier. Assign these through the standard access module; do not manage login authority inside the provider profile.
Fiscal And Business-Day Bootstrap
Every Health business unit that posts invoices, receives cashier payments, issues stock, or runs day-control workflows must have its own fiscal and business-day readiness. Do not rely on the default company branch as proof that Health is ready.
Required setup:
- Health calendar policy.
- Current fiscal calendar and fiscal year.
- Monthly fiscal periods plus adjustment period.
- BU period state for every approved Health branch.
- Current period opened for every posting Health branch.
- Current business day opened for every Health branch that uses teller/day control.
- Approved currency usage for the branch, such as UGX.
- Till, cashier, payment-channel, and settlement setup where collections occur.
Use the standard financial setup screens to prepare fiscal policy, fiscal years, periods, and branch period state for Health branches. Daily business-day opening is still an operational action and should follow the same controls used by other services.
Parties First
Patients and providers are parties first.
| Person or organization | Party setup |
|---|---|
| Patient | Individual party with the Health patient role/profile and patient identifiers. |
| Clinician | Individual party with provider credentials and optionally a linked system user. |
| External provider group | Group or organization party with provider metadata where needed. |
| Payer | Organization party linked to payer profile and coverage rules. |
| Employer or corporate sponsor | Organization party linked to coverage, billing, or credit terms. |
Do not duplicate names, phone numbers, or demographic identity inside Health when the party module already owns the master data.
Clinical Terminology
Use Clinical Terminology to maintain:
- concepts and concept names
- concept classes and datatypes
- value sets and coded answer lists
- concept mappings to LOINC, SNOMED, ICD, RxNorm, UCUM, or national codes
- reference ranges and unit mappings
Clinical forms, observations, lab results, HMIS facts, interoperability mappings, and reports should use coded concepts where possible.
Clinical Service Catalog
The Health service catalog stores clinical meaning. The commercial and operational owners remain outside Health.
| Health profile | Required bindings |
|---|---|
| Lab test profile | Concept, orderable item/service, billing item where charged, specimen behavior, result concept or panel. |
| Medication profile | Operational item, stock item where stocked, dose form, strength, controlled-drug rules, billing/price item where sold. |
| Imaging/procedure profile | Concept, modality/procedure metadata, billing item, stock consumables where applicable. |
| Theatre procedure profile | Procedure concept, consent/checklist needs, resource and billing context. |
Starter Profiles
Starter profiles are applied from Healthcare -> Setup -> Operating Model. They can load or expose:
- concepts and names
- OpenMRS-style clinical forms
- OPD, ANC, and clinic starter order sets
- payer and coverage templates
- visit-charge default templates
- recommended capabilities
Applying a starter profile does not complete tenant-specific setup. Users still need to bind local billing items, stock items, pricing, rooms, providers, and cashier points.
Branch Readiness
Each branch, clinic, ward, lab, pharmacy, theatre, or cashier point should be reviewed before users start charging, collecting, issuing stock, or submitting claims.
Confirm:
- the branch belongs to the correct Health service context
- operational locations match the real facility layout
- fiscal periods and business-day controls are ready where posting is required
- approved currencies are available
- cashier/till/payment channels are configured
- user roles are assigned to the right facility
- Billing items, pricing, stock items, and service profiles are bound
- reports show the branch under the correct business unit
Record Numbers
Do not add patient numbers, note numbers, accession numbers, claim numbers, dispense numbers, admission numbers, discharge numbers, or theatre case numbers to create/edit forms. Health generates these user-facing record numbers from the configured numbering templates.