Difference between revisions of "SWF on FHIR"

From IHE Wiki
Jump to navigation Jump to search
Line 22: Line 22:
 
* IHE Scheduled Workflow
 
* IHE Scheduled Workflow
 
* HL7 FHIR  
 
* HL7 FHIR  
 +
* DICOM
 
==5. Discussion==
 
==5. Discussion==
Currently, the joint HL7/DICOM Imaging Integration Working group is planning to address gaps with the HL7 v2/FHIR mapping relevant to imagingThis will be key input.
+
A comprehensive inclusion of FHIR with the existing SWF is a major effort.  This level of effort should not inhibit IHE Radiology from starting this project. This project proposal scope needs to limited to a focused component of the overall transformation to a FHIR-based workflowThe initial proposed scope is to focus on the Imaging Orders to FHIR Data Model.
  
The RSNA IAIP demonstration is currently defining FHIR resources relative to SWF that will be accessed during the demonstration.
+
This project needs to leverage and collaborate with existing profiling work that is either in progress or completed by other IHE domains and HL7. 
 +
 
 +
HL7 Orders and Observations currently has an IG in progress for v2 to FHIR mapping which includes a General Order Message.  This work can be leveraged and can help O&O with usage of the implementation guide.
 +
 
 +
The joint DICOM WG20/HL7 Imaging Integration Working group has a workitem to address gaps with the HL7 v2/FHIR mapping relevant to imaging.
 +
 
 +
IHE PCC has a profile QEDm which utilized FHIR for query of existing Data.  While the profile does have an option for procedures, it is missing an option for ServiceRequests.  This project could utilize the Procedures option to be refined for imaging and add a Query for Imaging ServiceRequests.
 +
 
 +
An initial draft of the Imaging Orders mapping to FHIR is in the HL7 Confluence page [https://confluence.hl7.org/display/IMIN/FHIR+ServiceRequest+Mapping+to+Imaging+Order "FHIR ServiceRequest Mapping to Imaging Order"]
  
 
IHE is the owner of SWF. IHE is the appropriate venue for incorporating FHIR with the profile.  IHE has the most expertise on this subject.   
 
IHE is the owner of SWF. IHE is the appropriate venue for incorporating FHIR with the profile.  IHE has the most expertise on this subject.   
Line 31: Line 40:
 
Realizing that this is an extensive and most significant update requested of SWF,  the level of effort should be constrained in the first cycle to resource mapping with no changes to the existing Transactions.  This will ensure backward compatibility and support of mixed environments.   
 
Realizing that this is an extensive and most significant update requested of SWF,  the level of effort should be constrained in the first cycle to resource mapping with no changes to the existing Transactions.  This will ensure backward compatibility and support of mixed environments.   
  
No new Transactions or Actors are proposed.  The profile will add the applicable FHIR resources and the mapping of the existing HL7 v2.5 messaging fields.
+
No new Actors are proposed.  The profile will add the applicable FHIR resources and the mapping of the existing HL7 v2.5 messaging fields.
:'''Proposed FHIR Resources:''' ImagingStudy, ServiceRequest, Procedure, Patient, Visit
+
 
 +
For transactions, propose to leverage existing QEDm transactions with refinements to imaging.

Revision as of 10:08, 2 August 2022

1. Proposed Workitem: SWF on FHIR

  • Proposal Editor: Chris Lindop, Jonathan Whitby
  • Editor: <Name of candidate Lead Editor for the Profile, if known>
  • Domain: Radiology

2. The Problem

FHIR is the emerging clinical information standard that industry has adopted world-wide. Scheduled Workflow is the most widely adopted IHE profile throughout the world. However, it provides no guidance on implementing FHIR. HL7 provides minimal guidance with regards to implementing FHIR for Imaging.

This leaves vendors and users to develop their own implementations for deploying FHIR-based imaging workflows. The result is apparent. Each deployed site will be unique. Vendors will need to adopt and implement a unique configuration for every clinical site's deployed environment.

3. Key Use Case

The key use cases are documented in the IHE Radiology Technical Framework Volume 1 Section 3.3 Scheduled Workflow Process flow. No changes are proposed.

4. Standards and Systems

Relevant Systems

Relevant systems are the same as those systems implementing Scheduled workflow. No change is proposed to the existing relevant systems.

Relevant Standards

  • IHE Scheduled Workflow
  • HL7 FHIR
  • DICOM

5. Discussion

A comprehensive inclusion of FHIR with the existing SWF is a major effort. This level of effort should not inhibit IHE Radiology from starting this project. This project proposal scope needs to limited to a focused component of the overall transformation to a FHIR-based workflow. The initial proposed scope is to focus on the Imaging Orders to FHIR Data Model.

This project needs to leverage and collaborate with existing profiling work that is either in progress or completed by other IHE domains and HL7.

HL7 Orders and Observations currently has an IG in progress for v2 to FHIR mapping which includes a General Order Message. This work can be leveraged and can help O&O with usage of the implementation guide.

The joint DICOM WG20/HL7 Imaging Integration Working group has a workitem to address gaps with the HL7 v2/FHIR mapping relevant to imaging.

IHE PCC has a profile QEDm which utilized FHIR for query of existing Data. While the profile does have an option for procedures, it is missing an option for ServiceRequests. This project could utilize the Procedures option to be refined for imaging and add a Query for Imaging ServiceRequests.

An initial draft of the Imaging Orders mapping to FHIR is in the HL7 Confluence page "FHIR ServiceRequest Mapping to Imaging Order"

IHE is the owner of SWF. IHE is the appropriate venue for incorporating FHIR with the profile. IHE has the most expertise on this subject.

Realizing that this is an extensive and most significant update requested of SWF, the level of effort should be constrained in the first cycle to resource mapping with no changes to the existing Transactions. This will ensure backward compatibility and support of mixed environments.

No new Actors are proposed. The profile will add the applicable FHIR resources and the mapping of the existing HL7 v2.5 messaging fields.

For transactions, propose to leverage existing QEDm transactions with refinements to imaging.