Secure information transport mechanism and HTTPS

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • US Da Vinci HRex (FHIR)
    • Patient Care
    • STU
    • Profile overview [deprecated]
    • Hide

      We will make the language consistent for all interactions.  We will remove the "(https)" from each and will instead include a hyperlink on the text "secure information transport mechanism" that points to the place in the HRex spec that specifically speaks to requirements for secure transport (e.g. what version of TLS, etc.)

      Show
      We will make the language consistent for all interactions.  We will remove the "(https)" from each and will instead include a hyperlink on the text "secure information transport mechanism" that points to the place in the HRex spec that specifically speaks to requirements for secure transport (e.g. what version of TLS, etc.)
    • Richard Esmond / Marti Velezis : 9-0-0
    • Correction
    • Non-substantive

      Secure information transport mechanism and HTTPS

      The actor interaction diagram preconditions for the Push (POST and PUT) and Pull (GET) references HTTPS as a secure information transport mechanism.

      However, the actor interaction diagram preconditions the Push (Unsolicited Communication - with and without Task) and Request (Solicited Communication - with and without Task) do not reference HTTPS as a secure information transport mechanism.

      Request is that HRex is consistent in referencing HTTPS as a secure information transport mechanism for all Interactions.

            Assignee:
            Unassigned
            Reporter:
            Patricia Craig
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: