Documentation SupportCosta Rica · Contact

Assessment

Interoperability assessment

We analyze systems, workflows, standards and integration points to build a clear view of the current state and interoperability priorities.

Capabilities

Interoperability map↗Maturity level↗Gaps and risks↗Target architecture and roadmap↗

Starting point

Understand before building.

A structured assessment reduces rework and helps decide what to integrate first and how.

Integration

FHIR layer

We build transformation and FHIR exposure layers to connect existing systems, normalize data and enable new exchange scenarios without unnecessary replacement.

Capabilities

Mapping and transformation↗On-the-fly or materialized↗FHIR exposure and APIs↗Validation and conformance↗

Progressive modernization

FHIR without replacing the entire stack.

A well-designed layer lets legacy systems evolve while preserving existing clinical operations.

Conformance

We design, profile and publish HL7 FHIR implementation guides — institutional, or national and regional — with their profiles, terminology, examples and conformance rules, on R4 or R5 depending on what the ecosystem requires.

Capabilities

Institutional or national scope↗Profiles, extensions and terminology↗R4 / R5 version strategy↗Publication and conformance↗

Applied standards

From specification to verifiable implementation.

Implementation guides turn technical and semantic decisions into shared ecosystem rules.

Semantics

Data modeling

We analyze and redesign the data model across its four layers — governance, semantic, syntactic and technical — define the terminology strategy (SNOMED CT, LOINC, national CodeSystems and ValueSets) and the normalization and migration path.

Capabilities

Model review and scope↗Terminology and semantic mapping↗Canonical, FHIR and openEHR models↗Normalization and migration↗

Meaningful data

Interoperability starts with the model.

Before transport come structure, semantics and the rules that make data understandable.

Architecture

Architecture definition

We define the organization's digital health architecture: which components exist, which zone each one lives in, what crosses each boundary, and how it connects to the national exchange platform without widening the exposure surface.

Capabilities

Components: MPI, catalogues and registries↗Trust zones and DMZ↗National network connection (X-Road)↗Governance and cybersecurity↗

Solution design

Architectures that can operate and evolve.

The goal is not more components, but clear responsibilities, boundaries and flows between them.

Ecosystems

HIE Integration

We connect your organization to an HIE according to the role it carries — consumer, producer or custodian: which capabilities are required of you, what you still have to build, how to prove technical and regulatory compliance, and how transactions run with the ecosystem.

Capabilities

Consumer, producer or custodian↗Gap assessment by role↗IHE profiles and OpenHIE↗Compliance and connection testing↗

Connected exchange

From local systems to the health ecosystem.

A well-designed HIE integration connects organizations without losing governance, traceability or control over clinical flows.

Clinical cloud

Cloud Repositories

We deploy and operate FHIR R4/R5, medical imaging (PACS/VNA) and digitally signed document repositories, with identity, authorization, auditing and backup included, and validated against national implementation guides.

Capabilities

FHIR R4 / R5 repositories↗Medical imaging PACS / VNA↗SMART on FHIR and IHE IUA↗Digitally signed documents↗

Turnkey

The repository, running in weeks.

You choose what you need to hold. The foundation underneath it — identity, authorization, audit, encryption, backup and operations — is included and never quoted separately.

KivúProducts↗

Radiology

Kivú RIS

Radiology workflow management built to integrate with the organization's clinical and imaging ecosystem.

Capabilities

Scheduling and workflow↗Radiology worklists↗Clinical integration↗DICOM / FHIR interoperability↗

Kivú · Radiology

Connected radiology workflows.

An operational layer to coordinate radiology work and connect it with the broader clinical infrastructure.

Medical imaging

Kivú PACS

Infrastructure to store, access and exchange medical imaging within DICOM workflows and modern clinical integrations.

Capabilities

DICOM storage↗Study access↗RIS integration↗Imaging connectivity↗

Kivú · Imaging

Images where the workflow needs them.

PACS as part of a connected clinical architecture rather than an isolated silo.

Clinical data

Kivú FHIR

FHIR repositories and services for exposing, exchanging and operating clinical data through standards-based APIs.

Capabilities

FHIR repository↗Interoperability APIs↗Validation and profiles↗Application integration↗

Kivú · FHIR

FHIR as infrastructure.

A reusable component for clinical exchange and digital services on a standards-based foundation.

Terminology

Kivú Terminology

Terminology services to centralize clinical vocabularies, validation, expansion and semantic normalization.

Capabilities

CodeSystem / ValueSet↗Code validation↗ValueSet expansion↗Semantic normalization↗

Kivú · Semantics

The same meaning across systems.

Semantic interoperability needs shared services to interpret and validate clinical codes.

Identity & access

Kivú Conquest

Authentication and authorization services for health ecosystems, built around open standards and interoperable security profiles.

Capabilities

OAuth 2.0 / OpenID Connect↗SMART on FHIR↗IHE IUA↗Access control and tokens↗

Kivú · Security

Interoperable identity and access.

A security layer to control who can access which clinical resource and in what context, while decoupling applications from authorization complexity.

Digital trust

Kivú eSignature

A digital signature component with certificates and cryptographic validation for documents, transactions and clinical workflows that require verifiable authenticity and integrity.

Capabilities

PKI and certificates↗Clinical document signing↗Sealing and validation↗API and workflow integration↗

Kivú · Trust

Verifiable trust in every transaction.

Digital signatures add evidence of authorship, integrity and validation to clinical and administrative processes.

Knowledge

We share what we learn.

Technical content, events and analysis on digital health, FHIR, DICOM, terminology and architecture.

Blog↗Events↗News↗

Community

FHIR, architecture and clinical data.

Resources for technical, clinical and digital transformation teams.

Contact

ES EN PT

Let’s talk

About

Services

Services Interoperability assessment FHIR layer Implementation Guides Data modeling Architecture definition HIE Integration Cloud Repositories

Products

Products · Kivú Kivú RIS Kivú PACS Kivú FHIR Kivú Terminology Kivú Conquest Kivú eSignature

Resources

Blog Events News

Contact Let’s talk→

ES EN PT

Meddyg/
Resources/
Events

Resources

Events

Meddyg participation, workshops and technical meetings.

ULatina San Pedro, Edificio C

Foro "Iniciativa Salud Digital Costa Rica"

Free national forum on health interoperability, organized by ULatina and Global Life Centered Hub, on Friday, September 25, 2026 in San Pedro. Full agenda, keynote and real use cases from Costa Rica.

September 25, 2026Explore→

Interoperability, architecture and products for digital health infrastructure.

HL7®, FHIR® and the FHIR logo are registered trademarks of Health Level Seven International; SNOMED CT® of SNOMED International; LOINC® of the Regenstrief Institute; DICOM® of NEMA. Their use on this site is descriptive only and does not constitute endorsement or certification by these organizations.

Cookies and measurement

This site measures your visit without cookies from the first page. Google Analytics and Microsoft Clarity go further, and only run if you allow it. Read the privacy policy.

Always on: cookieless measurement by Cloudflare and Ahrefs. It identifies no one and does not follow you beyond this site.

Audience analyticsGoogle Analytics, with cookies. How many people arrive, where from and which pages they read.Session recordingMicrosoft Clarity. Records clicks, scrolling and movement through the page to show where the design fails.