QA 4e: consider adding unknown and other to CarePlan code element value sets

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Patient Care
    • STU
    • CarePlan
    • Hide

      Add unknown to the CarePlan.status value set and the CarePlan.activity.detail.status value set with same usage note as the workflow pattern.

      CarePlan is one of the Request resources in the FHIR Workflow specification. Per gForge 10633, workflow is adding "unknown" to the list of statuses for Event, Request and Definition patterns.

      Will add a usage note that "unknown" is not to be used to convey "other" statuses but should be used when one of the existing statuses applies but the authoring system doesn't know the current state of the resource

      Show
      Add unknown to the CarePlan.status value set and the CarePlan.activity.detail.status value set with same usage note as the workflow pattern. CarePlan is one of the Request resources in the FHIR Workflow specification. Per gForge 10633, workflow is adding "unknown" to the list of statuses for Event, Request and Definition patterns. Will add a usage note that "unknown" is not to be used to convey "other" statuses but should be used when one of the existing statuses applies but the authoring system doesn't know the current state of the resource
    • Stephen/Elaine: 5-0-1
    • Enhancement
    • Compatible, substantive
    • DSTU2

      Per QA 4e: If constraining to the "code" data type, ensure that the set of available codes will be sufficient in all possible business scenarios (including "unknown" and possibly "other" situations), particularly if the element is minOccurs = 1

      http://wiki.hl7.org/index.php?title=DSTU_QA_Guidelines

      CarePlan.status is a "code" and has minOccurs = 1, yet there is not an "unknown" or "other" code available in the value set.

      While we are thinking about this, we should review the other CarePlan "code" elements with minOccurs = 0 as well – CarePlan.relatedPlan.code and CarePlan.activity.detail.status

            Assignee:
            Unassigned
            Reporter:
            Michelle Miller
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: