Need clarification on Verify - 2016-09 core #296

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Very High
    • FHIR Core (FHIR)
    • DSTU2
    • Electronic Health Record
    • (profiles)
    • RLE IG
    • John Ritter/Reed Gelzer: 9-0-1
    • Correction
    • Compatible, substantive
    • DSTU2

      Existing Wording: (Lifecycle event 25.) Verify: Content is reviewed and affirmed for accuracy, completeness

      Proposed Wording: Note: It is difficult for this author to propose alternate wording, being unfamiliar with options for adding elements.

      A blind stab: Perhaps Verify (and two others intended for addition as new RLE, Encrypt, Decrypt) can be called out as additional (options, resources, RLEs) determined to add value specifically to FHIR, placing them under the FHIR development "umbrella", managed by EHR WG. Perhaps it might also be possible to subsume each as subtypes of existing RLE, which has apparently received some passing discussion previously. Ex: Verify as a subtype of RLE Attest)

      Comment:

      Narrative explanation for the appearance of additional RLE in this IG is necessary, insofar as the current narrative represents that all 27 come from EHR FM R2. The RLE "Verify" does not currently appear as a specified LE with conformance criteria. (It is, however mentioned in the header narrative for the RI section of the FM). The Implementation Guide will benefit (and, IMO requires) additional narrative text that may exist elsewhere but in the IG appears missing. (The same, IMO, applies to two other new ones, Encrypt and Decrypt. I support the additions but a better foundation is required.

      Summary:

      Need clarification on Verify

            Assignee:
            Unassigned
            Reporter:
            Reed Gelzer
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: