Difference between revisions of "Follow-up of Non-critical Actionable Findings (FUNC) profile completion- Proposal"

From IHE Wiki
Jump to navigation Jump to search
Line 17: Line 17:
 
==2. The Problem==
 
==2. The Problem==
  
'''The IHE TC problem:'''  The possibility exists that the Follow-up of Non-critical Actionable Findings (FUNC) profile was underestimated in 2016 for level of complexity, scope, global differences, as well as technical challenges adopting a new and evolving technology (FHIR).  As a result, the Results Distribution (RD- HL7 v2.5.1 ORU message) was separated from the FUNC profile and went to public comment in June, 2017, but the FUNC profile itself was not quite completed.
+
'''The IHE TC problem:'''  The possibility exists that the Follow-up of Non-critical Actionable Findings (FUNC) profile was underestimated in 2016 for level of complexity, scope, global differences, as well as technical challenges adopting a new and evolving technology (FHIR).  As a result, the Results Distribution (RD- HL7 v2.5.1 ORU message) was separated from the FUNC profile and went to public comment in June, 2017, but, in spite of valiant efforts, the FUNC profile itself was not quite completed.
  
 
'''Current state of FUNC supplement:'''
 
'''Current state of FUNC supplement:'''
<TBD>
+
The scope of the FUNC profile itself was cut almost in half, in terms of # of pages, when the Results Distribution profile was separated it.  As an example, it is currently >100 pages in length with RD removed.  In the short term, however, focus and resources were redirected from FUNC to focus on actual completion of RD.
 +
 
 +
'''FUNC Volume 1:'''
 +
The use cases and background material in Volume 1 are fairly well thought through and have been reviewed several times by the IHE Rad Tech Committee.  These will need to be re-reviewed in light of RD being removed, but should be reduced, not expanded.
 +
'''FUNC Volume 2:'''
 +
The basic architecture has been determined, after quite intense and lengthy discussions, the "Alert Manager" actor is effectively a "FHIR server" also.
 +
The exact FHIR resources continue to evolve for two of the transactions, in part because FHIR is still evolving, in larger part because of the IHE Rad TC learning curve.
  
 
'''The FUNC problem statement:'''
 
'''The FUNC problem statement:'''
  
Also see the original FUNC 2016 Profile Proposal.
+
Taken from Volume 1:
 +
 
 +
In a University of Pennsylvania (HUP) two-year study presented at RSNA 2016 looking at recommendations for follow-up based on abdominal imaging, researchers found that 14% of such exams recommended follow-up imaging for non-critical, actionable findings (Cook2016). A substudy looking at six months of these recommendations noted that there was a 4:1 ratio of in-system to out-of-system physicians ordering abdominal imaging performed at this large academic medical center. Combining these results, it is estimated that, at least for abdominal imaging, approximately 3% of exams contain non-critical, actionable findings that need to be communicated outside a single health system. As such, these patients are automatically at a much higher risk of not having their findings communicated (because the communication may currently rely on faxing printed results or calling ordering physicians’ offices). Using the large, academic center in the study above as an example, this translates to approximately 30,000 at-risk patients every year at HUP.
 +
 
 +
Also see the original FUNC 2016 Profile Proposal. [[Critical_Finding_Follow-up_and_Communication]]
  
 +
Also see the current FUNC supplement under development: [https://docs.google.com/document/d/1pEQAIWDuD0HPQisBLlzF_FaovG8aWuIKgl163I3kr8E/edit]
  
  
''<Now describe the Value Statement: what is the underlying cost incurred by the problem, what is to be gained by solving it>''
 
  
 
==3. Key Use Case==
 
==3. Key Use Case==
  
''<Describe a short use case scenario from the user perspectiveThe use case should demonstrate the integration/workflow problem.>''
+
This profile focuses alert notifications within affiliated facilities and across enterprisesSpecifically, FUNC addresses ACR Category 3 findings, or "Non-critical actionable finding" communication and feedback.
  
''<Feel free to add a second use case scenario demonstrating how it “should” work.  Try to indicate the people/systems, the tasks they are doing, the information they need, and hopefully where the information should come from.>''
 
  
  
 
==4. Standards and Systems==
 
==4. Standards and Systems==
  
 +
The transaction within the Radiology Department, to set up the alert notification, is an HL7 v2.5.1. order message (ORM).
 +
The transactions to communicate this alert throughout the enterprise are FHIR CommunicationRequest and Communication Resources.
  
 
+
The Alert Report actor does not yet exist, at least en masse, in the real world today  using standards.
''<List existing systems that are/could be involved in the problem/solution.>''
 
 
 
''<If known, list standards which might be relevant to the solution>''
 
  
 
==5. Discussion==
 
==5. Discussion==
  
''<Include additional discussion or consider a few details which might be useful for the detailed proposal>''
+
A ballpark estimate is that FUNC Volume 1 development (writing) is 80% complete.
:''<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>''
 
:''<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>''
 
:''<What are some of the risks or open issues to be addressed?>''
 
 
 
  
''<This is the brief proposal. Try to keep it to 1 or at most 2 pages>''
+
A ballpark estimate is that that FUNC Volume 2 development (writing) is 50% complete, specifically the FHIR resource definitions are still being worked upon.
  
  
''<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>'' [[Category:Templates]]
+
[[Category:Templates]]

Revision as of 12:49, 8 August 2017



1. Proposed Workitem: Completion of Follow-up of Non-critical Actionable Findings (FUNC) supplement

  • Proposal Editor: Teri Sippel Schmidt/Vital Images, Steve Langer/ Mayo Clinic, Tessa Cook, MD/ Univ of Pennsylvania
  • Editor: Teri Sippel Schmidt/Vital Images
  • Date: N/A (Wiki keeps history)
  • Version: N/A (Wiki keeps history)
  • Domain: Radiology


2. The Problem

The IHE TC problem: The possibility exists that the Follow-up of Non-critical Actionable Findings (FUNC) profile was underestimated in 2016 for level of complexity, scope, global differences, as well as technical challenges adopting a new and evolving technology (FHIR). As a result, the Results Distribution (RD- HL7 v2.5.1 ORU message) was separated from the FUNC profile and went to public comment in June, 2017, but, in spite of valiant efforts, the FUNC profile itself was not quite completed.

Current state of FUNC supplement: The scope of the FUNC profile itself was cut almost in half, in terms of # of pages, when the Results Distribution profile was separated it. As an example, it is currently >100 pages in length with RD removed. In the short term, however, focus and resources were redirected from FUNC to focus on actual completion of RD.

FUNC Volume 1: The use cases and background material in Volume 1 are fairly well thought through and have been reviewed several times by the IHE Rad Tech Committee. These will need to be re-reviewed in light of RD being removed, but should be reduced, not expanded. FUNC Volume 2: The basic architecture has been determined, after quite intense and lengthy discussions, the "Alert Manager" actor is effectively a "FHIR server" also. The exact FHIR resources continue to evolve for two of the transactions, in part because FHIR is still evolving, in larger part because of the IHE Rad TC learning curve.

The FUNC problem statement:

Taken from Volume 1:

In a University of Pennsylvania (HUP) two-year study presented at RSNA 2016 looking at recommendations for follow-up based on abdominal imaging, researchers found that 14% of such exams recommended follow-up imaging for non-critical, actionable findings (Cook2016). A substudy looking at six months of these recommendations noted that there was a 4:1 ratio of in-system to out-of-system physicians ordering abdominal imaging performed at this large academic medical center. Combining these results, it is estimated that, at least for abdominal imaging, approximately 3% of exams contain non-critical, actionable findings that need to be communicated outside a single health system. As such, these patients are automatically at a much higher risk of not having their findings communicated (because the communication may currently rely on faxing printed results or calling ordering physicians’ offices). Using the large, academic center in the study above as an example, this translates to approximately 30,000 at-risk patients every year at HUP.

Also see the original FUNC 2016 Profile Proposal. Critical_Finding_Follow-up_and_Communication

Also see the current FUNC supplement under development: [1]


3. Key Use Case

This profile focuses alert notifications within affiliated facilities and across enterprises. Specifically, FUNC addresses ACR Category 3 findings, or "Non-critical actionable finding" communication and feedback.


4. Standards and Systems

The transaction within the Radiology Department, to set up the alert notification, is an HL7 v2.5.1. order message (ORM). The transactions to communicate this alert throughout the enterprise are FHIR CommunicationRequest and Communication Resources.

The Alert Report actor does not yet exist, at least en masse, in the real world today using standards.

5. Discussion

A ballpark estimate is that FUNC Volume 1 development (writing) is 80% complete.

A ballpark estimate is that that FUNC Volume 2 development (writing) is 50% complete, specifically the FHIR resource definitions are still being worked upon.