SpecsModelExploreRequirements
SpecsModelExploreRequirements
Observation Service
Overview
Guide
Observation Service API
Twin streams
Links and Communications
IDproduct.clinical_data.observation_service
DescriptionVitals, labs and clinical observations.
Keyobservation_service
Typemicroservice:service
Statusactive
TeamClinical Data
Owner
clinical-data@healthcare.example
TechnologiesGo, PostgreSQL, Kafka
Tags
Table of contents
Guide
Observation Service
Internal structure
Components
Write path
Store
Flag
API
Lab result delivery
Observation Service API
Links and Communications
Requirements

Attributes

alertingin-process
typesvitals, labs

Guide

Observation Service

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.

Internal structure

Could not build diagram for model "example-healthcare".

Components

Observation Repository

Time-series store for observations.

Unit Normalizer

Normalizes UCUM units across sources.

Critical Flag Engine

Flags critical results for clinicians.

Write path

Normalise

The Unit Normalizer converts units to UCUM before persist.

Store

The Observation Repository appends the time-series value.

Flag

The Critical Flag Engine evaluates panic thresholds and emits alerts.

API

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.

Lab result delivery

Observation Service API

Links and Communications

1 workflow

Related Workflows(1)

WorkflowModelParticipant idParticipant label
Lab result delivery

clinical-flows.lab-result

example-healthcareproduct.clinical_data.observation_serviceObservation service

Requirements