CDA R3 legalAuthenticator
See CDA R3 Formal Proposals for instructions on using this form. Failure to adhere to these instructions may result in delays. Editing of formal proposals is restricted to the submitter and SDTC co-chairs. Other changes will be undone. Comments can be captured in the associated discussion page.
(An announcement of this proposal must be submitted to the Structured Documents list to be formally submitted.)
|Submitted by: Rick Geimer||Revision date: December 11, 2009|
|Submitted date: December 11, 2009||Change request ID: <<Change Request ID>>|
CDA R2 does not require an assignedPerson element inside legalAuthenticator, leading some to believe that is is ok for the legalAuthenticator to be an organization.
- Require assignedPerson to be present, and make it explicitly clear in the text that the legalAuthenticator must be a person.
Organizations cannot legally sign a document. A document must always be signed by a person, even if this is just an officer at an organization (for example, pay checks).
Recommended Action Items
March 23 SDWG teleconference: will clarify in narrative that it must be person. role.ID (that identifies the person in the role of ASSIGNED) has and will continue to be required. Not necessary to require the playing entity. Persuasive with mod (in that we need to clarify narrative). Opposed: 0; Abstain: 0; In favor: 6.