Skip to main content
MediSync Connect exchanges the same clinical information regardless of the connectivity model. What changes is the wire format: FHIR resources for API-based systems, and GDT records / HL7 messages / structured XML for file-based systems reached through the Agent.
  • Inbound — MediSync reads patient context from the source system.
  • Outbound — MediSync writes finished documentation back into the source system.

​
Capability matrix

The exact set of capabilities depends on what a given system exposes. Scheduling (Slot / Appointment) is available on ISiK hospital systems and selected PVS; file-based systems primarily exchange patient context inbound and clinical documentation outbound. We confirm the capabilities of your specific system during onboarding.

​
Reading patient context (inbound)

Before documentation begins, MediSync pulls the patient and relevant context from the source system:
  • Patient identity & demographics — the current patient, brought into MediSync.
  • Diagnoses — the existing problem list, as coded Condition resources (ICD-10-GM) where the system provides them.
  • Observations & results — prior results and measurements.
  • Documents — existing clinical documents where available.

​
Writing documentation back (outbound)

Once documentation is complete in MediSync, it is filed back into the record:
  • Clinical note — written as a DocumentReference, a GDT 6310 result record, an HL7 v2 message, or the system’s native XML format, depending on the system.
  • Referral / doctor’s letter — written the same way, in the system’s format.
  • Diagnosis — written back as coded data (Condition / ICD-10-GM) where the system supports structured write-back.
Diagnoses are exchanged as coded data rather than free text, so they land as structured, queryable entries in the receiving system.