Instrument, apparatus, machine, equipment, implant, software, hardware, or related component or accessory intended to diagnose, treat, cure, mitigate, or prevent disease, or to affect the structure or function of the body.

Data Element
Unique Mobile Health Application Identifier (UMHAI)
Submitted By: Gora Datta / CAL2CAL
Data Element Information
Data Element Description This is a unique identifier that uniquely identifies mobile health application instance as installed on a mobile device.
Related data elements would include Application name, App Builder, version, build number, hosting device, unique identifiers [similar to a Vehicle Identification Number (VIN) used to track and identify individual vehicle]. Unique Mobile Health Application Identifier enables identification of application instance to facilitate recall, maintenance, transparency and traceability.
Rationale for Separate Consideration Proposed data element UMHAI is similar to UDI but has more complexity and additional details that are not available in UDI.
For example: Host Device where App resides, Device Manufacture, OS Build, ability to support multiple users.
It is recognized that App Store may have their own proprietary mechanism for tracking Application installs. UMHAI standards development process will factor-in these existing methods as HL7 Mobile Health Workgroup develops UMHAI standard.
Use Case Description(s)
Use Case Description Consumer use of Mobile Health Apps for Health and Fitness Tracking
Mobile Health Apps are used on mobile devices to collect and aggregate Patient Generated Health Data (PGHD). Mobile Health Apps can utilize mobile device components (GPS, accelerometers, audio data, visual data) to improve health and support independent living. Integration with Wearable and Smart Devices facilitate remote monitor and track longitudinal data trends to improve patient health or quality of life.

Prescription of Mobile Health Apps for Care Management
Mobile Health Apps and wearable device are moving toward prescribe healthcare solutions. It is becoming increasing important to understand the context and provenance of the mobile health app and devices used to acquire and manage PGHD/PRO/PRE/SDOH and meta data collected by these apps and devices. Also, for safety and privacy it will be beneficial to track Apps and the context of their deployment to facilitate timely updates and possible recall of defect in implementation and deployment.

Patient Safety and Data Privacy
Safety and Data Privacy concerns are factors driving the need for tracking of Unique Mobile Health Application Identifier (UMHAI), many nations are looking to provide safeguards and guidance to Mobile Health App Developers to ensure patient safety and consumer privacy measures comply to local or national standards. How will Mobile Health App assert conformance? If a defect is discovered in App Build affecting safety or privacy how will the user receive update build or disable App usage?

Data Interoperability Compliance
What standards for data interoperability are support for a given application instance by the mobile health app.
Estimate the breadth of applicability of the use case(s) for this data element As of 2019, there are between 400,000 to 500,000[1] health, wellness and fitness apps that run on smartphones, watches, tablets, and other mobile devices, available for download from platform-specific application stores such as the Apple App Store (iOS) and Google Play (Android). This number has rapidly grown from 325,000 [2] apps in 2017.

[1] https://www.fda.gov/medical-devices/digital-health
[2] https://research2guidance.com/hipaa-gdpr-and-connected-health-interview-with-jovan-stevovic-ceo-of-chino-io/
Link to use case project page https://confluence.hl7.org/display/MH/Unique+Mobile+Health+Application+Identifier+%28UMHAI%29+Project
Supporting Attachments Mobile Health App CA & Certification Guidance Concept Note - Gora Datta.pdf
Healthcare Aims
  • Improving patient experience of care (quality and/or satisfaction)
  • Improving the health of populations
  • Reducing the cost of care
  • Improving provider experience of care
Maturity of Use and Technical Specifications for Data Element
Applicable Standard(s) N/A
Additional Specifications N/A
Current Use Not currently captured or accessed with an organization
Extent of exchange N/A
Potential Challenges
Restrictions on Standardization (e.g. proprietary code) This is a green field not many requirement or constraints have been developed at this time.
Restrictions on Use (e.g. licensing, user fees) It is envisaged that there may be registry fee associated with obtaining an identifier.
Privacy and Security Concerns Possible unique privacy and/or security concerns must be addressed here. These concerns may invoke existing privacy and security regulations or restrictions such as HIPAA or 42 CFR Part 2. If a new data class/element is not specifically covered by these, this would need to be stated clearly, not assumed to be not applicable.
Estimate of Overall Burden How hard is it to access and provide the data?
Is it only available in an outside system, such as a lab reporting system?
Does it need to be calculated by the patient or provider, or can it be automatically retrieved or calculated by the system in a production environment?
Does it require significant time on the part of patient or provider to access or record or does it require an interuption in normal workflow to capture?
Does it require significant developer time to implement in EHR systems?
This may be unknown to the submitter and additional information would be needed from industry or may be determined as part of the ONC consideration process.
Other Implementation Challenges This can include concepts such as regulatory impact analysis, development burden/cost, cultural barriers, etc. Again, it may not be fully known to the submitter.
ASTP Evaluation Details
Each submitted Data Element has been evaluated based on the following criteria. The overall Level classification is a composite of the maturity based on these individual criteria. This information can be used to identify areas that require additional work to raise the overall classification level and consideration for inclusion in future versions of USCDI
Criterion #1
Maturity - Current Standards		 Level 0 - Data element is not represented by a terminology standard or SDO-balloted technical specification or implementation guide.
Criterion #2
Maturity - Current Use 		Level 0 - Data element is captured, stored, or accessed in limited settings such as a pilot or proof of concept demonstration.
Criterion #3
Maturity - Current Exchange		 Level 0 - Data element is electronically exchanged in limited environments, such as connectathons or pilots.
Criterion #4
Use Case(s) - Breadth of Applicability		 Level 0 - Use cases apply to a limited number of care settings or specialties, or data element represents a specialization of other, more general data elements.

Comment

Submitted by jiahweing on

Important data element for data safety and privacy

Given the rise of mobile health app development, there is an important need to track if these mobile apps are following proper data safety and privacy measures. Having this data element is important to make sure that the mobile apps can be tracked and followed up longitudinally. 

Submitted by goradatta on

Error correction on of the links + new input

Hello:

This message is regarding the Comment section Data element: Unique Mobile Health Application Identifier (UMHAI) under Medical Device

We have a wrong link for the row: "Link to use case project page".

The correct link is: https://confluence.hl7.org/display/MH/Unique+Mobile+Health+Application+Identifier+%28UMHAI%29+Project

Kindly replace.

 

In addition, wanted to update that HL7 Mobile Health Workgroup is now developing a new standard called "Unique Mobile Health Application Identifier (UMHAI)".

The group meets virtually every Tuesday at 1pm ET. 

Submitted by scarini on

Important data element

As apps are prescribed to manage chronic disease and some are approved as digital therapeutics, the need to track individual builds becomes more and more important. A unique identifier is needed with defined characteristics (including the role of each portion), scope and management.

Log in or register to post comments

FormGuide

Help

1. Optional: Background Text / Cover Letter

The "Optional Background Text / Cover Letter" field provides space for additional context or introductory information related to your comment.

If you wish to provide context, explanation, or an introduction to your comment, enter this information in the field labeled "Optional Background Text / Cover Letter." This is entirely optional and is most useful when submitting multiple related comments or when additional background would help reviewers understand your feedback.

If you are only commenting on a single data class or element, you may leave this field blank.

2. Select the Data Class

To specify which data class your comment addresses:

  1. In the "Data Class" drop-down menu, select the appropriate data class you want to comment on.
  2. If you are providing a general comment that is not specific to a data element, select "General" from the options. Comments with this designation will be displayed on the USCDI landing page.
  3. Note that the Data Class field will automatically populate based on your current location in the platform:
    1. If you are on a data class page, the field will be set to that specific data class
    2. If you are on a data element page, the corresponding data class will be pre-selected
       

3. Select the Data Element

To specify which data element your comment addresses:

  1. In the "Data Element" drop-down menu, select the specific data element you want to comment on.
  2. The drop-down menu will display only the elements available under the data class you selected in the previous step.
  3. You can use the search function within the drop-down to quickly locate a specific data element.
  4. If you are commenting on the data class itself rather than a specific element, you may leave this field blank.

Note: Comments on a specific data element will appear on the respective data element page, while comments on a data class (without a specific element selected) will appear on the landing page for that data class.
 

Data Class and Data Element

Fig 1 The "Data Class" and "Data Element" dropdown menus allow users to specify the exact content they wish to comment on.

4. Optional: Propose New Data Class or Element

If you cannot find the appropriate data class or element for your comment:

  1. Instead of clicking the "Comment On An Existing Data Class Or Element" button, click the adjacent button labeled "Propose a New Data Class or Data Element."
  2. This will redirect you to the ONDEC (ONC New Data Element and Class) Submission System.
  3. In the ONDEC system, follow the provided instructions to submit your proposal for a new data class or element.
  4. Once your proposal is submitted through ONDEC, it will be reviewed separately from the commenting process.
Propose New Data Class or Element

Fig 2 The "Propose a New Data Class or Data Element" button redirects users to the ONDEC Submission System for proposing new data elements not currently available in the system.

5. Complete the Comment Form

Fill out the required fields in the comment form:

Subject: Enter a brief, descriptive title that summarizes your comment. This helps reviewers quickly understand the nature of your feedback.

Comment: In this field, provide the full details of your comment or feedback. Be as clear and specific as possible about your suggestions, concerns, or observations. Include any relevant details that support your position.

6. Optional: Add Additional Comments

If you need to comment on multiple data classes or elements:

  1. After completing your first comment, click the link labeled "Comment on another data element" at the bottom of the form.
  2. A new comment section will appear, allowing you to enter details for your additional comment.
  3. For each additional comment, you must select the appropriate data class and data element from the drop-down menus.
  4. Complete the Subject and Comment fields for your additional comment.
  5. Repeat this process for each additional comment you wish to submit.

Fig 3 The "Comment on another data element" link enables users to create multiple comments addressing different elements within a single submission.

7. Optional: Upload Supporting Files

The platform allows you to upload supporting documentation to enhance your comment:

  • Locate the "File Upload" section at the bottom of the comment form.
  • Click to upload any files (such as PDFs or documents) that provide additional context, evidence, or clarification for your comment.

Important: If you have already entered your comments using the form fields, there is no need to upload duplicate content in PDF format. The file upload feature is intended for supplementary materials only. Please avoid uploading files that contain the same information already provided in your comment text.

Upload Supporting Files

Fig 4 The "File Upload" section permits users to attach supporting documentation that supplements their written comments.

8. Optional: Save and Exit

If you need to pause your work and return to complete your comment later:

  1. Click the "Save and Exit" button at the bottom of the form.
  2. Your comment will be saved as a draft that you can access and complete later.
  3. When you return to the platform, you will see a red triangle with an exclamation mark next to the “Return to saved Comment” button, indicating that you have saved comments in draft status.
  4. Click this button to continue working on your draft.
  5. You will be taken to a review page where you can:
    1. Select "Submit Comment" to officially submit your feedback.
    2. Click "Edit" to return to the comment form and make changes
    3. Select "Discard Draft" to delete the saved draft and start fresh

Fig 5 A red triangle with exclamation mark indicator appears next to the “Return to saved Comment” button when draft comments are saved in the system.

9. Review and Submit

Once you have completed your comment:

  1. Click the "Review and Submit" button at the bottom of the form.
  2. This will take you to a review screen displaying your comment(s) in full.
  3. Review all information for accuracy and completeness.
  4. On this review screen, you have three options: 
    1. Click "Submit Comment" to officially submit your feedback
    2. Click "Edit" to return to the comment form and make changes
    3. Click "Discard Draft" to delete the comment and start fresh
  5. The review screen also includes a "Print" button that allows you to create a printed copy of your comments for your records. 
  6. If you choose to submit, your comment will be recorded in the system and made available for review by the appropriate stakeholders.
Review and Submit

Fig 6 The review screen allows users to verify comment content and make any necessary modifications before final submission.

USCDI Comments

Close

Add a New Comment

Review comment and Submit

Edit
Comment #1
PDF, Doc, Docx
Max Size : 10 MB