Jan 2015 Ballot Comment #54

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Very High
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Patient Care
    • Procedure
      ProcedureRequest (see ServiceRequest) [deprecated]
    • Resources
    • Hide

      Change: Add to all of the event-like resources add a "did not do" and an explanation that includes invariants. ?Any resource that has something that should be done - needs a way to indicate not done. ?

      ACTION: Add a "not done" and "not done reason" to Procedure with invariants.

      Show
      Change: Add to all of the event-like resources add a "did not do" and an explanation that includes invariants. ?Any resource that has something that should be done - needs a way to indicate not done. ? ACTION: Add a "not done" and "not done reason" to Procedure with invariants.
    • Claude/Emma: 11-0-0
    • Enhancement
    • Compatible, substantive
    • DSTU1 [deprecated]

      Comments
      How does one specify using FHIR that a procedure did not occur? Is such expressivity consistent across resources?

      Grahame's Comments
      it can be consistent, if the problem is consistent. I'm not sure that it is consistent though; procedures that didn't occur are typically thought of differently that medication adminsitrations that didn't occur (in my experience, anyway)

      Disposition
      Pending input from submitter

      Disposition Comment
      At present, this would typically be captured as a flag against a CarePlan, ProcedureRequest, Referral or other resource that "requested" the procedure. Is it common for systems to capture that procedures did not occur in the same tables/user interfaces as they capture procedures that occurred?

            Assignee:
            Unassigned
            Reporter:
            Claude Nanjo (Inactive)
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: