valueset-event-status doesn't contain unknown or other

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Modeling & Methodology
    • STU
    • Event Pattern
    • Hide

      Will add "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.

      We will not add "other" as the expectation is that the state machines are comprehensive.

      Show
      Will add "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. We will not add "other" as the expectation is that the state machines are comprehensive.
    • Jose Costa Teixeira/Hans Buitendijk: 9-0-0
    • Enhancement
    • Compatible, substantive
    • DSTU2

      Event.status is a "code" with minOccurs = 1 yet the valueset-event-status doesn't contain unknown or other.

      Although Event is only a pattern, it seems like we should either explain why it is intentionally inconsistent with the QA guideline or else note that as "real" resources are created, the "real" resource should consider whether to change the minOccurs, add other/unknown, etc.

      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

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

              Created:
              Updated:
              Resolved: