Suggested Apple (iOS) Google Windows Comments “standardized” equivalent (Android OS) Phone (generic) term for equivalent cMHAFF Message Generally Generally Sometimes Message, or Any computer to refers to used to refer used to Messaging, can computer or messages to messages describe the describe cMHAFF’s computer-to-human within specific from one purpose or overarching term interface, whether via types of apps, device (or content of one for the data visual, aural, haptic, like email, server) to of the packages that are olfactory, taste, or text, IM, another. notification sent by apps. While neural mediums. Facebook… types, e.g., a we consider However, when toast can be notifications and discussing described as a alerts as special interoperability, the short types of messages, focus is on message the specific term that appears to “message” is used messaging. Note that let the user a lot for messages the messages can be know about within apps, but transmitted within transient data. not generally used the same physical when describing computer, but alerts and between different notifications. We in software (e.g., APIs). HL7 also have the HIT-specific legacy of structured “messaging” formats that include healthcare content and sometimes PHI (e.g., HL7 v2 message). Notification Notification – Notification – Notification. Generic term that A device-specific generic term generic term Push has subtypes. message to cover many to cover many notification is communicated to a types of types of the preferred While HIT also has user to inform them notifications. notifications. method, where “notifications” that of device or app notifications may delivered to activities that are are pushed an app, not just to deemed important to from a a human user, let’s the user. Some types Microsoft stick with the of notifications cloud-based common require a response server to the consumer-based
Suggested “standardized” (generic) term for cMHAFF Apple (iOS) equivalent Google (Android OS) equivalent Windows Phone Comments Message Any computer to computer or computer-to-human interface, whether via visual, aural, haptic, olfactory, taste, or neural mediums. However, when discussing interoperability, the focus is on messaging. Note that the messages can be transmitted within the same physical computer, but between different software (e.g., APIs). Generally refers to messages within specific types of apps, like email, text, IM, Facebook… Generally used to refer to messages from one device (or server) to another. Sometimes used to describe the purpose or content of one of the notification types, e.g., a toast can be described as a short message that appears to let the user know about transient data. Message, or Messaging, can describe cMHAFF’s overarching term for the data packages that are sent by apps. While we consider notifications and alerts as special types of messages, the specific term “message” is used a lot for messages within apps, but not generally used when describing alerts and notifications. We in HL7 also have the HIT-specific legacy of structured “messaging” formats that include healthcare content and sometimes PHI (e.g., HL7 v2 message). Notification A device-specific message communicated to a user to inform them of device or app activities that are deemed important to the user. Some types of notifications require a response Notification – generic term to cover many types of notifications. Notification – generic term to cover many types of notifications. Notification. Push notification is the preferred method, where notifications are pushed from a Microsoft cloud-based server to the Generic term that has subtypes. While HIT also has “notifications” that may delivered to an app, not just to a human user, let’s stick with the common consumer-based
HL7_cMHAFF_Informative_Ballot_Draft_Clean_2017-01-30.docx