---
# System prepended metadata

title: 2025.08.05 Agenda

---

# 2025.08.05 Agenda

* Current items
    * Charter submitted
    * GitHub org https://github.com/openehr-fhir exists, need to request for repo
    * Confluence space requested, waiting on creation
* Severin doc
    * [Data Type Mappings](https://hackmd.io/WGPXcTiiRM2j0NwAgcwqMA?both)
* Review of known mapping projects / documentation
    * [FHIRConnect](https://sevkohler.github.io/FHIRconnect-spec/build/site/FHIRconnect/v1.0.0/index.html)
        * [FHIRConnect-mapping-lib](https://github.com/SevKohler/FHIRconnect-mapping-lib/tree/main)
        * [medblocks openFHIR](https://github.com/medblocks/openFHIR/tree/main)
    * [openEHR: HL7 FHIR choice x analysis](https://openehr.atlassian.net/wiki/spaces/stds/pages/441581569/HL7+FHIR+choice+x+analysis)

    * Other / prototype / stale?
        * [Mapping of OpenEHR Archetypes to FHIR Resources is Use Case Oncology](https://pubmed.ncbi.nlm.nih.gov/34734888/)
        * [MapEHR](https://mapehr.com/docs/introduction) ([schema](https://www.schemastore.org/mapehr.json))
        * [ALUR](https://github.com/alpamax/ALUR)


---


HL7 & openEHR Collaboration: Group Charter & Reporting Framework

This document provides a standardized framework for the four technology collaboration groups. It is designed to ensure clarity of purpose, consistent operations, and transparent reporting to the joint leadership group.

# Part 1: Workstream Charter Template
To be completed by each of the four collaboration groups (Archetypes in HL7, IPS Alignment, Archetype Mapping, and Technology) and agreed upon with the leadership group.

1. Workstream Title: > Archetype Mapping and Technology
2. Workstream Co-Chairs:
*	HL7 Lead: Gino Canessa, Microsoft
*	openEHR Lead: Severin Kohler, BIH @ Charité Berlin

(Note: The co-chairs are responsible for facilitating meetings, driving progress, and serving as the primary point of contact for the leadership group.)

3. Mission Statement (The "Why"):

Improve healthcare interoperability by establishing a robust and bi-directional mapping methodology to convert data between openEHR and HL7 FHIR.

4. Key Objectives & Deliverables (The "What"):
A bulleted list of the specific, tangible outputs this group will produce. These should be SMART (Specific, Measurable, Achievable, Relevant, Time-bound).

### Phase 1

From now through Q4 2025.

#### Concrete datatype mappings between FHIR and openEHR are complete, correct, and stable

* P0: Create a maintainable list of 'arbitrary' questions and their answers (e.g.: the FHIR system URL for openEHR local codes)
* P0: Complete a list of datatypes that can converted losslessly
    * P0: openEHR -> FHIR
    * P0: FHIR -> openEHR
* P0: Complete a list of datatypes that need additional functionality to convert without data loss
    * P0: openEHR -> FHIR
    * P0: FHIR -> openEHR
* P0: Use the list of 'additional functionality' to build a set of recommendations:
    * P0: to HL7 for FHIR Extensions, datatypes, or metadatatypes
    * P0: to openEHR for clusters, archetypes, and RM
* P1: Publish a draft specification that includes lossless datatype mappings:
    * P1: *From* every FHIR datatype
    * P1: *From* every openEHR datatype
* P1: Create and publish a set of examples that can be used in data conversion
* P2: Provide at least one open-source utility for data conversion
* P2: Create and publish a set of tests that can be used to validate a data conversion utility
* P4: Provide structured mapping files for conversion
    * P4: FHIR ConceptMap and/or StructureMap/FML (FHIR Mapping Language)


### Phase 2

From Q4 2025 through Q2 2026. Will review and refine once Phase 1 is complete.

#### Methodology for designing / creating / viewing mappings between openEHR Templates and FHIR Resources

* Define process for conceptual mapping from:
    * an openEHR [archetype,template,RM] to one or more FHIR resources
    * a set of FHIR resources into an openEHR [archetype,template,RM]
* Mappings between openEHR models and FHIR resource models
* Create and publish a set of examples that can be used in data conversion
* Create and publish a set of tests that can be used to validate a data conversion utility

##### Platform for designing / creating / viewing mappings between openEHR Templates and FHIR Resources

* Develop and release a set of open-source reference implementation tools (e.g., libraries, transformation services) by Q1 2026.
* Demonstrate successful data exchange using the methodology at the next HL7 Connectathon.




5. Methodology & Approach (The "How"):
A brief description of how the group will operate and the key activities it will undertake.
*	Conduct bi-weekly working group calls.
    * Known TimeZones: UK, Central US (UTC-5/-6), Eastern AU, CET
    * Bi-weeky: Tuesday 2025-07-22, 2025-08-05, 2025-08-19 etc.
    * Time: 1pm GMT / 3pm CET / 2pm BST / CDT 8am / AEST 11pm
    * openEHR/HL7 Archetype Mapping Working Group.
        * Join Zoom Meeting
        * https://hl7-au.zoom.us/j/83138323593?pwd=16B93hKvlVqvZ2aYckVgNzF4EA7E9z.1
        * Meeting ID: 831 3832 3593
        * Passcode: 111111
          
*	Utilize GitHub for all specification and code development.
*	Engage with the wider community for feedback through regular webinars and presentations.
*	Perform joint clinical and technical modelling sessions to resolve specific mapping challenges.

---

# Part 2: Operational & Reporting Framework

1. Collaboration Platforms (The "Where"):
*	Source Control & Artefact Management: A shared repository under a joint organizational structure.
    *	TODO: GitHub Repos / Orgs:
        *	Want an org for this work
        *	Is there one for other groups already
        *	If not, we will create one (likely via Marcus Baw)
    *	TODO: What are the outputs (e.g., software, spec)
        *	Both, see OKRs
*	Documentation & Knowledge Base: A shared Wiki/Confluence or similar platform for meeting minutes, architectural decisions, and public-facing documentation.
    *	Meeting minutes in confluence (after today =) - TODO: which org / space?
        *	@GinoCanessa will create a space in the FHIR Confluence
*	Communication: A dedicated Slack or Zulip channel for day-to-day discussion and coordination.
        *	Zulip Channel: [FHIR-OpenEHR Mapping](https://chat.fhir.org/#narrow/channel/517188-FHIR-OpenEHR-Mapping)
        *	Currently public, @GinoCanessa - make web-public
*	Meetings: Recurring video calls (Zoom/Teams) with published agendas and minutes stored on the group's Wiki/Confluence page.
    *	Zoom calls...
        *	Every-other Monday (July 22 is on) at 13:00 GMT

2. Quarterly Leadership Report Template (The "How We're Doing"):
To be submitted by the co-chairs on the last working day of each quarter.
*	Workstream: [Group Name]
*	Reporting Period: [Month, Year]
*	Overall Status: [ Green - On Track | Amber - At Risk | Red - Blocked ]
*	Executive Summary: (2-3 sentences summarizing key achievements, challenges, and outlook.)
*	Key Accomplishments (This quarter):
    *	[Bulleted list of completed tasks and significant progress.]
*	Progress Against Key Objectives:
    *	Objective 1: [On Track / At Risk / Blocked] - Brief update.
    *	Objective 2: [On Track / At Risk / Blocked] - Brief update.
    *	Objective 3: [On Track / At Risk / Blocked] - Brief update.
*	Risks, Issues & Blockers:
    *	['Risk' name]: [Description of potential issue and impact.]
    *	['Issue' name]: [Description of current problem and impact.]
*	Support Required from Leadership:
    *	['Decision needed' / 'Resource request' / 'Cross-group alignment']: [Specific ask from the leadership group.]
*	Focus for Next quarter:
    *	['Priority 1']: [Description of key focus area.]
    *	['Priority 2']: [Description of key focus area.]

