Skip to end of metadata
Go to start of metadata




1a. Project Name

FHIR IG for Device Information Client Applications

1b. Project ID

1643

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

No

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

No

1e. Today's Date

1f. Name of standard being reaffirmed

1g. Project Artifact Information

1h. ISO/IEC Standard to Adopt

1i. Does the standard include excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption?

1j. Unit of Measure

2a. Primary/Sponsor WG

Health Care Devices

2d. Project Facilitator

Stefan Schlichting

2e. Other Interested Parties (and roles)

2f. Modeling Facilitator

2g. Publishing Facilitator

2h. Vocabulary Facilitator

2i. Domain Expert Representative

2j. Business Requirements Analyst

2k. Conformance Facilitator

Michael Faughn

2l. Other Facilitators

2m. Implementers

3a. Project Scope

Development of a FHIR Implementation Guide that provides simple answers to the basic questions that client "consumer" applications developers ask.

The project will not only provide guidance to user clients of device-sourced information, but will include FHIR artifacts to streamline the implementation of device informatics integration into applications such as care coordination and decision support.

The project's intent is to limit the basic topics to a Top 10 List (notionally) that most developers need answered, including:
* How can a client app determine what device sensor-based information is available for a given individual?
* How can notifications be sent when devices are attached to / detached from a patient?
* How can the device source for a patient observation be determined?
* When does it matter what kind of device and sensor that is used and how is that identified?

Note that this FHIR IG will endeavor to minimize the distinction of whether a device is a PHD or PoCD, especially since some use scenarios involve applications that have to integrate data from devices that is at one point from a hospital environment and at others from a home or clinic. For example, a cloud-based CDSS that supports care coordination for a mother with preeclampsia before, during and after delivery.

Implementation guidance that is already detailed in either the PHD or PoCD FHIR IGs will be leveraged and referenced in this IG. Note that the PHD FHIR IG also includes a client application focused section that will directly inform this more general device guidance

This IG will be developed in collaboration with the HL7-IHE Gemini Device Interoperability program, and will also involve groups such as HL7 Mobile Health WG and others.

Attachments

3b. Project Need

The HL7 Devices WG "Devices on FHIR" project has advanced two FHIR implementation guides, one for hospital-based Point-of-Care Devices (PoCD) and one for home / mobile based Personal Health Devices. (PHD). These both generally target developers of these devices and the information systems that PROVIDE device-sourced content, with all the granular, sometimes confusing detail that may be necessary. For developers of CONSUMING applications this complexity quickly gets in the way of understanding the basics, and implementing the Devices on FHIR approaches.

3c. Security Risk

Unknown

3d. External Drivers

3e. Objectives/Deliverables and Target Dates

3f. Common Names / Keywords / Aliases:

FHIR, SDC, IEEE 11073, device, health software, SAMD, SOA, web services

3g. Lineage

3h. Project Dependencies

3i. HL7-Managed Project Document Repository URL:

3j. Backwards Compatibility

No

3k. Additional Backwards Compatibility Information (if applicable)

3l. Using Current V3 Data Types?

3l. Reason for not using current V3 data types?

3m. External Vocabularies

3n. List of Vocabularies

3o. Earliest prior release and/or version to which the compatibility applies

4a. Products

FHIR Implementation Guide, Guidance (e.g. Companion Guide, Cookbook, etc), Non Product Project - (Educ. Marketing, Elec. Services, etc.)

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

R4

4c. FHIR Profiles Version

4d. Please define your New Product Definition

4d. Please define your New Product Family

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. White Paper Type

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Externally developed IG is to be (select one)

5a. Specify external organization

HL7-IHE Gemini Project
IHE Devices
IEEE 11073 Standards Committee

5a. Revising Current Standard Info

5b. Project Ballot Type

STU to Normative

5c. Additional Ballot Info

5d. Joint Copyright

No

5e. I understand I must submit a Joint Copyright Letter of Agreement to the TSC in order for the PSS to receive TSC approval.

no

6a. External Project Collaboration

6b. Content Already Developed

6c. Content externally developed?

6d. List Developers of Externally Developed Content

6e. Is this a hosted (externally funded) project?

6f. Stakeholders

Regulatory Agency, Standards Development Organizations (SDOs)

6f. Other Stakeholders

6g. Vendors

EHR, PHR, Health Care IT, Clinical Decision Support Systems

6g. Other Vendors

6h. Providers

6h. Other Providers

6i. Realm

Universal

7d. US Realm Approval Date

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

7c. Co-Sponsor Approval Date

7c. Co-Sponsor 2 Approval Date

7c. Co-Sponsor 3 Approval Date

7c. Co-Sponsor 4 Approval Date

7c. Co-Sponsor 5 Approval Date

7c. Co-Sponsor 6 Approval Date

7c. Co-Sponsor 7 Approval Date

7c. Co-Sponsor 8 Approval Date

7c. Co-Sponsor 9 Approval Date

7c. Co-Sponsor 10 Approval Date

7e. CDA MG Approval Date

7f. FMG Approval Date

7g. V2 MG Approval Date

7h. Architecture Review Board Approval Date

7i. Steering Division Approval Date

7j. TSC Approval Date



 Show Changes

Version

4

Modifier

Todd Cooper

Modify Date

Aug 05, 2020 16:18

1a. Project Name

FHIR IG for Device Information Client Applications

1b. Project ID

1643

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

No

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

No

2a. Primary/Sponsor WG

Health Care Devices

2d. Project Facilitator

Stefan Schlichting

2k. Conformance Facilitator

Michael Faughn

3a. Project Scope

Development of a FHIR Implementation Guide that provides simple answers to the basic questions that client "consumer" applications developers ask.

The project will not only provide guidance to user clients of device-sourced information, but will include FHIR artifacts to streamline the implementation of device informatics integration into applications such as care coordination and decision support.

The project's intent is to limit the basic topics to a Top 10 List (notionally) that most developers need answered, including:
* How can a client app determine what device sensor-based information is available for a given individual?
* How can notifications be sent when devices are attached to / detached from a patient?
* How can the device source for a patient observation be determined?
* When does it matter what kind of device and sensor that is used and how is that identified?

Note that this FHIR IG will endeavor to minimize the distinction of whether a device is a PHD or PoCD, especially since some use scenarios involve applications that have to integrate data from devices that is at one point from a hospital environment and at others from a home or clinic. For example, a cloud-based CDSS that supports care coordination for a mother with preeclampsia before, during and after delivery.

Implementation guidance that is already detailed in either the PHD or PoCD FHIR IGs will be leveraged and referenced in this IG. Note that the PHD FHIR IG also includes a client application focused section that will directly inform this more general device guidance

This IG will be developed in collaboration with the HL7-IHE Gemini Device Interoperability program, and will also involve groups such as HL7 Mobile Health WG and others.

3b. Project Need

The HL7 Devices WG "Devices on FHIR" project has advanced two FHIR implementation guides, one for hospital-based Point-of-Care Devices (PoCD) and one for home / mobile based Personal Health Devices. (PHD). These both generally target developers of these devices and the information systems that PROVIDE device-sourced content, with all the granular, sometimes confusing detail that may be necessary. For developers of CONSUMING applications this complexity quickly gets in the way of understanding the basics, and implementing the Devices on FHIR approaches.

3c. Security Risk

Unknown

3f. Common Names / Keywords / Aliases:

FHIR, SDC, IEEE 11073, device, health software, SAMD, SOA, web services

3j. Backwards Compatibility

No

4a. Products

FHIR Implementation Guide, Guidance (e.g. Companion Guide, Cookbook, etc), Non Product Project - (Educ. Marketing, Elec. Services, etc.)

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

R4

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

HL7-IHE Gemini Project
IHE Devices
IEEE 11073 Standards Committee

5b. Project Ballot Type

STU to Normative

5d. Joint Copyright

No

6f. Stakeholders

Regulatory Agency, Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT, Clinical Decision Support Systems

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

3

Modifier

Chris Courville

Modify Date

Jul 22, 2020 13:41

1a. Project Name

FHIR IG for Device Information Client Applications

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

No

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

No

2a. Primary/Sponsor WG

Health Care Devices

2d. Project Facilitator

Stefan Schlichting

2k. Conformance Facilitator

Michael Faughn

3a. Project Scope

Development of a FHIR Implementation Guide that provides simple answers to the basic questions that client "consumer" applications developers ask.

The project will not only provide guidance to user clients of device-sourced information, but will include FHIR artifacts to streamline the implementation of device informatics integration into applications such as care coordination and decision support.

The project's intent is to limit the basic topics to a Top 10 List (notionally) that most developers need answered, including:
* How can a client app determine what device sensor-based information is available for a given individual?
* How can notifications be sent when devices are attached to / detached from a patient?
* How can the device source for a patient observation be determined?
* When does it matter what kind of device and sensor that is used and how is that identified?

Note that this FHIR IG will endeavor to minimize the distinction of whether a device is a PHD or PoCD, especially since some use scenarios involve applications that have to integrate data from devices that is at one point from a hospital environment and at others from a home or clinic. For example, a cloud-based CDSS that supports care coordination for a mother with preeclampsia before, during and after delivery.

Implementation guidance that is already detailed in either the PHD or PoCD FHIR IGs will be leveraged and referenced in this IG. Note that the PHD FHIR IG also includes a client application focused section that will directly inform this more general device guidance

This IG will be developed in collaboration with the HL7-IHE Gemini Device Interoperability program, and will also involve groups such as HL7 Mobile Health WG and others.

3b. Project Need

The HL7 Devices WG "Devices on FHIR" project has advanced two FHIR implementation guides, one for hospital-based Point-of-Care Devices (PoCD) and one for home / mobile based Personal Health Devices. (PHD). These both generally target developers of these devices and the information systems that PROVIDE device-sourced content, with all the granular, sometimes confusing detail that may be necessary. For developers of CONSUMING applications this complexity quickly gets in the way of understanding the basics, and implementing the Devices on FHIR approaches.

3c. Security Risk

Unknown

3f. Common Names / Keywords / Aliases:

FHIR, SDC, IEEE 11073, device, health software, SAMD, SOA, web services

3j. Backwards Compatibility

No

4a. Products

FHIR Implementation Guide, Guidance (e.g. Companion Guide, Cookbook, etc), Non Product Project - (Educ. Marketing, Elec. Services, etc.)

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

R4

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

HL7-IHE Gemini Project
IHE Devices
IEEE 11073 Standards Committee

5b. Project Ballot Type

STU to Normative

5d. Joint Copyright

No

6f. Stakeholders

Regulatory Agency, Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT, Clinical Decision Support Systems

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

2

Modifier

Chris Courville

Modify Date

Jul 22, 2020 12:40

1a. Project Name

FHIR IG for Device Information Client Applications

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

No

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

No

2a. Primary/Sponsor WG

Health Care Devices

2d. Project Facilitator

Stefan Schlichting

2k. Conformance Facilitator

Michael Faughn

3a. Project Scope

Development of a FHIR Implementation Guide that provides simple answers to the basic questions that client "consumer" applications developers ask.

The project will not only provide guidance to user clients of device-sourced information, but will include FHIR artifacts to streamline the implementation of device informatics integration into applications such as care coordination and decision support.

The project's intent is to limit the basic topics to a Top 10 List (notionally) that most developers need answered, including:
* How can a client app determine what device sensor-based information is available for a given individual?
* How can notifications be sent when devices are attached to / detached from a patient?
* How can the device source for a patient observation be determined?
* When does it matter what kind of device and sensor that is used and how is that identified?

Note that this FHIR IG will endeavor to minimize the distinction of whether a device is a PHD or PoCD, especially since some use scenarios involve applications that have to integrate data from devices that is at one point from a hospital environment and at others from a home or clinic. For example, a cloud-based CDSS that supports care coordination for a mother with preeclampsia before, during and after delivery.

Implementation guidance that is already detailed in either the PHD or PoCD FHIR IGs will be leveraged and referenced in this IG. Note that the PHD FHIR IG also includes a client application focused section that will directly inform this more general device guidance

This IG will be developed in collaboration with the HL7-IHE Gemini Device Interoperability program, and will also involve groups such as HL7 Mobile Health WG and others.

3b. Project Need

The HL7 Devices WG "Devices on FHIR" project has advanced two FHIR implementation guides, one for hospital-based Point-of-Care Devices (PoCD) and one for home / mobile based Personal Health Devices. (PHD). These both generally target developers of these devices and the information systems that PROVIDE device-sourced content, with all the granular, sometimes confusing detail that may be necessary. For developers of CONSUMING applications this complexity quickly gets in the way of understanding the basics, and implementing the Devices on FHIR approaches.

3c. Security Risk

Unknown

3f. Common Names / Keywords / Aliases:

FHIR, SDC, IEEE 11073, device, health software, SAMD, SOA, web services

3j. Backwards Compatibility

No

4a. Products

FHIR Implementation Guide

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

HL7-IHE Gemini Project
IHE Devices
IEEE 11073 Standards Committee

5b. Project Ballot Type

STU to Normative

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

1

Modifier

Chris Courville

Modify Date

Jul 13, 2020 16:03

1a. Project Name

FHIR IG for Device Information Client Applications

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

No

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

No

2a. Primary/Sponsor WG

Health Care Devices

2d. Project Facilitator

Todd Cooper

2k. Conformance Facilitator

Michael Faughn

3a. Project Scope

Development of a FHIR Implementation Guide that provides simple answers to the basic questions that client "consumer" applications developers ask.

The project will not only provide guidance to user clients of device-sourced information, but will include FHIR artifacts to streamline the implementation of device informatics integration into applications such as care coordination and decision support.

The project's intent is to limit the basic topics to a Top 10 List (notionally) that most developers need answered, including:
* How can a client app determine what device sensor-based information is available for a given individual?
* How can notifications be sent when devices are attached to / detached from a patient?
* How can the device source for a patient observation be determined?
* When does it matter what kind of device and sensor that is used and how is that identified?

Note that this FHIR IG will endeavor to minimize the distinction of whether a device is a PHD or PoCD, especially since some use scenarios involve applications that have to integrate data from devices that is at one point from a hospital environment and at others from a home or clinic. For example, a cloud-based CDSS that supports care coordination for a mother with preeclampsia before, during and after delivery.

Implementation guidance that is already detailed in either the PHD or PoCD FHIR IGs will be leveraged and referenced in this IG. Note that the PHD FHIR IG also includes a client application focused section that will directly inform this more general device guidance

This IG will be developed in collaboration with the HL7-IHE Gemini Device Interoperability program, and will also involve groups such as HL7 Mobile Health WG and others.

3b. Project Need

The HL7 Devices WG "Devices on FHIR" project has advanced two FHIR implementation guides, one for hospital-based Point-of-Care Devices (PoCD) and one for home / mobile based Personal Health Devices. (PHD). These both generally target developers of these devices and the information systems that PROVIDE device-sourced content, with all the granular, sometimes confusing detail that may be necessary. For developers of CONSUMING applications this complexity quickly gets in the way of understanding the basics, and implementing the Devices on FHIR approaches.

3c. Security Risk

Unknown

3f. Common Names / Keywords / Aliases:

FHIR, SDC, IEEE 11073, device, health software, SAMD, SOA, web services

3j. Backwards Compatibility

No

4a. Products

FHIR Implementation Guide

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

HL7-IHE Gemini Project
IHE Devices
IEEE 11073 Standards Committee

5b. Project Ballot Type

STU to Normative

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR