Материал: part02

Notice and Disclaimer​

The information in this publication was considered technically sound by the consensus of persons engaged in the development and​ approval of the document at the time it was developed. Consensus does not necessarily mean that there is unanimous agreement​ among every person participating in the development of this document.​

NEMA standards and guideline publications, of which the document contained herein is one, are developed through a voluntary​ consensus standards development process. This process brings together volunteers and/or seeks out the views of persons who have​ an interest in the topic covered by this publication. While NEMA administers the process and establishes rules to promote fairness​ in the development of consensus, it does not write the document and it does not independently test, evaluate, or verify the accuracy​ or completeness of any information or the soundness of any judgments contained in its standards and guideline publications.​

NEMA disclaims liability for any personal injury, property, or other damages of any nature whatsoever, whether special, indirect,​ consequential, or compensatory, directly or indirectly resulting from the publication, use of, application, or reliance on this document.​ NEMA disclaims and makes no guaranty or warranty, expressed or implied, as to the accuracy or completeness of any information​ published herein, and disclaims and makes no warranty that the information in this document will fulfill any of your particular purposes​ or needs. NEMA does not undertake to guarantee the performance of any individual manufacturer or seller's products or services by​ virtue of this standard or guide.​

In publishing and making this document available, NEMA is not undertaking to render professional or other services for or on behalf​ of any person or entity, nor is NEMA undertaking to perform any duty owed by any person or entity to someone else. Anyone using​ this document should rely on his or her own independent judgment or, as appropriate, seek the advice of a competent professional​ in determining the exercise of reasonable care in any given circumstances. Information and other standards on the topic covered by​ thispublicationmaybeavailablefromothersources,whichtheusermaywishtoconsultforadditionalviewsorinformationnotcovered​ by this publication.​

NEMA has no power, nor does it undertake to police or enforce compliance with the contents of this document. NEMA does not cer-​ tify, test, or inspect products, designs, or installations for safety or health purposes. Any certification or other statement of compliance​ with any health or safety-related information in this document shall not be attributable to NEMA and is solely the responsibility of the​ certifier or maker of the statement.​

- Standard -​

- Standard -​

Foreword​

This DICOM Standard was developed according to the procedures of the DICOM Standards Committee.​

The DICOM Standard is structured as a multi-part document using the guidelines established in [ISO/IEC Directives, Part 2].​

DICOM® is the registered trademark of the National Electrical Manufacturers Association for its standards publications relating to di-​ gital communications of medical information, all rights reserved.​

HL7® and CDA® are the registered trademarks of Health Level Seven International, all rights reserved.​

SNOMED®, SNOMED Clinical Terms®, SNOMED CT® are the registered trademarks of the International Health Terminology​ Standards Development Organisation (IHTSDO), all rights reserved.​

LOINC® is the registered trademark of Regenstrief Institute, Inc, all rights reserved.​

- Standard -​

- Standard -​

1 Scope and Field of Application​

Conformance Statements are critical to interoperability because they provide important information for implementers and system in-​ tegrators in order to determine whether or not applications do interoperate. In addition, when issues occur, they provide a source of​ information in order to potentially resolve any problems. Lastly, it is important to provide potential implementers with a consistent​ template for generating these documents.​

PS3.2 defines principles that implementations claiming conformance to the Standard shall follow. PS3.2 specifies:​

•​the minimum general conformance requirements that must be met by any implementation claiming conformance to the DICOM​ Standard. Additional conformance requirements for particular features, Service Classes, Information Objects, and communications​ protocols may be found in the conformance sections of other Parts of the DICOM Standard;​

•​the purpose and structure of a Conformance Statement. PS3.2 provides a framework by which conformance information can be​ placed into a Conformance Statement as dictated by the conformance sections of other Parts of the DICOM Standard.​

The DICOM Standard does not specify:​

•​testing or validation procedures to assess an implementation's conformance to the Standard;​

•​testing or validation procedures to assess whether an implementation matches to its Conformance Statement;​

•​what optional features, Service Classes, or Information Objects should be supported for a given type of device.​

- Standard -​