MACM Volume2 Standards Assessment: Difference between revisions
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
==Standards== | |||
{|class="wikitable" | |||
|+ | |||
!Standard | |||
!Reference | |||
!notes | |||
|- | |||
|FHIR DTSU v2 | |||
|http://www.hl7.org/implement/standards/fhir/alert.html | |||
|would likely need to define an extension or something similar | |||
|- | |||
|XMPP | |||
|http://xmpp.org/xmpp-protocols/protocol-namespaces/ | |||
|perhaps not offi | |||
|- | |||
|WEA | |||
|http://en.wikipedia.org/wiki/Wireless_Emergency_Alerts | |||
|US centric | |||
|- | |||
|CAP | |||
|http://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.html | |||
|no transactions specified | |||
|- | |||
|IPAWS | |||
|https://www.fema.gov/integrated-public-alert-warning-system | |||
|no transactions specified | |||
|- | |||
|WS-Notifications | |||
|http://docs.oasis-open.org/wsn/wsn-ws_base_notification-1.3-spec-os.htm | |||
| | |||
|- | |||
|WS-Reliable Messaging | |||
|http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-spec-os-01.pdf | |||
| | |||
|- | |||
|HL7v3 ? | |||
| | |||
| | |||
|- | |||
|Open Mobile Alliance: | |||
RESTful Network API for Notification Channel | |||
|http://technical.openmobilealliance.org/Technical/technical-information/release-program/release-program-copyright-notice?rp=2549&r_type=technical&fp=Technical%2FRelease_Program%2Fdocs%2FNotifChanREST%2FV1_0-20130730-C%2FOMA-TS-REST_NetAPI_NotificationChannel-V1_0-20130730-C.pdf | |||
| | |||
|- | |||
|PCD ACM | |||
|http://wiki.ihe.net/index.php?title=PCD_Technical_Framework | |||
| | |||
|- | |||
|Bespoke Solution for mACM | |||
| | |||
| | |||
|} | |||
==Availability and Maturity of Standard for Use == | ==Availability and Maturity of Standard for Use == | ||
{|class="wikitable" | {|class="wikitable" | ||
Revision as of 21:30, 8 March 2015
Standards
Availability and Maturity of Standard for Use
| Standard | Accessibility of Standard | Market Penetration / Availability of Implementations |
|---|---|---|
| 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 |
| 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 |