Appearance
0.1 Legal Notices
Disclaimer
DirectTrust® Standards are developed by the DirectTrust community for the public good with feedback from a broad spectrum of healthcare constituencies. It is the responsibility of the organizations making use of these standards and related materials to determine if they are fit for the particular purpose in which the standards will be used including validation for clinical and operational use. DirectTrust takes no responsibility or accepts any liability for your use of the DirectTrust Standard.
Licenses and Intellectual Property
This DirectTrust Standard has been developed under the terms of the DirectTrust IP Policy with regard to copyright, trademark, and patent laws. You may exercise the rights in this DirectTrust Standard in accordance with the Creative Commons Attribution 4.0 License and in accordance with the IP Policy.
DirectTrust®, Direct Standard®, and the registered DirectTrust logo are trademarks owned by DirectTrust with all rights reserved. This document is itself licensed under the Creative Commons License which allows the community to share and adapt the documentation as long as the terms of the license including attribution are observed.
Third-party References
Outside specifications or other Intellectual Property provided in the Normative References table and others which may be referenced are owned by the respective parties. License to this DirectTrust Standard grants no rights respective to these other artifacts, specifications or terminologies
Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
An implementation is not compliant if it fails to satisfy one or more of the SHALL or REQUIRED level requirements for the protocols it implements. An implementation that satisfies all the SHALL or REQUIRED level and all the SHOULD level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the SHALL level requirements but not all the SHOULD level requirements for its protocols is said to be "conditionally compliant".
More information
All questions or other communications relating to this DirectTrust Standard and all requests for information on any DirectTrust procedures governing its codes and standards development process, including information on the procedures for requesting formal interpretations, and for proposing revisions to this DirectTrust Standard should be sent to:
DirectTrust
1629 K Street NW Suite 300, Washington DC 20006
www.DirectTrust.org