Make performer consistent across Procedure & ProcedureRequest - 2016-09 core #171

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Patient Care
    • Procedure
      ProcedureRequest (see ServiceRequest) [deprecated]
    • 9.8 & 9.9
    • Hide

      It is uncommon for procedure requests to specify details such as who the anaesthesiologist or scrub nurse or other roles would be - or even who should assist. Instead, if anyone is requested, it's just the primary performer. On the other hand, for performed procedures, capturing everyone who was involved and what they did is typical. If there's a desire to capture the nuances of who should do what on a ProcedureRequest, this can be done with an extension.

      Show
      It is uncommon for procedure requests to specify details such as who the anaesthesiologist or scrub nurse or other roles would be - or even who should assist. Instead, if anyone is requested, it's just the primary performer. On the other hand, for performed procedures, capturing everyone who was involved and what they did is typical. If there's a desire to capture the nuances of who should do what on a ProcedureRequest, this can be done with an extension.
    • Stephen/Elaine: 5-0-1
    • Enhancement

      Comment:

      In Procedure, "performer" is a component containing "actor" and "role"; but in ProcedureRequest, "performer" is a simple reference. Consider making these consistent.

      Summary:

      Make performer consistent across Procedure & ProcedureRequest

            Assignee:
            Unassigned
            Reporter:
            cmoesel
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: