Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-30516

Physician Burden relevance

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Highest Highest
    • CDISC Mappings (FHIR)
    • 0.1.0
    • Biomedical Research & Regulation
    • (NA)
    • Hide

      Please STOP submitting the same block comment on all implementation guides - which you obviously haven't actually reviewed, because if you had you would realize that they have no relevance to physician burden.

      This is a mapping IG. It shows how data in one specification maps to another specificaiton. It has zero impact on workflow and, by it's scope, never will.

      Negative balloting every IG without reviewing it with a block comment is NOT the way to achieve any reduction of physician burden. Meaningful review and specific, context-specific comments is. Yes, that's more work, but it' the only useful way to drive change.

      Show
      Please STOP submitting the same block comment on all implementation guides - which you obviously haven't actually reviewed, because if you had you would realize that they have no relevance to physician burden. This is a mapping IG. It shows how data in one specification maps to another specificaiton. It has zero impact on workflow and, by it's scope, never will. Negative balloting every IG without reviewing it with a block comment is NOT the way to achieve any reduction of physician burden. Meaningful review and specific, context-specific comments is. Yes, that's more work, but it' the only useful way to drive change.
    • Rebecca Baker / Mike Hamidi : 23-0-0

    Description

      1) We reviewed the ballot material with an eye to ascertain whether this specification is advantageous, disadvantageous or neutral with regard to clinician burden reduction and patient safety assurance. Have clinician burden and patient safety been considered? Is there any formal documentation of this analysis? Are there specific points of guidance which might be included to show how this specification can be used to enhance front-line clinician practice, reduce burden and ensure patient safety?

      2a) Not clear if/how provenance is captured, represented and persisted (over time) in this specification. Knowing who did what when were and why is essential. Capture points include: i) point of origination (at the source, for newly captured content), ii) point of update (for newly updated content whilst preserving previous content and its provenance).

      Who = subject of care/information (typically the patient)
      Who = participant in action taken, including role (e.g., performer, assistant, observer) and credentials (e.g., MD, RN, PharmD, therapist, MA...)
      Who = author of information captured or updated
      Who = organization
      What = action taken
      When = date/time of action taken
      When = date/time of information capture or update
      Where = physical location of action taken
      Where = physical location of information capture or update
      Where = network address and/or device ID where information captured or updated
      Why = rationale, purpose of action taken

      2b) Provenance elements, if not captured at the point of origination or point of update, are often forever lost beyond that moment.

      2c) Granularity of provenance (e.g., binding authorship to content) may be at the dataset or element level, as appropriate.

      2d) Provenance elements are intrinsic to what the source system or device already “knows” at the point of origination or update and thus should not increase burden by requiring extra input on the part of the entering author (clinician or other end user).

      3) For FHIR IGs, please include reference to Clinical Safety - FHIR Implementer’s Safety Checklist: http://hl7.org/fhir/safety.html

      (Comment 1 - imported by: Lloyd McKenzie)

      Attachments

        Activity

          People

            Unassigned Unassigned
            gdickinson Gary Dickinson
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: