Personal Health Device Observation Upload

From IHE Wiki
Revision as of 06:37, 15 April 2020 by Breinhold (talk | contribs) (Completed Benefits section)
Jump to navigation Jump to search


To do: put in POU Profile content

Profile Overview Template

This is a template page. CLICK HERE if you're not sure how to use it. DO NOT MODIFY this page unless you are changing the template for all future users.


This template is for the one or two page user-oriented overview of an IHE Profile that is in Final Text, Trial Implementation or perhaps Public Comment. Delete text in italics and replace it with your material. Don't forget to delete the double quotes too.

Your page name should simply be Full Profile Name with spaces, with capitals, without the acronym. e.g. Scheduled Workflow. so it provides a title to the page. You can redirect the acronym to the full named page if you like for bonus points.


Personal Health Device Observation Upload moves observations generated by Personal Health Device to FHIR servers on enterprise health systems.


   1 Summary
   2 Benefits
   3 Details
   4 Systems Affected
   5 Specification
   6 See Also


Summary

Health care is increasingly being delivered outside of a clinical setting. Personal Health devices are often used in non clinical settings. This profile prescribes a framework for moving the health information generated by personal health devices into the enterprise in an interoperable manner. The profile addresses concerns associated with representation and translation of personal health device information fostering usability and trust of the personal health device data.

<Insert a simple graphic that, at a glance, visually summarizes what the profile is about. Do not use an actor/transaction diagram here. Show your graphic to someone for 5 seconds (literally) and ask them what it's about. If what they say hits the main points in your summary paragraph, you have succeeded. E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them. .>

<See Help - Tips and Tricks for details on inserting an image/graphic.>


Benefits

The COVID-19 pandemic has underlined the value of being able to provide more care in the home, especially as it relates to disease transmission. Effective care in the home requires medical devices that can collect health data to be in the home. This profile provides the following benefits that support home health monitoring:

  • It provides a framework for the creation of an interoperable ecosystem for simple medical sensors. This, in turn, leads to lower costs for manufacturers, system integrators, and others in the supply chain. The end result being more choice and lower prices for patients.
  • It requires the use of well established mechanisms for representing medical information bringing consistency and clarity to the nature of the data being reported to enterprise health systems.
  • It uses FHIR resources and documents how these resources are delivered to a FHIR server, reducing the domain specific knowledge required to work with health information.
  • It provides a detailed mapping between IEEE and FHIR which helps ensure that data arrives at the enterprise health service without transcription errors, fostering confidence and usage of the data from home monitoring. The willingness of the medical community to use this data enables doctors to see patient vitals over a broader period of time and in the setting of their daily ives.

A simple example of cost reduction that this profile allows is for a company developing a thermometer. The developer can focus simply on the thermometer. There is no need to create an application to read the data. Regulatory processes are simplified as the device follows a well known model, and the device can be deployed for a wide range of monitoring programs as there is no need to integrate it into these programs.


Details

<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>

<If the user might be familiar with the mechanisms used by the profile, you can mention them here. E.g. Evidence Documents is based on DICOM Structured Report (SR) Templates.>

<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short. E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.> 4 Systems Affected

<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>

   PACS systems may store, manage, and/or display Evidence Documents.
   Display systems may query, retrieve and display Evidence Documents.
   Reporting workstations may retrieve, process and include details from Evidence Documents in reports

Actors & Transactions:

<Insert an actor-transaction diagram, and or list of Content Definitions> 5 Specification

Profile Status: Final Text <Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>

Documents:

<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text. If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below. If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>

IHE Radiology Technical Framework:

       Vol. 1 - Section 5 (SWF Profile)
       Vol. 2 - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
       Vol. 3 - Appendix E

Underlying Standards:

<list all the standards on which the profile is based; if possible with links to sources>

       DICOM
       HL7
       ...

6 See Also

<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>


Related Profiles

<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one. Start with the name of the other profile as a link and then explain the relationship.>

   Reporting Workflow [RWF] may use Evidence Documents as inputs to the reporting process.
   Simple Image & Numeric Reports [SINR] may include data copied from Evidence Documents.
   Cross-enterprise Document Sharing for Imaging [XDS-I] can be used to share Evidence Documents between sites over a network.
   Portable Data for Imaging [PDI] can store Evidence Documents on media such as CDs.
   Import Reconciliation Workflow [IRWF] can fix patient ids, etc. of Evidence Documents when importing.


Consumer Information

The Profile FAQ Template answers typical questions about what the Profile does. <Replace the link with a link to the actual FAQ page for the Profile>

The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile. <Replace the link with a link to the actual Purchasing page for the Profile>

Implementer Information

The Profile Implementation Template provides additional information about implementing this Profile in software. <Replace the link with a link to the actual Implementation page for the Profile>

Reference Articles

<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis). Go ahead, Google: IHE <Profile Name> abstract or Google: IHE <Profile Name> and under the "more" select "Scholar". You might be surprised. >