PUBLIC HEALTH & REGISTRIES CONNECTORS
Clinical & Population Registries
3 of 6Connect authorized public-health authorities and registries with governed reporting, longitudinal registry updates and population-health workflows.
Clinical RegistriesPopulation RegistriesFHIRLongitudinalCohortsQualityGovernance
Structured Registry Data
Capture registry-specific structured information.
Longitudinal Follow-Up
Support updates and outcomes over time.
Interoperable Submissions
Use standard resources/terminologies plus registry profiles.
Governed Access
Respect registry legal basis, purpose and access controls.
Registry Workflow
1
Eligibility
Determine registry inclusion criteria
2
Normalize
Map diagnoses, observations and procedures
3
Create Entry
Build registry dataset/profile
4
Submit
Registry API/file connector
5
Follow-Up
Longitudinal outcomes and corrections
6
Quality & Audit
Completeness, acknowledgement and lineage
Registry Types
Disease Registries
Cancer, rare disease and chronic-condition registries.
Population Registries
Population cohorts, outcomes and surveillance datasets.
Procedure / Device Registries
Procedure, implant or medical-device outcomes.
Immunization Registries
Vaccination history and population coverage.
Data Model
| Data area | Examples | FHIR / terminology |
|---|---|---|
| Patient / demographics | Age, sex, residence/region | Patient + governed demographics |
| Diagnosis | Cancer stage, chronic disease | Condition, SNOMED CT / ICD |
| Observations | Labs, biomarkers, outcomes | Observation, LOINC / SNOMED |
| Treatment / procedures | Medication, procedure, device | Medication*, Procedure, Device |
| Follow-up | Status, recurrence, outcome | Observation / Encounter / custom profile |
Registry Submission & Updates
Use stable registry entry and source references
Support initial submission, periodic follow-up and corrections
Do not silently replace prior registry values
Store registry acknowledgement/version
Handle patient relocation/death/withdrawal according to program rules
APIs & Examples
httpCopy
# Illustrative registry submission
POST /v1/public-health/registries/cancer/entries
Authorization: Bearer <token>
{ "patientId":"patient_123", "condition":"Condition/456", "jurisdiction":"FR" }Illustrative. Each registry can require its own dataset, identifiers, profile and legal basis.
Data Quality & Reconciliation
Completeness checks by registry schema
Terminology conformance via MSIS
Duplicate registry-entry detection
Source-vs-registry version comparison
Correction/rejection queues
Provenance and submission history
Security & Governance
Registry-specific legal basis and purpose
Minimum necessary identifiable data
Role/organization authorization
Retention and patient-right handling according to law/program
Audit all extraction/submission/access
Controlled secondary-use handoff where applicable
Developer Integration Surface
| Surface | Operation / resource | Use | Status |
|---|---|---|---|
| Registry API | create / update / status | Registry orchestration | Planned/versioned |
| FHIR | registry-specific profiles/resources | Structured submission | Profile-specific |
| Batch | CSV/XML/SFTP/national format | Legacy/bulk registry feeds | Registry-specific |
| MSIS | terminology mapping / validation | Semantic quality | Semantic service |
Next Steps
Select registry and official dataset
Map eligibility and fields
Implement initial + follow-up submissions
Validate duplicates/corrections
Add quality and audit monitoring