Skip to end of metadata
Go to start of metadata


 Show Changes

Version

2

Modifier

Nathan Botts

Modify Date

Oct 02, 2019 16:23

1a. Project Name

Mobile Health App Data Exchange

1b. Project ID

1551

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

Yes

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Modeling & Methodology

2d. Project Facilitator

Keith Boone

2e. Other Interested Parties (and roles)

US Office of the National Coordinator for Health IT (AllOfUs Health IT standards research sponsor)
US National Institutes of Health, All of Us Research Project
Open mHealth
Audacious Inquiry

3a. Project Scope

The initial scope of this project is to analyze variation in FHIR data exchanged from mobile health apps and devices for personal health information. Because mobile health apps and devices can convey a wide variety of data including hundreds of different kinds of measurements, this project will first look at a limited scope of data, including vital signs, physical activity, sleep and blood sugar.

These data elements are readily accessible in many mobile health apps and devices. Similar data is often used during treatment of disease affecting cardiovascular, cereberovascular, lower respiratory, and endocryne systems. These diseases are five of the top ten leading causes of death in the US (https://www.cdc.gov/nchs/fastats/leading-causes-of-death.htm) and four out of ten in the world (https://ourworldindata.org/causes-of-death). Thus, they are high priority items to address in this project.

Attachments

3b. Project Need

There are multiple pathways to obtain personal health data from mobile apps and devices in FHIR. Some of these pathways are shown in the attached Powerpoint diagram and include:

* Proprietary API to FHIR Conversion (via cloud, mobile platform, or direct to device APIs).
* Proprietary to FHIR Conversion via an Intermediate Format (e.g., Open mHealth)
* Direct output in FHIR from a Device Gateway
* Exchange to EHR w/ Output in FHIR generated from an EHR

Each of these pathways can introduce variation due to the encoding of sematic codes describing the measurement, or variations in the way that units are expressed, or in the precision of data exchanged.

Because of the increasing use of personal health devices to augment care, this is of concern because it can introduce variation in personal health data that may be used for diagnosis, treatment and research.

The goal of this project is to determine the degree of semantic and precision variation in these pathways and determine what steps are needed to address this challenge to enable healthcare providers to use personal health device data for diagnosis, treatment and research.

3e. Objectives/Deliverables and Target Dates

1. Promote a FHIR Connectathon track (see https://confluence.hl7.org/display/FHIR/2019-09+Mobile+Health+Data+Exchange) to compare variations in pathways for getting FHIR Data. September and possibly January WGM.
2. Analyze variation and develop a plan to address sources of variation. Such a plan might include development of functional requirements or an implementation guide, but those details are not yet determined.
3. Implement action plan.

3i. HL7-Managed Project Document Repository URL:

https://confluence.hl7.org/pages/viewpageattachments.action?pageId=61505681

3j. Backwards Compatibility

No

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Aug 02, 2019

7f. FMG Approval Date

Aug 14, 2019

7i. Steering Division Approval Date

Sep 16, 2019

Version

1

Modifier

Anne Wizauer

Modify Date

Sep 17, 2019 00:58

1a. Project Name

Mobile Health App Data Exchange

1b. Project ID

1551

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

Yes

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Modeling & Methodology

2d. Project Facilitator

Keith Boone

2e. Other Interested Parties (and roles)

US Office of the National Coordinator for Health IT (AllOfUs Health IT standards research sponsor)
US National Institutes of Health, All of Us Research Project
Open mHealth
Audacious Inquiry

3a. Project Scope

The initial scope of this project is to analyze variation in FHIR data exchanged from mobile health apps and devices for personal health information. Because mobile health apps and devices can convey a wide variety of data including hundreds of different kinds of measurements, this project will first look at a limited scope of data, including vital signs, physical activity, sleep and blood sugar.

These data elements are readily accessible in many mobile health apps and devices. Similar data is often used during treatment of disease affecting cardiovascular, cereberovascular, lower respiratory, and endocryne systems. These diseases are five of the top ten leading causes of death in the US (https://www.cdc.gov/nchs/fastats/leading-causes-of-death.htm) and four out of ten in the world (https://ourworldindata.org/causes-of-death). Thus, they are high priority items to address in this project.

Attachments

3b. Project Need

There are multiple pathways to obtain personal health data from mobile apps and devices in FHIR. Some of these pathways are shown in the attached Powerpoint diagram and include:

* Proprietary API to FHIR Conversion (via cloud, mobile platform, or direct to device APIs).
* Proprietary to FHIR Conversion via an Intermediate Format (e.g., Open mHealth)
* Direct output in FHIR from a Device Gateway
* Exchange to EHR w/ Output in FHIR generated from an EHR

Each of these pathways can introduce variation due to the encoding of sematic codes describing the measurement, or variations in the way that units are expressed, or in the precision of data exchanged.

Because of the increasing use of personal health devices to augment care, this is of concern because it can introduce variation in personal health data that may be used for diagnosis, treatment and research.

The goal of this project is to determine the degree of semantic and precision variation in these pathways and determine what steps are needed to address this challenge to enable healthcare providers to use personal health device data for diagnosis, treatment and research.

3e. Objectives/Deliverables and Target Dates

1. Promote a FHIR Connectathon track (see https://confluence.hl7.org/display/FHIR/2019-09+Mobile+Health+Data+Exchange) to compare variations in pathways for getting FHIR Data. September and possibly January WGM.
2. Analyze variation and develop a plan to address sources of variation. Such a plan might include development of functional requirements or an implementation guide, but those details are not yet determined.
3. Implement action plan.

3j. Backwards Compatibility

No

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Aug 02, 2019

7f. FMG Approval Date

Aug 14, 2019

7i. Steering Division Approval Date

Sep 16, 2019


1a. Project Name

Mobile Health App Data Exchange

1b. Project ID

1551

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

Yes

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Mobile Health

2d. Project Facilitator

Keith Boone

2e. Other Interested Parties (and roles)

US Office of the National Coordinator for Health IT (AllOfUs Health IT standards research sponsor)
US National Institutes of Health, All of Us Research Project
Open mHealth
Audacious Inquiry

3a. Project Scope

The initial scope of this project is to analyze variation in FHIR data exchanged from mobile health apps and devices for personal health information. Because mobile health apps and devices can convey a wide variety of data including hundreds of different kinds of measurements, this project will first look at a limited scope of data, including vital signs, physical activity, sleep and blood sugar.

These data elements are readily accessible in many mobile health apps and devices. Similar data is often used during treatment of disease affecting cardiovascular, cereberovascular, lower respiratory, and endocryne systems. These diseases are five of the top ten leading causes of death in the US (https://www.cdc.gov/nchs/fastats/leading-causes-of-death.htm) and four out of ten in the world (https://ourworldindata.org/causes-of-death). Thus, they are high priority items to address in this project.

Attachments

3b. Project Need

There are multiple pathways to obtain personal health data from mobile apps and devices in FHIR. Some of these pathways are shown in the attached Powerpoint diagram and include:

* Proprietary API to FHIR Conversion (via cloud, mobile platform, or direct to device APIs).
* Proprietary to FHIR Conversion via an Intermediate Format (e.g., Open mHealth)
* Direct output in FHIR from a Device Gateway
* Exchange to EHR w/ Output in FHIR generated from an EHR

Each of these pathways can introduce variation due to the encoding of sematic codes describing the measurement, or variations in the way that units are expressed, or in the precision of data exchanged.

Because of the increasing use of personal health devices to augment care, this is of concern because it can introduce variation in personal health data that may be used for diagnosis, treatment and research.

The goal of this project is to determine the degree of semantic and precision variation in these pathways and determine what steps are needed to address this challenge to enable healthcare providers to use personal health device data for diagnosis, treatment and research.

3e. Objectives/Deliverables and Target Dates

1. Promote a FHIR Connectathon track (see https://confluence.hl7.org/display/FHIR/2019-09+Mobile+Health+Data+Exchange) to compare variations in pathways for getting FHIR Data. September and possibly January WGM.
2. Analyze variation and develop a plan to address sources of variation. Such a plan might include development of functional requirements or an implementation guide, but those details are not yet determined.
3. Implement action plan.

3i. HL7-Managed Project Document Repository URL:

https://confluence.hl7.org/pages/viewpageattachments.action?pageId=61505681

3j. Backwards Compatibility

No

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Aug 02, 2019

7f. FMG Approval Date

Aug 14, 2019

7i. Steering Division Approval Date

Sep 16, 2019






8 Comments

  1. Keith W. Boone Hi Keith! Initial review of this PSS revealed the following:

    1. I updated the sponsor to be Mobile Health. The PSS had Learning Health Systems listed. My apologies if that was the intention.
    2. Section 3.i: Please add a link to the HL7-managed project document repository
    3. This must be reviewed by the FHIR Management Group. I can add to their next call on 2019-08-14 at 4pm Eastern. It is preferred that a representative of the project attend the call to answer any questions. Please let me know who can attend and I will send a calendar invite.
    4. Following FMG approval, the PSS should be sent to the Infrastructure Steering Division for approval.
  2. Keith W. Boone Rob McClure Greetings! Before I can send this to TSC, it still needs a link to an HL7-managed project document repository in section 3.i. Once we've got that, I can send it for approval. Thank you!

    1. I've added a link to the repository in 3i now.

  3. Anne Wizauer Looks like this is ready for TSC.

    1. I just tried the link you posted, Ulrike and it worked for me. Maybe try again?

      1. thanks - it worked this time (smile)