SpecsModelExploreRequirements
SpecsModelExploreRequirements
Encounter Repository
Overview
Guide
Schema
Twin streams
Links and Communications
IDproduct.clinical_data.encounter_service.encounter_repo
DescriptionStores encounter aggregates.
Keyencounter_repo
Typecomponent:database
Statusactive
TeamClinical Data
Tags
Table of contents
Guide
Encounter Repository
Data model
Notes
Schema
Links and Communications
Requirements

Attributes

retention7y
storePostgreSQL

Guide

Encounter Repository

The Encounter Repository stores encounter aggregates — patient link, location, class, timing and current status — as the durable source for FHIR Encounter.

Data model

The schema is small and audit-oriented. The ERD is embedded on the Overview tab.

Notes

One row per visit/admission episode; updates are ADT-driven from ingestion.
  • status mirrors the state machine — never updated without a valid transition.
  • Discharged encounters remain readable for longitudinal chart views.

    • Schema

    Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
    Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
    100%

    Links and Communications

    2 incoming links

    Incoming Links(2)

    Source objectLabelLink typeRelationRaw idRequiredDescription
    Encounter State Machine

    example-healthcare.product.clinical_data.encounter_service.state_machine

    component
    		——linksproduct.clinical_data.encounter_service.encounter_repo——
    Event Publisher

    example-healthcare.product.clinical_data.encounter_service.event_publisher

    component
    		——linksproduct.clinical_data.encounter_service.encounter_repo——

    Requirements