Difference between revisions of "201801 Encounter"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template for FHIR Connectathon Track Proposals}}")
 
 
(2 intermediate revisions by the same user not shown)
Line 2: Line 2:
 
[[Category:201801_FHIR_Connectathon_Track_Proposals|Jan 2018 Proposals]]
 
[[Category:201801_FHIR_Connectathon_Track_Proposals|Jan 2018 Proposals]]
 
__NOTOC__
 
__NOTOC__
=Track Name=
+
=Encounter=
  
 
==Submitting WG/Project/Implementer Group==
 
==Submitting WG/Project/Implementer Group==
<!-- Who is asking for this track? -->
+
Patient Administration
  
 
==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. -->
 +
The Encounter resource has been around for quite a while now, and we would like to get some real implementer feedback on the readiness of the resource is to move up the FMM levels.
 +
 +
Of particular interest is the part of and history parts of the Encounter resource, and if some are able to, the linkage from the Appointment resource.
 +
 +
Given the slow uptake or exposure of this resource, we're considering a different style of connectathon here. We're looking for example resources from as far and wide from everyone's systems (even better if you've got the API for us to read them all!)
 +
The result of the connectathon we'd like to report a list of the systems, and the properties that they've used. A kind-of resource property coverage matrix.
 +
 +
Essentially planning to statistically compare
 +
[https://sqlonfhir-stu3.azurewebsites.net/fhir/Patient/example/$extract?expression=descendants().commonpathname()|meta.profile example property usage]
 +
 +
We expect that the real effort for participants in this track will be in getting the spread of different encounter types (that contain the various different properties - e.g. Hospitalization, Inpatient, outpatient, emergency, general practice, community ...)
 +
  
 
==Proposed Track Lead==
 
==Proposed Track Lead==
 
<!-- Name, email and Skype id of individual who will coordinate the track at the connectathon -->
 
<!-- Name, email and Skype id of individual who will coordinate the track at the connectathon -->
 +
Brian Postlethwaite (skype: sgtshultzpos email: brian_pos at hotmail dot com)
 
See [[Connectathon_Track_Lead_Responsibilities]]
 
See [[Connectathon_Track_Lead_Responsibilities]]
  
 
==Expected participants==
 
==Expected participants==
 
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
 
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
 +
* Telstra Health
 +
* Epic (Cooper)
 +
* Cerner
  
 
==Roles==
 
==Roles==
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
 
 
<!-- 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===
+
===Encounter Server===
 
<!-- Provide a description of the capabilities this role will have within the connectathon -->
 
<!-- Provide a description of the capabilities this role will have within the connectathon -->
 +
The Encounter server just needs to be a FHIR server that will respond to either the search or history operation and provide a set of resources
 +
 +
===Statistics Counter===
 +
This will be a client app that simple interrogates the Encounter resources provided, and collates an aggregate of the usage of values in a server
 +
(data generated by Synthia, Crucible or touchstone should be excluded)
 +
Output could be in the form of a TestReport resource
 +
 +
Brian from Telstra Health plans to provide a simple one of these, based on the data format found in the link in the justification section.
  
 
==Scenarios==
 
==Scenarios==
 
<!-- What will be the actions performed by participants? -->
 
<!-- What will be the actions performed by participants? -->
 +
Expose your encounter server (or resources) for testing
  
 
===Scenario Step 1 Name===
 
===Scenario Step 1 Name===
:Action: <!--Who does what?  (Use the role names listed above when referring to the participants -->
+
:Action: Tester uses a Statistics Counter to connect to the FHIR server
:Precondition: <!-- What setup is required prior to executing this step? -->
+
:Precondition: The server must have Encounter resources available
:Success Criteria: <!-- How will the participants know if the test was successful? -->
+
:Success Criteria: The Counter is able to retrieve the resources and report the property usage results
:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->
+
:Bonus point: SMART Authentication was used to access the data
  
 
<!-- Provide a description of each task -->
 
<!-- Provide a description of each task -->
  
 
==TestScript(s)==
 
==TestScript(s)==
<!-- Optional (for initial proposal): Provide links to the TestScript instance(s) that define the behavior to be tested. 
+
There will be no fixed test scripts as this is a quantitative test to verify the resource usage, rather than an implementations conformance
These should be committed to SVN under trunk/connectathons/[connectathon]
 
-->
 
  
 
==Security and Privacy Considerations==
 
==Security and Privacy Considerations==
Line 48: Line 70:
 
I am happy to help: JohnMoehrke@gmail.com -- security co-chair
 
I am happy to help: JohnMoehrke@gmail.com -- security co-chair
 
-->
 
-->
 +
As we would like to get details on data that is as real as possible, a downloadable tool (from GitHub) may be provided to run on your own internal data, and report the results.

Latest revision as of 20:26, 1 November 2017


Encounter

Submitting WG/Project/Implementer Group

Patient Administration

Justification

The Encounter resource has been around for quite a while now, and we would like to get some real implementer feedback on the readiness of the resource is to move up the FMM levels.

Of particular interest is the part of and history parts of the Encounter resource, and if some are able to, the linkage from the Appointment resource.

Given the slow uptake or exposure of this resource, we're considering a different style of connectathon here. We're looking for example resources from as far and wide from everyone's systems (even better if you've got the API for us to read them all!) The result of the connectathon we'd like to report a list of the systems, and the properties that they've used. A kind-of resource property coverage matrix.

Essentially planning to statistically compare example property usage

We expect that the real effort for participants in this track will be in getting the spread of different encounter types (that contain the various different properties - e.g. Hospitalization, Inpatient, outpatient, emergency, general practice, community ...)


Proposed Track Lead

Brian Postlethwaite (skype: sgtshultzpos email: brian_pos at hotmail dot com) See Connectathon_Track_Lead_Responsibilities

Expected participants

  • Telstra Health
  • Epic (Cooper)
  • Cerner

Roles

Encounter Server

The Encounter server just needs to be a FHIR server that will respond to either the search or history operation and provide a set of resources

Statistics Counter

This will be a client app that simple interrogates the Encounter resources provided, and collates an aggregate of the usage of values in a server (data generated by Synthia, Crucible or touchstone should be excluded) Output could be in the form of a TestReport resource

Brian from Telstra Health plans to provide a simple one of these, based on the data format found in the link in the justification section.

Scenarios

Expose your encounter server (or resources) for testing

Scenario Step 1 Name

Action: Tester uses a Statistics Counter to connect to the FHIR server
Precondition: The server must have Encounter resources available
Success Criteria: The Counter is able to retrieve the resources and report the property usage results
Bonus point: SMART Authentication was used to access the data


TestScript(s)

There will be no fixed test scripts as this is a quantitative test to verify the resource usage, rather than an implementations conformance

Security and Privacy Considerations

As we would like to get details on data that is as real as possible, a downloadable tool (from GitHub) may be provided to run on your own internal data, and report the results.