MACM Volume2 Standards Assessment: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Litlfred (talk | contribs)
No edit summary
Litlfred (talk | contribs)
Line 213: Line 213:
|-
|-
|PCD ACM
|PCD ACM
|
|no: Report Alert transaction is not mobile friendly
|
|no: there was a related PCD-05 that was excised from the TF, but it was initiated by AM not AR
|-
|-
|Bespoke Solution
|Bespoke Solution
|
|
|}
|}

Revision as of 12:03, 8 March 2015

Availability and Maturity of Standard for Use

Standard Criteria A Criteria B
FHIR DTSU v2
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 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
Standard Criteria A Criteria B
FHIR DTSU v2
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 no: there was a related PCD-05 that was excised from the TF, but it was initiated by AM not AR
Bespoke Solution