Interoperability in healthcare

HL7 v2/v3, HL7 FHIR – Profiling, validation, Implementation Guide (IG).. Practical, testable, and operable.

HL7 v2/v3 – Integration & data flows

Process HL7 messages — and make them usable for analysis.

We integrate HL7 message flows so that they don’t just “arrive,” but serve as continuously updatable data streams for analytics and quality assurance. Our project experience includes Mirth Connect and HAPI among other things, typical ADT/ORU/… message.

Deliverables:

  • HL7 mapping → target model (including rules and plausibility checks)
  • Message pipelines (legacy records + current data combined in a single analytics model)
  • Incremental data updates(legacy data + current data in a single analytics model)

FHIR – profiling, terminologies, validation, IG

FHIR only becomes “real” with profiles and tests.

Interoperability rarely fails because of “FHIR itself”, but because translating process knowledge into clear, verifiable rules is hard. That’s why we deliver profiles + terminologies + validation + IG as a cohesive package

Leistungen:

  • Profiling:StructureDefinitions, Must Support, cardinalities, required logic
  • Terminologies:CodeSystems/ValueSets/ConceptMaps, extensions, coding rules
  • Validation:instances/examples against profiles, test cases, simulations
  • Implementation Guide (IG):structure, examples, FAQ/glossary, release/change management logic
  • Tooling / practical experience:Simplifier, Forge, FHIR Java Validator, Shorthand (including from recent projects)

CDA ↔ FHIR – classification & migration paths

Not “CDA or FHIR,” but how they work together.

CDA remains relevant as a robust document and archiving layer, while FHIR takes on the integration, analytics, and interaction layer. We support coexistence architectures and transformation paths CDA → FHIR (for fine-grained analytics) as well as FHIR-based document generation.

Three health use cases

  • Use Case 1 – FHIR profiling for a defined exchange scenario

    Profile set + terminologies + examples + validator pipeline + IG chapter structure.

  • Use Case 2 – HL7 v2/v3 integration + analytics

    HL7 processing (Mirth/HAPI) and transformation into an analyzable structure, including incremental updates of historical data.

  • Use Case 3 – Semantic layer (ontologies/metadata) as a sustainability lever

    FHIR as the technical exchange layer, complemented by terminology services and ISO-aligned metadata governance.

FAQ (Health)

  1. Do you “only do FHIR” or also HL7 v2/v3?

    Both — including integration experience with Mirth Connect and HAPI.

  2. What do you include under “validation”?

    Examples/instances, testable rules, validator setup, simulations, and review loops.

  3. Do you really support Implementation Guides (IG) end-to-end?

    Yes — structure, examples, maintenance/change logic, and quality evidence (testability).

  4. How do you deal with existing CDA environments?

    CDA often still makes sense as a document/archiving layer; we define coexistence and migration paths to FHIR.

Are you planning HL7/FHIR interoperability, profiling, or validation? Then send us an email.

Email

Contact