PUBLIC HEALTH & REGISTRIES CONNECTORS

Overview

1 of 6

Connect authorized public-health authorities and registries with governed reporting, longitudinal registry updates and population-health workflows.

SurveillanceRegistriesImmunizationScreeningFHIRMSISGovernance

Stronger Public Health

Support timely reporting, surveillance and prevention.

Compliant by Design

Apply legal-basis, privacy and minimization controls.

Standardized & Interoperable

Use FHIR/IHE and standard terminologies through MSIS.

Better Population Health

Enable trusted population-level insight and action.

How It Works

Clinical Event

Diagnosis, lab result, vaccination, hospitalization or other event

Eligibility & Rules

Determine reportability/program/registry applicability

MSIS Validation

Normalize codes, units, terminology and data quality

Consent & Legal Basis

Mandatory reporting, consent or other authorized basis

Public Health Connector

Transform and send FHIR/API/SFTP/national format

Authority / Registry

Receive, validate and acknowledge

Key Public Health & Registry Domains

Notifiable Diseases

Infectious-disease and mandatory-event reporting.

Immunizations

Vaccination registries and coverage programs.

Clinical Registries

Cancer, rare disease and other condition registries.

Screening Programs

Organized prevention and follow-up programs.

Chronic Disease

Population-level chronic-disease reporting and programs.

Environmental Health

Exposure, air quality, climate and population signals.

Example Authorities & Registries

Authority / ecosystem	Examples	Status
Luxembourg health authorities	Surveillance, vaccination, registries	Planned / authority-specific
Santé publique France / national programs	Surveillance and organized programs	Planned / authority-specific
ECDC / EU networks	Cross-border surveillance	Planned / governed
Other national registries	Country-specific registry interfaces	On demand / adapter-based

Architecture

Data Sources

EHR, LIS, pharmacy, imaging, devices and public data

MSIS

Clinical semantic normalization and quality

Governance

Legal basis, minimization, purpose and access

Public Health Connectors

FHIR/API/IHE/SFTP/national adapters

Authorities & Registries

Reporting, acknowledgement and updates

Monitoring

Reconciliation, corrections and audit

Standards & Compliance

Standard / framework	Use	Status
HL7 FHIR	Reporting/registry resources and APIs	Profile-dependent
IHE profiles	Document/identity/public-health exchange where applicable	Profile-dependent
SNOMED CT / LOINC / ICD / UCUM	Terminology and units through MSIS	Semantic layer
National reporting formats	Authority-specific payloads	Adapter-specific
EHDS / EEHRxF	EU alignment for applicable future obligations	Future/staged

Business Value

Meet mandatory reporting obligations with less manual work

Improve timeliness and data quality

Support prevention and organized programs

Provide auditable authority acknowledgements/corrections

Enable authorized population insights while protecting identifiable data

Developer Integration Surface

How developers interact with this capability

Public-health connectors are authority-specific. Documentation should identify whether an adapter is implemented, planned, sandbox-only or awaiting official onboarding rather than imply universal support.

Surface	Operation / resource	Use	Status
FHIR / authority API	submit / update / query report or registry entry	Structured reporting	Authority/profile-specific
Batch / SFTP	scheduled national files	Legacy/large-volume reporting	Authority-specific
Webhooks/events	acknowledgement / rejection / correction	Async status	Provider-dependent
MSIS	normalize / validate terminology	Clinical semantics	Semantic service
Public Health API	eligibility / reporting orchestration	Mediloop app integration	Planned/versioned

Next Steps

Choose authority/registry and legal basis

Obtain official specification/onboarding

Map reportable data and terminology

Implement sandbox reporting/acknowledgement

Add monitoring, correction and audit