SpecsModelExploreRequirements
SpecsModelExploreRequirements
Clinical Data
Overview
Guide
Twin streams
Links and Communications
IDproduct.clinical_data
DescriptionPatient master, encounters and observations.
Keyclinical_data
Typesystem
Statusactive
TeamClinical Data
Owner
clinical-data@healthcare.example
TechnologiesGo, PostgreSQL, Kafka
Tags
Table of contents
Guide
Clinical Data
Internal structure
Containers
Admission flow
Links and Communications
Requirements

Attributes

consistencystrong
phitrue

Guide

Clinical Data

Clinical Data is the governed PHI core of the platform — enterprise patient identity, encounters and observations. Every write is auditable; apps and FHIR gateways read from here rather than maintaining parallel stores.

System of record

If a fact about a patient is not in Clinical Data, it is not authoritative for care or compliance.

Internal structure

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

Containers

Patient Master

EMPI — enterprise master patient index.

Encounter Service

Encounters, visits and admissions.

Observation Service

Vitals, labs and clinical observations.

  • EMPI / patient identity and duplicate resolution.
  • Encounter lifecycle (admit, transfer, discharge).
  • Observations including critical lab flagging.

Admission flow

Links and Communications

2 incoming links · 1 outgoing link

Incoming Links(2)

Source objectLabelLink typeRelationRaw idRequiredDescription
Clinical Ingestion

example-healthcare.product.ingestion

system
writes into—linksproduct.clinical_data——
Clinical Apps

example-healthcare.product.clinical_apps

system
reads via FHIR from—linksproduct.clinical_data——

Outgoing Links(1)

Target objectLabelLink typeRelationRaw idRequiredDescription
Governance & Audit

example-healthcare.product.governance

system
audited by—linksproduct.governance——

Requirements