This wiki has undergone a migration to Confluence found Here

Difference between revisions of "201709 PatientReportedObservations"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template for FHIR Connectathon Track Proposals}}")
 
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
  
[[Category:201709_FHIR_Connectathon_Track_Proposals|Sept 2017 Proposals]]
+
 
 
__NOTOC__
 
__NOTOC__
=Track Name=
+
=Patient Reported Observations=
  
 
==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
  
 
==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. -->
 +
Readiness of Observation to handle Patient reported data.
  
 
==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 -->
See [[Connectathon_Track_Lead_Responsibilities]]
+
[mailto:ehaas@healthedatainc.com Eric Haas]
  
 
==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 -->
 +
* [http://www.openmhealth.org/ Open mHealth]
 +
* Epic
 +
* (Soliciting participation on Zulip)
  
 
==Roles==
 
==Roles==
Line 22: Line 27:
 
===Role 1 Name===
 
===Role 1 Name===
 
<!-- 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 -->
 +
 +
<!--
 +
User
 +
App
 +
Server
 +
-->
  
 
==Scenarios==
 
==Scenarios==
Line 27: Line 38:
  
 
===Scenario Step 1 Name===
 
===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 -->
+
(TODO) Create a few scenarios:
 +
 
 +
* Patient reported history (e.g., dietary data )
 +
* Patient reported measurements ( i.e., typing in a blood glucose reading )
 +
* Other ?
  
 
==TestScript(s)==
 
==TestScript(s)==

Latest revision as of 21:03, 14 June 2017


Patient Reported Observations

Submitting WG/Project/Implementer Group

Orders and Observations

Justification

Readiness of Observation to handle Patient reported data.

Proposed Track Lead

Eric Haas

Expected participants

Roles

Please include information here regarding how much advance preparation will be required if creating a client and/or server.

Role 1 Name

Scenarios

Scenario Step 1 Name

(TODO) Create a few scenarios:

  • Patient reported history (e.g., dietary data )
  • Patient reported measurements ( i.e., typing in a blood glucose reading )
  • Other ?

TestScript(s)

Security and Privacy Considerations