This wiki has undergone a migration to Confluence found Here

Difference between revisions of "201809 CIMI Laboratory and Wound FHIR Profile Track"

From HL7Wiki
Jump to navigation Jump to search
(Replaced content with "entered in error")
Line 1: Line 1:
[ Return to Connectathon 19 page]
entered in error
[ Return to Sep 2018 Proposals]
[[Category:201809_FHIR_Connectathon_Track_Proposals|Sep 2018 Proposals]]
{| align="right"
| __TOC__
=CIMI Laboratory and Wound Assessment FHIR Profiles=
==Submitting WG/Project/Implementer Group==
<!-- Who is asking for this track? -->
* Clinical Information Model Initiative
<!--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 track will investigate the following questions:
* The specification of detailed laboratory result and wound assessment models.
* The translation of these detailed clinical models into FHIR as both Logical FHIR profiles and resource profiles.
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.
A deliverable of this track is an implementation guide for CIMI Laboratory Result profiles for review by the HL7 community. Profiles will also be published on
All profiles shall be developed using the FHIR R4 version made available to connectathon participants.
==Proposed Track Lead==
<!-- Name, email and Skype id of individual who will coordinate the track at the connectathon -->
See [[Connectathon_Track_Lead_Responsibilities]]
:Claude Nanjo
::Zulip: cnanjo
==Expected participants==
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
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 profile
*University of Utah shall participate in the generation of FHIR Logical Profiles from CIMI and the use of FHIR resource profiles developed by Intermountain in a CDS application.
*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
* ''Your organization here!''
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.
<!-- 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 -->
* Content provider: CIMI Detailed Clinical Models for labs and wound assessment. Corresponding knowledge artifacts for CDS scenario.
* Translation tool providers: CIMI-to-FHIR translation tooling for both resource and logical profiles.
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

Latest revision as of 23:24, 23 August 2018

entered in error