This wiki has undergone a migration to Confluence found Here
Difference between revisions of "201601 DiagnosticOrderandResults"
Jump to navigation
Jump to search
| Line 19: | Line 19: | ||
'''FMM readiness of the resources:''' | '''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. | + | *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. Specifically DiagnosticOrder contains a recursive structure of event which is unlike any other request resource in FHIR. One question is whether this can be handled better as a separate requests. |
*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. | *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 | *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 19:26, 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. Specifically DiagnosticOrder contains a recursive structure of event which is unlike any other request resource in FHIR. One question is whether this can be handled better as a separate requests.
- 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:
