HEALTHCARE SYSTEMS CONNECTORS
Appointments & Scheduling
3 of 9Synchronize appointments, schedules and availability between HIS/EHR systems and Mediloop. Support clinical, teleconsultation and resource-based bookings with real-time updates.
FHIR AppointmentFHIR ScheduleFHIR SlotHL7 v2 SIUPractitionerLocationDeviceHealthcareService
Scheduling Integration Flow
1
Source System
HIS/EHR creates appointments, schedules and availability
2
Mediloop Connector
Receives, validates and transforms scheduling data
3
Scheduling Engine
Reconciles appointments, resources and constraints
4
Mediloop Calendars
Patient, clinician, room and equipment calendars
5
Notifications
Confirmations, reminders, changes and cancellations
6
Downstream Systems
HIS/EHR, teleconsultation and portals updated
Bidirectional synchronization keeps scheduling consistent across all systems and prevents conflicting bookings.
Supported Standards
FHIR R4 / R4B
Appointment
Schedule
Slot
HealthcareService
Practitioner
Location
Device
Patient
Encounter
RelatedPerson
HL7 v2 SIU
Schedule Information Unsolicited messages
New / rescheduled / modified / cancelled bookings
Participant and resource updates
ACK-based delivery confirmation
FHIR Scheduling Resources
| Resource | Purpose | Typical operations |
|---|---|---|
| Appointment | Booked clinical encounter / procedure | create, read, update, cancel/search |
| Schedule | Availability container for actor/resource | read/search |
| Slot | Bookable time interval | read/search/status update |
| HealthcareService | Service definition and eligibility context | read/search |
| Practitioner / Location / Device | Resources participating in booking | read/search |
| Patient / RelatedPerson | Patient and delegate context | read/search |
Resource Scheduling & Conflict Resolution
Synchronize clinicians, rooms and equipment as first-class resources
Detect overlapping bookings and resource constraints
Preserve authoritative source when multiple systems can update the same appointment
Use optimistic concurrency / version checks for updates
Keep cancellation reason, actor and timestamps
Reconcile stale slots after reconnect or batch imports
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 | Appointment / Schedule / Slot / HealthcareService / Practitioner / Location / Device | Build modern scheduling and availability workflows | FHIR surface |
| HL7 v2 | SIU scheduling messages + ACK | Integrate legacy hospital scheduling systems | Protocol operation |
| Events | appointment.created / updated / cancelled / rescheduled | Keep portals, teleconsultation and downstream apps synchronized | Planned contract |
| REST / SDK | Scheduling façade and conflict/reconciliation services | Accelerate new applications and legacy modernization | Planned contract |
Events & Notifications
| Event | Typical consumer |
|---|---|
| appointment.created | Patient/clinician calendars, notifications |
| appointment.updated | HIS/EHR sync, patient portal |
| appointment.rescheduled | Reminder service, teleconsultation |
| appointment.cancelled | Resource release and patient notification |
| slot.status.changed | Availability search and booking UX |
Best Practices
Choose and document the authoritative scheduling source
Use stable external identifiers for appointments and resources
Treat time zone and daylight-saving handling explicitly
Make updates idempotent and version-aware
Test simultaneous booking and cancellation races
Monitor synchronization lag and reconciliation backlog