Jan 2015 Ballot Comment #279

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Duplicate
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Financial Mgmt
    • Contract
    • 1.15.2.1.513.1
    • Hide

      See 7752 where submission was in person with same submitter

      For Future Consideration

      Show
      See 7752 where submission was in person with same submitter For Future Consideration
    • Andy Stechishin/Kathleen Connor: 2-0-0
    • Enhancement

      Existing Wording
      Contract Signer Type Codes - "The Digital Signature Purposes" These codes are excerpted from ASTM Standard, E1762-95(2013) - Standard Guide for Electronic Authenticaiton of Health Care Information, Copyright by ASTM crypto.stanford.edu/

      Proposed Wording
      The FHIR Contract Resource sponsoring WG, Financial Management, and the FHIR Consent Directive profile on Contract sponsoring WG, CBCC, did not approve this value set. It was provided as a "placeholder" rather than the example of codes that were approved - e.g., grantor, grantee, delegator, delegatee, health insurer and health insurance enrollee. While there are several codes in this value set that could be signer types on a Contract/Consent Directive, it is far from complete and there are a majority of the excerpted codes are inappropriate as signer types. The intent for this value set was not "Digital Signature Purpose" - so this statement should be removed. The intended purpose was to capture the roles played by signers to the Contract/Consent Directive. FM/CBCC are constructing a FHIR signer type value set that will include the ASTM signer types that make sense, e.g., Witness, adding signer type roles from HL7 v.3, and adding additional signer types per business requirements. This value set should be deprecated.

      Grahame's Comments
      better to just fix it

            Assignee:
            Unassigned
            Reporter:
            Kathleen Connor
            Kathleen Connor
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: