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

Contract.signer should just be the Signature datatype

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Unresolved
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • STU3
    • Financial Mgmt
    • Contract
    • Enhancement

    Description

      The Contract.signer element should simply be the Signature datatype. As it is modeled today the Contract has Contract.signer.type and Contract.signer.party; which are duplicates of Contract.signer.signature.type, and Contract.signer.signature.who. I suspect these left behind elements are from an earler Signature Datatype. Now that the Signature Datatype is stable, the Contract.signer should just use the Signature datatype alone.

      Contract.signature 0..* Signature

      Attachments

        Activity

          People

            Unassigned Unassigned
            john_moehrke John Moehrke
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: