Profile for CommunicationRequest is incomplete

XMLWordPrintableJSON

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

      We're moving away from using CommunicationRequest at all.  However, the new Task profile will clearly express what elements are required vs. mustSupport vs. ignored

      Show
      We're moving away from using CommunicationRequest at all.  However, the new Task profile will clearly express what elements are required vs. mustSupport vs. ignored
    • Bob Dieterle / Laura Herrman : 13-0-2
    • Correction
    • Non-substantive

      The CommunicationRequest Profile does not indicate all of the Resource fields that MAY, SHOULD, or SHALL be populated and the profile doesn't explain what each is to be used to represent. This profile should include every assumption, for example, what the text element is supposed to say, if/when contained resources may be needed/used, Other key elements that seem to be missing any explanation include: about and reasonCode.

      Profile does not reflect what was done at Connectathons.

            Assignee:
            Unassigned
            Reporter:
            Lisa R. Nelson
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: