| ID | product.clinical_data.observation_service |
|---|---|
| Description | Vitals, labs and clinical observations. |
| Key | observation_service |
| Type | microservice:service |
| Team | Clinical Data |
| Owner | clinical-data@healthcare.example |
| Status | active |
| Technologies | Go, PostgreSQL, Kafka |
| Attributes | alerting: in-process, types: vitals, labs |
| Tags |
The Observation Service stores vitals, labs and clinical observations with normalised units and real-time critical-value flagging — the path panic labs take before the clinician alert panel.
Patient safety path
Panic values must flag in-process. Batch scoring is too slow for ORU results that need immediate clinician attention.
Could not build diagram for model "example-healthcare".
The Unit Normalizer converts units to UCUM before persist.
The Observation Repository appends the time-series value.
The Critical Flag Engine evaluates panic thresholds and emits alerts.
Read APIs support chart viewer and FHIR Observation search; writes are internal from ingestion. Contract on Overview tab.
Contract
Reference ranges are stored per analyte and care setting; flag engine reads the same table.
1 workflow
| Workflow | Model | Participant id | Participant label |
|---|---|---|---|
| Lab result delivery clinical-flows.lab-result | example-healthcare | product.clinical_data.observation_service | Observation service |