CLINICAL DEVICE CONNECTORS

Data Capture & Streaming

6 of 10

Connect clinical devices and professional peripherals through standards-based local, network and vendor-specific interfaces.

ParsingValidationNormalizationFHIR mappingProvenanceMSIS

From raw payload to usable clinical data

Receive raw data

Packet, event, file or API response

Validate

Schema, checksum, timestamp and source

Normalize units

UCUM and precision handling

Map semantics

Code, interpretation and context

Create FHIR

Observation / Device / report

Route downstream

Store, trigger, notify or reconcile

Audit

Preserve raw source and lineage

Normalization examples

Raw device value	Normalized value	Mapping note
Temp = 98.6 F	37.0 °C (UCUM Cel)	Unit converted and normalized
PulseOx = 97 pct	97 %	Canonical representation retained
BP = 120/80 mmHg	Systolic + diastolic Observations	Composite payload split into standard observations
Vendor code HR01	LOINC-backed heart-rate code	Terminology mapping with provenance retained
Transcript payload	Clinical note draft / transcript event	Not a classical measurement but still structured output

Data quality controls

Range and plausibility checks

Duplicate suppression / idempotency

Timestamp and time-zone normalization

Patient-context binding verification

Device identity consistency checks

Raw-source retention for traceability

Clinical caution

Normalization must never silently distort clinical meaning. Retain raw values and transformation provenance whenever possible.

Canonical outputs

ObservationVitals, measurements, scores and waveform-derived metrics

DiagnosticReportGrouped device result sets or interpretation summaries

Device / DeviceMetricSource device identity and characteristics

Task / workflow eventOperational follow-up actions

Transcript / note draftSpeech-recognition and dictation use cases

Mapping example

jsonCopy

{
  "raw": { "code": "TEMP", "value": 98.6, "unit": "F" },
  "normalized": { "value": 37, "unit": "Cel", "ucum": "Cel" },
  "fhir": {
    "resourceType": "Observation",
    "status": "final",
    "code": { "coding": [{ "system": "http://loinc.org", "code": "8310-5" }] },
    "valueQuantity": { "value": 37, "unit": "°C", "system": "http://unitsofmeasure.org", "code": "Cel" }
  }
}