Appearance
Health Privacy, Reporting, And Interoperability
Health governance covers privacy controls, auditability, HMIS reporting, integrations, and offline clinical sync.
Privacy And Sensitive Access
Health privacy controls should include:
- patient privacy level
- protection flags
- consent records
- disclosure logs
- break-glass access
- break-glass review
- legal holds
- chart access audit
- note view, print, and download audit
- amendment and void history
This is HIPAA-aligned infrastructure, not a legal compliance claim. Compliance still depends on organizational policies, staff training, breach process, device control, access reviews, contracts, and local legal requirements.
Break Glass
Break-glass should be used only when ordinary access is insufficient for urgent care.
- User starts a break-glass episode with reason and patient context.
- System records access and opens temporary access according to policy.
- Reviewers approve, reject, or follow up.
- Privacy reports show the event, user, patient, reason, and outcome.
HMIS Reporting
HMIS reporting uses indicator definitions, source rules, generated facts, facility periodic reports, validations, locks, and exports.
Report examples include:
- OPD visit summary
- visit revenue summary
- cashier collections
- claims aging
- medicine consumption
- privacy access audit
- lab turnaround and critical results
- service-line revenue
- outstanding patient balances
- inpatient bed occupancy
- provider activity
- break-glass review
Report Runner
Health reports are executed from the shared Reporting module. The Health workspace should deep-link to the RPG-HEALTH report group instead of duplicating report runner screens.
Report filters should use lookups and enums:
- patient lookup
- provider lookup
- business unit lookup
- operational location lookup
- payer lookup
- claim status select
- encounter status select
- service line select
- date range
Interoperability
Health interoperability records should cover:
- FHIR endpoint profiles
- HL7 endpoint profiles
- DICOM endpoint profiles
- analyser and modality endpoints
- payer and clearinghouse endpoints
- resource profiles
- mappings
- subscriptions
- messages
- retries
- dead letters
- export bundles
Terminology mappings are required before reliable FHIR, HL7, DICOM, national HMIS, or payer exchange.
Offline Clinical Sync
Offline support should manage:
- offline devices
- offline user profiles
- encrypted offline packages
- sync batches
- idempotency keys
- conflict detection
- server-authority resolution
- revoked or expired packages
Clinical offline writes must preserve patient, encounter, provider, concept, form version, and audit provenance.