|
|
| (3 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | [http://wiki.hl7.org/index.php?title=FHIR_Connectathon_19 Return to Connectathon 19 page]
| + | entered in error |
| − | | |
| − | [http://wiki.hl7.org/index.php?title=Category:201809_FHIR_Connectathon_Track_Proposals 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
| |
| − | | |
| − | ==Justification==
| |
| − | <!--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 lab result 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.
| |
| − | | |
| − | ==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
| |
| − | ::Email: claude.nanjo@utah.edu
| |
| − | ::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
| |
| − | * ''Your organization here!''
| |
| − | | |
| − | ==Roles==
| |
| − | Please include information here regarding how much advance preparation will be required if creating a client and/or server.
| |
| − | <!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
| |
| − | ===Catalog Server===
| |
| − | <!-- Provide a description of the capabilities this role will have within the connectathon -->
| |
| − | * A HAPI FHIR Server for the persistence of FHIR instances to support this use case.
| |
| − | * CIMI Detailed Clinical Models for labs and wound assessment
| |
| − | * CIMI-to-FHIR translation tooling
| |
| − | * A CDS client and server
| |
| − | * Knowledge artifacts to support CIMI use case - TBD
| |
| − | | |
| − | ==Scenarios==
| |
| − | This connectathon track will test the following interactions
| |
| − | * Generation of FHIR profiles from CIMI models
| |
| − | * Definition of FHIR instance that conform to these profiles
| |
| − | * Use and validation of FHIR instance in a CDS Hook context
| |
| − | | |
| − | ==Security and Privacy Considerations==
| |
| − | Authentication shall not be addressed in this track
| |
