Difference between revisions of "2.16.840.1.113883.10.22.2.4"
(Automatic ADBot page (b2c672bbfe72ebf34d65a361e629f35c1818988f)) |
(Automatic ADBot page (b2c672bbfe72ebf34d65a361e629f35c1818988f)) |
||
(3 intermediate revisions by the same user not shown) | |||
Line 5: | Line 5: | ||
=Template ''IPSCDAlegalAuthenticator''= | =Template ''IPSCDAlegalAuthenticator''= | ||
− | <p>The legalAuthenticator identifies the single person legally responsible for the document and must be present if the document has been legally authenticated. A clinical document that does not contain this element has not been legally authenticated.The act of legal authentication requires a certain privilege be granted to the legal authenticator depending upon local policy. Based on local practice, clinical documents may be released before legal authentication.All clinical documents have the potential for legal authentication, given the appropriate credentials.Local policies MAY choose to delegate the function of legal authentication to a device or system that generates the clinical document. In these cases, the legal authenticator is a person accepting responsibility for the document, not the generating device or system.Note that the legal authenticator, if present, must be a person.</p> | + | <p> |
+ | The legalAuthenticator identifies the single person legally responsible for the document and must be present if the document has been legally authenticated. A clinical document that does not contain this element has not been legally authenticated. | ||
+ | The act of legal authentication requires a certain privilege be granted to the legal authenticator depending upon local policy. Based on local practice, clinical documents may be released before legal authentication. | ||
+ | All clinical documents have the potential for legal authentication, given the appropriate credentials. | ||
+ | Local policies MAY choose to delegate the function of legal authentication to a device or system that generates the clinical document. In these cases, the legal authenticator is a person accepting responsibility for the document, not the generating device or system. | ||
+ | Note that the legal authenticator, if present, must be a person. | ||
+ | </p> | ||
==Actual version== | ==Actual version== | ||
{{:{{BASEPAGENAME}}/dynamic}} | {{:{{BASEPAGENAME}}/dynamic}} | ||
Line 11: | Line 17: | ||
==List of all versions of this template== | ==List of all versions of this template== | ||
*[[2.16.840.1.113883.10.22.2.4/static-2017-04-11T000000|2017-04-11 (Under pre-publication review)]] | *[[2.16.840.1.113883.10.22.2.4/static-2017-04-11T000000|2017-04-11 (Under pre-publication review)]] | ||
− | <!-- | + | <!--33ea79317bbd2717c674678e7d0adfb75dc5e50d--> |
Latest revision as of 05:11, 13 June 2024
Comments on this page |
---|
Template IPSCDAlegalAuthenticator
The legalAuthenticator identifies the single person legally responsible for the document and must be present if the document has been legally authenticated. A clinical document that does not contain this element has not been legally authenticated. The act of legal authentication requires a certain privilege be granted to the legal authenticator depending upon local policy. Based on local practice, clinical documents may be released before legal authentication. All clinical documents have the potential for legal authentication, given the appropriate credentials. Local policies MAY choose to delegate the function of legal authentication to a device or system that generates the clinical document. In these cases, the legal authenticator is a person accepting responsibility for the document, not the generating device or system. Note that the legal authenticator, if present, must be a person.
Actual version