Skip to content

Commit

Permalink
spec: Clarify expected process around handling of Confirmation Codes
Browse files Browse the repository at this point in the history
Suggested-by: David Spence <[email protected]>
Signed-off-by: Michael Brown <[email protected]>
  • Loading branch information
mcb30 committed Apr 28, 2020
1 parent 7d6f6f4 commit af1dc11
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions spec/cx.lyx
Original file line number Diff line number Diff line change
Expand Up @@ -3914,6 +3914,14 @@ An SMS message sent to the patient containing a link that is recognised
A QR code that is scanned by the patient
\end_layout

\begin_layout Standard
A Confirmation Code is essentially an authorisation token that grants permission
for the holder of the token to create a Notification at an Alert Level
selected by the Publisher.
A Publisher MUST implement processes to ensure that only appropriately
authorised personnel are able to issue and access new Confirmation Codes.
\end_layout

\begin_layout Standard
An Advertiser MUST provide a capability for the user to interactively enter
an arbitrary UTF-8 string as the Confirmation Code, and MAY provide other
Expand Down

0 comments on commit af1dc11

Please sign in to comment.