Health Technology

    Healthcare interoperability: what it is, its levels and how to connect operations with the HIS

    Healthcare interoperability is the ability of two or more systems to exchange data and use it without anyone having to re-enter it. In a clinic, it connects the clinical record system (HIS) with scheduling, contact channels, documents and reports. It is achieved through standards such as HL7 and FHIR, clear rules on which system owns each piece of data, and security controls. It does not require replacing the HIS.

    COCO Tech AI
    23 January 202613 min read
    Healthcare interoperability: what it is, its levels and how to connect operations with the HIS

    In most clinics, the clinical record lives in one system, the schedule in another, and the call center confirms by phone what the system already knows. Reports, meanwhile, are built in Excel. Every jump between systems means re-keying data, a possible error and a patient who waits.

    In this guide we explain what healthcare interoperability is, its levels, the types of tools available to connect with the HIS, and how to move forward in stages without stopping operations. For Colombia's regulatory framework, see health record interoperability in Colombia. For the technical detail of the standards, see FHIR and HL7 interoperability.

    What healthcare interoperability is and its levels

    Healthcare interoperability is the ability of different systems, applications and devices to connect in order to access, exchange and use data in a coordinated way, within an institution and across institutions. It is not enough for data to travel: the receiving system has to understand it and be able to act on it.

    HIMSS, the international healthcare information and management systems society, divides it into four levels. Each one builds on the previous one.

    Level

    What it solves

    Example in a clinic

    Foundational

    One system can send data to another securely

    The HIS sends an appointment file to another platform

    Structural

    Data arrives in a format the other system recognizes

    The appointment arrives with defined fields: patient, date, provider, site

    Semantic

    Both systems understand the same thing by each data element

    "Canceled" means the same in the schedule and in the HIS

    Organizational

    There are rules, owners and agreements for using the data

    It is defined which system owns availability and who fixes an error

    Most projects that fail stay at the foundational level: the systems are connected, but no one defined what each status means or who is responsible when a data point does not match.

    Where operations break when systems don't talk to each other

    A lack of interoperability is felt less in the IT department than in day-to-day operations. These are the most common signs:

    • Availability in two places. The call center can't see the real schedule and confirms by phone what the system already knows.

    • Orders that are re-keyed. A medical order arrives as a PDF or on paper, and someone copies its data to be able to book.

    • Cancellations that don't free the slot. The patient cancels through one channel, but the waitlist never finds out and the slot stays empty.

    • Patient data repeated on every channel. Whoever writes on WhatsApp has to give their ID and contact details again.

    • Reports that arrive late. Management decides with a hand-built Excel file, one or two weeks after the fact.

    Each of these failures has a cost: staff time, unused slots and patients who wait longer than necessary.

    Standards and regulations: necessary, but not sufficient

    Standards define how data is structured and understood. Most of them are published by HL7 International, the organization that develops the main digital health standards; FHIR is the most recent of them. The most widely used are:

    • HL7 v2: messages between systems, widely used in hospitals for admissions, orders and results.

    • [HL7 FHIR](https://hl7.org/fhir/overview.html): organizes data into resources (Patient, Appointment, Order) that are queried through a web API. It is the standard most new projects adopt today.

    • Clinical terminologies: ICD-10 for diagnoses, SNOMED CT for clinical concepts and LOINC for laboratory tests. They make the semantic level possible.

    Several countries in the region already require interoperability by law. In Colombia, Law 2015 of 2020 regulates electronic health record interoperability, and Resolution 1888 of 2025 adopted the Digital Care Summary (Resumen Digital de Atención, RDA); we explain it in health record interoperability in Colombia. In Peru, Law 30024 created the National Registry of Electronic Health Records (RENHICE), which regulates their interoperability. Before starting a project, it is worth checking what the health authority requires in each country where the institution operates.

    A standard ensures that two systems speak the same language. It does not decide which system is the source of each data element, what happens when a connection fails or who corrects a duplicate record. Those decisions belong to the institution and are made before development starts.

    Which tools are used to connect systems with the HIS

    Not all interoperability tools solve the same problem. Before comparing vendors, it helps to know which category each one falls into.

    Type of tool

    What it does

    When it fits

    HIS API

    Exposes HIS data so other systems can read or write it

    When the HIS offers one and the use case is narrow

    Integration engine

    Receives, translates and routes messages among many systems (for example, from HL7 v2 to FHIR)

    Hospitals with many systems and their own integration team

    FHIR server or cloud FHIR service

    Stores and publishes clinical data in FHIR format

    Clinical data exchange, analytics or reporting to the authority

    Operational platform connected to the HIS

    Takes HIS data and runs processes: booking, confirming, recovering slots, validating orders

    When the problem is in access and operations, not just in moving data

    The first three move and organize data. The fourth turns it into actions. In practice, many institutions combine a connection to the HIS (through an API or an integration engine) with operational platforms that work on that data.

    Artificial intelligence shows up mainly in the fourth category: reading clinical documents, understanding what the patient writes or prioritizing whom to offer a slot. For it to work, the connection with the HIS has to be in place first.

    Want to connect your HIS with your scheduling operations?

    Let's review the systems you use and where to start.

    Start an integration

    How to connect operations without replacing the HIS

    An interoperability project moves forward better by use case than by system. This roadmap works for most institutions:

    1. Take inventory. List the systems, what data each one holds and how they connect today (API, file, manual entry).

    2. Pick a use case with visible impact. For example: appointments from the HIS reach the confirmation platform and the patient's response goes back to the HIS.

    3. Define the source of truth for each data element. The clinical record usually owns clinical data; the schedule owns availability. Document who can change each status.

    4. Map and test with test data. Review fields, codes and statuses. Test duplicates, cancellations, retries and connection failures before going live.

    5. Measure and expand. Track these indicators and add the next use case once the first one is stable: percentage of records synced without manual intervention; errors and duplicates per 1,000 records; time between an event in one system and its reflection in the other; data-entry hours no longer needed.

    If the focus is scheduling, in HIS scheduling module or dedicated platform we explain what each should handle, and in AI scheduling integrated with the HIS, how they connect without replacing each other.

    Security: what to control in every integration

    More connections mean more entry points to health data, which most laws in the region treat as sensitive data. These are the minimum controls to require from any vendor:

    • A dedicated identity for each integration, using certificates or OAuth 2.0, never shared users.

    • Least privilege: each integration account accesses only the data it needs.

    • Encryption in transit (current TLS) and at rest, including backups.

    • Credentials kept in a secrets manager and rotated under a defined procedure.

    • An audit log of every exchange: who, when, which resource and with what result.

    • Compliance with the data protection law of each country where the institution operates.

    HL7 FHIR organizes the exchange, but it does not protect it by itself. Security depends on how each connection is implemented.

    How COCO integrates with the institution's systems

    COCO is an operational platform that connects with the HIS: it is not a clinical record system and does not replace one. It integrates without modifying existing systems and uses their data to manage patient access. COCO complies with HL7 standards for the exchange of clinical and administrative information.

    • Available integrations: OSIGU and SAP Salud. If the institution's system is not on the list, the connection is made through an API.

    • Processes it connects: medical scheduling, appointment confirmation, patient campaigns, waitlists and clinical OCR to read orders and test results.

    • Where to start: patient campaigns can begin with an Excel file while the HIS connection is being set up.

    The scope of each integration is defined during implementation, based on the institution's system and processes.

    Frequently asked questions

    Are interoperability and integration the same thing?
    No. An integration connects two specific systems, for example the HIS with a scheduling platform. Interoperability is the broader ability of many systems to exchange data with a shared format and meaning, under agreed rules of use. An institution can have many integrations and still be poorly interoperable if each one runs on its own rules.
    Do you have to change the HIS to make it interoperable?
    Not necessarily. Most projects connect the existing HIS through its API, an integration engine or a platform that integrates with it. Changing the HIS is only justified when the system allows no form of exchange or when a regulation requires capabilities the vendor does not offer.
    Is it enough for a system to use HL7 FHIR?
    No. FHIR defines how data is structured and queried, but it does not decide which system owns each data element or what happens when there is an error or a duplicate. Nor does it guarantee security. The institution defines those rules with its vendors before development starts.
    What should you ask a vendor before integrating it with the HIS?
    Ask them to show an integration running with a system like yours. Ask which data it reads and which it writes, how it handles errors and retries, who maintains the connection when the HIS is updated, and what access and audit controls it offers.

    Connecting operations with the HIS is a staged project that can start with a single process.

    Connect your HIS with scheduling, confirmation and waitlists

    We'll show you how COCO works with the systems you already use.

    Request a demo

    COCO in the press

    What independent media have published on this topic.

    Related articles

    Cybersecurity in Healthcare: Why Protecting Clinical Data Is Now a Strategic Priority (Not Just a Technical One)

    Cybersecurity in Healthcare: Why Protecting Clinical Data Is Now a Strategic Priority (Not Just a Technical One)

    Protecting clinical data is crucial for patient care and trust, learn how cybersecurity is evolving into a strategic priority in healthcare

    Health Record Interoperability in Colombia: What Changes in 2026

    Health Record Interoperability in Colombia: What Changes in 2026

    Health record interoperability in Colombia: since 2026, medical data is shared across institutions, reducing duplication and improving care.

    COCO vs. Cliniweb: two very different ways to approach healthcare scheduling

    COCO vs. Cliniweb: two very different ways to approach healthcare scheduling

    Many healthcare institutions in Panama discover that a traditional scheduling tool does not solve the real problem: no-shows, underused capacity, operational friction, and limited interoperability. This article compares COCO and Cliniweb to show which type of institution fits each solution and when an access platform can drive better efficiency and results.