Connector Types
2 of 7Explore the operational system categories you can integrate with Mediloop, including common use cases, protocols, domain boundaries and the developer-facing integration surfaces for each pattern.
Accounting, budgeting, cost management and financial reporting.
Purchase orders, suppliers, contracts, catalogs and approvals.
Stock levels, movements, reservations, reordering and multi-site inventory.
Medication stock, suppliers, delivery and temperature-sensitive logistics.
Staff records, credentials, shifts, payroll references and workforce planning.
Rooms, equipment, maintenance, utilization and building systems.
Billing, claims, remittance and reconciliation with payer/finance systems.
Coverage, claim status, pricing references and remittance advice.
Delivery creation, routing, tracking, proof of delivery and cold-chain events.
CRM, BI, ECM, partner and custom operational systems.
| Clinical connectors | Operational connectors | Boundary rule |
|---|---|---|
| HIS/EHR, LIS, RIS/PACS, clinical devices | ERP, procurement, inventory, HR, facilities, finance | Clinical semantics remain clinical; operational data uses its own canonical model |
| FHIR/HL7/DICOM and clinical terminologies | REST/EDI/OData/SFTP/queues and business reference data | Use MSIS only where clinical meaning actually applies |
| Patient care and clinical workflows | Resources, logistics, staffing, assets and finance | Cross-domain workflows are explicit and auditable |
Catalog → approval → PO → receipt → invoice → reconciliation
Stock levels, reservations, batches, transfers and replenishment
Staff master data, shifts, availability and training references
Equipment registry, work orders, maintenance and utilization
Shipment creation, tracking, proof of delivery and exceptions
Billing references, claim status, remittance and reconciliation
| Category | Typical protocols | When to choose |
|---|---|---|
| Modern enterprise | REST, GraphQL, OData | Vendor-supported online APIs |
| Legacy enterprise | SOAP, proprietary APIs, database/export adapters | Controlled modernization or bridge projects |
| B2B supply chain | EDI / EDIFACT / X12 | Structured partner transactions |
| Batch | SFTP + CSV/XML/JSON | Catalogs, master data and scheduled reconciliation |
| Events | HTTPS webhooks, AMQP/Kafka/RabbitMQ where applicable | Decoupled real-time workflows |
| Healthcare overlap | FHIR/HL7 | Only for data with real clinical/healthcare-standard semantics |
| Surface | Operation / resource | Use | Status |
|---|---|---|---|
| Connector adapter | REST/SOAP/OData/GraphQL client | Vendor API integrations | External API |
| EDI adapter | EDIFACT/X12 parser + acknowledgements | B2B orders/invoices/claims | Protocol surface |
| File adapter | SFTP + CSV/XML/JSON | Batch/legacy systems | Protocol surface |
| Event adapter | Webhook/queue producer & consumer | Status changes and automation | Contract by domain |
| Mediloop domain APIs | Procurement/Supplier/Delivery APIs | Build applications against Mediloop operational services | Use API Reference |
| Operations Connector SDK | Adapter lifecycle, mapping and reliability helpers | Custom and modernization projects | Planned/evolving |