Mediloop
HEALTHCARE SYSTEMS CONNECTORS

Medications, Allergies & Diagnoses

6 of 9

Synchronize medication lists, prescriptions, allergies/intolerances and diagnoses across Mediloop, HIS/EHR and external systems using FHIR and HL7 v2 with terminology reconciliation and safety controls.

MedicationRequestMedicationStatementMedicationAllergyIntoleranceConditionFHIR R4 / R4BHL7 v2SNOMED CTICD-10ATC / RxNorm
Integration Flow
1
External EHR / HIS
Sends medication, allergy and diagnosis data
2
Mediloop Connector
Receives, validates and transforms data
3
MSIS – Semantic Layer
Normalizes, reconciles and deduplicates
4
Patient Record
Updates longitudinal meds, allergies and problems
5
Clinical Workflows
Prescribing, safety checks and care plans
Unified medication, allergy and diagnosis data improves patient safety and enables coordinated care across providers.
Medication Data
Active and historical medications
Prescriptions — MedicationRequest
Medication use/history — MedicationStatement
Medication catalog — Medication
Dosage, frequency, route and duration
Start/stop dates and status
Generic/brand coding (ATC/RxNorm or national codes)
Substitution and therapeutic-equivalence context
Duplicate-therapy and interaction workflows
Pharmacy-system integration
Allergy & Intolerance Data
Allergen / substance
Clinical status and verification status
Reaction manifestation and severity
Criticality and onset
Recorder / asserter and source provenance
SNOMED CT or local-code mapping through MSIS
Distinguish allergy from intolerance and other adverse reactions
Diagnoses & Problem List
Active and historical conditions
Encounter diagnoses vs longitudinal problem list
Clinical status / verification status
Onset, abatement and recorded dates
Body site and severity where relevant
ICD and SNOMED CT representations
Source system, author and provenance
Terminology & MSIS
DomainStandards / codesMSIS role
Medication conceptsATC, RxNorm, national medication codes, SNOMED CT where applicableMap and reconcile medication identity while preserving source
Allergies / findingsSNOMED CTNormalize clinical concepts and relationships
DiagnosesICD-10/ICD-11, SNOMED CTMap classification and clinical terminology according to use
Units / dosageUCUMValidate and normalize quantity units
Local codesVendor / nationalRetain original and record mapping provenance
Reconciliation & Safety
Medication reconciliation
Compare source lists across care settings
Detect additions, discontinuations and duplicates
Require controlled review for conflicting medication states
Preserve who changed what and why
Safety boundaries
Do not infer allergies from medications
Do not silently replace ambiguous medication codes
Separate source facts from decision-support suggestions
Keep clinician oversight for reconciled lists
Developer Integration Surface
How to read this section
FHIR resources and HL7/IHE operations are standards-based integration surfaces. Mediloop REST routes shown here are documentation contracts and must remain marked planned until the corresponding backend route is implemented and production-approved.
SurfaceOperation / resourceUseStatus
FHIRMedicationRequest / MedicationStatement / Medication / AllergyIntolerance / ConditionModern longitudinal medication/allergy/problem-list integrationFHIR surface
HL7 v2Medication/clinical segments as supported by source interfaceLegacy HIS/EHR synchronizationProtocol operation
Eventsmedication.changed / allergy.changed / condition.changedDrive clinical and pharmacy workflowsPlanned contract
REST / SDKReconciliation and longitudinal-record façadeModernization path for legacy medication/problem modulesPlanned contract
Best Practices
Separate prescribed, dispensed and patient-reported medication states
Keep original code/system/version for every mapped concept
Do not overwrite contradictory data without reconciliation
Version longitudinal lists and record amendments
Make safety alerts explainable and auditable
Test care-transition medication reconciliation explicitly