DocumentationSupportCosta Rica · Contact

Digital infrastructure for connected healthcare.

Meddyg · Interoperability & Health Standards

Digital infrastructure for connected healthcare.

We design and implement interoperability, clinical data and medical imaging solutions so different health systems can operate as one ecosystem.

HL7 FHIRDICOMIHE / OpenHIE
Clinical interoperability layer
MEDDYG
EHR / EMR
LAB
RIS / PACS
HIE
TERMINOLOGY
Interoperability services

We connect health systems without replacing them.

We assess architecture, model data and build FHIR layers that integrate existing systems through open standards and a sustainable evolution path.

AssessmentFHIR layerData modeling
Open standards
FHIRClinical exchange & APIs
DICOMMedical imaging
IHEInteroperability profiles
LOINCClinical terminology
Kivú ecosystem

Technology to operate digital health.

FHIR repositories, terminology, RIS, PACS and DICOM connectivity as components that can be deployed independently or as an integrated platform.

Kivú FHIRKivú TerminologyKivú RIS · PACS
Kivú digital health infrastructure
Clinical dataKivú FHIRFHIR repositories and interoperability services.
SemanticsTerminologyClinical terminology services.
ImagingRIS / PACSRadiology and medical imaging workflows.
We work with standards and reference models
Problems we solve

If any of this sounds familiar, it is the ground we work on.

These problems are rarely solved by buying a product alone. They are solved with architecture, standards and an implementation path that respects what already runs.

  • Every system works; together they don't

    The EHR, the lab, imaging and billing each run fine on their own. What moves between them lives in one-off interfaces, often poorly documented, that break when a version changes.

    We address it withInteroperability assessment
  • We are being asked to expose data in FHIR

    An authority, a network or a partner asks for FHIR, and the system holding the data neither speaks the standard nor can be replaced within the time available.

    We address it withFHIR layer
  • One patient, several identities

    Each system issues its own identifier and nobody owns the mapping between them, so assembling a single history comes down to matching names and dates.

    We address it withArchitecture definition
  • The codes don't mean the same thing

    Two systems report the same test with different catalogues, different units and free-text descriptions. The data arrives, but it cannot be compared or aggregated.

    We address it withData modeling
  • We have to connect with other organisations

    Joining an exchange network — national or between institutions — takes profiles, testing and a defined role, not just a published API.

    We address it withHIE Integration
  • There is a guide to meet, and to prove

    An implementation guide, a regulatory requirement or a tender is on the table, and conformance has to be demonstrated with reproducible evidence rather than stated.

    We address it withImplementation Guides
Verifiable experience

Milestones you can check, with the scope we actually had.

We don't publish impact figures we cannot stand behind. We publish what the work was, who it was with, and the part Meddyg played.

  1. International expansionPACS architectures in the Dominican Republic
  2. 2022First FHIR guide for AEFI reporting
  3. 2024First national FHIR server for EDUS/CCSS
  4. 2025Digitally signing FHIR resources with the Central Bank of Costa Rica
  5. 2025–2026National interoperability over X-Road
See the full history
Services

Solve interoperability without turning it into another problem.

We combine architecture, standards and software to address anything from a focused assessment to a complete interoperability layer.

Resources

Content for people building digital health.

Technical analysis, event participation, and Meddyg updates on interoperability and digital health.

Facing an interoperability or health data architecture challenge?

We can start by understanding the problem, the systems involved and the current maturity level.

Talk to Meddyg