Biology Reference
In-Depth Information
14.5.5.1 CAP Profile Considerations for RTBP Project
It was recommended that RTBP adopt the CAP v1.1 code values and defi-
nitions for <alert.msgType> within the CAP envelope. The research team
also suggested that RTBP adopt EDXL Distribution Element v1.0 code val-
ues and definitions for message distribution, mapped appropriately to
the CAP v1.1 values for the EDXL envelope (e.g., “Alert” is equivalent to
“Report”; “Update is equivalent to “Update). It was suggested that it is not
necessary for RTBP to implement the code values “Request,” “Response,”
and “Dispatch” at this time, as these do not apply to the aims or activi-
ties of the biosurveillance program. The research team also identified the
need to establish a procedure and associated rules for issuing various mes-
sage types, with particular guidelines for updates, cancellations, and errors.
There is a need to establish a method for generating and assigning <alert.
reference> when required.
14.5.6 Message attribute { scope }
Each RTBP message must indicate the scope of distribution for the alert (i.e.,
public, restricted, private). PHIN PCA Guide v1.0 specifies that “PHIN alert-
ing systems should always use the value 'Restricted,' meaning 'for dissemi-
nation only to users with a known operational requirement.'” This is not
a required attribute in PHIN-PCA Guide v1.0, but it is acknowledged that
the attribute must be included to produce valid XML messages conforming
to CAP. CAP v1.1 specifies this as a required sub-element within the alert
element as <alert.scope>. CAP v1.1 further specifies that it is to be repre-
sented as one of three designated code values, each with specific meaning
and intent:
“Public”—for general dissemination to unrestricted audiences
“Restricted”—for dissemination only to users with a known opera-
tional requirement
“Private”—for dissemination only to specific addresses
CAP v1.1 requires that sub-element <alert.restriction> be used when the
scope value is “Restricted.” The <alert.restriction> sub-element is therefore
conditional, and contains “text describing the rule for limiting distribution
of the restricted alert message.” CAP v1.1 requires that sub-element <alert.
addresses> be used when the scope value is “Private.” The <alert.addresses>
element is therefore conditional, and contains “the group listing of intended
recipients of the private alert message.” CAP v1.1 specifies certain rules for
this sub-element: “each recipient SHALL be identified by an identifier or
address”; “multiple space-delimited addresses MAY be included. Addresses
including white space MUST be enclosed in double-quotes.”
Search WWH ::




Custom Search