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

Difference between revisions of "201601 DiagnosticOrderandResults"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template for FHIR Connectathon Track Proposals}}")
 
Line 3: Line 3:
 
__NOTOC__
 
__NOTOC__
 
=Track Name=
 
=Track Name=
 +
Laboratory Order and Result
  
 
==Submitting WG/Project/Implementer Group==
 
==Submitting WG/Project/Implementer Group==
 
<!-- Who is asking for this track? -->
 
<!-- Who is asking for this track? -->
 +
Orders and Observations Working Group
 +
 +
todo:  See if any implementors interested
  
 
==Justification==
 
==Justification==
 
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. -->
 
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. -->
 +
'''Implementer need:'''
 +
 +
'''Impact on ballot:'''
 +
 +
'''FMM readiness of the resources:'''
 +
 +
*Diagnostic Order, Action (nee Order) and ActionResponse (nee OrderResponse) are FMM 1 and FMM 0 respectively - see above for discussion on Impact on ballot for these resources.  These resource have not been the topic of any Connectathons to date and need to be exposed to testing to help understand the issues and potential solution for request and workflow resources.
 +
 
 +
*DiagnosticReport and Observation are FMM3 and would benefit from being the focus of Connectathos to help move them forward to FMM4 as well as identify issues surrounding nested grouping of observation for cases such as culture and sensitivies.
 +
 +
*Specimen resource is FMM1 and has not been supported in any connectathon.  This is needed to uncover issues with the resource and help move it to FMM2
 +
 +
  
 
==Proposed Track Lead==
 
==Proposed Track Lead==

Revision as of 18:53, 19 November 2015


Track Name

Laboratory Order and Result

Submitting WG/Project/Implementer Group

Orders and Observations Working Group

todo: See if any implementors interested

Justification

Implementer need:

Impact on ballot:

FMM readiness of the resources:

  • Diagnostic Order, Action (nee Order) and ActionResponse (nee OrderResponse) are FMM 1 and FMM 0 respectively - see above for discussion on Impact on ballot for these resources. These resource have not been the topic of any Connectathons to date and need to be exposed to testing to help understand the issues and potential solution for request and workflow resources.
  • DiagnosticReport and Observation are FMM3 and would benefit from being the focus of Connectathos to help move them forward to FMM4 as well as identify issues surrounding nested grouping of observation for cases such as culture and sensitivies.
  • Specimen resource is FMM1 and has not been supported in any connectathon. This is needed to uncover issues with the resource and help move it to FMM2


Proposed Track Lead

Expected participants

Roles

Role 1 Name

Scenarios

Scenario Step 1 Name

Action:
Precondition:
Success Criteria:
Bonus point:


TestScript(s)