MACM Volume2 Standards Assessment: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 45: | Line 45: | ||
|PCD ACM | |PCD ACM | ||
|http://wiki.ihe.net/index.php?title=PCD_Technical_Framework | |http://wiki.ihe.net/index.php?title=PCD_Technical_Framework | ||
| | |||
|- | |||
| IEEE 10101a | |||
|http://standards.ieee.org/develop/project/11073-10101a.html | |||
| | | | ||
|- | |- | ||
| Line 120: | Line 124: | ||
| | | | ||
|However, there may be copyright restrictions if IHE were to include the formal IEEE Descriptions/Definitions or Systematic Names documentation available on the IHE Wiki or ftp sites in an unrestricted manner. You/we would need to contact [the program manager] | |However, there may be copyright restrictions if IHE were to include the formal IEEE Descriptions/Definitions or Systematic Names documentation available on the IHE Wiki or ftp sites in an unrestricted manner. You/we would need to contact [the program manager] | ||
That said, there are alternative methods that you could use. First, anyone who purchases a copy of IEEE Std 11073-10103-2012 standard is granted royalty-free access to the XML files on the IEEE website that contain the Description/Definitions. Also, the same information is available on the NIST RTMMS site (and if it isn’t already there, it should be shortly). This would allow users to look up the Description/Definition and other information, given a REFID or numeric code identifier. | |||
Whether or not the IHE can include the Descriptions/Definitions or Systematic Names in HIMSS/IHE publications is somewhat in a grey zone. For example, NIST has a MoU with the IEEE to make all the IEEE 11073 nomenclature content available on the NIST RTMMS, so anyone can go there to view the material, including the formal definitions, and to a large extent, most of it can be downloaded as well." | |||
| | |||
| | |||
|- | |- | ||
|Bespoke Solution for mACM | |Bespoke Solution for mACM | ||
Revision as of 03:20, 23 March 2015
Standards
Availability and Maturity of Standard for Use
| Standard | Openness of Standard | Market Penetration / Availability of Implementations | Potential for evolution of the standard | |||
|---|---|---|---|---|---|---|
|
|
| ||||
| FHIR DTSU v2 | ||||||
| XMPP | ||||||
| WEA | ||||||
| CAP | ||||||
| IPAWS | ||||||
| WS-Notifications | ||||||
| WS-Reliable Messaging | ||||||
| HL7v3 ? | ||||||
| Open Mobile Alliance:
RESTful Network API for Notification Channel |
||||||
| PCD ACM | public | Alert Reporters and Alert Managers | ||||
| IEEE 10101a | http://standards.ieee.org/develop/project/11073-10101a.html | Response on use: "Regarding the use of the Reference ID and numeric code identifiers, there is no restriction regarding your inclusion of that information in any documentation published by the IHE or, for that matter, by vendors in their documentation. | However, there may be copyright restrictions if IHE were to include the formal IEEE Descriptions/Definitions or Systematic Names documentation available on the IHE Wiki or ftp sites in an unrestricted manner. You/we would need to contact [the program manager]
That said, there are alternative methods that you could use. First, anyone who purchases a copy of IEEE Std 11073-10103-2012 standard is granted royalty-free access to the XML files on the IEEE website that contain the Description/Definitions. Also, the same information is available on the NIST RTMMS site (and if it isn’t already there, it should be shortly). This would allow users to look up the Description/Definition and other information, given a REFID or numeric code identifier. Whether or not the IHE can include the Descriptions/Definitions or Systematic Names in HIMSS/IHE publications is somewhat in a grey zone. For example, NIST has a MoU with the IEEE to make all the IEEE 11073 nomenclature content available on the NIST RTMMS, so anyone can go there to view the material, including the formal definitions, and to a large extent, most of it can be downloaded as well." |
|||
| Bespoke Solution for mACM | would be public | none |
mACM Specific Data Fields
| Standard | timestamp | subject of care identifier | recipient identifier | alert status | alert priority | alert type | geo-location of status/response | status/response for alert | content type of alert |
|---|---|---|---|---|---|---|---|---|---|
| FHIR DTSU v2 | no | yes (required) | no | maybe: status, but restricted code set | no | category | no | no | plain text string in note |
| XMPP | |||||||||
| WEA | |||||||||
| CAP | |||||||||
| IPAWS | |||||||||
| WS-Notifications | |||||||||
| WS-Reliable Messaging | |||||||||
| HL7v3 ? | |||||||||
| Open Mobile Alliance:
RESTful Network API for Notification Channel |
|||||||||
| PCD ACM | |||||||||
| Bespoke Solution |
mACM Specific Transactions
| Standard | Mobile Report Alert | Query for Alert Status |
|---|---|---|
| FHIR DTSU v2 | yes: PUT | no (can either augment alert resource to include status, or create a new resource) |
| XMPP | ||
| WEA | ||
| CAP | ||
| IPAWS | ||
| WS-Notifications | ||
| WS-Reliable Messaging | ||
| HL7v3 ? | ||
| Open Mobile Alliance:
RESTful Network API for Notification Channel |
||
| PCD ACM | no: Report Alert transaction is not mobile friendly. HL7v2 message is semantically invalid when a subject of care is identified in alert | no: there was a related PCD-05 that was excised from the TF, but it was initiated by AM not AR |
| Bespoke Solution |