Hospital information system and EMR
The clinical record: what happened to a patient, documented by the people who treated them.
01 What it holds
The data inside it
Encounters, diagnoses, procedures, orders, results and notes — the description of care that the billing record is derived from but never identical to.
Patient, Encounter, Diagnosis (ICD), Procedure (CPT / OPCS), Order, Result, Medication, Clinical note
02 Getting the data out
Extraction, and the keys that decide whether it joins
HL7 v2 messaging, FHIR APIs, or a vendor clinical data warehouse. Governance and patient privacy constraints shape the design more than the technology does.
Patient identity spans the master patient index, local site numbers and national identifiers. Duplicate patient records are common and clinically significant.
03 What goes wrong
The failures that look like success
Each of these produces a number that is plausible, reconciles to something, and is wrong. They are worth reading before the first extract, not after the first dispute.
Clinical record versus billing record
They describe the same episode differently by design. The gap between documented care and coded care is measurable revenue.
Free-text clinical notes
Much of the diagnostic detail is prose, so structured analysis systematically misses what the clinician actually observed.
Encounter versus episode
A patient journey spans encounters across departments and sites; costing and outcomes are only meaningful at episode level.
Access control is not optional
Role-based access, purpose limitation and audit are design requirements from the first extract, not a later hardening step.
04 Joins that matter
What this system is worth joining to
| Join to | What it lets you answer |
|---|---|
| Revenue cycle and billing | documented care against coded and claimed care |
| ERP and item master | implants, supplies and pharmacy consumed in the episode |
| Scheduling and theatre | capacity consumed, and length of stay |
05 Metrics it feeds
The numbers that come out of it
06 Questions
Frequently asked
Can clinical data be used for financial analysis?
Yes, and it must be for cost per episode to exist — but under strict access control and usually de-identified for anything beyond direct care. The governance model is part of the design, not a constraint on it.
What is the highest-value join in a hospital?
Every consumption event to the encounter, and encounters to the episode. It is the only route to a true cost per episode across theatre, ward, diagnostics and pharmacy.
Connect this system without replacing it
SCIKIQ reads it in place, resolves the entities inside it and governs what the fields mean.