PUBLIC HEALTH & REGISTRIES CONNECTORS

Surveillance & Mandatory Reporting

2 of 6

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

Notifiable EventsRulesJurisdictionFHIRAcknowledgementsCorrectionsAudit

Automated Detection

Identify reportable events from clinical data.

Jurisdictional Rules

Apply country/regional rules and timeframes.

Compliant Reporting

Send only required data to the right authority.

Full Audit Trail

Track submissions, acknowledgements and corrections.

Mandatory Reporting Workflow

Event Detection

Diagnosis, lab result or hospitalization

Rule Evaluation

Jurisdiction and reportability criteria

MSIS Validation

Required fields, codes and quality

Legal Basis Check

Mandatory reporting / minimization

Submit Report

FHIR/API/SFTP/national format

Acknowledgement

Receive result and handle follow-up

Reporting Statuses

Status	Meaning	Next action
detected	Potential reportable event identified	Evaluate rules
evaluated	Rules applied	Prepare report or close
pending	Awaiting submission/prerequisite	Resolve prerequisite
submitted	Sent to authority	Await acknowledgement
acknowledged	Accepted/confirmed	Monitor/update if needed
rejected	Authority rejected	Review/correct/resubmit
updated	Correction/follow-up sent	Await acknowledgement
closed	Cycle complete	Retain audit evidence

Common Reportable Events

Domain	Examples	Typical triggers
Infectious disease	Influenza, measles, TB, hepatitis, emerging infections	Diagnosis, positive lab, hospitalization
Antimicrobial resistance	Resistant organism / susceptibility pattern	Microbiology result
Adverse / sentinel events	Authority-defined events	Clinical event / incident
Other mandatory reports	Country-specific programs	Rule-defined trigger

Data Requirements

Patient/subject identifiers only to the extent required

Event/condition/lab coding and onset/specimen/result timing

Facility/professional reporting context where mandated

Jurisdiction and report type

Source/provenance and correction references

Legal-basis/reportability decision evidence

APIs & Examples

httpCopy

# Illustrative public-health submission
POST /v1/public-health/reports
Authorization: Bearer <token>

{
  "jurisdiction":"LU",
  "reportType":"notifiable-disease",
  "eventReference":"Observation/lab-123"
}

Illustrative Mediloop orchestration route. Official authority schemas/endpoints and mandatory fields are country/program specific.

Error Handling

Failure	Handling
Rule ambiguity	Do not silently suppress/submit; route to review
Validation failure	Block submission with field/code detail
Authority unavailable	Queue/retry within legal timeframe and alert
Rejected report	Store acknowledgement/reason and correction workflow
Duplicate event	Use jurisdiction-specific deduplication/idempotency

Best Practices

Version reportability rules by jurisdiction/effective date

Preserve original clinical codes and normalized mappings

Minimize data to statutory/program requirements

Test mandatory time limits and outage procedures

Treat authority acknowledgement as authoritative submission outcome

Audit corrections and resubmissions

Developer Integration Surface

Surface	Operation / resource	Use	Status
Reporting API	submit / amend / status	Mediloop reporting workflow	Planned/versioned
FHIR	Condition / Observation / DiagnosticReport / Bundle/profile	Structured authority payload	Profile-specific
National adapter	official endpoint / file format	Authority connectivity	Country-specific
Events	report.acknowledged / rejected	Async status	Adapter-dependent

Next Steps

Load jurisdiction rules

Map report data

Validate with official sandbox/test fixtures

Test rejection/correction/outage flows

Go live with alerts and legal-timeframe monitoring