|
|
| (9 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| | | | |
| − | [[Category:201601_FHIR_Connectathon_Track_Proposals|Jan 2016 Proposals]]
| |
| − | __NOTOC__
| |
| − | =Track Name=
| |
| − | Laboratory Order and Result
| |
| − |
| |
| − | ==Submitting WG/Project/Implementer Group==
| |
| − | <!-- Who is asking for this track? -->
| |
| − | Orders and Observations Working Group
| |
| − |
| |
| − | todo: See if any implementors interested
| |
| − |
| |
| − | ==Justification==
| |
| − | <!--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:'''
| |
| − |
| |
| − | todo - clarify grouping of observations such as components vs related and diagnostic reports.
| |
| − |
| |
| − | '''Impact on ballot:'''
| |
| − |
| |
| − | The OO workflow resourses DiagnosticOrder, ActionRequest, ActionResponse are the main focus of DSTU 2.1 and the 2106 connectathon. For DiagnosticReport, Observation, and Speicimen, any discovered issues as a result of the connectathon would be balloted as part of DSTU 3.0
| |
| − |
| |
| − | '''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 thi immature resource and help move it to FMM2
| |
| − |
| |
| − | ==Proposed Track Lead==
| |
| − | <!-- Name, email and Skype id of individual who will coordinate the track at the connectathon -->
| |
| − |
| |
| − | Eric M Haas
| |
| − |
| |
| − | [[mailto:ehaas@healthedatainc.com]]
| |
| − |
| |
| − | Skype: haas.eric1
| |
| − |
| |
| − | others?
| |
| − |
| |
| − | ==Expected participants==
| |
| − | <!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
| |
| − |
| |
| − | ==Roles==
| |
| − | <!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
| |
| − | ===Role 1 Name===
| |
| − | <!-- Provide a description of the capabilities this role will have within the connectathon -->
| |
| − |
| |
| − | ==Scenarios==
| |
| − | <!-- What will be the actions performed by participants? -->
| |
| − |
| |
| − | ===Scenario Step 1 Name===
| |
| − | :Action: <!--Who does what? (Use the role names listed above when referring to the participants -->
| |
| − | :Precondition: <!-- What setup is required prior to executing this step? -->
| |
| − | :Success Criteria: <!-- How will the participants know if the test was successful? -->
| |
| − | :Bonus point: <!-- Any additional complexity to make the scenario more challenging -->
| |
| − |
| |
| − | <!-- Provide a description of each task -->
| |
| − |
| |
| − | ==TestScript(s)==
| |
| − | <!-- Optional (for initial proposal): Provide links to the TestScript instance(s) that define the behavior to be tested.
| |
| − | These should be committed to SVN under trunk/connectathons/[connectathon]
| |
| − | -->
| |
