Difference between revisions of "201809 CIMI Logical Model To FHIR Resource Profile Translation Track"
(→Roles) |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 14: | Line 14: | ||
==Justification== | ==Justification== | ||
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. --> | <!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. --> | ||
| − | In order to support the interoperable exchange of health information, detailed profiles for common conditions, observations, and procedures will be required. This | + | In order to support the interoperable exchange of health information, detailed profiles for common conditions, observations, and procedures will be required. This hands-on 'bird-of-a-feather' session will investigate the following questions: |
| − | * | + | * How domain specific detailed clinical logical models are mapped to their equivalent FHIR resource profiles. |
* The translation of these detailed clinical models into FHIR as both Logical FHIR profiles and resource profiles. | * The translation of these detailed clinical models into FHIR as both Logical FHIR profiles and resource profiles. | ||
| + | * The exploration of opportunities for various tools to work together to address this challenge. | ||
| − | The purpose of the track is to learn more about the conversion of logical models into FHIR profiles and to raise important questions for discussion at HL7 | + | Future connectathons will explore the use of these FHIR profiles in applications but is out-of-scope of this track. |
| − | + | ||
| + | The purpose of the session/track is to learn more about the conversion of clinical logical models into FHIR logical models and resource profiles and to raise important questions for subsequent discussion at HL7. | ||
All profiles shall be developed using the FHIR R4 version made available to connectathon participants. | All profiles shall be developed using the FHIR R4 version made available to connectathon participants. | ||
| Line 42: | Line 44: | ||
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on --> | <!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on --> | ||
<!-- Provide a description of the capabilities this role will have within the connectathon --> | <!-- Provide a description of the capabilities this role will have within the connectathon --> | ||
| − | * Content provider | + | * Content provider shall provide formal logical models expressed as either using the OpenEHR/CIMI specification or as FHIR Logical Profiles. |
| − | * Mapping specification providers | + | * Mapping specification providers shall provide a specification for the mapping between logical model and FHIR resource profiles. Participants are welcome to use the FHIR mapping tools and language. |
| − | * Translation tool providers | + | * Translation tool providers shall provide Logical-Model-to-FHIR translation tooling for both resource and logical profiles. |
| + | * Authoring/Visualization tool providers | ||
==Scenario== | ==Scenario== | ||
Latest revision as of 19:30, 23 August 2018
Return to Connectathon 19 page
CIMI Logical Model To FHIR Resource Profile Translation Track
Submitting WG/Project/Implementer Group
- Clinical Information Model Initiative
Justification
In order to support the interoperable exchange of health information, detailed profiles for common conditions, observations, and procedures will be required. This hands-on 'bird-of-a-feather' session will investigate the following questions:
- How domain specific detailed clinical logical models are mapped to their equivalent FHIR resource profiles.
- The translation of these detailed clinical models into FHIR as both Logical FHIR profiles and resource profiles.
- The exploration of opportunities for various tools to work together to address this challenge.
Future connectathons will explore the use of these FHIR profiles in applications but is out-of-scope of this track.
The purpose of the session/track is to learn more about the conversion of clinical logical models into FHIR logical models and resource profiles and to raise important questions for subsequent discussion at HL7. All profiles shall be developed using the FHIR R4 version made available to connectathon participants.
Proposed Track Lead
See Connectathon_Track_Lead_Responsibilities
- Claude Nanjo
- Email: claude.nanjo@utah.edu
- Zulip: cnanjo
Expected participants
The following organizations have indicated an interest in participating in this track:
- Intermountain Health Care shall provide the detailed clinical model specification and tooling to convert DCMs into FHIR Resource Profiles
- University of Utah shall participate in the generation of FHIR Logical Profiles from CIMI and their translation to FHIR Resource Profiles.
- Mitre shall also explore the conversion of CIMI wound assessment models to FHIR profiles
- Richard Esmond will be demonstrating a tool to represent profiles and DCMs as clinician-friendly forms
- Any participant interested in the translation of domain-specific logical models into FHIR logical and resource profiles.
Roles
Please include information here regarding how much advance preparation will be required if creating a client and/or server or relevant track-related tooling and content.
- Content provider shall provide formal logical models expressed as either using the OpenEHR/CIMI specification or as FHIR Logical Profiles.
- Mapping specification providers shall provide a specification for the mapping between logical model and FHIR resource profiles. Participants are welcome to use the FHIR mapping tools and language.
- Translation tool providers shall provide Logical-Model-to-FHIR translation tooling for both resource and logical profiles.
- Authoring/Visualization tool providers
Scenario
This connectathon track is concerned primarily with the translation from logical models to FHIR resource profiles. In this connectathon, we invite any participant who is interested in this process. Prior knowledge of CIMI is a plus but the discussion will also apply to the translation of other logical models to FHIR. FHIR R4 knowledge is a must. We would like to also encourage clinical participation as we discuss the proper representation of both logical models and FHIR resource profiles from a clinical perspective. This connectathon track shall not make use of the FHIR API. It shall explore the FHIR mapping language and FHIR translation tools as well as tools and mapping languages developed by community members.
- Prerequisites
- CIMI logical models for the domain of interest or non-CIMI FHIR logical profiles for a domain of interest (CIMI models and logical profiles shall be provided to participants who do not have such models developed.)
- Familiarity with FHIR R4
- Knowledge of the FHIR mapping language and tooling a plus. Other mapping languages may be considered for this track.
- Tooling to support the translation of logical models (either CIMI native models or FHIR logical profiles) into FHIR resource profiles
- Part I - Participants shall explore and discuss how to optimally represent logical models as FHIR resources.
- Part II - Participants shall provide tooling and/or a specification for the authoring of declarative mappings from proposed logical models to FHIR resource profiles
- Participants are encouraged to provide a formal specification for a grammar to support this model mapping exercise.
- Part III - Participants shall run translation tooling against proposed declarative mappings to generate FHIR resource profiles
Security and Privacy Considerations
Authentication shall not be addressed in this track
