Add UsageStatus and usageReason to Event Pattern

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • R4
    • FHIR Infrastructure
    • Event Pattern
    • Hide

      This was raised a year ago.  We still don't see any elements in any of the Event resources that reflect this proposed pattern change.  In general, we look to see the same sort of element appearing in at least two, and ideally more, resources before adding something to the pattern.  Also, we don't believe the notion being captured is a 'status' of the usage - but seems more related to compliance.

      Show
      This was raised a year ago.  We still don't see any elements in any of the Event resources that reflect this proposed pattern change.  In general, we look to see the same sort of element appearing in at least two, and ideally more, resources before adding something to the pattern.  Also, we don't believe the notion being captured is a 'status' of the usage - but seems more related to compliance.
    • Jose Costa Teixeira/John Hatem: 5-0-0

      When resolving FHIR-20913 we determined that the .status in a DeviceUseStatement (an Event) should not be mixed with documenting whether the use statement describes a "non-event", e.g., "I am not wearing a hearing aid now".  Rather, this should be described separately, while the DeviceUseStatement is still considered active, entered-in-error or other reasonable statuses.

      We suggest to add to the Event Pattern two new fields, primarily applicable to UseStatements/Usages resources.

      Event.usageStatus 0..1 CodeableConcept, example values: always, sometimes, never, usually 

      EventUseStatement.usageReason 0..* CodeableConcept, example values: forgot, lost, stolen, broken, the dog ate it.

       

      We ask that other UseStatement/Usage resources similarly disambiguate the difference between status and usageStatus.

            Assignee:
            Unassigned
            Reporter:
            Hans Buitendijk
            Hans Buitendijk
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: