This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "201801 Apps for Imaging Research"

From HL7Wiki
Jump to navigation Jump to search
Line 28: Line 28:
  
 
==Roles==
 
==Roles==
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
+
The NIH Sync for Science program is described here: [http://syncfor.science Sync for Science].
 +
This program defines communication between a Research App and an EHR that use Smart on FHIR for authorization.
 +
The RSNA and NIH have expanded this to include imaging data with details listed below for each role.
 
<!-- 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 -->
===Role 1 Name===
+
===Research App===
<!-- Provide a description of the capabilities this role will have within the connectathon -->
+
The Research App will be expected to:
 +
* Implement the API defined here to retrieve clinical data: [http://syncfor.science/api-calls]
 +
* Implement the API defined here to retrieve imaging data: TBD
 +
* Use Smart on FHIR ...
 +
 
 +
 
 +
===Smart on FHIR Enabled EHR===
 +
The EHR will be expected to:
 +
* Implement the API defined here to retrieve clinical data: [http://syncfor.science/api-calls]
 +
* Communicate with a Token Introspection Service to allow a broker system (FHIR Broker) to request authorization for image retrieval. Specifications are here:
 +
* (Optional) Directly support the FHIR ImagingStudy resource to support image search
 +
* (Optional) Support DICOM QIDO-RS and WADO-RS queries that will be passed through to a PACS. Detailed specifications are here:
 +
 
 +
===S4S FHIR Broker===
 +
The FHIR Broker is designed to serve as a delegate for an EHR that supports the Sync for Science API but does not implement the imaging extensions.
 +
The FHIR Broker is required to:
 +
* Accept ....
 +
 
 +
 
 +
===S4S Token Introspection Service===
 +
 
 +
 
 +
===PACS===
  
 
==Scenarios==
 
==Scenarios==

Revision as of 22:03, 31 October 2017


Apps for Imaging Research

Submitting WG/Project/Implementer Group

RSNA Image Sharing Project

Justification

Image Share is a network created to enable radiologists to share medical images with patients using personal health record (PHR) accounts. RSNA Image Share gives patients control over their medical images and radiology reports. It lets them maintain their personal imaging history online and securely share information with care providers. This extension is based on the NIH Sync 4 Science program and is designed to allow research apps to search for and retrieve radiology images from clinical systems to support research. The approach uses a combination of FHIR resources and DICOM web services with Smart on FHIR authorization to first search for (FHIR resources) and then retrieve (DICOM web services) radiology images.


Proposed Track Lead

  • Chris Carr (RSNA): ccarr@rsna.org
  • Steve Moore: moores@mir.wustl.edu -- skype id = stephenmmoore

Expected participants

This track would exercise systems in the following roles:

  • Research apps that will use FHIR and DICOM web services to retrieve images
  • EHR systems that will support retrieval of clinical data using the NIH Sync for Science program
  • DICOM web services enabled (QIDO-RS, WADO-RS) Picture, Archive and Communication Systems (PACS) that can supply imaging data.
  • Existing PACS who have not yet implemented DICOM web services

Roles

The NIH Sync for Science program is described here: Sync for Science. This program defines communication between a Research App and an EHR that use Smart on FHIR for authorization. The RSNA and NIH have expanded this to include imaging data with details listed below for each role.

Research App

The Research App will be expected to:

  • Implement the API defined here to retrieve clinical data: [1]
  • Implement the API defined here to retrieve imaging data: TBD
  • Use Smart on FHIR ...


Smart on FHIR Enabled EHR

The EHR will be expected to:

  • Implement the API defined here to retrieve clinical data: [2]
  • Communicate with a Token Introspection Service to allow a broker system (FHIR Broker) to request authorization for image retrieval. Specifications are here:
  • (Optional) Directly support the FHIR ImagingStudy resource to support image search
  • (Optional) Support DICOM QIDO-RS and WADO-RS queries that will be passed through to a PACS. Detailed specifications are here:

S4S FHIR Broker

The FHIR Broker is designed to serve as a delegate for an EHR that supports the Sync for Science API but does not implement the imaging extensions. The FHIR Broker is required to:

  • Accept ....


S4S Token Introspection Service

PACS

Scenarios

Scenario Step 1 Name

Action:
Precondition:
Success Criteria:
Bonus point:


TestScript(s)

Security and Privacy Considerations