HEALTHCARE SYSTEMS CONNECTORS
Documents & CDA / C-CDA
5 of 9Exchange clinical documents between Mediloop, HIS/EHR and external platforms using HL7 CDA/C-CDA, FHIR DocumentReference and other standard formats with secure metadata and lifecycle management.
HL7 CDAC-CDA / CCDFHIR DocumentReferenceFHIR CompositionPDF / TextMetadata & IndexingDigital SignaturesInteroperability
Document Exchange Architecture
1
Source System
HIS/EHR/department generates CDA, C-CDA or PDF
2
Mediloop Connector
Receives, validates, parses and extracts metadata
3
MSIS – Semantic Layer
Classifies and normalizes coded metadata
4
Document Store (FHIR)
Links document to patient, encounter and episode
5
Mediloop Applications
Clinical search, viewing and workflow access
6
External Recipients
National platforms and care-network exchange
Supported Formats
| Format | Usage |
|---|---|
| HL7 CDA | Structured clinical document exchange |
| C-CDA / CCD | Clinical summaries and transitions of care |
| PDF / Text | Human-readable documents and legacy outputs |
| FHIR Composition | Structured document composition |
| FHIR DocumentReference | Metadata/index and access to document content |
| Binary / attachment | Document payload when appropriate |
Metadata & Indexing
Patient and encounter identifiers
Document type / class and clinical specialty
Author, custodian and organization
Creation, service and signature timestamps
Confidentiality / security labels
Language, status and version
External source and repository identifiers
Terminology-coded metadata with provenance
FHIR Document Model
| Resource | Purpose | Key links |
|---|---|---|
| DocumentReference | Search/index metadata and attachment reference | Patient, Encounter, author, custodian, content |
| Composition | Structured clinical document assembly | Patient, encounter, author, sections |
| Bundle (document) | Portable FHIR document package | Composition + referenced resources |
| Binary | Raw content where applicable | Referenced from DocumentReference/content |
| Provenance | Who/what created or transformed the resource | Target resources + agents |
IHE Exchange
MHD for FHIR-based document sharing
XDS/XDS-b style registry/repository integration where required
Patient identity/profile dependencies via PIX/PDQ patterns
ATNA-style audit/security patterns
Cross-enterprise exchange through national/regional adapters
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.
| Surface | Operation / resource | Use | Status |
|---|---|---|---|
| FHIR | DocumentReference / Composition / Bundle / Binary / Provenance | Create, search and retrieve clinical documents | FHIR surface |
| CDA / C-CDA | Clinical document payloads | Legacy and standards-based enterprise document exchange | Document standard |
| IHE | MHD / XDS-style exchange | Regional/national and cross-enterprise document sharing | Profile operation |
| Events / SDK | document.created / indexed / shared / amended | Trigger workflows and modernized application UX | Planned contract |
Security & Digital Signatures
Encrypt document transport and storage
Respect confidentiality/security labels and tenant boundaries
Validate digital signatures where source workflows use them
Do not alter a signed source document silently
Keep immutable version/amendment history
Audit search, view, download and share actions
Best Practices
Store searchable metadata separately from opaque binary content
Preserve original source document and identifiers
Classify documents with controlled terminology
Support versioning/amendments instead of destructive overwrite
Avoid exposing documents before authorization/consent checks
Provide migration tooling for legacy document repositories