This wiki has undergone a migration to Confluence found Here

Difference between revisions of "201709 Patient Reported Observations"

From HL7Wiki
Jump to navigation Jump to search
Line 11: Line 11:
 
<!--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 Orders and Observation Work Group is interested in the readiness of the Observation resources to progress to a normative [http://build.fhir.org/versions.html#maturity Maturity level]. This tract is specifically focused on readiness of Observation to handle Patient reported data - in other words, observations that are reported directly by the patient. In many cases patients are asked to record and report clinical and nutritional data for example using an app on a smart phone. ('gateway'). The goal is to identify any potential issues or Gaps in the Observation resource by stepping through a couple of simple scenarios [[#scenarios|described below]].  For example, we discovered that constraining the timing of event to only dateTimes did not account for patient's oftentimes reporting the events as occurring relative to another event - e.g., "before breakfast".
+
The Orders and Observation Work Group is interested in the readiness of the Observation resources to progress to a normative [http://build.fhir.org/versions.html#maturity Maturity level]. This tract is specifically focused on readiness of Observation to handle Patient reported data - in other words, observations that are reported directly by the patient. In many cases patients are asked to record and report clinical and nutritional data for example using an app on a smart phone. ('gateway'). The goal of this tract is to identify any potential issues and gaps in the Observation resource by stepping through a couple of simple scenarios [[#Scenarios|described below]].  For example, we discovered that constraining the timing of event to only dateTimes did not account for patient's oftentimes reporting the events as occurring relative to another event - e.g., "before breakfast".
  
 
==Proposed Track Lead==
 
==Proposed Track Lead==

Revision as of 23:02, 21 June 2017


Patient Reported Observations

Submitting WG/Project/Implementer Group

Orders and Observations

Justification

The Orders and Observation Work Group is interested in the readiness of the Observation resources to progress to a normative Maturity level. This tract is specifically focused on readiness of Observation to handle Patient reported data - in other words, observations that are reported directly by the patient. In many cases patients are asked to record and report clinical and nutritional data for example using an app on a smart phone. ('gateway'). The goal of this tract is to identify any potential issues and gaps in the Observation resource by stepping through a couple of simple scenarios described below. For example, we discovered that constraining the timing of event to only dateTimes did not account for patient's oftentimes reporting the events as occurring relative to another event - e.g., "before breakfast".

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.

Screen Shot 2017-06-21 at 11.11.09 AM.png

Scenarios

Scenario 1: Diet

Patient reports what they ate via their Iphone using a nutrition or some other application

Scenario 1: Home Blood Glucose Monitoring

Patient reports the measurements from there home glucometer via their Iphone using some application supplied by there healthcare provider

TestScript(s)

Security and Privacy Considerations