Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-33481

.meta.security is Must Support without an indication of how to use them

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • Cancer Pathology Data Sharing (FHIR)
    • 0.1.0 [deprecated]
    • Orders & Observations
    • US Pathology MessageHeader
    • Hide

      This is a mistake; .meta.security is not intended to be flagged as MS. There is nothing special about the .meta element for this profile beyond general FHIR security considerations.

      Will remove .meta.security MustSupport flag.

      Show
      This is a mistake; .meta.security is not intended to be flagged as MS. There is nothing special about the .meta element for this profile beyond general FHIR security considerations. Will remove .meta.security MustSupport flag.
    • Lorraine Constable/Ruby Nash: 11-3-0
    • Clarification
    • Compatible, substantive

    Description

      In the MessageHeader profile, .meta.security is labelled as Must Support but there doesn't seem to be any explanation of how to use this element. Is it sufficient for the sender just to populate the element from the usual value set? Is there something unique about this workflow which requires security labelling? Please clarify the use case specific security requirements.

      Attachments

        Activity

          People

            Unassigned Unassigned
            craig.newman Craig Newman
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: