PS3.16

Информация, содержащаяся в данной публикации, была признана технически обоснованной по консенсусу лиц, участвовавших в разработке и утверждении документа на момент его разработки. Консенсус не обязательно означает единодушное согласие каждого лица, участвовавшего в разработке настоящего документа.

Стандарты и руководства NEMA, одним из которых является настоящий документ, разрабатываются в рамках процесса добровольной разработки стандартов на основе консенсуса. Этот процесс объединяет добровольцев и/или учитывает мнения лиц, заинтересованных в теме, освещаемой данной публикацией. Хотя NEMA администрирует этот процесс и устанавливает правила для обеспечения справедливости при достижении консенсуса, она не пишет документ и независимо не проверяет, не оценивает и не подтверждает точность или полноту какой-либо информации, а также обоснованность каких-либо суждений, содержащихся в её стандартах и руководствах.

NEMA не несёт ответственности за любой вред здоровью, имуществу или иной ущерб любого характера — специальный, косвенный, случайный или компенсационный, — прямо или косвенно возникший в результате публикации, использования, применения настоящего документа или доверия к нему. NEMA не даёт никаких гарантий, явных или подразумеваемых, в отношении точности или полноты какой-либо информации, опубликованной в настоящем документе, и не гарантирует, что информация в этом документе будет отвечать каким-либо конкретным целям или потребностям. NEMA не берёт на себя обязательств гарантировать эффективность продукции или услуг какого-либо отдельного производителя или продавца в силу настоящего стандарта или руководства.

Публикуя и предоставляя доступ к настоящему документу, NEMA не берёт на себя обязательства оказывать профессиональные или иные услуги от имени или в интересах какого-либо лица или организации, а также не выполняет какие-либо обязанности, которые одно лицо или организация несёт перед другим. Любой пользователь настоящего документа должен полагаться на собственное независимое суждение или, при необходимости, обращаться за консультацией к компетентному специалисту при определении разумной осмотрительности в конкретных обстоятельствах. Информация и другие стандарты по теме, освещаемой данной публикацией, могут быть доступны из иных источников, к которым пользователь может обратиться для получения дополнительных сведений или мнений, не охваченных данной публикацией.

NEMA не обладает полномочиями и не берёт на себя обязательства контролировать или обеспечивать соблюдение положений настоящего документа. NEMA не сертифицирует, не испытывает и не инспектирует продукцию, конструкции или установки на предмет безопасности или охраны здоровья. Любая сертификация или иное заявление о соответствии информации, связанной со здоровьем или безопасностью, содержащейся в настоящем документе, не может быть отнесена к NEMA и является исключительной ответственностью лица, выдавшего сертификат или сделавшего такое заявление.

Предисловие

Настоящий Стандарт DICOM был разработан в соответствии с процедурами Комитета по стандартам DICOM (DICOM Standards Committee).

Стандарт DICOM структурирован как многочастевой документ в соответствии с руководящими принципами, установленными в [ISO/IEC Directives, Part 2].

PS3.1 следует использовать в качестве базового справочного документа для текущих частей настоящего Стандарта.

DICOM® является зарегистрированным товарным знаком National Electrical Manufacturers Association для его публикаций стандартов, относящихся к цифровой передаче медицинской информации, все права защищены.

1 Область и сфера применения

Настоящая часть Стандарта DICOM определяет Ресурс сопоставления содержимого DICOM (DICOM Content Mapping Resource, DCMR), который определяет Шаблоны (Templates) и Контекстные группы (Context Groups), используемые в других частях Стандарта.

2 Нормативные ссылки

Следующие стандарты содержат положения, которые посредством ссылок в настоящем тексте составляют положения настоящего Стандарта. На момент публикации указанные редакции были действующими. Все стандарты подлежат пересмотру, и сторонам соглашений, основанных на настоящем Стандарте, рекомендуется изучить возможности применения самых последних редакций указанных ниже стандартов.

2.1 Общие сведения

[Alderman 1992] Coronary Artery Disease. Alderman EL and Stadius M. 1992. 3. 12. 1189-208. “The angiographic definitions of the bypass angioplasty revascularization investigation”. http://journals.lww.com/coronary-artery/Abstract/1992/12000/The_angiographie_definitions_of_the_Bypass.12.aspx .

[Berry 2012] Berry RB, Brooks R, and Gamaldo CE. 2012. “The AASM Manual for the scoring of sleep and associated events: rules, terminology and technical specifications. Version 2.0.”. http://www.aasmnet.org .

[ASTM E 1762-04] ASTM. . Standard Guide for Electronic Authentication of Health Care Information, ASTM International.

[ASTM E 2084-00] ASTM. . Standard Specification for Authentication of Healthcare Information Using Digital Signatures, ASTM International.

[ASTM F 67] ASTM. . Standard Specification for Unalloyed Titanium, for Surgical Implant Applications.

[ASTM F 75] ASTM. . Standard Specification for Cobalt-28 Chromium-6 Molybdenum Alloy Castings and Casting Alloy for Surgical Implants.

[ASTM F 90] ASTM. . Standard Specification for Wrought Cobalt-20Chromium-15Tungsten-10Nickel Alloy for Surgical Implant Applications.

[ASTM F 136] ASTM. . Standard Specification for Wrought Titanium-6Aluminum-4Vanadium ELI (Extra Low Interstitial) Alloy for Surgical Implant Applications.

[ASTM F 138] ASTM. . Standard Specification for Wrought 18Chromium-14Nickel-2.5Molybdenum Stainless Steel Bar and Wire for Surgical Implants.

[ASTM F 688] ASTM. . Standard Specification for Wrought Cobalt-35Nickel-20Chromium-10Molybdenum Alloy Plate, Sheet, and Foil for Surgical Implants.

[ASTM F 1058] ASTM. . Standard Specification for Wrought 40Cobalt-20Chromium-16Iron-15Nickel-7Molybdenum Alloy Wire, Strip, and Strip Bar for Surgical Implant Applications.

[ASTM F 1295] ASTM. . Standard Specification for Wrought Titanium-6Aluminum-7Niobium Alloy for Surgical Implant Applications.

[AAPM Report 204] American Association of Physicists in Medicine, College Park, Maryland. 2011. Size-Specific Dose Estimates (SSDE) in Pediatric and Adult Body CT Examinations. http://www.aapm.org/pubs/reports/RPT_204.pdf .

[AAPM Report 220] American Association of Physicists in Medicine. September 2014. Report of AAPM Task Group 220 - Use of Water Equivalent Diameter for Calculating Patient Size and Size-Specific Dose Estimates (SSDE) in CT. http://www.aapm.org/pubs/reports/rpt_220.pdf .

[AAPM OR 03] American Association of Physicists in Medicine. 2005. Assessment of Display Performance for Medical Imaging Systems. http://www.aapm.org/pubs/reports/OR_03.pdf .

[ETDRS Report Number 10] ETDRS. . Report Number 10, Grading Diabetic Retinopathy from Stereoscopic Color Fundus Photographs- An Extension of the Modified Airlie House Classification. Ophthalmology, May 1991, vol98 (p786-805), Supplement.

[Feuvret] International Journal of Radiation Oncology, Biology, Physics. Feuvret L, Noël G, Mazeron JJ, and Bey P. 2006. 64. 2. 333-342. “Conformity index: a review”. http://dx.doi.org/10.1016/j.ijrobp.2005.09.028 .

[HL7 v3 CMET] HL7. . Version 3 Standard: Common Message Element Types.

[IBSI Features] >arXiv. Zwanenburg A, Leger S, Vallières M, and Löck S. 17 Sep 2018. arXiv:1612.07003v7. “Image biomarker standardisation initiative - Reference manual”. http://arxiv.org/abs/1612.07003 .

[ICRU Report 50] International Commission on Radiation Units and Measurements. 1993. Prescribing, Recording, and Reporting Photon Beam Therapy.

[ICRU Report 62] International Commission on Radiation Units and Measurements. 1999. Prescribing, recording, and reporting photon beam therapy (supplement to ICRU Report 50).

[IEC 60601-2-1] IEC. . Medical Electrical Equipment - Part 2-1: Particular requirements for the basic safety and essential performance of electron accelerators in the range 1 MeV to 50 MeV.

[IEC 60601-2-44] IEC. . Medical Electrical Equipment - Part 2-44: Particular Requirements for the Safety of X-Ray Equipment for Computed Tomography.

[IEC 60601-2-64] IEC. . Medical Electrical Equipment - Part 2-64: Particular requirements for the basic safety and essential performance of light ion beam medical electrical equipment.

[IEC 61217] IEC. 2011. Ed 2.0. Radiotherapy Equipment - Coordinates, Movements and Scales.

[IEC 62563-1] IEC. 2009. Ed 1.0. Medical Electrical Equipment - Medical image display systems - Part 1: Evaluation methods.

[IEC 62985] IEC. 2019. Methods For Calculating Size Specific Dose Estimates (SSDE) For Computed Tomography.

[IHE RAD TF-1] IHE International. IHE Radiology (RAD) Technical Framework, Volume 1 - Integration Profiles. http://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_TF_Vol1.pdf .

[ISO/IEC Directives, Part 2] ISO/IEC. 2021. 9.0. Rules for the structure and drafting of International Standards. http://www.iso.org/sites/directives/current/part2/index.xhtml .

[ISO 639] ISO. . Codes for the representation of names of languages.

[ISO 639-1] ISO. 2002. Codes for the representation of names of languages — Part 1: Alpha-2 code.

[ISO 639-2] ISO. 1998. Codes for the representation of names of languages — Part 2: Alpha-3 code.

[ISO 639-3] ISO. 2007. Codes for the representation of names of languages — Part 3: Alpha-3 code for comprehensive coverage of languages.

[ISO 3166] ISO. . Codes for the representation of names of countries.

[ISO 3166-1] ISO. . Codes for the representation of names of countries — Part 1: Country codes.

[ISO 5832-1] ISO. . Implants for surgery – Metallic materials — Part 1: Wrought stainless steel.

[ISO 5832-2] ISO. . Implants for surgery – Metallic materials — Part 2: Unalloyed titanium.

[ISO 5832-3] ISO. . Implants for surgery – Metallic materials — Part 3: Wrought titanium 6-aluminium 4-vanadium alloy.

[ISO 5832-4] ISO. . Implants for surgery – Metallic materials — Part 4: Cobalt-chromium-molybdenum casting alloy.

[ISO 5832-5] ISO. . Implants for surgery – Metallic materials — Part 5: Wrought cobalt-chromium-tungsten-nickel alloy.

[ISO 5832-6] ISO. . Implants for surgery – Metallic materials — Part 6: Wrought cobalt-nickel-chromium-molybdenum alloy.

[ISO 5832-7] ISO. . Implants for surgery – Metallic materials — Part 7: Forgeable and cold-formed cobalt-chromium-nickel-molybdenum-iron alloy.

[ISO 5832-11] ISO. . Implants for surgery – Metallic materials — Part 11: Wrought titanium 6-aluminium 7-niobium alloy.

[ISO 5832-14] ISO. . Implants for surgery – Metallic materials — Part 14: Wrought titanium 15-molybdenum 5-zirconium 3-aluminium alloy.

[ISO 8824-1] ISO. 2015. Information Technology - Abstract Syntax 1 (ASN.1): Specification of Basic Notation.

[ISO 9834-1] ISO. 2012. Information technology - Open Systems Interconnection - Procedures for the operation of OSI Registration Authorities: General procedures and top arcs of the ASN.1 Object Identifier tree.

[ISO 15924] ISO. 2004. Codes for the representation of names of scripts.

[JJ1017] Japan Medical Imaging and Radiological Systems Industries Association (JIRA) and Japanese Association of Healthcare Information Systems Industry (JAHIS). October 5, 2005. 3.0. Guidelines for HIS, RIS, PACS - Modality Data Communication on Scheduling, Billing, and Examination Records. http://www.jira-net.or.jp/commission/system/04_information/files/JJ1017VER3_20051005.doc .

[Kenneweg 2019] J Am Acad Dermatol. Kenneweg KA and et al. 2019. 80. 6. 1564–84. “Developing an international standard for the classification of surface anatomic location for use in clinical practice and epidemiologic research”. doi:10.1016/j.jaad.2018.08.035 http://www.jaad.org/article/S0190-9622(18)32489-7/ .

[NEMA XR 25-2019] National Electrical Manufacturers Association, Rosslyn, Virginia. 2019. Computed Tomography Dose Check Standard. http://www.nema.org/Standards/view/Computed-Tomography-Dose-Check .

[RadLex] RSNA, Chicago. 2006. A Lexicon for Uniform Indexing and Retrieval of Radiology Information Resources. http://www.radlex.org/ .

[RadElement] RSNA, Chicago. Common Data Elements (CDEs) for Radiology. http://radelement.org/ .

[RFC 1766] IETF. March 1995. Tags for the Identification of Languages.

[RFC 3066] IETF. January 2001. Tags for the Identification of Languages.

[RFC 3881] IETF. September 2004. Security Audit and Access Accountability Message - XML Data Definitions for Healthcare Applications.

[RFC 3986] IETF. January 2005. Uniform Resource Identifier (URI): Generic Syntax. http://www.rfc-editor.org/info/rfc3986 .

[RFC 4646] IETF. September 2006. Tags for Identifying Languages.

[RFC 4647] IETF. September 2006. Matching of Language Tags.

[RFC 5646] IETF. September 2009. Tags for Identifying Languages.

[J1086_201210] SAE. Oct 2012. Numbering Metals and Alloys. http://www.sae.org/standards/content/j1086_201210/ .

[Scanlon 1999] Journal of the American College of Cardiology. Scanlon PJ and et al. May 1999. 33. 6. 1756-824. “ACC/AHA guidelines for coronary angiography - A report of the American College of Cardiology/American Heart Association Task Force on Practice Guidelines (Committee on Coronary Angiography) developed in collaboration with the Society for Cardiac Angiography and Interventions”. doi:10.1016/S0735-1097(99)00126-6 http://www.sciencedirect.com/science/article/pii/S0735109799001266 .

[Seeck 2017] Clinical Neurophysiology. Seeck M and et al. 2017. 128. 10. 2070-7. “The standardized EEG electrode array of the IFCN”. doi:10.1016/j.clinph.2017.06.254 http://www.sciencedirect.com/science/article/pii/S1388245717304832 .

[SMPTE RP133] Society of Motion Picture and Television Engineers (SMPTE). 1991. Specifications for Medical Diagnostic Imaging Test Pattern for Television Monitors and Hard-copy Recording Cameras.

[Stout et al 2013] Molecular Imaging. Stout D, Berr SS, LeBlanc A, Kalen JD, Osborne D, Price J, Schiffer W, Kuntner C, and Wall J. 2013. 12. 7. 1-15. “Guidance for Methods Descriptions Used in Preclinical Imaging Papers”. http://journals.sagepub.com/doi/pdf/10.2310/7290.2013.00055 .

2.2 BI-RADS® Terminology and Nomenclature

A portion of the terminology used within the Mammography CAD SR SOP Class and the Breast Imaging Report and Relevant Patient Information for Breast Imaging Templates is derived from BI-RADS®, a copyrighted lexicon of breast imaging terminology and nomenclature licensed by DICOM from the American College of Radiology.

[BI-RADS®] American College of Radiology, Reston, Virginia. 1998. 3.0. Breast Imaging Reporting and Data System Atlas. http://www.acr.org/Quality-Safety/Resources/BIRADS .

2.3 MQCM 1999 Terminology and Nomenclature

References to MQCM 1999 are made in the description of the Mammography CAD SR SOP Class. In this MQCM 1999 refers to the Mammography Quality Control Manual 1999, available from the American College of Radiology. This document describes a standardized approach to mammographic acquisition standards, patient positioning, and so on. The DICOM Standard does not require Mammography CAD SR SOP Class implementations to adhere to MQCM 1999.

[MQCM] American College of Radiology, Reston, Virginia. 1999. Mammography Quality Control Manual. http://www.acr.org/Education/Education-Catalog/Products/639 .

2.4 MQSA Terminology and Nomenclature

References to MQSA are made in the description of the Mammography CAD SR SOP Class. In this MQSA refers to the Mammography Quality Standards Act final rules. While MQSA is a federal regulation of the United States government, it provides the only widely published standards for mammographic quality and is incorporated in this document for that reason. The DICOM Standard does not require Mammography CAD SR SOP Class implementations to adhere to MQSA.

[MQSA] U.S. Food and Drug Administration, Silver Spring, Maryland. 2002. Mammography Quality Standards Act Regulations. http://www.fda.gov/Radiation-EmittingProducts/MammographyQualityStandardsActandProgram/Regulations/ucm110906.htm .

2.5 ACR Position Statement

[ACR Position Statement] American College of Radiology, Reston, Virginia. 2001. Quality Control and Improvement, Safety, Infection Control, and Patient Education. http://www.acr.org/Quality-Safety/Radiology-Safety .

2.6 Chest Radiology and CT

References are made in the description of the Chest CAD SR Templates and Context Groups.

[Fraser and Pare] Fraser, Muller, Colman, and Pare. 1999. 4th. I. xvii-xxxi. Diagnosis of Diseases of the Chest. Terms Used in Chest Radiology.

[Fraser and Pare] Fraser, Muller, Colman, and Pare. 1999. 4th. I. xxxiii-xxxvi. Diagnosis of Diseases of the Chest. Terms for CT of the Lungs.

[ACR CT PE] American College of Radiology, Reston, Virginia. 2001. 109-113. ACR Standards. ACR Standard for the Performance of Computed Tomography for the Detection of Pulmonary Embolism in Adults.

[ACR HR CT] American College of Radiology, Reston, Virginia. 2001. 115-118. ACR Standards. ACR Standard for the Performance of High-Resolution Computed Tomography (HRCT) of the Lungs in Adults.

[ACR Radiography] American College of Radiology, Reston, Virginia. 2001. 95-98. ACR Standards. ACR Standard for the Performance of Pediatric and Adult Chest Radiography.

[ACR Thoracic CT] American College of Radiology, Reston, Virginia. 2001. 103-107. ACR Standards. ACR Standard for the Performance of Pediatric and Adult Thoracic Computed Tomography (CT).

2.7 Response Evaluation Criteria

References to Response Evaluation Criteria are made from the Chest CAD SR Templates and Context Groups

[RECIST] Journal of the National Cancer Institute. Therasse. February 2, 2000. 92. 3. 205-216. “New Guidelines to Evaluate the Response to Treatment in Solid Tumors”. http://www.eortc.be/recist/ .

[WHO] World Health Organization, Geneva. 1979. WHO Handbook for Reporting Results for Cancer Treatment. WHO Offset Publication No. 48. http://whqlibdoc.who.int/publications/9241700483.pdf .

2.8 Myocardial Segmentation

[Cerqueira 2002] Circulation. Cerqueira MD. 2002. 105. 4. 539. “AHA Scientific Statement: Standardized Myocardial Segmentation and Nomenclature for Tomographic Imaging of the Heart”. doi:10.1161/hc0402.102975 Describes 16- and 17-segment models. .

[Voigt 2015] Eur Heart J Cardiovasc Imaging. Voigt JU. 2015. 16. 1. 1-11. “Definitions for a common standard for 2D speckle tracking echocardiography: consensus document of the EACVI/ASE/Industry Task Force to standardize deformation imaging”. doi:10.1093/ehjci/jeu184 Describes 16-, 17-, and 18-segment models. .

2.9 Quantitation of the Left Ventricle

[Schiller 1989] Journal of the American Society of Echocardiography. Schiller. Oct 1989. 2. 5. 358-367. “Recommendations for Quantitation of the Left Ventricle by Two-Dimensional Echocardiography”.

2.10 Cancer Staging

[AJCC] American Joint Committee on Cancer. 2002. Sixth. AJCC Cancer Staging Handbook: From the AJCC Cancer Staging Manual. Springer-Verlag. 0-387-95270-5.

2.11 Quantitative Arteriography and Ventriculography

[Sheehan, 1986] Circulation. Sheehan FH, Bolson EL, Dodge HT, Mathey DG, Schofer J, and Woo HW. 1986. 74. 2. 293-305. “Advantages and applications of the centerline method for characterizing regional ventricular function”. doi:10.1161/01.CIR.74.2.293

[Slager, 1986] J Am Coll Cardiol.. Slager CJ, Hooghoudt TE, Serruys PW, Schuurbiers JC, Reiber JH, Meester GT, Verdouw PD, and Hugenholtz PG. 1986. 6. 2. 317-26. “Quantitative assessment of regional left ventricular motion using endocardial landmarks”. doi:10.1016/S0735-1097(86)80498-3

[Kennedy, 1970] Am Heart J. Kennedy JW, Trenholme SE, and Kasser IS. 1970. 80. 3. 343. “Left ventricular volume and mass from single-plane cineangiocardiogram. A comparison of anteroposterior and right anterior oblique methods”.

[Dodge, 1960] Am Heart J. Dodge HT, Sandler H, Ballew DW, and Lord JD. 1960. 60. 5. 762. “The use of biplane angiocardiography for the measurement of left ventricular volume in man”. http://www.sciencedirect.com/science/article/pii/0002870360903598 .

[Wynne, 1978] Am J Cardiol. Wynne J, Green LH, Mann T, Levin D, and Grossman W. 1978. 41. 4. 726. “Estimation of left ventricular volumes in man from biplane cineangiograms filmed in oblique projections”.

[Boak, 1977] Cathet Cardiovasc Diagn. Boak, JG, Bove AA, Kreulen T, and Spann JF. 1977. 3. 3. 217-30. “A geometric basis for calculation of right ventricular volume in man”. doi:10.1002/ccd.1810030305

[Ferlinz, 1977] Am Heart J. Ferlinz J. 1977. 94. 1. 87-90. “Measurements of right ventricular volumes in man from single plane cineangiograms. A comparison to the biplane approach”. http://www.sciencedirect.com/science/article/pii/S0002870377803487 .

[Graham, 1973] Circulation. Graham TP, Jarmakani JM, Atwood GF, and Canent RV. 1973. 47. 1. 144-53. “Right ventricular volume determinations in children. Normal values and observations with volume or pressure overload”. doi:10.1161/01.CIR.47.1.144

[Arcilla, 1971] Chest. Arcilla RA, Tsai P, Thilenius O, and Ranniger K. 1971. 60. 5. 446. “Angiographic method for volume estimation of right and left ventricles”. doi:10.1378/chest.60.5.446

2.12 IVUS

[Mintz, 2001] Journal of the American College of Cardiology. Mintz GS. 2001. 37. 5. 1478-1492. “American College of Cardiology Clinical Expert Consensus Document on Standards for Acquisition, Measurement and Reporting of Intravascular Ultrasound Studies (IVUS)”. doi:10.1016/S0735-1097(01)01175-5

[Di Mario, 1998] European Heart Journal. Di Mario C. 1998. 19. 2. 207-229. “Clinical Application and Image Interpretation in Intravascular Ultrasound”. doi:10.1053/euhj.1996.0433

[Tobis and Yock] Tobis JM and Yock PC. 1992. Intravascular Ultrasound Imaging. 0443088098.

2.13 C-RADS CT Colonography Reporting and Data System

[Zalis, 2005] Radiology. Zalis ME. 2005. 236. 1. 3-9. “CT Colonography Reporting and Data System: A Consensus Proposal”. doi:10.1148/radiol.2361041926

2.14 Implants

[Eggli, 1998] J Bone Joint Surg Br. Eggli S, Pisan M, and Müller ME. 1998. 80-B. 3. 382-390. “The value of preoperative planning for total hip arthroplasty”. http://www.bjj.boneandjoint.org.uk/content/80-B/3/382 .

2.15 LOINC

[LOINC] Regenstrief Institute, Indianapolis. 2014. Logical Observation Identifier Names and Codes. http://loinc.org/ .

This product includes all or a portion of the LOINC® table, LOINC panels and forms file, LOINC document ontology file, and/or LOINC hierarchies file, or is derived from one or more of the foregoing, subject to a license from Regenstrief Institute, Inc. Your use of the LOINC table, LOINC codes, LOINC panels and forms file, LOINC document ontology file, and LOINC hierarchies file also is subject to this license, a copy of which is available at http://loinc.org/terms-of-use. The current complete LOINC table, LOINC Users' Guide, LOINC panels and forms file, LOINC document ontology file, and LOINC hierarchies file are available for download at http://loinc.org/. The LOINC table and LOINC codes are copyright © 1995-2014, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee. The LOINC panels and forms file, LOINC document ontology file, and LOINC hierarchies file are copyright © 1995-2014, Regenstrief Institute, Inc. All rights reserved.

The LOINC table (in all formats), LOINC panels and forms file, LOINC document ontology file, and LOINC hierarchies are provided "as is." Any express or implied warranties are disclaimed, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose.

A small portion of the LOINC table may include content (e.g., survey instruments) that is subject to copyrights owned by third parties. Such content has been mapped to LOINC terms under applicable copyright and terms of use. Notice of such third party copyright and license terms would need to be included if such content is included.

2.16 UCUM

[UCUM] Regenstrief Institute, Indianapolis. 2013. Unified Code for Units of Measure. http://unitsofmeasure.org/ .

This product includes all or a portion of the UCUM table, UCUM codes, and UCUM definitions or is derived from it, subject to a license from Regenstrief Institute, Inc. and The UCUM Organization. Your use of the UCUM table, UCUM codes, UCUM definitions also is subject to this license, a copy of which is available at http://unitsofmeasure.org/. The current complete UCUM table, UCUM Specification are available for download at http://unitsofmeasure.org/. The UCUM table and UCUM codes are copyright © 1995-2013, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved.

The UCUM table (in all formats), UCUM definitions, and specification are provided "as is." Any express or implied warranties are disclaimed, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose.

2.17 Anesthesia Quality Institute Schema

[AQI Schema] Anesthesia Quality Institute, Schaumburg, IL. 2015/07/30. Anesthesia Quality Institute Schema. http://www.aqihq.org/qcdrDataSample/prodFiles/2018%20Files/AQISchDoc/default.html .

Used by permission of the Anesthesia Quality Institute (AQI) (http://www.aqihq.org/), established by the American Society of Anesthesiologists (ASA).

2.18 Point-of-Care Medical Device Nomenclature

Extracts of ISO/IEEE 11073 reprinted by permission of IEEE, 3 Park Avenue, New York, NY 10016-5997 USA. Copyright by IEEE. http://standards.ieee.org/.

Under license from IEEE, the term codes and descriptions of the ISO/IEEE 11073 Nomenclature are available at no cost through the Rosetta Terminology Mapping Management System of the U.S. National Institute of Standards and Technology. http://rtmms.nist.gov/rtmms/index.htm

[ISO/IEEE 11073-10101] ISO/IEEE. 2004. Health informatics - Point-of-care medical device communication - Nomenclature.

[ISO/IEEE 11073-10101a] ISO/IEEE. 2015. Health informatics - Point-of-care medical device communication - Nomenclature Amendment 1: Additional Definitions.

[ISO/IEEE 11073-10102] ISO/IEEE. 2015. . Health informatics - Point-of-care medical device communication - Annotated ECG - Nomenclature.

2.19 SNOMED Clinical Terms

This DICOM Standard incorporates SNOMED CT® International Edition 2021/07/31, used by permission of SNOMED International. SNOMED CT®, was originally created by The College of American Pathologists (CAP). SNOMED International was formerly known as the International Health Terminology Standards Development Organisation (IHTSDO).

The SNOMED CT terms used in this Standard (the SNOMED CT DICOM Subset) are the subject of a licensing agreement between NEMA and SNOMED International that allows the use of this defined subset in DICOM conformant applications without further license or payment of fee. Any use of SNOMED CT beyond the terms published in the DICOM Standard is subject to SNOMED CT licensing rules, which may include a fee. For further information about SNOMED CT licensing, go to http://www.snomed.org/snomed-ct/get-snomed or contact SNOMED International at info@snomed.org.

This DICOM Standard incorporates various veterinary terms from the SNOMED CT VetSCT extension, used by permission of the Veterinary Terminology Services Laboratory (VTSL) (http://vtsl.vetmed.vt.edu/). These terms were previously included in SNOMED CT but have since been inactivated as moved elsewhere.

[SNOMED] SNOMED International. . SNOMED CT Systematized Nomenclature of Medicine - Clinical Terms.

2.20 Prostate Reporting Terminology and Nomenclature

The Prostate Imaging and Report and Data System Version 2 (PI-RADS) is a joint effort of the European Society of Urogenital Radiology, the American College of Radiology and the AdMeTech Foundation.

[PI-RADS] Eur Urol. Weinreb JC, Barentsz JO, Choyke PL, Cornud F, Haider MA, Macura KJ, Margolis, D, Schnall, MD, Shtern, F, Tempany, CM., Thoeny, HC, and Verma, S. 2016/01. 69. 1. 16-40. “PI-RADS Prostate Imaging - Reporting and Data System: 2015, Version 2”. doi:10.1016/j.eururo.2015.08.052 http://www.europeanurology.com/article/S0302-2838%2815%2900848-9/ .

Note

PI-RADS is also available from the following source:

American College of Radiology: http://www.acr.org/~/media/ACR/Documents/PDF/QualitySafety/Resources/PIRADS/PIRADS%20V2.pdf

[PI-RADS v2.1] Eur Urol. Turkbey B, Rosenkrantz AB, Haider MA, Padhani AR, Villeirs G, Macura KJ, Tempany, CM, Choyke PL, Cornud F, Margolis, D, Thoeny, HC, Verma, S, Barentsz JO, and Weinreb JC. 2019/09. 76. 3. 340–351. “Prostate Imaging Reporting and Data System Version 2.1: 2019 Update of Prostate Imaging Reporting and Data System Version 2”. doi:10.1016/j.eururo.2019.02.033 http://www.europeanurology.com/article/S0302-2838(19)30180-0/abstract .

[Prostate Eu Concensus] Eur Urol. Dickinson L, Ahmed HU., Allen C, Barentsz JO, Carey B, Futterer JJ, Heijmink SW, Hoskin PJ, Kirkham A, and Padhani AR. 2011. 59. 4. 477-94. “Magnetic resonance imaging for the detection, localisation, and characterisation of prostate cancer: recommendations from a European consensus meeting”. doi:10.1016/j.eururo.2010.12.009 http://www.europeanurology.com/article/S0302-2838(10)01187-5/ .

[ESUR Guidelines] Eur Radiol. Barentsz JO, Richenberg J, Clements R, Choyke P, Verma S, Villeirs G, Rouviere O, Logager V, and Fütterer JJ. 2012/04. 22. 4. 746-57. “ESUR prostate MR guidelines 2012”. doi:10.1007/s00330-011-2377-y http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3297750/ .

[Rozenkrantz 2013] Radiology. Rosenkrantz AB, Kim S, Lim RP, Hindman N, Deng FM, Babb JS, and Taneja SS. 2013/11. 269. 2. 482–492. “Prostate cancer localization using multiparametric MR imaging: comparison of Prostate Imaging Reporting and Data System (PI-RADS) and Likert scales”. doi:10.1148/radiol.13122233 http://dx.doi.org/10.1148/radiol.13122233 .

[Kuru 2013] BJU Int. Kuru TH. 2013. 112. 5. 568–577. “Definitions of terms, processes and a minimum dataset for transperineal prostate biopsies: a standardization approach of the Ginsburg Study Group for Enhanced Prostate Diagnostics”. doi:10.1111/bju.12132 http://onlinelibrary.wiley.com/doi/10.1111/bju.12132/full .

2.21 Imaging Agent Administration Concepts

Injector and modality manufacturers use the CiA 425 CANopen standard for communication and synchronization between devices.

[CiA 425 CANopen] CANopen. 30 October 2010. CiA 425 Draft Standard Proposal, Application profile for medical diagnostic add-on modules Part 2: Injector, Version: 2.1.0.

2.22 CAD-RADS™ Terminology and Nomenclature

A portion of the terminology used within the CT/MR Cardiovascular Analysis Report is derived from CAD-RADS™.

[CAD-RADS™] Journal of Cardiovascular Computed Tomography. Cury RC and et al. 2016. 10. 269-81. “CAD-RADS™ Coronary Artery Disease – Reporting and Data System. An expert consensus document of the Society of Cardiovascular Computed Tomography (SCCT), the American College of Radiology (ACR) and the North American Society for Cardiovascular Imaging (NASCI). Endorsed by the American College of Cardiology.”. doi:10.1016/j.jcct.2016.04.005 http://www.journalofcardiovascularct.com/article/S1934-5925(16)30048-X/ .

3 Определения

Для целей настоящего Стандарта применяются следующие определения.

3.1 Определения кодов и контролируемой терминологии

В настоящей части Стандарта DICOM обычно используются следующие определения:

Baseline Context Group Identifier (BCID)

Идентификатор, определяющий предлагаемую Контекстную группу для атрибута Code Sequence.

See Table 5.6-1 “Conventions for Specification of Context Groups” in PS3.3 .

Baseline Template Identifier (BTID)

Идентификатор, определяющий Шаблон, предлагаемый для использования при создании набора элементов содержимого.

Coding Scheme

Словарь (лексикон) концептов (терминов) с присвоенными кодами и чётко определёнными значениями.

Note

Примерами схем кодирования являются SNOMED и LOINC.

Context Group

Набор кодированных концептов, определённый Ресурсом сопоставления, образующий набор, подходящий для использования в конкретном контексте.

Context Group Version

Версия Контекстной группы.

Context ID (CID)

Идентификатор Контекстной группы.

Defined Context Group Identifier (DCID)

Идентификатор, определяющий Контекстную группу для атрибута Code Sequence, которая должна использоваться.

See Table 5.6-1 “Conventions for Specification of Context Groups” in PS3.3 .

Defined Template Identifier (DTID)

Идентификатор, определяющий Шаблон, который должен использоваться при создании набора элементов содержимого.

DICOM Content Mapping Resource (DCMR)

Ресурс сопоставления, определяющий Шаблоны и Контекстные группы для использования в IOD DICOM.

Extensible Context Group

Контекстная группа, которая может быть расширена конкретным приложением путём включения дополнительных концептов.

See Table 5.6-1 “Conventions for Specification of Context Groups” in PS3.3 .

Extensible Template

Шаблон, который может быть расширен конкретным приложением путём включения дополнительных элементов содержимого сверх указанных в Шаблоне.

Mapping Resource

Ресурс, определяющий контекстно-зависимые ограничения использования (то есть ограничения набора значений или типа отношения) для атрибутов. Ресурс, определяющий сопоставление содержимого внешней контролируемой терминологии с компонентами стандарта сообщений.

Non-Extensible Context Group

Контекстная группа, определённый набор концептов которой не должен расширяться приложением.

See Table 5.6-1 “Conventions for Specification of Context Groups” in PS3.3 .

Non-Extensible Template

Шаблон, определяющий точный набор элементов содержимого и соответствующих наборов значений, которые должны использоваться и не должны расширяться приложением.

Relationship Type

Связь между двумя концептами. Примеры: «HAS PROPERTIES», «CONTAINS», «INFERRED FROM».

Root Template

Шаблон, первым элементом содержимого которого является элемент содержимого CONTAINER, предназначенный для кодирования в наборе данных верхнего уровня экземпляра SOP. То есть корневой узел дерева содержимого.

Template

Шаблон (образец), описывающий элементы содержимого, типы значений, типы отношений и наборы значений, которые могут использоваться в части дерева содержимого структурированного отчёта или в других конструкциях элементов содержимого, таких как Acquisition Context или Protocol Context. Аналогичен модулю информационной объектной дефиниции.

Template ID (TID)

Идентификатор Шаблона.

Value Set

Допустимые значения атрибута Code Sequence в данном контексте. Задаётся либо как одно или несколько отдельных значений, либо посредством ссылки на Контекстную группу.

3.2 Информационные объектные дефиниции

В настоящей части Стандарта используются следующие термины, определённые в PS3.3:

Attribute Value: See Attribute Value in PS3.3 .
Coded Entry Value: See Coded Entry Value in PS3.3 .
Code Sequence Attribute: See Code Sequence Attribute in PS3.3 .

3.3 Определения, связанные с введением контрастного вещества

Imaging Agent

Вещество, вводимое для улучшения визуализации определённых органов, тканей, заболеваний и физиологических функций. Адаптировано из Wikipedia http://en.wikipedia.org/wiki/Imaging_agent.

Note

К визуализирующим агентам относятся йодсодержащие рентгеновские и гадолиниевые МР-контрастные вещества.
Промывка физиологическим раствором не является визуализирующим агентом, но может вводиться совместно с визуализирующими агентами.
Воздух, используемый в качестве отрицательного контрастного вещества, является визуализирующим агентом.

3.4 Определения из части «Введение и обзор» DICOM

В настоящей части Стандарта используются следующие термины, определённые в PS3.1:

Service-Object Pair Class (SOP Class): See Service-Object Pair Class in PS3.1 .

3.5 Определения сервисных классов DICOM

В настоящей части Стандарта используются следующие термины, определённые в PS3.4:

Service-Object Pair Instance (SOP Instance): See Service-Object Pair Instance in PS3.4 .

3.6 Структуры данных и кодирование DICOM

В настоящей части Стандарта используются следующие термины, определённые в PS3.5:

Data Set: See Data Set in PS3.5 .
Item: See Item in PS3.5 .
Value: See Value in PS3.5 .

3.7 Радиотерапия

Monitor Units (MU): Единица выходного излучения, используемая для количественной оценки Meterset. См. Section C.36.1.1.3 “Meterset” in PS3.3 .

3.8 Определения структурированного отчёта

В настоящей части Стандарта используются следующие термины, определённые в PS3.3:

Content Item: See Content Item in PS3.3 .
Content Tree: See Content Tree in PS3.3 .

4 Обозначения и сокращения

В настоящей части Стандарта используются следующие обозначения и сокращения.

ACR: Американская коллегия радиологов
ASE: Американское общество эхокардиографии
BCID: Базовый идентификатор контекстной группы
BTID: Базовый идентификатор шаблона
CAP: Коллегия американских патологов
Chest CAD: Компьютерное обнаружение и/или компьютерная диагностика для рентгенографии грудной клетки
CNAME: Имя контекстной группы
Colon CAD: Компьютерное обнаружение и/или компьютерная диагностика для рентгенографии толстой кишки
CSV: Значения, разделённые запятыми
DCID: Определённый идентификатор контекстной группы
DCMR: Ресурс сопоставления содержимого DICOM
DICOM: Цифровые изображения и связь в медицине
DT: Определённый термин
DTID: Определённый идентификатор шаблона
EV: Перечислимое значение
FHIR: Быстрые ресурсы взаимодействия в здравоохранении
HTML: Язык гипертекстовой разметки
IHE: Интеграция медицинских учреждений
IHE SVS: Совместное использование наборов значений IHE
JSON: Нотация объектов JavaScript
Mammography CAD: Компьютерное обнаружение и/или компьютерная диагностика для маммографии
MPPS: Выполненный этап процедуры модальности
NEMA: Национальная ассоциация производителей электрооборудования
OWL: Язык веб-онтологий
RDSR: Структурированный отчёт о дозе облучения
RECIST: Критерии оценки ответа при солидных опухолях
SNOMED: Систематизированная номенклатура медицины
TNAME: Имя шаблона
UCUM: Единый код для единиц измерения
WHO: Всемирная организация здравоохранения
XML: Расширяемый язык разметки

Следующие сокращения прописными буквами обозначают конкретные атрибуты:

CM: Значение кода (Code Meaning) (0008,0104)
CSD: Обозначение схемы кодирования (Coding Scheme Designator) (0008,0102)
CSV: Версия схемы кодирования (Coding Scheme Version) (0008,0103)
CV: Значение кода (Code Value) (0008,0100), длинное значение кода (Long Code Value) (0008,0119) или значение кода URN (URN Code Value) (0008,0120)

5 Соглашения

Термины, перечисленные в Section 3, пишутся с заглавной буквы по всему документу.

6 Форма спецификаций шаблонов

Шаблоны — это образцы, определяющие имена концептов, требования, условия, типы значений, кратность значений, ограничения набора значений, типы отношений и другие атрибуты элементов содержимого для конкретного приложения.

IOD может определять, что конкретные Стандартные шаблоны должны использоваться или могут использоваться для определения или ограничения содержимого конструкции элемента содержимого. Конструкция элемента содержимого включает кодированное имя концепта и один из нескольких типов кодированных значений. Конструкции элементов содержимого используются в:

основном наборе данных и рекурсивно вложенных Content Sequence (0040,A730) модуля SR Document Content Module
Acquisition Context Sequence (0040,0555) модуля Acquisition Context Module,
Protocol Context Sequence (0040,0440) и Content Item Modifier Sequence (0040,0441) модулей Scheduled Procedure Step Module, Image Acquisition Results Module и других.
Specimen Preparation Step Content Item Sequence (0040,0612) модуля Specimen Module.

Annex A и Annex C настоящей части определяют Стандартные шаблоны.

Note

Реализаторы Стандарта могут определять Стандартные расширенные и частные шаблоны. Правила определения Стандартных расширенных и частных шаблонов SR аналогичны правилам определения Стандартных расширенных и частных классов SOP. Одна строка таблицы шаблона соответствует одной строке таблицы модуля в IOD PS3.3.

Каждый Стандартный шаблон определяется таблицей шаблона в настоящей части. Каждая таблица шаблона определяет ровно один шаблон, соответствующий образцу содержимого в рамках конструкции элемента содержимого.

Каждая таблица шаблона указывает, является ли порядок элементов содержимого значимым или незначимым. Экземпляры SOP, содержимое которых основано на шаблоне со значимым порядком, должны кодировать элементы содержимого верхнего уровня в порядке, указанном в шаблоне, а вспомогательные элементы содержимого под каждым родительским элементом — в указанном порядке, и так далее для каждого уровня вложенности. Значимость порядка применяется только к самому шаблону; включённые вспомогательные шаблоны могут иметь иную значимость порядка.

Note

Даже если шаблон указывает, что порядок незначим, порядок кодирования элементов содержимого в экземпляре SOP может иметь значение. Например, элементы содержимого CONTAINER со значением Continuity of Content (0040,A050), равным CONTINUOUS, кодируют элементы содержимого в повествовательной последовательности, а журналы процедур кодируют элементы содержимого во временнóм порядке.

Элементы содержимого из вспомогательных шаблонов могут перемежаться только в том случае, если и родительский, и вспомогательный шаблоны указывают, что порядок незначим. Это позволяет впоследствии выполнять рефакторинг в переиспользуемые шаблоны.

Диапазон концептов и опций, допустимых в семействе документов SR, изменяется обратно пропорционально уровню ограничений, накладываемых соответствующим шаблоном SR. Чем уже диапазон концептов и чем более ограничены допустимые шаблоном опции, тем предсказуемее будет содержимое документов SR.

Note

Очень специфичный шаблон определяет семейство документов SR, очень похожих друг на друга. Они имеют узкий диапазон опций содержимого (например, высокий уровень ограничения значений элементов содержимого; использование CODE или NUM с определёнными идентификаторами контекстных групп), и поэтому их содержимое высоко предсказуемо. Очень общий (например, разрешительный или широкий) шаблон определяет семейство документов SR, которые могут значительно различаться между собой. Они имеют более широкий диапазон опций содержимого (например, низкий уровень ограничения значений элементов содержимого; использование TEXT с относительно небольшим ограничением значений элементов содержимого), и их содержимое менее предсказуемо.
Степень интероперабельности, которая может быть достигнута для семейства документов SR, созданных на основе шаблона, может быть намеренно и точно установлена на желаемом уровне посредством соответствующего проектирования шаблона для достижения необходимой степени предсказуемости содержимого документов SR.

6.1 Определение полей таблицы шаблона

Шаблоны SR описываются с помощью таблиц следующей формы:

Тип:: (Не)расширяемый
Порядок:: (Не)значимый
Корневой:: Да или Нет

Table TID <#>. <SR Context Template Name>

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1
2
3

Шаблоны Acquisition Context описываются с помощью таблиц следующей формы:

Type:: (Non-) Extensible
Order:: (Non-) Significant

Table TID <#>. <Acquisition Context Template Name>

	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1
2
3

Шаблоны Protocol Context описываются с помощью таблиц следующей формы:

Type:: (Non-) Extensible
Order:: (Non-) Significant

Table TID <#>. <Protocol Context Template Name>

	NL	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1
2
3

Семантика полей (столбцов) таблиц шаблонов определена в подразделах настоящего раздела. Строка таблицы шаблона определяет либо один элемент содержимого, либо включение другого шаблона, который может определять любое количество элементов содержимого (см. Section 6.2.3 для определения понятия «включённые шаблоны»). Каждая таблица шаблона именуется заголовком, идентифицируется номером TID и далее поясняется описанием, таким как разъяснение содержимого, назначения и сценариев использования шаблона.

Для описания отдельных строк, то есть элементов содержимого, может использоваться отдельная таблица следующей формы:

Описания элементов содержимого

Строка 1
Строки 2, 3

Первый столбец содержит ссылку на строку(и) таблицы шаблона с использованием соответствующего номера(ов) строки (см. Section 6.1.1), например, «Row 1» относится к строке, обозначенной как первая строка таблицы шаблона, а «Rows 2, 3» относится к строкам, обозначенным как вторая и третья строки таблицы шаблона. При ссылке на несколько строк номера строк перечисляются полностью. Второй столбец содержит описание указанной строки (строк).

Note

Диапазоны, такие как «Rows 1-3», или иные виды сокращений не используются.
Описывать все строки таблицы шаблона в этой дополнительной таблице не обязательно.

Для формы ссылок на кодированные концепты, контекстные группы и шаблоны определены следующие соглашения.

Значения Code Meaning заключаются в кавычки (например, «cm»). Значения Code Value и обозначения Coding Scheme Designator не заключаются в кавычки, если только в строке не встречается запятая.

Ссылки на кодированные концепты имеют следующую форму:

EV or DT (CV, CSD, "CM")

например, перечислимое значение (Enumerated Value), для которого определены только CV, CSD и CM, представляется следующим образом: EV (CV, CSD, "CM"), например EV (76752008, SCT, "Breast").
MemberOf { BCID or DCID (CID) CNAME } — конструкция MemberOf выбирает один термин из указанной контекстной группы.

Если требуется ссылка на конкретную версию схемы кодирования, она имеет следующую форму:

EV or DT (CV, CSD [CSV], "CM")

например, DT (MA.II.A.5.4A, BI [4.0], "4A - Low suspicion").

Ссылки на контекстные группы имеют следующую форму:

BCID or DCID (CID) CNAME

например, определённый идентификатор контекстной группы (Defined Context Group Identifier) 5000 представляется следующим образом: DCID (5000) Language.

Ссылки на шаблоны имеют следующую форму:

BTID or DTID (TID) TNAME

например, базовый идентификатор шаблона (Baseline Template Identifier) 1000 представляется следующим образом: BTID (1000) Quotation.

6.1.1 Номер строки

Каждая строка таблицы шаблона обозначается номером строки. Первая строка нумеруется как 1, а последующие строки нумеруются по возрастанию с шагом 1. Этот номер обозначает строку для удобства описания, а также для ссылок в условиях.

Note

Когда шаблоны изменяются путём добавления новой строки, вставляемой в существующую таблицу шаблона, то есть не добавляемой после последней строки, к номеру строки предшествующей строки добавляется буквенный суффикс. Например, номер строки «2a» или «2b» используется для вставки новой строки между строками «2» и «3».

Номер строки элемента содержимого в шаблоне может как совпадать, так и не совпадать с порядковой позицией соответствующего элемента последовательности (Sequence Item), представляющего элемент содержимого, в Content Sequence (0040,A730), в зависимости от количества повторений элемента содержимого.

Элемент содержимого, указанный в первой строке таблицы шаблона, может иметь любой тип значения. В частности, он не обязан быть CONTAINER.

6.1.2 Уровень вложенности (Nesting Level, NL)

Когда между двумя элементами содержимого присутствует отношение «родитель-потомок», родитель считается исходным элементом содержимого (Source Content Item), а потомок — целевым элементом содержимого (Target Content Item); см. Section C.17.3.2.4 Content Sequence and Relationship Type in PS3.3 .

Уровень вложенности элементов содержимого обозначается символами «>», по одному на каждый уровень вложенности ниже исходного (Source) элемента содержимого шаблона, аналогично изображению вложенных последовательностей элементов в таблицах модулей в PS3.3. Когда необходимо указать целевой элемент(ы) содержимого отношения, они указываются в строке(ах), непосредственно следующей за соответствующим исходным элементом содержимого. Уровень вложенности целевого элемента содержимого на единицу больше уровня вложенности соответствующего (родительского) исходного элемента содержимого. Элемент содержимого, указанный в строке 1 таблицы шаблона, находится на верхнем уровне (то есть символ «>» никогда не присутствует в поле NL для первого элемента содержимого в таблице).

Шаблоны Acquisition Context не имеют поля Nesting Level. Шаблоны Protocol Context и UPS Processing Parameter допускают один уровень вложенности, реализуемый через Content Item Modifier Sequence (см. PS3.3).

6.1.3 Отношение с исходным элементом содержимого (родительским)

В этом поле указывается тип отношения (Relationship Type) и ограничения «по значению» (by-value) или «по ссылке» (by-reference), если они определены, как описано в Table 6.1.3-1.

Тип отношения и режим указываются для каждой строки, определяющей целевой элемент содержимого.

Тип отношения и режим также могут указываться при включении другого шаблона — «сверху вниз», «снизу вверх» или обоими способами (то есть в строке «INCLUDE Template» вызывающего шаблона, или во всех строках включаемого шаблона, или в обоих местах). Не должно быть противоречия между типом отношения и режимом строки, включающей другой шаблон, и типом отношения и режимом строк включаемого шаблона. См. Section 6.2.3 для дальнейшего описания понятия «включённые шаблоны».

Note

IOD SR определяют перечислимые значения для типов отношений. Если в частном классе SOP указан тип отношения, отличный от одного из определённых терминов для Relationship Type (0040,A010), существует значительный риск для интероперабельности. Документация, сопровождающая шаблоны для частных классов SOP, должна определять любые расширения типов отношений так же, как стандартные типы отношений определены в PS3.3.

Шаблоны Acquisition Context и Protocol Context не имеют поля Relationship.

Table 6.1.3-1. Синтаксис ограничений отношений

Выражение	Определение
RTYPE	Режим отношения (Relationship Mode) — «по значению» (by-value), а тип отношения — RTYPE. Например, «INFERRED FROM».
R-RTYPE	Режим отношения — «по ссылке» (by-reference), а тип отношения — RTYPE. Например, «R-INFERRED FROM».

6.1.4 Тип значения (Value Type, VT)

Поле Value Type определяет тип значения SR элемента содержимого либо содержит слово «INCLUDE», указывающее, что должен быть включён другой шаблон (подставленный вместо строки). См. Section 6.2.3 для дальнейшего описания понятия «включённые шаблоны».

6.1.5 Имя концепта (Concept Name)

Любые ограничения на имя концепта указываются в поле Concept Name в виде определённых или перечислимых кодированных записей, либо в виде базовых или определённых идентификаторов контекстных групп. В качестве альтернативы, когда поле VT содержит «INCLUDE», поле Concept Name указывает включаемый шаблон. См. Section 6.2.3 для дальнейшего описания понятия «включённые шаблоны».

Отсутствие записи в поле Concept Name означает, что может использоваться любой код из любой схемы кодирования, включая коды из частных схем кодирования.

6.1.6 Кратность значения (Value Multiplicity, VM)

Поле VM указывает количество повторений элемента содержимого заданного образца или включённого шаблона в этой позиции. Table 6.1.6-1 определяет значения, допустимые в этом поле.

Table 6.1.6-1. Допустимые значения для VM

Выражение	Определение
i (где «i» — целое число)	Ровно i повторений, где i>=1. Например, при i=1 в этой позиции должно быть одно повторение элемента содержимого.
i-j (где «i» и «j» — целые числа)	От i до j повторений, где i и j >=1 и j>i.
i-n (где «i» и «n» — целые числа)	i или более повторений, где i>=1.

6.1.7 Тип требования

Поле Requirement Type определяет требования к наличию или отсутствию элемента содержимого или включённого шаблона.

Note

Обычно нет необходимости отдельно указывать тип требования для SCU и SCP классов SOP SR, поскольку SCP обязан поддерживать всё содержимое любого получаемого документа SR. Поэтому для классов SOP SR тип требования фактически применяется только к SCU.

Используются следующие обозначения:

M: Обязательный (Mandatory). Должен присутствовать. Пустая Measured Value Sequence (0040,A300) не допускается при неизвестном значении, только при сбоях. См. Section 6.1.7.1.
MC: Обязательный условный (Mandatory Conditional). Должен присутствовать, если выполняется указанное условие. Пустая Measured Value Sequence (0040,A300) не допускается при неизвестном значении, только при сбоях. См. Section 6.1.7.1.
U: Пользовательская опция (User Option). Может присутствовать или отсутствовать.
UC: Пользовательская опция условная (User Option Conditional). Может отсутствовать. Может присутствовать в соответствии с указанным условием.

Note

Между VM и типом требования существует взаимодействие в отношении количества фактических повторений элемента содержимого (или включённого шаблона), как показано ниже:

Req Type	VM	Фактическое количество повторений в дереве содержимого
M or MC	1	1
M or MC	1-n	от 1 до n
U or UC	1	0 или 1
U or UC	1-n	от 0 до n

6.1.7.1 Тип требования для числовых элементов содержимого в структурированных отчётах

Section C.18.1 Numeric Measurement Macro in PS3.3 допускает, чтобы Measured Value Sequence (0040,A300), содержащая Numeric Value (0040,A30A) и Measurement Units Code Sequence (0040,08EA), имела нулевую длину.

Note

Это не применяется к Section 10.2 Content Item Macro in PS3.3 , которая не допускает пустую Measured Value Sequence (0040,A300) и не включает Numeric Value Qualifier Code Sequence (0040,A301).

Неизвестное состояние должно отличаться от допустимых состояний, связанных со сбоем арифметики, устройства или алгоритма (в этих случаях числовая строка, соответствующая представлению значения (Value Representation) DS в PS3.5, не может быть создана).

Если тип требования шаблона — M или MC, то:

Measured Value Sequence (0040,A300) нулевой длины допускается по любой из причин, перечисленных в CID 43 “Numeric Value Failure Qualifier”
Measured Value Sequence (0040,A300) нулевой длины не допускается по любой из причин, перечисленных в CID 44 “Numeric Value Unknown Qualifier”, или по любой иной семантически эквивалентной причине

Note

Цель вышеизложенного — не допустить, чтобы реализатор обходил требования шаблона. Отправка бессмысленных значений, таких как значение ноль, когда ноль не является реалистичным значением, также не приветствуется.

6.1.8 Условие

Поле Condition определяет любые условия, от которых зависит наличие или отсутствие элемента содержимого или его значений. Это поле указывает любые имена концептов или значения, от которых существуют зависимости.

Ссылки в выражениях Condition на кодированные концепты или значения — будь то выбор элемента содержимого для проверки или указание значения для сравнения — имеют форму (CV, CSD, "CM"). Как и всегда для кодированных записей, сопоставление выполняется по CV и CSD, независимо от строкового значения CM.

Также могут делаться ссылки на номера строк (например, для указания условий исключающего ИЛИ, охватывающих несколько строк таблицы шаблона). При ссылке на несколько строк номера строк должны быть полностью перечислены, например, «Rows 1, 2, 3». При ссылке на одну строку используется форма единственного числа, например, «Row 2».

Note

Диапазоны, такие как «Rows 1-3», или иные виды сокращений не используются.

В поле Condition используются следующие сокращения:

XOR: Исключающее ИЛИ (Exclusive OR). Должна быть выбрана одна и только одна строка из взаимоисключающих вариантов.

Note

Например, если может быть включена одна из строк 1, 2, 3 или 4, то для строки 2 в качестве условия указывается сокращение «XOR Rows 1, 3, 4».
IF: Должен присутствовать, если условие истинно (TRUE); в противном случае может присутствовать.
IFF: Тогда и только тогда (If and only if). Должен присутствовать, если условие истинно (TRUE); в противном случае не должен присутствовать.

6.1.9 Ограничение набора значений

Любые ограничения на набор значений для элемента содержимого CODE указываются в этом поле в виде определённых или перечислимых кодированных записей, либо в виде базовых или определённых контекстных групп.

Отсутствие записи в поле Value Set Constraint для элемента содержимого CODE означает, что может использоваться любой код из любой схемы кодирования, включая коды из частных схем кодирования.

Поле Value Set Constraint может указывать значение по умолчанию для элемента содержимого на случай, если элемент содержимого отсутствует, либо в виде фиксированного значения, либо по ссылке на другой элемент содержимого, либо по ссылке на атрибут набора данных вне Content Sequence (0040,A730). Например:

По умолчанию (121006, DCM, "Person")
По умолчанию равно значению Institution Name (0008,0080) модуля General Equipment Module

Значение по умолчанию также может указываться для обозначения того, что от элемента содержимого ожидается конкретное значение, если только нет причины для его отличия. Это особенно верно в случае, когда элемент содержимого является обязательным и, следовательно, не должен отсутствовать.

Note

Для элемента содержимого UIDREF в строке 1 TID 1004 “Device Observer Identifying Attributes” столбец Value Set Constraint указывает: «По умолчанию равно значению Device UID (0018,1002) модуля General Equipment Module». Это означает, что значение данного элемента содержимого должно совпадать со значением указанного атрибута, если только нет причины для его отличия.

6.1.9.1 Ограничение единиц измерения NUM

Любые ограничения на единицы измерения указываются в поле Value Set Constraint тогда и только тогда, когда тип значения — NUM. Ограничения указываются либо в виде определённых или перечислимых кодированных записей, либо в виде базовых или определённых контекстных групп. Например:

UNITS = EV (mm, UCUM, "mm")
UNITS = DCID 7460 “Linear Measurement Unit”

Ограничения на единицы измерения применяются только тогда, когда Measured Value Sequence (0040,A300) содержит элемент (то есть числовое значение присутствует).

Note

Наличие ограничений на единицы измерения не означает, что значение обязательно должно быть отправлено, поскольку Measured Value Sequence (0040,A300) имеет Type 2 и может иметь нулевую длину, если это допускается типом требования элемента содержимого в шаблоне.

Отсутствие ограничения на единицы измерения означает, что может использоваться любой код единиц из любой схемы кодирования, включая коды из частных схем кодирования.

6.1.9.2 Ограничение флага продолжения CONTAINER

Значение Continuity of Content Flag (0040,A050) может быть указано в поле Value Set Constraint тогда и только тогда, когда тип значения — CONTAINER.

Note

Модуль SR Document Content Module определяет «SEPARATE» и «CONTINUOUS» как перечислимые значения для Continuity of Content Flag (0040,A050).

6.1.9.3 Ограничение графического типа SCOORD

Ограничения на значение Graphic Type (0070,0023) могут быть указаны в поле Value Set Constraint тогда и только тогда, когда тип значения — SCOORD. Ограничение может указывать набор допустимых значений или набор недопустимых значений. Например:

GRAPHIC TYPE = {POINT}
GRAPHIC TYPE = {CIRCLE, ELLIPSE}
GRAPHIC TYPE = not {MULTIPOINT}

6.1.9.4 Ограничения строк, столбцов, единиц измерения и кодированного содержимого TABLE

Ограничения на различные аспекты элемента содержимого TABLE могут быть указаны в поле Value Set Constraint, включая способ кодирования табулированных значений — по строкам, по столбцам, по отдельным ячейкам или по ссылке на другие элементы содержимого, — путём указания:

фиксированных значений, минимумов и/или максимумов количества строк (NROWS) и/или столбцов (NCOLUMNS) таблицы
определённых или перечислимых кодированных записей, либо базовых или определённых контекстных групп для Concept Name Code Sequence (0040,A043), используемых в Table Row Definition Sequence (0040,A806) (ROW n) и/или Table Column Definition Sequence (0040,A807) (COLUMN n)
определённых или перечислимых кодированных записей, либо базовых или определённых контекстных групп для Concept Code Sequence (0040,A168), используемых в Cell Values Sequence (0040,A808) (ROW n VALUES) и/или (COLUMN n VALUES) и/или (CELL r, c VALUES)
определённых или перечислимых кодированных записей, либо базовых или определённых контекстных групп для Measurement Units Code Sequence (0040,08EA), используемых в Table Row Definition Sequence (0040,A806) (ROW n UNITS) и/или Table Column Definition Sequence (0040,A807) (COLUMN n UNITS) и/или Cell Values Sequence (0040,A808) (CELL r, c UNITS)
допустимого VR для использования в Selector Attribute VR (0072,0050) для указанных строк (ROW n VR), столбцов (COLUMN n VR) или ячеек (CELL r,c VR), когда значения кодируются буквально
допустимого целевого элемента содержимого по ссылке (TID ttt ROW rrr) для указанных строк (ROW n REF), столбцов (COLUMN n REF) или ячеек (CELL r,c REF), когда значения указываются по ссылке

Также полезно приводить подробное описание формы таблицы в соответствующем Content Item Description.

Пример 1:

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
5		CONTAINS	TABLE	EV (113734, DCM, "X-Ray Tube Current")	1	M		NCOLUMNS = 2 COLUMN 1 = EV (111526, DCM, "DateTime Started") COLUMN 2 = EV (113734, DCM, "X-Ray Tube Current") COLUMN 2 UNITS = EV (mA, UCUM, "mA") COLUMN 1 VR = DT COLUMN 2 VR = FL

Rel with Parent

Concept Name

Req Type

Condition

Value Set Constraint

CONTAINS

TABLE

EV (113734, DCM, "X-Ray Tube Current")

NCOLUMNS = 2

COLUMN 1 = EV (111526, DCM, "DateTime Started")

COLUMN 2 = EV (113734, DCM, "X-Ray Tube Current")

COLUMN 2 UNITS = EV (mA, UCUM, "mA")

COLUMN 1 VR = DT

COLUMN 2 VR = FL

Content Item Descriptions

Строка 5

Таблица X-Ray Tube Current кодируется как таблица с двумя столбцами, состоящая из нескольких строк, описывающих соответствующие значения datetime и тока рентгеновской трубки. Количество строк не ограничено.

Пример 2:

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
5		CONTAINS	TABLE	EV (130520, DCM, "Transformation Matrix")	1	M		NCOLUMNS = 4 NROWS= 4 CELL VR = FD

Rel with Parent

Concept Name

Req Type

Condition

Value Set Constraint

CONTAINS

TABLE

EV (130520, DCM, "Transformation Matrix")

NCOLUMNS = 4

NROWS= 4

CELL VR = FD

Content Item Descriptions

Строка 5

Transformation Matrix кодируется как матрица 4 на 4 безразмерных чисел в форме, определённой в Section C.20.2.1.1 Frame of Reference Transformation Matrix in PS3.3 . Таблица может кодироваться как целые строки, целые столбцы или отдельные ячейки числовых значений двойной точности (double float).

Пример 3:

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
5		CONTAINS	TABLE	EV (126081, DCM, "RECIST 1.1")	1	M		NCOLUMNS = 4 COLUMN 1 = EV (112039, DCM, "Tracking Identifier") COLUMN 2 = EV (363698007, SCT, "Finding Site") COLUMN 3 = EV (272741003, SCT, "Laterality") COLUMN 4 = EV (103339001, SCT, "Long Axis") COLUMN 4 UNITS = EV (mm, UCUM, "mm") COLUMN 1 REF = TID 1500 ROW 9 > TID 1501 ROW 2 COLUMN 2 REF = TID 1500 ROW 9 > TID 1501 ROW 6 COLUMN 3 REF = TID 1500 ROW 9 > TID 1501 ROW 7 COLUMN 4 REF = TID 1500 ROW 9 > TID 1501 ROW 10 > TID 300 ROW 1

Rel with Parent

Concept Name

Req Type

Condition

Value Set Constraint

CONTAINS

TABLE

EV (126081, DCM, "RECIST 1.1")

NCOLUMNS = 4

COLUMN 1 = EV (112039, DCM, "Tracking Identifier")

COLUMN 2 = EV (363698007, SCT, "Finding Site")

COLUMN 3 = EV (272741003, SCT, "Laterality")

COLUMN 4 = EV (103339001, SCT, "Long Axis")

COLUMN 4 UNITS = EV (mm, UCUM, "mm")

COLUMN 1 REF = TID 1500 ROW 9 > TID 1501 ROW 2

COLUMN 2 REF = TID 1500 ROW 9 > TID 1501 ROW 6

COLUMN 3 REF = TID 1500 ROW 9 > TID 1501 ROW 7

COLUMN 4 REF = TID 1500 ROW 9 > TID 1501 ROW 10 > TID 300 ROW 1

Content Item Descriptions

Строка 5

Таблица измерений длинной оси RECIST для каждого целевого очага кодируется как таблица с четырьмя столбцами, состоящая из нескольких строк, описывающих соответствующие значения Tracking Identifier, Finding Site, Laterality и Long Axis в мм по ссылке на другие элементы содержимого. Количество строк не ограничено. Response Criteria используется в качестве имени концепта таблицы.

Пример 4:

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
6	>	CONTAINS	TABLE	EV (111632, DCM, "Anode Target Material")	1	UC	XOR Row 6a	>NCOLUMNS = 2 COLUMN 1 = EV (111526, DCM, "DateTime Started") COLUMN 2 = EV (111632, DCM, "Anode Target Material") COLUMN 2 VALUES = DCID 10016 "Anode Target Material" COLUMN 1 VR = DT COLUMN 2 VR = SQ

Rel with Parent

Concept Name

Req Type

Condition

Value Set Constraint

CONTAINS

TABLE

EV (111632, DCM, "Anode Target Material")

XOR Row 6a

>NCOLUMNS = 2

COLUMN 1 = EV (111526, DCM, "DateTime Started")

COLUMN 2 = EV (111632, DCM, "Anode Target Material")

COLUMN 2 VALUES = DCID 10016 "Anode Target Material"

COLUMN 1 VR = DT

COLUMN 2 VR = SQ

Content Item Descriptions

Строка 6

Таблица значений Anode Target Material кодируется как таблица с двумя столбцами, состоящая из нескольких строк, описывающих соответствующие значения DateTime Started и кодовых значений Anode Target Material. Количество строк не ограничено. Anode Target Material кодируется с помощью кода, выбранного из определённой контекстной группы.

6.2 Специальные соглашения для таблиц шаблонов

6.2.1 Несколько наборов значений в зависимости от разных условий

Когда элемент содержимого может иметь разные наборы значений, каждый из которых зависит от разных условий, описание каждого отдельного случая начинается в отдельной строке таблицы шаблона.

6.2.2 Целевые элементы содержимого отношений

Когда необходимо указать целевой элемент(ы) содержимого отношения, они указываются в строке(ах), непосредственно следующей за исходным элементом содержимого. Уровень вложенности целевого элемента содержимого (или набора целевых элементов содержимого, указанных косвенно посредством включения другого шаблона, см. Section 6.2.3) на единицу больше уровня вложенности соответствующего исходного элемента содержимого, что обозначается увеличением числа символов «>» в поле Nesting Level.

Когда элемент содержимого может быть исходным элементом содержимого нескольких отношений с разными типами отношений и/или разными режимами отношений и/или разными образцами целевого элемента(ов) содержимого, описание каждого отдельного случая начинается в отдельной строке таблицы шаблона.

Когда исходный элемент содержимого отношения имеет VM больше 1, указанный образец целевых элементов содержимого применяется ко всем экземплярам исходного элемента содержимого.

Note

Например, если шаблон указывает, что VM исходного элемента содержимого равно 1-n, и определяет отношение «по значению» к двум элементам содержимого CODE с конкретными ограничениями набора значений, то каждый экземпляр исходного элемента содержимого имеет отношение «по значению» к двум элементам содержимого CODE с указанными ограничениями значений.

Когда исходный элемент содержимого с типом требования U, UC или MC отсутствует (не создан), никакие целевые элементы содержимого этого исходного элемента содержимого не присутствуют, даже если один или несколько целевых элементов содержимого обозначены типом требования M или MC.

Note

Другими словами, потенциальные потомки отсутствуют, если нет родителя.

6.2.3 Включение шаблонов

Шаблон может указывать включение другого шаблона, указав «INCLUDE» в поле Value Type и идентификатор включаемого шаблона в поле Concept Name. Все строки указанного шаблона включаются в вызывающий шаблон, фактически заменяя указанным шаблоном строку, в которой вызвано включение. Является ли включение пользовательской опцией, обязательным или условным, указывается в полях Requirement и Condition. Количество повторений включаемого шаблона указывается в поле VM.

Note

Как определено в Section 6.1.3, не может быть противоречия между типом отношения и режимом строки, включающей другой шаблон, и типом отношения и режимом строк включаемого шаблона.

6.2.3.1 Параметры шаблона

Шаблон, включаемый другим шаблоном, может содержать параметры, которые заменяются значениями, определёнными во вызывающем шаблоне. Параметры могут использоваться для указания кодированных концептов или идентификаторов контекстных групп в полях Concept Name, Condition или Value Set Constraint шаблона.

Включаемый шаблон, принимающий параметры, должен вводиться таблицей, перечисляющей эти параметры, следующей формы:

Имя параметра	Использование параметра
...	...
...	...

Параметры обозначаются именем, начинающимся с символа «$».

Вызывающий шаблон может указывать значение параметров включаемого шаблона по имени в поле Value Set Constraint строки INCLUDE. Параметр во включаемом шаблоне должен быть заменён указанным значением параметра. Указание значения параметра должно иметь одну из следующих форм:

Обозначение	Определение
$parametername = EV or DT (CV, CSD, "CM")	Параметр, передаваемый шаблону, — указанный кодированный термин.
$parametername = (CV, CSD, "CM")	Параметр, передаваемый шаблону, — указанный кодированный термин, используемый как параметр в поле Condition включаемого шаблона.
$parametername = BCID or DCID (CID) CNAME	Параметр, передаваемый шаблону, — контекстная группа.
$parametername = MemberOf {BCID or DCID (CID) CNAME}	Параметр, передаваемый шаблону, — единичный кодированный термин из контекстной группы в фигурных скобках.

Указание значения параметра действительно только для непосредственно включаемого шаблона. Поэтому его необходимо явно переуказывать в промежуточных шаблонах между исходно указывающим шаблоном и целевым шаблоном. Промежуточный шаблон может использовать то же имя параметра, что и вызываемый им шаблон; в этом случае промежуточный шаблон вызывал бы вспомогательный шаблон с указанием в поле Value Set Constraint вида:

$parametername = $parametername

Note

В этом случае левый экземпляр $parametername — это имя во вспомогательном шаблоне, а правый экземпляр — (параметризованное) значение, переданное в текущий шаблон.

Вызывающий шаблон не обязан указывать все параметры включаемых шаблонов. Если параметр не указан, набор значений (термин или контекстная группа) для этого параметра не ограничен. Неограниченное значение в условии (Condition) приведёт к невыполнению условия.

6.2.4 Пост-координированные коды и отношение Has Concept Modifier

Хотя это может не быть явно показано в конкретном шаблоне, использование любого кодированного имени концепта в любом элементе содержимого может определяться в пост-координированной, а не пре-координированной форме, если это явно не запрещено IOD или шаблоном.

Соответственно, любой такой элемент содержимого может иметь любое количество целевых элементов содержимого через отношение «HAS CONCEPT MOD», даже если это явно не указано в шаблоне. Каждый целевой элемент содержимого такого отношения может быть сложнее одного элемента содержимого, если это допускает IOD (то есть пост-координированный концепт потенциально может определяться сложным поддеревом).

6.2.5 Расширение шаблонов

Расширяемый шаблон может быть расширен в приложении, создающем экземпляры SOP, для включения в его определение дополнительных элементов содержимого. Такие элементы содержимого не должны дублировать концепты, для которых в шаблоне определено кодирование. То есть, если в шаблоне предусмотрен способ кодирования концепта, этот концепт не должен кодироваться с помощью другого элемента содержимого в расширении шаблона.

Note

Не требуется, чтобы дополнительные элементы содержимого, включённые в расширение шаблона, размещались в конце шаблона. Дополнительные элементы содержимого могут включаться в любом семантически подходящем месте шаблона, независимо от того, является ли порядок элементов содержимого в шаблоне значимым.

Нерасширяемый шаблон не должен изменяться в приложении путём добавления элементов содержимого в его определение.

Note

Набор элементов содержимого как в расширяемом, так и в нерасширяемом шаблоне может быть изменён в последующих редакциях Стандарта в соответствии с процедурами Комитета по стандартам DICOM.

Нерасширяемый шаблон может включать расширяемый шаблон. При вызове такого шаблона структура содержимого экземпляров SOP, созданных на основе нерасширяемого шаблона, может варьироваться в соответствии с изменяющейся структурой содержимого, допускаемой расширением включаемого шаблона.

Note

Указание такого расширяемого содержимого в нерасширяемом шаблоне может быть желательным, если шаблон определяет, например, фиксированную структуру верхнего уровня, в которую могут быть «подключены» различные структуры более низкого уровня.

7 Спецификации контекстных групп DCMR

Контекстные группы определяют ограничения набора значений для Code Value (0008,0100) (или Long Code Value (0008,0119), или URN Code Value (0008,0120)) и Code Meaning (0008,0104) атрибутов Code Sequence для заданных функциональных или операционных контекстов. Настоящий раздел определяет семантику таблиц контекстных групп DCMR.

7.1 Определение полей таблицы контекстной группы

Контекстные группы описываются с помощью таблиц следующей формы (необязательные столбцы показаны заголовками курсивом):

Ресурсы:: HTML | FHIR JSON | FHIR XML | IHE SVS XML
Ключевое слово:: <Context Group Keyword>
Ключевое слово FHIR:: dicom-cid-<#>-<Context Group Keyword>
Type:: (Non-) Extensible
Версия:: <yyyymmdd> or Без версии
UID:: 1.2.840.10008.6.1.uuuu

Table CID <#>. <Context Group Name>

Coding Scheme Designator	Coding Scheme Version	Code Value	Code Meaning	<Reference Terminology> Equivalent Value	Units
...	...	...	...	...	...
...	...	...	...	...	...

Строка таблицы контекстной группы определяет один кодированный концепт. Каждая таблица контекстной группы:

именуется заголовком
идентифицируется номером CID
идентифицируется версией
идентифицируется ключевым словом
идентифицируется ключевым словом FHIR
имеет присвоенный UID (определённый в PS3.6)
связана с различными файлами ресурсов, содержащими представления контекстной группы (в FHIR JSON, FHIR XML и IHE SVS XML)

Столбцы таблиц состоят из:

Coding Scheme Designator: значение Coding Scheme Designator (0008,0102)
Code Value: значение Code Value (0008,0100) или Long Code Value (0008,0119), или URN Code Value (0008,0120)
Coding Meaning: значение Code Meaning (0008,0104)

В случаях, где это необходимо, также может указываться Coding Scheme Version (значение Coding Scheme Version (0008,0103)). Этот столбец может отсутствовать, если Coding Scheme Version не требуется ни для одного из кодированных концептов в контекстной группе.

Значение, указанное в поле Code Meaning, является допустимым значением для указанного Code Value, но не исключает использования иного синонимичного текста на том же или ином языке.

Note

Некоторые схемы кодирования не определяют эквивалент Code Meaning.
Регистр букв в Code Meaning в целом не имеет значения, за исключением сокращений, используемых в приставках единиц измерения (например, «ml» миллилитр в сравнении с «Ml» мегалитр, или «pV» пиковольт в сравнении с «PV» петавольт).

Если в DCMR требуется дальнейшее описание концепта, представленного кодом (вместо ссылки на внешнюю схему кодирования), оно приводится в отдельной таблице.

Необязательные столбцы могут предоставлять информативное сопоставление кодированных концептов контекстной группы с эталонной терминологией, указанной в заголовке столбца. Типичные эталонные терминологии включают SNOMED CT и UMLS.

Необязательный столбец может определять нормативный базовый или заданный набор единиц измерения для числовых измерений, использующих данный концепт, либо в виде отдельного термина (например, DT ({ratio}, UCUM, "ratio")), списка таких терминов, либо ссылки на контекстную группу (например, DCID 7277 "Units of Diffusion Rate Area Over Time").

Контекстная группа может альтернативно определяться описательной ссылкой на внешне определённую схему кодирования.

Note

См., например, CID 82 “Measurement Unit”.

7.2 Специальные соглашения для таблиц контекстных групп

7.2.1 Включение контекстной группы

Макрос «Include Context Group» — это лаконичный механизм включения (по ссылке) всех строк указанной контекстной группы во вызывающую контекстную группу, фактически заменяющий указанной контекстной группой строку, в которой вызван макрос. Если указан «Include Context Group», он должен быть указан в столбце Concept Name таблицы контекстной группы. Table 7.2.1-1 определяет синтаксис макроса «Include Context Group». Включение может быть вложенным, поскольку включённые контекстные группы сами могут включать другие контекстные группы. Это создаёт возможность циклического включения и множественного включения, и в этом случае контекстная группа должна состоять из транзитивного замыкания набора всех кодированных концептов внутри включённых контекстных групп.

Note

Например, разумно иметь следующие определения контекстных групп:

Context ID 1 включает Context ID 2 и 3
Context ID 2 включает Context ID 4 и 5
Context ID 3 включает Context ID 5 и 6
Context ID 4 содержит a, b, c
Context ID 5 содержит e, f, g
Context ID 6 содержит a, h, i

Содержимым Context ID 1 будет a, b, c, e, f, g, h, i.

Table 7.2.1-1. Макрос Include Context Group

Coding Scheme Designator	Code Value	Code Meaning
…	…	…
Include CID nnn
…	…	…

7.2.2 Единица измерения

Контекстная группа 82 определена так, чтобы включать все единицы измерения, относящиеся к IOD DICOM. Ранее предполагалось, что в ресурс сопоставления будет включён расширяемый список пре-координированных кодов.

DICOM теперь принял стандарт Unified Codes for Units of Measurement (UCUM) для всех единиц измерения. Эта схема кодирования позволяет «конструировать» пре-координированные коды из атомарных компонентов.

Специализация стандарта UCUM в том виде, в котором он используется в DICOM, включает следующие правила:

Coding Scheme Designator указывается как «UCUM»
версия UCUM, из которой сконструирован код, не требуется, так как она не нужна для разрешения неоднозначности в Code Value или Code Meaning; однако нет ограничения на указание версии в Coding Scheme Version
Code Value будет сконструировано из UCUM с использованием «регистрозависимой» (case-sensitive) формы кода UCUM (например, «ml/s»)
Code Meaning, отличное от единицы UCUM, может быть одним из следующих:
- значение «print», указанное в UCUM (например, «mmHg» для Code Value mm[Hg])
- та же строка, что отправлена в Code Value (например, «ml/s»)
- сконструировано из «названий» отдельных компонентов с использованием американизированной формы названия (например, «milliliters/second»)
- сконструировано из «названий» отдельных компонентов с использованием европейской формы названия (например, « millilitres /second»)
В случае единицы UCUM («1» или выражения в фигурных скобках) запрещается использовать «1» в качестве Code Meaning. Annex G предоставляет значения Code Meaning для Code Value (0008,0100), равного 1. Шаблон или контекстная группа могут ограничивать Code Meaning в соответствии со следующими правилами:
- единица UCUM по умолчанию 1 должна использовать один из синонимов Code Meaning, указанных в Annex G
- отношения идентично размерных величин могут использовать ({ratio}, UCUM, "ratio")
- безразмерные числовые оценки могут использовать ({M:N}, UCUM, "range: M:N") для указания минимального и максимального значения, например, ({0:10}, UCUM, "range: 0:10")
- счётные значения с аннотацией UCUM должны всегда использовать текст внутри фигурных скобок в качестве Code Meaning, например, ({masses}, UCUM, "masses")
- составные выражения в фигурных скобках с другими значениями UCUM могут использовать общепринятое клиническое представление, например, ({H.B.}/min, UCUM, "BPM")

Стандарт UCUM указывает, что предпочтительными отображаемыми значениями для кодов deg (градусы плоского угла) и Cel (градусы Цельсия) являются «°» и «°C». Однако символ ° не имеет представления в наборе символов DICOM по умолчанию (ASCII, ISO-IR 6). Поэтому Code Meaning, указанное в настоящей части, использует «deg» и «C». Экземпляры SOP, указывающие Specific Character Set, допускающий символ °, могут использовать значения Code Meaning «°» и «°C».

Note

Code Meaning «C» формально конфликтует с Code Meaning для кулона (Coulomb). В контексте использования в DICOM вероятность путаницы у пользователя из-за отображения Code Meaning считается незначительной, поскольку кулон мало используется в визуализации, а контекст отображаемого Concept Name элемента позволит различить температуру и электрический заряд. Автоматизированная обработка на основе Code Value не должна сталкиваться с проблемой, так как значения Code Value различаются.
Символ ° имеет кодовую позицию Unicode U+00B0 и представляется как 0xB0 в ISO-IR 100 (Latin-1), ISO-IR 101 (Latin-2), ISO-IR 109 (Latin-3), ISO-IR 110 (Latin-4), ISO-IR 126 (Greek), ISO-IR 138 (Hebrew) и ISO-IR 148 (Latin-5). Он не кодируется в ISO-IR 13 (Katakana), ISO-IR 144 (Cyrillic), ISO-IR 127 (Arabic) или ISO-IR 166 (Thai).

7.2.3 Расширение контекстных групп

Приложение может расширять расширяемую контекстную группу, добавляя термины для новых концептов. Приложения не могут подменять другие термины того же концепта в контекстной группе. Приложения не могут добавлять термин, означающий «не указано», «отсутствует», «неизвестно» или подобное; если такой концепт предполагается допустимым, Стандарт уже включит его в контекстную группу. Такое расширение может быть выполнено без изменения идентификатора контекстной группы, но с указанием расширений контекстной группы (Context Group Extensions) (см. PS3.3).

Нерасширяемые контекстные группы не должны изменяться в приложении.

Note

Набор концептов как в расширяемой, так и в нерасширяемой контекстной группе может быть изменён в последующих редакциях Стандарта в соответствии с процедурами Комитета по стандартам DICOM.

8 Схемы кодирования

Table 8-1 перечисляет схемы кодирования (и их обозначения), определённые для использования в DICOM; Table 8-2 перечисляет схемы кодирования HL7v3, на которые есть ссылки для использования в DICOM. Кроме того, может использоваться любая схема кодирования, имеющая запись в реестре схем кодирования HL7 (HL7 v2 Table 0396 или эквивалентном онлайн-реестре), и в этом случае символьное имя HL7 должно использоваться как значение Coding Scheme Designator в DICOM, если оно не конфликтует с записью Table 8-1 и укладывается в представление значения (Value Representation) атрибута Coding Scheme Designator (0008,0102) DICOM. Как указано в HL7 v2 Table 0396, локальные или частные схемы кодирования должны идентифицироваться буквенно-цифровым идентификатором, начинающимся с символов «99».

Note

Более ранняя версия этой таблицы ранее содержалась в Annex D PS3.3.
Дальнейшее описание см. в Section 8.2 “Coding Scheme Designator and Coding Scheme Version” in PS3.3 .
UID схем кодирования приведены только для справки; нормативное определение UID и их значения является ответственностью разработчика схемы кодирования и/или HL7.
Текущая версия HL7 v2 Table 0396 доступна по адресу http://www.hl7.org/special/committees/vocab/table_0396/index.cfm.
Регистрация схем кодирования HL7 доступна по адресу http://www.hl7.org/oid/index.cfm.
Публикация кодов или ссылок на схемы кодирования в DICOM не является предоставлением прав интеллектуальной собственности реализаторам. Использование некоторых схем кодирования может требовать лицензии или приобретения соответствующей публикации схемы кодирования. Реализаторам следует обращаться к соответствующему издателю схемы кодирования; см. также Section 2.
Значения Coding Scheme Name (0008,0115), Coding Scheme Responsible Organization (0008,0116) и Coding Scheme Resources Sequence (0008,0109), если доступны, могут использоваться для заполнения соответствующих необязательных атрибутов Coding Scheme Identification Sequence (0008,0110) в Section C.12.1 “SOP Common Module” in PS3.3 .

Table 8-1. Схемы кодирования

Coding Scheme Designator (0008,0102)	Coding Scheme UID (0008,010C)	Coding Scheme Name (0008,0115)	Coding Scheme Responsible Organization (0008,0116)	Coding Scheme Resources Sequence (0008,0109) Type: URL	Description
ACR	2.16.840.1.113883.6.76	ACR Index	ACR		ACR Index for Radiological Diagnosis Revised, 3^rd Edition 1986
ASTM-sigpurpose	1.2.840.10065.1.12	ASTM E 2084	ASTM		[ASTM E 2084-00] Signature Purpose codes (see Annex A1 of ASTM E 2084), ASTM Subcommittee E 31.20 Data and System Security for Health Information
BARI		BARI			Bypass Angioplasty Revascularization Investigation[Alderman 1992]; endorsed by ACC/AHA Guidelines for Coronary Angiography[Scanlon 1999].
BI		BI-RADS	ACR		ACR Breast Imaging Reporting and Data System [BI-RADS®], Coding Scheme Version (0008,0103) is required; Code Values are section and paragraph identifiers within the publication where the code meaning is defined (e.g., "I.D.1", where I = Breast Imaging Lexicon, D = Special Cases, 1 = Tubular Density, as the Code Value for "Tubular Density"). Note In the HL7 registry, the abbreviation BI is assigned to a different Coding Scheme, specifically the Beth Israel problem list.
C4	2.16.840.1.113883.6.12	CPT-4	AMA		American Medical Association's Current Procedure Terminology 4 (CPT-4)
C5	2.16.840.1.113883.6.82	CPT-5	AMA		American Medical Association's Current Procedure Terminology 5 (CPT-5)
caDSR	2.16.840.1.113883.3.26.2	Cancer Data Standard Repository	NCI		The Public ID is used as the Code Value. These can be looked up as in the following example (the version is required): http://cdebrowser.nci.nih.gov/CDEBrowser/search?dataElementDetails=9/&cdeId=2178693&version=2.1&PageId=DataElementsGroup
CD2	2.16.840.1.113883.6.13	CDT-2	ADA		American Dental Association's (ADA) Current Dental Terminology 2 (CDT-2)
CTV3	2.16.840.1.113883.6.6	Clinical Terms Version 3	UK NHS		Read Codes
DC	1.2.840.10008.2.16.10	Dublin Core	W3C	DOC: http://dublincore.org/documents/1998/09/dces/ DOC: http://www.ietf.org/rfc/rfc2413.txt	Dublin Code Metadata for Resource Discovery. The Code Value is the Label field, e.g., "Creator" (capitalization significant).
DCM	1.2.840.10008.2.16.4	DICOM Controlled Terminology	DICOM	DOC: http://dicom.nema.org/medical/dicom/current/output/chtml/part16/chapter_D.html OWL: ftp://medical.nema.org/MEDICAL/Dicom/Resources/Ontology/DCM/dcm.owl.zip FHIR: http://dicom.nema.org/resources/ontology/DCM	PS3.16 Content Mapping Resource, Annex D (Note that HL7 also specifies an OID of 2.16.840.1.113883.6.31, but deprecates it in favor of 1.2.840.10008.2.16.4).
DCMUID	1.2.840.10008.2.6.1	DICOM UID Registry	DICOM	DOC: http://dicom.nema.org/medical/dicom/current/output/chtml/part06/chapter_A.html FHIR: http://dicom.nema.org/resources/ontology/DCMUID
FMA	2.16.840.1.113883.6.119	FMA	University of Washington, Seattle	DOC: http://sig.biostr.washington.edu/projects/fm/AboutFM.html OWL: http://sig.biostr.washington.edu/share/downloads/fma/release/latest/fma.zip	Digital Anatomist Foundational Model of Anatomy
HPC	2.16.840.1.113883.6.14				Healthcare Financing Administration (HCFA) Common Procedure Coding System (HCPCS)
I10	2.16.840.1.113883.6.3	ICD-10	WHO		International Classification of Diseases revision 10 (ICD-10)
I10C	2.16.840.1.113883.6.90	ICD-10-CM	US DHHS CDC	DOC: http://www.cdc.gov/nchs/icd/icd10cm.htm	International Classification of Diseases, Tenth Revision, Clinical Modification
I10P	2.16.840.1.113883.6.4	ICD-10-PCS	US DHHS CMS	DOC: http://www.cms.gov/Medicare/Coding/ICD10	ICD-10 Procedure Coding System (ICD 10 PCS)
I11	1.2.840.10008.2.16.16	ICD-11	WHO	DOC: http://icd.who.int/browse11/l-m/en	International Classification of Diseases revision 11 (ICD-11)
I9	2.16.840.1.113883.6.42	ICD-9	WHO		International Classification of Diseases revision 9 (ICD-9)
I9C	2.16.840.1.113883.6.2	ICD-9-CM			International Classification of Diseases revision 9, with Clinical Modifications (ICD-9-CM)
ICDO3	2.16.840.1.113883.6.43.1	ICD-O-3	WHO	DOC: http://www.who.int/standards/classifications/other-classifications/international-classification-of-diseases-for-oncology	International Classification of Diseases for Oncology, 3rd Edition Note ICD-O-3 version 3.2 is described at http://www.iacr.com.fr/index.php?option=com_content&view=article&id=149.
IBSI	1.2.840.10008.2.16.13	Image Biomarker Standardisation Initiative		DOC: http://arxiv.org/abs/1612.07003
IETF4646		RFC 4646	IETF	DOC: http://tools.ietf.org/html/rfc4646	[RFC 4646], Tags for Identifying Languages, The Internet Society (2005) [RFC 4646] has been superceded by [RFC 5646].
ISO639_1	2.16.840.1.113883.6.99	ISO 639-1	ISO		[ISO 639-1] Two-letter language codes Note HL7 uses "ISO639-1" for the symbolic name, with a hyphen rather than an underscore
ISO639_2	2.16.840.1.113883.6.100	ISO 639-2	ISO		[ISO 639-2] Three-letter language codes Note HL7 uses "ISO639-2" for the symbolic name, with a hyphen rather than an underscore
ISO3166_1	2.16.1	ISO 3166-1	ISO		[ISO 3166-1] alpha-2 Country Codes Note HL7 uses "ISO3166-1" for the symbolic name, with a hyphen rather than an underscore
ISO5218_1		ISO 5218-1	ISO		Representation of Human Sexes (not used) ISO5218_1, which uses numeric codes, was improperly specified in CID 7455 Sex in earlier editions of the Standard. The alphabetic codes improperly attributed to that Coding Scheme have been added to the DICOM Controlled Terminology, and thus all references to Coding Scheme ISO5218_1 should be considered equivalent to Coding Scheme DCM.
ISO_OID		ISO OID	ISO		[ISO 8824-1] ISO/IEC 8824-1- Information Technology - Abstract Syntax 1 (ASN.1): Specification of Basic Notation, and [ISO 9834-1] - Information technology - Open Systems Interconnection - Procedures for the operation of OSI Registration Authorities: General procedures and top arcs of the ASN.1 Object Identifier tree
ITIS_TSN	1.2.840.10008.2.16.7	ITIS TSN	ITIS	DOC: http://www.itis.gov	A Taxonomic Serial Number (TSN) is a unique, persistent, non-intelligent identifier for a scientific name in the context of the Integrated Taxonomic Information System (ITIS).
LN	2.16.840.1.113883.6.1	LOINC	Regenstrief Institute	DOC: http://loinc.org/ FHIR: http://loinc.org	[LOINC] Logical Observation Identifier Names and Codes
MA	1.2.840.10008.2.16.5	Adult Mouse Anatomy Ontology	The Jackson Laboratory	DOC: http://www.informatics.jax.org/searches/AMA.cgi?id=MA:0002405	Hayamizu TF, Mangan M, Corradi JP, Kadin JA, Ringwald M. The Adult Mouse Anatomical Dictionary: a tool for annotating and integrating data. Genome Biology 2005;6(3):R29. doi:10.1186/gb-2005-6-3-r29. http://www.ncbi.nlm.nih.gov/pmc/articles/PMC1088948/
MAYOASRG	1.2.840.10008.2.16.12	Mayo Clinic Non-radiological Images Specific Body Structure Anatomical Surface Region Guide			The numeric code of entries in the Mayo Clinic Non-radiological Images Specific Body Structure Anatomical Surface Region Guide.
MDC	2.16.840.1.113883.6.24				ISO/IEEE 11073 Medical Device Nomenclature, including all its subsections ([ISO/IEEE 11073-10101], [ISO/IEEE 11073-10101a], [ISO/IEEE 11073-10102], etc.), encoded as decimal strings <partition>:<element>
MDNS					Universal Medical Device (UMD) Nomenclature System
MGI	1.2.840.10008.2.16.8	MGI	The Jackson Laboratory	DOC: http://www.informatics.jax.org/mgihome/nomen/	The MGI ID from the Mouse Genome Initiative (MGI) nomenclature.
MSH	2.16.840.1.113883.6.177	MeSH	NLM	DOC: http://www.nlm.nih.gov/mesh/meshhome.html	US National Library of Medicine (NLM) Medical Subject Headings (MeSH)
NBD	2.16.840.1.113883.15.2				NASPE/BPEG Defibrillator Code Bernstein AD, et al."The NASPE/BPEG Defibrillator Code" PACE, 16:1776-1780, 1993
NBG	2.16.840.1.113883.15.3			DOC: http://www.hrsonline.org/Practice-Guidance/Clinical-Guidelines-Documents/2002-The-Revised-NASPE-BPEG-Generic-Code-for-Antibradycardia-AdaptiveRate-and-Multisite-Pacing	NASPE/BPEG Generic Pacemaker Code (2000) Bernstein AD, et al."The Revised NASPE/BPEG Generic Code for antibradycardia, adaptive-rate, and multisite pacing." Pacing Clin Electrophysiol., 25:260-264, 2002 See http://www.hrsonline.org/Practice-Guidance/Clinical-Guidelines-Documents/2002-The-Revised-NASPE-BPEG-Generic-Code-for-Antibradycardia-AdaptiveRate-and-Multisite-Pacing.
NCDR					American College of Cardiology National Cardiovascular Data Registry™ Cath Lab Module Version 1.1, 1997; Version 2.0b, 1999
NCIt	2.16.840.1.113883.3.26.1.1	NCI Thesaurus	NCI	DOC: http://ncit.nci.nih.gov/
NDC	2.16.840.1.113883.6.69	National Drug Code Directory	US FDA	DOC: http://www.fda.gov/Drugs/InformationOnDrugs/ucm142438.htm DOC: http://www.hl7.org/fhir/ndc.html	The Code Value is the 10 digit 3 segment NDC code with "-" between segments included and no asterisk (leading zero placeholder).
NEU	2.16.840.1.113883.6.210	NeuroNames		DOC: http://braininfo.rprc.washington.edu/aboutBrainInfo.aspx#NeuroNames	The numeric brainInfoID is used as the Code Value.
NICIP	2.16.840.1.113883.2.1.3.2.4.21	NICIP	UK NHS	DOC: http://digital.nhs.uk/article/1108/National-Interim-Clinical-Imaging-Procedure-NICIP-Code-Set	UK National Health Service National Interim Clinical Imaging Procedures (NICIP) Short Code (e.g., "CCHAPC" for CT Thorax abdomen pelvis with contrast)
NPI					HCFA National Provider Identifier
NYUMCCG	1.2.840.10008.2.16.11	New York University Melanoma Clinical Cooperative Group		DOC: http://www.anatomymapper.com/nyu/	The numeric code of entries in the New York University Melanoma Clinical Cooperative Group's numbering system.
PATHLEX	1.3.6.1.4.1.19376.1.8.2.1	PathLex	IHE	DOC: http://www.ihe.net/Technical_Framework/upload/IHE_PAT_Suppl_APSR_Appendix_Value_Sets_2011_03_31.xls DOC: http://purl.bioontology.org/ontology/PATHLEX	The numeric pathLexCode is used as the Code Value.
POS	2.16.840.1.113883.6.50				HCFA Place of Service (POS) Codes for Professional Claims
PUBCHEM_CID	1.2.840.10008.2.16.9	PubChem	NCBI	DOC: http://pubchem.ncbi.nlm.nih.gov/	US National Center for Biotechnology Information (NCBI) PubChem Compound CID.
RADLEX	2.16.840.1.113883.6.256	RadLex	RSNA	DOC: http://www.radlex.org/ FHIR: http://www.radlex.org	[RadLex]
RADELEMENT	1.2.840.10008.2.16.15	RadElement	RSNA	DOC: http://radelement.org/	[RadElement]
RFC3066	2.16.840.1.113883.6.121	RFC 3066	IETF	DOC: http://tools.ietf.org/html/rfc3066	[RFC 3066], Tags for the Identification of Languages, Internet Engineering Task Force Note HL7 uses "IETF3066" for the symbolic name. [RFC 3066] has been superseded by [RFC 4646], which in turn has been superceded by [RFC 5646].
RFC-3881		RFC 3881	IETF	DOC: http://tools.ietf.org/html/rfc3881	[RFC 3881], Security Audit and Access Accountability Message - XML Data Definitions for Healthcare Applications Note A hyphen is used in the Coding Scheme Designator for consistency with historical use in IHE. See IHE ITI TF Vol2a. Section 3.20.7.1.3.
RFC5646	2.16.840.1.113883.6.316	RFC 5646	IETF	DOC: http://tools.ietf.org/html/rfc5646	[RFC 5646], Tags for Identifying Languages, The Internet Society (2009) Note The HL7 OID Registry specifies "rfc5646", not "ietf5646", as the Desired Symbolic Name (inconsistent with the pattern used for [RFC 4646]). [RFC 5646] constitutes one part of IETF Best Current Practice BCP 47 Tags for Identifying Languages, which also includes [RFC 4647] Matching of Language Tags; [RFC 4647] is not relevant in this context.
RO	1.2.840.10008.2.16.14	Radiomics Ontology		DOC: http://bioportal.bioontology.org/ontologies/RO
RRID	1.2.840.10008.2.16.18	RRID	Resource Identification Portal Community	DOC: http://www.rrids.org/	Research Resource Identification
RXNORM	2.16.840.1.113883.6.88	RXNORM	NLM	DOC: http://www.nlm.nih.gov/research/umls/rxnorm/ FHIR: http://www.nlm.nih.gov/research/umls/rxnorm	RxNorm provides normalized names for clinical drugs and links its names to many of the drug vocabularies commonly used in pharmacy management and drug interaction software.
99SDM	2.16.840.1.113883.6.53	SDM	DICOM		SNOMED DICOM Microglossary (Retired) (see Section 8.1)
SCPECG					Standard Communications Protocol for Computer-Assisted Electrocardiography, Draft proposal for ISO Standard, AAMI, Revision 1.3
SNM3	2.16.840.1.113883.6.51	SNOMED V3	SNOMED International	DOC: http://www.snomed.org/	SNOMED International Version 3 (see Section 8.1) Note This Coding Scheme is deprecated. The use of "SNOMED-RT style" Code Values is no longer authorized by SNOMED except for creation by legacy devices, legacy objects in archives, and receiving systems that need to understand them.
SCT	2.16.840.1.113883.6.96	SNOMED CT	SNOMED International	DOC: http://www.snomed.org/ FHIR: http://snomed.info/sct	[SNOMED], using the CT Code Values
SRT	2.16.840.1.113883.6.96	SNOMED CT	SNOMED International	DOC: http://www.snomed.org/	[SNOMED], using the "SNOMED-RT style" Code Values (see Section 8.1) Note HL7 uses "SNM" for the symbolic name. This Coding Scheme is deprecated. The use of "SNOMED-RT style" Code Values is no longer authorized by SNOMED except for creation by legacy devices, legacy objects in archives, and receiving systems that need to understand them.
UBERON	1.2.840.10008.2.16.6	UBERON		DOC: http://uberon.org/	The Uberon ID from the Uberon integrated cross-species ontology covering anatomical structures in animals.
UCUM	2.16.840.1.113883.6.8	UCUM	Regenstrief Institute	DOC: http://unitsofmeasure.org/ucum.html FHIR: http://unitsofmeasure.org	[UCUM] Unified Code for Units of Measure
UMLS	2.16.840.1.113883.6.86	UMLS	NLM	DOC: http://www.nlm.nih.gov/research/umls/	UMLS codes as CUIs making up the values in a coding system
UNS	1.2.840.10008.2.16.17	UNS	SAE International		Unified numbering system (UNS) for metals and alloys [J1086_201210]
UPC	2.16.840.1.113883.6.55				Universal Product Code - Universal Code Council

Table 8-2. Схемы кодирования HL7v3

Coding Scheme Designator	Coding Scheme UID	Description
ActCode	2.16.840.1.113883.5.4
ActPriority	2.16.840.1.113883.5.7
AdministrativeGender	2.16.840.1.113883.5.1
mediaType	2.16.840.1.113883.5.79	RFC2046
NullFlavor	2.16.840.1.113883.5.1008
ObservationInterpretation	2.16.840.1.113883.5.83
Confidentiality	2.16.840.1.113883.5.25
ParticipationType	2.16.840.1.113883.5.90

8.1 SNOMED CT

SNOMED (Систематизированная номенклатура медицины, Systematized Nomenclature of Medicine) Clinical Terms (CT) — предпочтительная система кодирования в DICOM для анатомии, клинических находок, процедур, фармацевтических/биологических продуктов (включая контрастные вещества) и других клинических терминов.

SNOMED имела различные версии, включая SNOMED International (Version 3), выпущенную в 1993 году и пересматривавшуюся до 1998 года, SNOMED Reference Terminology — преемницу SNOMED 3, опубликованную между 1999 и 2001 годами, и SNOMED Clinical Terms — название, используемое с 2002 года. Схема кодирования полностью обратно совместима между SNOMED 3, SNOMED-RT и SNOMED CT. SNOMED CT ввела исключительно числовой набор кодов (ConceptID) в дополнение к прежним буквенно-цифровым кодам (SnomedID), но все концепты терминологии SNOMED имеют как числовой, так и буквенно-цифровой код.

В предыдущих редакциях Стандарта DICOM для кодов SNOMED в DICOM использовались следующие обозначения схем кодирования:

«99SDM» — обозначающий предварительный SNOMED DICOM Microglossary
«SNM3» — обозначающий SNOMED International (Version 3)
«SRT» — изначально обозначавший SNOMED-RT, но позднее использовавшийся для идентификации концептов SNOMED CT с помощью буквенно-цифровых значений Code Value в «стиле SNOMED-RT»

Все случаи использования кодированных терминов SNOMED CT в DICOM теперь обозначаются Coding Scheme Designator «SCT», идентифицирующим их как числовые Concept ID SNOMED CT в качестве Code Value.

Когда принимающая система встречает Coding Scheme Designator «99SDM», «SNM3» или «SRT», буквенно-цифровое значение Code Value в «стиле SNOMED-RT» необходимо сопоставить с соответствующим концептом, обозначенным Concept ID SNOMED CT, присвоенным тому же концепту.

Note

«SRT» в качестве Coding Scheme Designator использовался только в Стандарте DICOM. HL7v2 не стандартизировал Coding Scheme Designator для SNOMED-RT.

При взаимодействии с системами, использующими коды SNOMED CT, прикладные сущности (Application Entities) могут получать и должны отправлять Code Sequence с числовым кодом ConceptID. Такие прикладные сущности несут ответственность за преобразование любого буквенно-цифрового SnomedID с Coding Scheme Designator «SRT», используемого в старых объектах и службах DICOM, в соответствующий числовой код ConceptID.

Note

Некоторые системы, не относящиеся к DICOM, могут использовать Coding Scheme Designator «SNOMED-CT» вместо «SCT», как принято в DICOM.
Политика организации SNOMED в отношении использования «предшествующих версий» (antecedent versions), включая продолжение использования буквенно-цифровых значений Code Value в «стиле SNOMED-RT», описана по адресу: http://www.snomed.org/news-articles/timetable-for-the-withdrawal-of-legacy-snomed-codes.
Поскольку организация SNOMED больше не распространяет справочный набор, содержащий сопоставление SNOMED ID в «стиле SNOMED-RT» с Concept ID SNOMED, полное сопоставление используемых в DICOM значений приведено в Annex O, чтобы позволить реализаторам обрабатывать устаревшие (legacy) объекты от устаревших устройств и архивов.

8.1.1 Использование анатомических концептов SNOMED

В общем случае DICOM использует анатомические концепты с термином «structure» (структура), а не с термином «entire» (целиком). Это важное различие в SNOMED. «Entire» — дочерний концепт по отношению к «structure», имеет более узкое значение и обычно используется применительно к лечебным вмешательствам (например, «удаление всей правой почки»). Он используется в противопоставлении другим родственным дочерним концептам родительского концепта, которые могут обозначать части родительской анатомической структуры. Поскольку визуализация обычно охватывает как саму анатомическую структуру, так и область вокруг неё, либо иногда только часть анатомической структуры, DICOM обычно использует концепты «structure», которые более всеобъемлющи, чем концепты «entire».

8.2 ISO_OID

[ISO 8824-1] и [ISO 9834-1] — стандарты, определённые для генерации идентификаторов объектов, используемых как уникальные идентификаторы (Unique Identifiers) DICOM (см. PS3.5), также могут служить общим механизмом идентификации организаций и объектов, определённых этими организациями.

Когда Coding Scheme Designator — ISO_OID, Code Value должно быть числовой (разделённой точками) формой действительного идентификатора объекта.

Репозиторий известных существующих идентификаторов объектов можно найти по адресу http://www.oid-info.com/index.htm. Например:

присвоенный ISO 9834-1 числовой идентификатор объекта для страны Франция — «1.0.3166.2.2.1.250» (поскольку ISO 3166 определяет способ ведения кодов стран с помощью идентификаторов объектов)
идентификатор объекта для криптографической хеш-функции RIPEMD-160 — «1.0.10118.3.0.49»
идентификатор объекта для таблицы кодов HL7 V2 семейного положения — «2.16.840.1.113883.12.2»

Повторное использование идентификаторов объектов для существующих концептов, не имеющих альтернативной, более подходящей схемы кодирования, совместимой с DICOM, предоставляет механизм, позволяющий избежать определения новых кодов. Например, присвоенные HL7 идентификаторы объектов можно найти по адресу http://www.hl7.org/oid/index.cfm.

Хотя назначение ISO_OID — определять организационные корни для иерархического присвоения идентификаторов объектов, а не непосредственно идентифицировать сами организации, значения организационных корней могут толковаться как идентифицирующие организацию. Например, сама организация DICOM Standards Organization может идентифицироваться значением «1.2.840.10008». См. также CID 5002 “Organization”.

8.3 Устаревшие коды и ожидаемое поведение

По мере сопровождения настоящего Стандарта и внешних схем кодирования коды, указанные как Concept Name, Concept Value и в условиях (Conditions), могут изменяться. Прежние коды считаются устаревшими (Retired), но реализации могут продолжать их отправлять, и от приёмников будет ожидаться способность продолжать распознавать устаревшие коды, включая Code Value и Coding Scheme Designator, даже если текущий Стандарт их больше не публикует.

Показательным примером является произошедший во всём Стандарте переход от использования значений Code Value в «стиле SNOMED-RT» с Coding Scheme Designator «SRT», «SNM3» или «99SDM» к использованию числовых значений Code Value SNOMED CT с Coding Scheme Designator «SCT». Сопоставление устаревших кодов с новыми кодами SNOMED приведено в Annex O.

A Structured Reporting Templates (Normative)

This Annex specifies the content of Standard Templates that may be used by DICOM SR IODs.

General Templates

TID 300 Measurement

This Template provides a general structure for a numeric measurement, together with evaluations of its normality and/or significance, and the inference source(s) for its value.

Table TID 300. Parameters

Parameter Name	Parameter Usage
$Measurement	Coded term or Context Group for Concept Name of measurement
$Units	Measurement Unit
$ModType	Modifier Name for Concept Name of measurement
$ModValue	Modifier Value for Concept Name of measurement
$Method	Value for Measurement Method
$Derivation	Value for Measurement Derivation
$TargetSite	Value(s) for Anatomic Location of measurement
$TargetSiteLaterality	Laterality Value for Anatomic Location of measurement
$TargetSiteMod	Modifier Value for Anatomic Location of measurement
$Equation	Coded term or Context Group for the equation or table from which the measurement was derived or computed
$ImagePurpose	Purpose of Reference for an image used as a source of the measurement
$WavePurpose	Purpose of Reference for a waveform used as a source of the measurement
$RefAuthority	Bibliographic reference or authority for statistical properties of a reference population
$RangeAuthority	Bibliographic reference or authority for the normal range of the measurement
$DerivationParameter	Coded term or Context Group for Concept Name of a derivation parameter
$DerivationParameterUnits	Units of derivation parameter
$PrecoordinatedMeasurementMeaning	Coded value for the precoordinated concept name of measurement

Type:: Extensible
Order:: Significant
Root:: No

Table TID 300. Measurement

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			NUM	$Measurement	1	M		UNITS = $Units
1b	>		INCLUDE	DTID 301 “Measurement Content”	1	M		$ModType = $ModType $ModValue = $ModValue $Method = $Method $Derivation = $Derivation $TargetSite = $TargetSite $TargetSiteLaterality = $TargetSiteLaterality $TargetSiteMod = $TargetSiteMod $Equation = $Equation $ImagePurpose = $ImagePurpose $WavePurpose = $WavePurpose $RefAuthority = $RefAuthority $RangeAuthority = $RangeAuthority $DerivationParameter = $DerivationParameter $DerivationParameterUnits = $DerivationParameterUnits $PrecoordinatedMeasurementMeaning = $PrecoordinatedMeasurementMeaning

Rel with Parent

Concept Name

Req Type

Condition

Value Set Constraint

NUM

$Measurement

UNITS = $Units

INCLUDE

DTID 301 “Measurement Content”

$ModType = $ModType

$ModValue = $ModValue

$Method = $Method

$Derivation = $Derivation

$TargetSite = $TargetSite

$TargetSiteLaterality = $TargetSiteLaterality

$TargetSiteMod = $TargetSiteMod

$Equation = $Equation

$ImagePurpose = $ImagePurpose

$WavePurpose = $WavePurpose

$RefAuthority = $RefAuthority

$RangeAuthority = $RangeAuthority

$DerivationParameter = $DerivationParameter

$DerivationParameterUnits = $DerivationParameterUnits

$PrecoordinatedMeasurementMeaning = $PrecoordinatedMeasurementMeaning

TID 301 Measurement Content

This Template provides a general structure for the content of a numeric measurement, together with evaluations of its normality and/or significance, and the inference source(s) for its value.

Table TID 301. Parameters

Parameter Name	Parameter Usage
$ModType	Modifier Name for Concept Name of measurement
$ModValue	Modifier Value for Concept Name of measurement
$Method	Value for Measurement Method
$Derivation	Value for Measurement Derivation
$TargetSite	Value(s) for Anatomic Location of measurement
$TargetSiteLaterality	Laterality Value for Anatomic Location of measurement
$TargetSiteMod	Modifier Value for Anatomic Location of measurement
$Equation	Coded term or Context Group for the equation or table from which the measurement was derived or computed
$ImagePurpose	Purpose of Reference for an image used as a source of the measurement
$WavePurpose	Purpose of Reference for a waveform used as a source of the measurement
$RefAuthority	Bibliographic reference or authority for statistical properties of a reference population
$PopulationIndex	The index concept whose value is used to select the subset reference population that is relevant to calculating the statistical properties of the current measurement.
$RangeAuthority	Bibliographic reference or authority for the normal range of the measurement
$DerivationParameter	Coded term or Context Group for Concept Name of a derivation parameter
$DerivationParameterUnits	Units of derivation parameter
$PrecoordinatedMeasurementMeaning	Coded value for the precoordinated concept name of measurement

Type:: Extensible
Order:: Significant
Root:: No

Table TID 301. Measurement Content

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
2		HAS CONCEPT MOD	CODE	$ModType	1-n	U		$ModValue
3		HAS CONCEPT MOD	CODE	EV (370129005, SCT, "Measurement Method")	1	U		$Method
4		HAS CONCEPT MOD	CODE	EV (121401, DCM, "Derivation")	1	U		$Derivation
5		HAS CONCEPT MOD	CODE	EV (363698007, SCT, "Finding Site")	1-n	U		$TargetSite
6	>	HAS CONCEPT MOD	CODE	EV (272741003, SCT, "Laterality")	1	U		$TargetSiteLaterality Defaults to DCID 244 “Laterality”
7	>	HAS CONCEPT MOD	CODE	DT (106233006, SCT, "Topographical modifier")	1	U		$TargetSiteMod
8		HAS PROPERTIES	INCLUDE	DTID 310 “Measurement Properties”	1	U		$RefAuthority = $RefAuthority $PopulationIndex = $PopulationIndex $RangeAuthority = $RangeAuthority
9		INFERRED FROM	NUM	$DerivationParameter	1-n	UC	XOR Row 10	UNITS = $DerivationParameterUnits
10		R-INFERRED FROM	NUM	$DerivationParameter	1-n	UC	XOR Row 9	UNITS = $DerivationParameterUnits
11		INFERRED FROM	INCLUDE	DTID 315 “Equation or Table”	1	UC	XOR Row 12	$Equation = $Equation
12		INFERRED FROM	TEXT	DCID 228 “Equation or Table”	1	UC	XOR Row 11
13			INCLUDE	DTID 320 “Image or Spatial Coordinates”	1-n	U		$Purpose = $ImagePurpose
14			INCLUDE	DTID 321 “Waveform or Temporal Coordinates”	1-n	U		$Purpose = $WavePurpose
15			INCLUDE	DTID 1000 “Quotation”	1	U
16		HAS CONCEPT MOD	TEXT	EV (121050, DCM, "Equivalent Meaning of Concept Name")	1	U
16b		HAS CONCEPT MOD	CODE	EV (121050, DCM, "Equivalent Meaning of Concept Name")	1	U		$PrecoordinatedMeasurementMeaning
17		HAS OBS CONTEXT	INCLUDE	DTID 4108 “Tracking Identifier”	1	U
18		INFERRED FROM	COMPOSITE	EV (126100, DCM, "Real World Value Map used for measurement")	1	U		SOP Class UID shall be Real World Value Mapping Storage ("1.2.840.10008.5.1.4.1.1.67")
19		HAS CONCEPT MOD	INCLUDE	DTID 4019 “Algorithm Identification”	1	U

Content Item Descriptions

Rows 2, 3, 4, 5	The HAS CONCEPT MOD items allow the explicit definition of terms for post-coordination of the measurement concept name. Additional post-coordinated modifier terms may be included in a SOP Instance based on this Template, in accordance with section 6.2.4, or as defined by Templates that invoke this Template and explicitly define additional post-coordinated modifiers (e.g., TID 5203).
Row 5	Finding site may be multiple when a region of interest spans multiple anatomical locations and there is not a single pre-coordinated code describing the combination of locations. E.g., when a maligant, inflammatory or traumatic process spans actual or defined anatomical boundaries. There is no requirement that the multiple locations be contiguous.
Rows 9, 10	The INFERRED FROM items allow the specification (by-value or by-reference) of numeric values that were used in the derivation of the numeric measurement of Row 1. The nature of the inference is not explicitly conveyed; it may be implicit in the Concept Names of the measurements. Inference by-reference is valid only in SOP Classes that permit the INFERRED FROM relationship by-reference.
Row 13	Multiple SCOORD Content Items may be necessary to describe the source of the measurement. E.g., the measurement of an angle between two non-intersecting line segments requires two separate POLYLINE SCOORD Content Items with the concept name of (121223, DCM, "Arm of angle") conveyed in $Purpose.
Rows 13, 14	(260753009, SCT, "Source") may be specified for $ImagePurpose or $WavePurpose as a generic Concept Name when there is a desire to avoid having an anonymous (unnamed) Content Item.
Rows 16, 16b	Equivalent Meaning of Concept Name allows the creating application to specify the preferred composed concept name representing the measurement and the associated post-coordinated concept modifiers. The concept modifiers may include those specified in this Template, in a Template that invokes this Template, or at the option of the creating application in accordance with Section 6.2.4. This composed concept name may be rendered by a display application. It may be supplied as text or coded concept or both.
Row 18	Row 18 is a reference to an RWV that describes how measurements were made in units that differ from the stored pixel values in the images referenced in Row 13. E.g., for a PET SUVbw measurement, the mapping from activity/concentration units in the referenced image that was used (and which may be reused for measurements in the future) may be encoded in a referenced RWV instance. This reference overrides any reference in an including Template (such as for a Measurement Group).

TID 310 Measurement Properties

This Template provides the properties of a numeric measurement, including evaluations of its normality and/or significance, its relationship to a reference population, and an indication of its selection from a set of measurements.

Table TID 310. Parameters

Parameter Name	Parameter Usage
$RefAuthority	Bibliographic reference or authority for statistical properties of a reference population
$PopulationIndex	The index concept whose value is used to select the subset reference population that is relevant to calculating the statistical properties of the current measurement.
$RangeAuthority	Bibliographic reference or authority for the normal range of the measurement

Type:: Extensible
Order:: Significant
Root:: No

Table TID 310. Measurement Properties

	VT	Concept Name	VM	Req Type	Value Set Constraint
1	CODE	EV (121402, DCM, "Normality")	1	U	DCID 222 “Normality”
2	INCLUDE	DTID 311 “Measurement Statistical Properties”	1	U	$RefAuthority = $RefAuthority PopulationIndex = $PopulationIndex
3	INCLUDE	DTID 312 “Normal Range Properties”	1	U	$RangeAuthority = $RangeAuthority
4	CODE	EV (121403, DCM, "Level of Significance")	1	U	DCID 220 “Significance Level”
5	NUM	DCID 225 “Measurement Uncertainty Concept”	1-n	U
6	CODE	EV (121404, DCM, "Selection Status")	1	U	DCID 224 “Selection Method”

TID 311 Measurement Statistical Properties

This Template provides the statistical properties of a reference population for a numeric measurement, and/or the position of a measurement in such a reference population.

Table TID 311. Parameters

Parameter Name	Parameter Usage
$RefAuthority	Bibliographic reference or authority for statistical properties of a reference population
$PopulationIndex	The index concept whose value is used to select the subset reference population that is relevant to calculating the statistical properties of the current measurement.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 311. Measurement Statistical Properties

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			NUM	DCID 221 “Measurement Range Concept”	1-n	M
1a	>	HAS CONCEPT MOD	CODE	EV (121418, DCM, "Population Index")	1	UC	IF Row 1 Concept Name = (121416, DCM, "Z-Score of measurement")	$PopulationIndex
2			TEXT	EV (121405, DCM, "Population description")	1	U
3			TEXT	EV (121406, DCM, "Reference Authority")	1	UC	XOR Row 4
4			CODE	EV (121406, DCM, "Reference Authority")	1	UC	XOR Row 3	$RefAuthority

TID 312 Normal Range Properties

This Template provides the normal range of values for a numeric measurement.

Table TID 312. Parameters

Parameter Name	Parameter Usage
$RangeAuthority	Bibliographic reference or authority for the normal range of the measurement

Type:: Extensible
Order:: Significant
Root:: No

Table TID 312. Normal Range Properties

	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1	NUM	DCID 223 “Normal Range Value”	1-n	M
2	TEXT	EV (121407, DCM, "Normal Range description")	1	U
3	TEXT	EV (121408, DCM, "Normal Range Authority")	1	UC	XOR Row 4
4	CODE	EV (121408, DCM, "Normal Range Authority")	1	UC	XOR Row 3	$RangeAuthority

TID 314 Ratio

This Template allows for encoding of numeric ratios with explicit numerator and denominator. The Container Concept Name (with modifiers) is equivalent to the numeric measurement Concept Name of TID 300, and uses the same parameter names.

Note

Compare to FHIR Ratio DataType http://www.hl7.org/fhir/datatypes.html#Ratio

Table TID 314. Parameters

Parameter Name	Parameter Usage
$Measurement	Coded term or Context Group for Concept Name ofratio
$ModType	Modifier Name for Concept Name of ratio
$ModValue	Modifier Value for Concept Name of ratio
$NumUnits	Numerator units of measurement
$DenomUnits	Denominator units of measurement
$RefAuthority	Bibliographic reference or authority for statistical properties of a reference population
$RangeAuthority	Bibliographic reference or authority for the normal range of the measurement

Type:: Extensible
Order:: Significant
Root:: No

Table TID 314. Ratio

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CONTAINER	$Measurement	1	M
2	>	HAS CONCEPT MOD	CODE	$ModType	1-n	U	$ModValue
3	>	CONTAINS	NUM	(C80490, NCIt, "Numerator")	1	M	UNITS = $NumUnits
4	>	CONTAINS	NUM	(C80489, NCIt, "Denominator")	1	M	UNITS = $DenomUnits
5	>	CONTAINS	INCLUDE	DTID 310 “Measurement Properties”	1	U	$RefAuthority = $RefAuthority $RangeAuthority = $RangeAuthority
6	>	HAS OBS CONTEXT	INCLUDE	DTID 4108 “Tracking Identifier”	1	U

TID 315 Equation or Table

Table TID 315. Parameters

Parameter Name	Parameter Usage
$Equation	Coded term or Context Group for the equation or table from which a measurement was derived or computed

Type:: Extensible
Order:: Significant
Root:: No

Table TID 315. Equation or Table

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CODE	DCID 228 “Equation or Table”	1	M	$Equation
2	>	HAS PROPERTIES	NUM		1-n	U
3	>	R-HAS PROPERTIES	NUM		1-n	U

Content Item Descriptions

Row 2	The HAS PROPERTIES allows the specification of the numeric values used as input to the equation or table identified in Row 1.
Row 3	The HAS PROPERTIES allows the specification by-reference of the numeric values used as input to the equation or table. This row is valid only in SOP Classes that permit the HAS PROPERTIES relationship by-reference.

Note

For example, if Row 1 identifies a specific Body Surface Area equation, Rows 2 and 3 can be used to convey (by-value or by-reference) the Patient Height and Patient Weight numeric measurements used in the BSA computation.

TID 320 Image or Spatial Coordinates

This Template provides a general structure for inference from an image, either as a whole, or with specific 2D or 3D spatial coordinates, as a single included Template in the invoking Template. If allowed by the IOD, the Image Content Item may be included by-reference.

Table TID 320. Parameters

Parameter Name	Parameter Usage
$Purpose	Purpose of Reference for an image used as a source of the measurement

Type:: Extensible
Order:: Significant
Root:: No

Table TID 320. Image or Spatial Coordinates

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition
1		INFERRED FROM	IMAGE	$Purpose	1	MC	XOR Rows 2, 3, 6
2		R-INFERRED FROM	IMAGE		1	MC	XOR Rows 1, 3, 6
3		INFERRED FROM	SCOORD	$Purpose	1	MC	XOR Rows 1, 2, 6
4	>	SELECTED FROM	IMAGE		1	MC	XOR Row 5
5	>	R-SELECTED FROM	IMAGE		1	MC	XOR Row 4
6		INFERRED FROM	SCOORD3D	$Purpose	1	MC	XOR Rows 1, 2, 3

Content Item Descriptions

Rows 1, 2, 3, 4, 5, 6

(260753009, SCT, "Source") may be be used as a generic Concept Name when there is a desire to avoid having an anonymous (unnamed) Content Item.

TID 321 Waveform or Temporal Coordinates

This Template provides a general structure for referencing a waveform, either as a whole, or with specific temporal coordinates, as a single included Template in the invoking Template. If allowed by the IOD, the Waveform Content Item may be included by-reference.

Table TID 321. Parameters

Parameter Name	Parameter Usage
$Purpose	Purpose of Reference for a waveform used as a source of the measurement

Type:: Extensible
Order:: Significant
Root:: No

Table TID 321. Waveform or Temporal Coordinates

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition
1		INFERRED FROM	WAVEFORM	$Purpose	1	MC	XOR Rows 2, 3
2		R-INFERRED FROM	WAVEFORM		1	MC	XOR Rows 1, 3
3		INFERRED FROM	TCOORD	$Purpose	1	MC	XOR Rows 1, 2
4	>	SELECTED FROM	WAVEFORM		1	MC	XOR Row 5
5	>	R-SELECTED FROM	WAVEFORM		1	MC	XOR Row 4

Content Item Descriptions

Rows 1, 2, 3, 4, 5

(260753009, SCT, "Source") may be be used as a generic Concept Name when there is a desire to avoid having an anonymous (unnamed) Content Item.

TID 350 References to Supporting Evidence

This Template provides references to supporting evidence in the form of DICOM composite objects. This includes references to images, spatial coordinates on images, and other composite objects, such as Structured Reports.

Type:: Non-Extensible
Order:: Significant
Root:: No

Table TID 350. References to Supporting Evidence

	NL	Rel with Parent	VT	Concept Name	VM	Req Type
1			IMAGE	BCID 7003 “Diagnostic Imaging Report Purpose of Reference”	1-n	U
2			SCOORD	BCID 7003 “Diagnostic Imaging Report Purpose of Reference”	1-n	U
3	>	SELECTED FROM	IMAGE		1	M
4			COMPOSITE	DT (122073, DCM, "Current procedure evidence")	1-n	U
5	>	HAS CONCEPT MOD	CODE	EV (121144, DCM, "Document Title")	1	U

TID 351 Previous Reports

This general Template provides a means to reference previous Structured Report SOP Instances.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 351. Previous Reports

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CONTAINER	EV (111549, DCM, "Previous Reports")	1	M
2	>	CONTAINS	COMPOSITE		1-n	M

Content Item Descriptions

Row 2

Concept Name may be the Root Concept Name (title) of a Structured Report SOP Instance.

TID 400 Reference Location

This TID is a subset of the Reference Location Macro. See Section 10.27 “Reference Location Macro” in PS3.3 .

Type:: Extensible
Order:: Non-Significant
Root:: No

Table TID 400. Reference Location

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CODE	EV (128772, DCM, "Reference Basis")	1	M		BCID 1001 “Anatomical Reference Basis”
2			CODE	EV (128773, DCM, "Reference Geometry")	1	M		BCID 1010 “Reference Geometry - Plane”

TID 1000 Quotation

Unless otherwise specified, content in an SR tree is "directly" observed. When material is quoted (from a source that is either a document or something spoken), then it is necessary to specify:

the fact that one is quoting
who is doing the quoting
the source of the quote
who is being quoted, and who and what the quote is about

This Template establishes a mechanism for quoting by specifying:

the fact that one is quoting, by the presence of the contents of the Template in the tree
that the "observer context" above the invocation of this Template establishes who is doing the quoting
the source of the quote, by the values of the Content Items in this Template
who is being quoted, and who and what the quote is about, by the observation context that is established at the start of the quoted material

This Template may be invoked recursively, to nest quotes within quotes. In essence, the chain of who is quoting whom can be established by maintaining a "stack" of observer context.

If a dimension of observation context is the same in the quoted material as in the enclosing tree, then the observation context does not need to be respecified (e.g., the quote may be about the same subject or procedure). Typically, the observer context would change (unless one were quoting oneself).

In the case of quoting something that was spoken, the "observer" is the person speaking.

TID 1000 is attached using HAS OBS CONTEXT relationships to the top node of the material that is being quoted. The presence of the Quoted Source concept signals the fact that the material is quoted rather than directly observed.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1000. Quotation

	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1	HAS OBS CONTEXT	CODE	EV (121001, DCM, "Quotation Mode")	1	M		EV (121003, DCM, "Document") EV (121004, DCM, "Verbal")
2	HAS OBS CONTEXT	COMPOSITE	EV (121002, DCM, "Quoted Source")	1	MC	Required if quoted material source is a DICOM composite object
3	HAS OBS CONTEXT	INCLUDE	DTID 1001 “Observation Context”	1	M

Rel with Parent

Concept Name

Req Type

Condition

Value Set Constraint

HAS OBS CONTEXT

CODE

EV (121001, DCM, "Quotation Mode")

EV (121003, DCM, "Document")

EV (121004, DCM, "Verbal")

HAS OBS CONTEXT

COMPOSITE

EV (121002, DCM, "Quoted Source")

Required if quoted material source is a DICOM composite object

HAS OBS CONTEXT

INCLUDE

DTID 1001 “Observation Context”

TID 1001 Observation Context

Specifies attributes of observation context that may be defined, extended or replaced at any location in the SR tree.

This includes attributes that specify:

who or what the observation is about ("subject context")
what procedure the observation is about ("procedure study context")
who or what is making the observation ("observer context")

Establishing context includes two aspects of each dimension: identification and description (e.g., patient name and ID vs. patient's age, height or weight).

Whenever one dimension of context is changed or an attribute is added, all attributes of that dimension of context are "flushed", that is they need to be repeated in their entirety. For example, when the subject is changed from patient (name, id) to fetus (number), then the parameters of the patient are discarded. E.g., the patient's ID does not apply to the fetus.

"Extending" the same class and dimension of observation context isn't feasible, since one cannot "null out" or remove a previously set attribute. Any time a dimension of observation context is "replaced", any attributes that are unspecified remain unspecified (i.e., they are not inherited).

Type:: Non-Extensible
Order:: Significant
Root:: No

Table TID 1001. Observation Context

	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1	HAS OBS CONTEXT	INCLUDE	DTID 1002 “Observer Context”	1-n	MC	Required if all aspects of observer context are not inherited.	Defaults to the Attributes of the Author Observer Sequence (0040,A078), or the Verifying Observer Sequence (0040,A073) if the Author Observer Sequence is not present
2	HAS OBS CONTEXT	INCLUDE	DTID 1005 “Procedure Study Context”	1	MC	Required if all aspects of procedure context are not inherited.
3	HAS OBS CONTEXT	INCLUDE	DTID 1006 “Subject Context”	1	MC	Required if all aspects of observation subject context are not inherited.

TID 1002 Observer Context

The observer (person or device) that created the Content Items to which this context applies.

Whenever this Template is invoked, all previously inherited attributes of Observer Context are discarded and replaced.

There may be more than one observer, as this Template may be invoked with a VM 1-n, and both person and device observers. In such a case, the Content Items of TID 1003 “Person Observer Identifying Attributes” and TID 1004 “Device Observer Identifying Attributes” shall be included in the order in which the values of Observer Type are specified. Since TID 1003 “Person Observer Identifying Attributes” and TID 1004 “Device Observer Identifying Attributes” both include a single mandatory Content Item as their first Content Item, which observer is being described can be determined

Type:: Non-Extensible
Order:: Significant
Root:: No

Table TID 1002. Observer Context

	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1	HAS OBS CONTEXT	CODE	EV (121005, DCM, "Observer Type")	1	MC	IF Observer type is device	DCID 270 “Observer Type” Defaults to (121006, DCM, "Person")
2	HAS OBS CONTEXT	INCLUDE	DTID 1003 “Person Observer Identifying Attributes”	1	MC	IFF Row 1 value = (121006, DCM, "Person") or Row 1 is absent
3	HAS OBS CONTEXT	INCLUDE	DTID 1004 “Device Observer Identifying Attributes”	1	MC	IFF Row 1 value = (121007, DCM, "Device")
4	HAS OBS CONTEXT	INCLUDE	DTID 1015 “Person Observer Description”	1	U

TID 1003 Person Observer Identifying Attributes

This Template contains identifying (and optionally descriptive) attributes of persons that are observers.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1003. Person Observer Identifying Attributes

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			PNAME	EV (121008, DCM, "Person Observer Name")	1	M
1a			TEXT	EV (128774, DCM, "Person Observer's Login Name")	1	U
2			TEXT	EV (121009, DCM, "Person Observer's Organization Name")	1	U	Defaults to Value of Institution Name (0008,0080) of the General Equipment Module
3			CODE	EV (121010, DCM, "Person Observer's Role in the Organization")	1	U	BCID 7452 “Organizational Role”
4			CODE	EV (121011, DCM, "Person Observer's Role in this Procedure")	1	U	BCID 7453 “Performing Role”
5	>	HAS CONCEPT MOD	TEXT	EV (128775, DCM, "Identifier within Person Observer's Role")	1	U

Row 5

E.g., "1" or "2", or "A" or "B"; should not recapitulate the role (i.e., should not be "READER1"), since it is used in conjunction with a separate coded concept for the role itself.

TID 1004 Device Observer Identifying Attributes

This Template (derived from the Section C.7.5.1 “General Equipment Module” in PS3.3 ) contains identifying (and optionally descriptive) attributes of devices that are observers.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1004. Device Observer Identifying Attributes

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			UIDREF	EV (121012, DCM, "Device Observer UID")	1	M	Defaults to Value of Device UID (0018,1002) of the General Equipment Module
2			TEXT	EV (121013, DCM, "Device Observer Name")	1	U	Defaults to Value of Station Name (0008,1010) of the General Equipment Module
3			TEXT	EV (121014, DCM, "Device Observer Manufacturer")	1	U	Defaults to Value of Manufacturer (0008,0070) of the General Equipment Module
4			TEXT	EV (121015, DCM, "Device Observer Model Name")	1	U	Defaults to Value of Manufacturer's Model Name (0008,1090) of the General Equipment Module
5			TEXT	EV (121016, DCM, "Device Observer Serial Number")	1	U	Defaults to Value of Device Serial Number (0018,1000) of the General Equipment Module
6			TEXT	EV (121017, DCM, "Device Observer Physical Location During Observation")	1	U
7			CODE	EV (113876, DCM, "Device Role in Procedure")	1-n	U	BCID 7445 “Device Participating Role”
8			TEXT	EV (110119, DCM, "Station AE Title")	1	U
9			UIDREF	EV (121061, DCM, "Device Observer Manufacturer Class UID")	1-n	U	Defaults to Value of Manufacturer's Device Class UID (0018,100B) of the General Equipment Module.
10			CONTAINER	EV (121000, DCM, "Unique Device Identifiers")	1-n	U	Defaults to Value of UDI Sequence (0018,100A) of the General Equipment Module
11	>	CONTAINS	TEXT	EV (74711-3, LN, "Unique Device Identifier")	1	M
12	>	CONTAINS	TEXT	EV (120999, DCM, "Device Description")	1	U

Content Item Descriptions

Row 7	If the device performing the observations has other roles, e.g., as the irradiating device in a dose report, this may be recorded here, if not implicit.
Rows 11, 12	The description can be used to distinguish between multiple UDIs.

TID 1005 Procedure Study Context

This Template contains identifying (and optionally descriptive) attributes of the procedure that is the source of evidence being interpreted.

Whenever this Template is invoked, all previously inherited attributes of Procedure Study Context are discarded and replaced.

Note

If an observed digital image is identified by other than a DICOM UID, a Study Instance UID must be generated for the non-DICOM evidence. The same must be done to document interpretation of hard-copy radiographs generated outside of the scope of the DICOM system.

Type:: Non-Extensible
Order:: Significant
Root:: No

Table TID 1005. Procedure Study Context

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			UIDREF	EV (121018, DCM, "Procedure Study Instance UID")	1	U	Defaults to Value of Study Instance UID (0020, 000D) of the General Study Module
2			UIDREF	EV (121019, DCM, "Procedure Study Component UID")	1-n	U
3			TEXT	EV (121020, DCM, "Placer Number")	1	U
4	>	HAS CONCEPT MOD	TEXT	EV (110190, DCM, "Issuer of Identifier")	1	U
5			TEXT	EV (121021, DCM, "Filler Number")	1	U
6	>	HAS CONCEPT MOD	TEXT	EV (110190, DCM, "Issuer of Identifier")	1	U
7			TEXT	EV (121022, DCM, "Accession Number")	1	U	Defaults to Value of Accession Number (0008,0050) of the General Study Module
8	>	HAS CONCEPT MOD	TEXT	EV (110190, DCM, "Issuer of Identifier")	1	U
9			CODE	EV (121023, DCM, "Procedure Code")	1-n	U	Defaults to Value of Procedure Code Sequence (0008,1032) of the General Study Module

Content Item Descriptions

Rows 5, 6

The issuer shall be formatted in accordance with the HL7v2 Hierarchic Designator Data Type. That format is [ Namespace ID]^[ Universal ID^ Universal ID Type], where Namespace IDidentifies an entity within the local namespace or domain, Universal IDis a universal or unique identifier for an entity, and Universal ID Typespecifies the standard format of the Universal ID (see HL7 v2 Section 2.A.33).

TID 1006 Subject Context

This Template contains identifying (and optionally descriptive) attributes of the subject of the observation.

Subject context identifies (and optionally) describes the subject of the observation, whether it be a patient (human or animal), a fetus (human or animal), a specimen, or a device.

Type:: Non-Extensible
Order:: Significant
Root:: No

Table TID 1006. Subject Context

	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1	CODE	EV (121024, DCM, "Subject Class")	1	MC	IF subject is not the Patient	DCID 271 “Observation Subject Class” Defaults to (121025, DCM, "Patient")
2	INCLUDE	DTID 1007 “Subject Context, Patient”	1	UC	IFF Row 1 value = (121025, DCM, "Patient") or Row 1 is absent	May be used for human or animal patients
3	INCLUDE	DTID 1008 “Subject Context, Fetus”	1	UC	IFF Row 1 value = (121026, DCM, "Fetus")	May be used for human or animal fetuses
4	INCLUDE	DTID 1009 “Subject Context, Specimen”	1	UC	IFF Row 1 value = (121027, DCM, "Specimen")
5	INCLUDE	DTID 1010 “Subject Context, Device”	1	UC	IFF Row 1 value = (121192, DCM, "Device Subject")

TID 1007 Subject Context, Patient

Identifies (and optionally describes) a patient who is the subject.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1007. Subject Context, Patient

	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1	UIDREF	EV (121028, DCM, "Subject UID")	1	U		E.g., SOP Instance UID of Detached Patient Instance
2	PNAME	EV (121029, DCM, "Subject Name")	1	MC	Required if not inherited.	Defaults to Value of Patient's Name (0010,0010) of the Patient Module
3	CODE	EV (121030, DCM, "Subject ID")	1	MC	Required if not inherited.	Defaults to Value of Patient ID (0010,0020) of the Patient Module
4	DATE	EV (121031, DCM, "Subject Birth Date")	1	U		Defaults to Value of Patient's Birth Date (0010,0030) of the Patient Module
5	CODE	EV (121032, DCM, "Subject Sex")	1	U		Defaults to a code equivalent to Value of Patient's Sex (0010,0040) of the Patient Module DCID 7455 “Sex”
5a	CODE	EV (131233, DCM, "Subject Sex Parameters for Clinical Use")	1-n	U		Defaults to a code equivalent to Value of Sex Parameters for Clinical Use Category Sequence (0010,0043) of the Patient Study Module DCID 7459 “Category of Sex Parameters for Clinical Use”
5b	TEXT	EV (131234, DCM, "Subject Sex Parameters for Clinical Use Category Comment")	1	U
5c	TEXT	EV (131235, DCM, "Subject Sex Parameters for Clinical Use Category Reference")	1-n	U
6	NUM	EV (121033, DCM, "Subject Age")	1	U		Defaults to Value equivalent to Value of Patient's Age (0010,1010) of the Patient Study Module UNITS = DCID 7456 “Age Unit”
7	CODE	EV (121034, DCM, "Subject Species")	1	MC	Required if not inherited.	DCID 7454 “Animal Taxonomic Rank Value” Defaults to Coded Entry Value of Patient Species Code Sequence (0010,2202) of the Patient Module, or if absent, (337915000, SCT, "Homo sapiens").
8	CODE	EV (121035, DCM, "Subject Breed")	1	U		Defaults to Coded Entry Value of Patient Breed Code Sequence (0010,2293) of the Patient Module DCID 7480 “Breed”
9	CODE	EV (415229000, SCT, "Racial group")	1-n	U		Defaults to Coded Entry Value(s) of Ethnic Group Code Sequence (0010,2161) of the Patient Module, or if absent, the coded equivalents of the text Values of Ethnic Groups (0010,2162) of the Patient Module, which is defined as "ethnic group(s) or race(s)", or if absent, the coded equivalent of the text Value of retired Ethnic Group (0010,2160). BCID 6099 “Racial Group”

TID 1008 Subject Context, Fetus

Identifies (and optionally describes) a fetus who is the subject.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1008. Subject Context, Fetus

	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1	PNAME	EV (121036, DCM, "Mother of fetus")	1	U		Defaults to an observation subject that is a patient prior to replacing the Observation Subject Class with Fetus.
2	UIDREF	EV (121028, DCM, "Subject UID")	1	U
3	TEXT	EV (121030, DCM, "Subject ID")	1	MC	IF Row 4 is absent
4	TEXT	EV (11951-1, LN, "Fetus ID")	1	MC	IF Row 3 is absent
5	NUM	EV (11878-6, LN, "Number of Fetuses by US")	1	U	XOR Row 6	UNITS = EV (1, UCUM, "no units")
6	NUM	EV (55281-0, LN, "Number of Fetuses")	1	UC	XOR Row 5	UNITS = EV (1, UCUM, "no units")

Content Item Descriptions

Row 2	For longitudinal tracking of individual fetuses
Row 3	For longitudinal tracking of individual fetuses (human readable value e.g., "A" or "1")
Row 4	For separation of multiple fetuses during this procedure e.g., fetus "1" of "2" … not for longitudinal comparisons.; i.e., the "m" of fetus "m" of "n"
Rows 5, 6	The "n" of fetus "m" of "n"; either the code for the ultrasound method (Row 5) or for the non-specific method (Row 6) may be used

TID 1009 Subject Context, Specimen

Identifies (and optionally describes) a specimen that is the subject.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1009. Subject Context, Specimen

	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1	UIDREF	EV (121039, DCM, "Specimen UID")	1	U
2	INCLUDE	DTID 1007 “Subject Context, Patient”	1	UC	IFF the source of the specimen is a human or animal patient
3	TEXT	EV (121041, DCM, "Specimen Identifier")	1	U
4	TEXT	EV (111724, DCM, "Issuer of Specimen Identifier")	1	U
5	CODE	EV (371439000, SCT, "Specimen Type")	1	U		DCID 8103 “Anatomic Pathology Specimen Type”
6	TEXT	EV (111700, DCM, "Specimen Container Identifier")	1	U

Content Item Descriptions

Rows 4, 5, 6

The Issuer of Specimen Identifier shall be formatted in accordance with the HL7 v2 Hierarchic Designator data type (see HL7 v2.6 Section 2.A.33), i.e., [ Namespace ID]^[ Universal ID^Universal ID Type]

TID 1010 Subject Context, Device

Identifies (and optionally describes) a device that is the subject of observations.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1010. Subject Context, Device

	VT	Concept Name	VM	Req Type
1	TEXT	EV (121193, DCM, "Device Subject Name")	1	M
2	UIDREF	EV (121198, DCM, "Device Subject UID")	1	U
3	TEXT	EV (121194, DCM, "Device Subject Manufacturer")	1	U
4	TEXT	EV (121195, DCM, "Device Subject Model Name")	1	U
5	TEXT	EV (121196, DCM, "Device Subject Serial Number")	1	U
6	TEXT	EV (121197, DCM, "Device Subject Physical Location during observation")	1	U

TID 1015 Person Observer Description

This Template includes attributes describing the qualifications of the person observer relevant to the content generated by the observer.

Type:: Extensible
Order:: Non-Significant
Root:: No

Table TID 1015. Person Observer Description

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CODE	EV (128003, DCM, "Reader Specialty")	1	M		DCID 7449 “Reader Specialty”
2	>	HAS PROPERTIES	NUM	EV (C54627, NCIt, "Experience")	1	M		UNITS = EV (a, UCUM, "Year")

TID 1020 Person Participant

This Template describes a person participating in an activity as other than an observer or subject. E.g., for a dose report documenting an irradiating procedure, participants include the person administering the irradiation and the person authorizing the irradiation.

This Template is included with specific contextual parameters from a parent Template.

Table TID 1020. Parameters

Parameter Name	Parameter Usage
$PersonProcedureRole	Coded term or Context Group for the Concept Name that describes the nature of the person's participation in this procedure.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1020. Person Participant

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			PNAME	EV (113870, DCM, "Person Name")	1	M
2	>	HAS PROPERTIES	CODE	EV (113875, DCM, "Person Role in Procedure")	1	M	$PersonProcedureRole
3	>	HAS PROPERTIES	TEXT	EV (113871, DCM, "Person ID")	1	U
4	>	HAS PROPERTIES	TEXT	EV (113872, DCM, "Person ID Issuer")	1	U
5	>	HAS PROPERTIES	TEXT	EV (113873, DCM, "Organization Name")	1	U
6	>	HAS PROPERTIES	CODE	EV (113874, DCM, "Person Role in Organization")	1	U	BCID 7452 “Organizational Role”

Content Item Descriptions

Row 1	The name of the person participating in the role identified in Row 2.
Row 2	The procedural role played by the person in this procedure.
Row 6	The organizational role played by the person in the organization.

TID 1021 Device Participant

This Template describes a device participating in an activity as other than an observer or subject. E.g., for a dose report documenting an irradiating procedure, participants include the irradiating device.

This Template is included with specific contextual parameters from a parent Template.

Table TID 1021. Parameters

Parameter Name	Parameter Usage
$DeviceProcedureRole	Coded term or Context Group for the Concept Name that describes the nature of the device's participation in this procedure.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1021. Device Participant

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CODE	EV (113876, DCM, "Device Role in Procedure")	1	M	$DeviceProcedureRole
2	>	HAS PROPERTIES	TEXT	EV (113877, DCM, "Device Name")	1	U
3	>	HAS PROPERTIES	TEXT	EV (113878, DCM, "Device Manufacturer")	1	M
4	>	HAS PROPERTIES	TEXT	EV (113879, DCM, "Device Model Name")	1	M
5	>	HAS PROPERTIES	TEXT	EV (113880, DCM, "Device Serial Number")	1	M
6	>	HAS PROPERTIES	UIDREF	EV (121012, DCM, "Device Observer UID")	1	M

Content Item Descriptions

Row 1	If no Device Procedure Role is provided, BCID 7445 “Device Participating Role” may be used.
Row 2	This may be used for the name by which the organization manages the device.

TID 1025 Indications for Procedure

Table TID 1025. Parameters

Parameter Name	Parameter Usage
$Findings	Coded term or Context Group for Finding.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1025. Indications for Procedure

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1		CONTAINS	CONTAINER	EV (18785-6, LN, "Indications for Procedure")	1	U
2	>	CONTAINS	CODE	EV (121071, DCM, "Finding")	1-n	U	$Findings
3	>	CONTAINS	TEXT	EV (121071, DCM, "Finding")	1	U

TID 1200 Language Designation

Defines a mechanism for specifying a language, optionally with designation of the country in which that language applies.

Note

For example, the French language could be specified unmodified, or French as written in France or Canada could be distinguished.
The language codes specified in CID 5000 “Language” optionally allow the encoding of the country of language in the Code Value for the language. Encoding of the country of language in a separate subsidiary Concept Modifier Content Item is allowed for backward compatibility with previous releases of the Standard.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1200. Language Designation

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CODE	EV (121045, DCM, "Language")	1	M		DCID 5000 “Language”
2	>	HAS CONCEPT MOD	CODE	EV (121046, DCM, "Country of Language")	1	U		DCID 5001 “Country”

TID 1201 Language of Value

Defines a mechanism for specifying the language in which the value of the parent Content Item (only) is written. Does not specify the language of the Concept Name of the parent Content Item, nor of any other descendants of the parent Content Item.

Note

The language codes specified in CID 5000 “Language” optionally allow the encoding of the country of language in the Code Value for the language. Encoding of the country of language in a separate subsidiary Concept Modifier Content Item is allowed for backward compatibility with previous releases of the Standard.

Type:: Non-Extensible
Order:: Significant
Root:: No

Table TID 1201. Language of Value

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1		HAS CONCEPT MOD	CODE	EV (121047, DCM, "Language of Value")	1	M		DCID 5000 “Language”
2	>	HAS CONCEPT MOD	CODE	EV (121046, DCM, "Country of Language")	1	U		DCID 5001 “Country”

TID 1202 Language of Name and Value

Defines a mechanism for specifying the language in which the value and the Concept Name of the parent Content Item (only) is written. Does not specify the language of any other descendants of the parent Content Item.

Note

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1202. Language of Name and Value

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1		HAS CONCEPT MOD	CODE	EV (121048, DCM, "Language of Name and Value")	1	M		DCID 5000 “Language”
2	>	HAS CONCEPT MOD	CODE	EV (121046, DCM, "Country of Language")	1	U		DCID 5001 “Country”

TID 1204 Language of Content Item and Descendants

Defines a mechanism for specifying the language in which the value and the Concept Name of the parent Content Item and any other descendants of the parent Content Item is written.

Note

Type:: Non-Extensible
Order:: Significant
Root:: No

Table TID 1204. Language of Content Item and Descendants

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1		HAS CONCEPT MOD	CODE	EV (121049, DCM, "Language of Content Item and Descendants")	1	M		DCID 5000 “Language”
2	>	HAS CONCEPT MOD	CODE	EV (121046, DCM, "Country of Language")	1	U		DCID 5001 “Country”

TID 1210 Equivalent Meaning(s) of Concept Name

Defines a mechanism for specifying one or more equivalent meanings for the Concept Name of the parent Content Item.

Type:: Non-Extensible
Order:: Significant
Root:: No

Table TID 1210. Equivalent Meaning(s) of Concept Name

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1		HAS CONCEPT MOD	TEXT	EV (121050, DCM, "Equivalent Meaning of Concept Name")	1-n	MC	XOR Row 3	Plain text equivalent of code meaning of the concept name of the Content Item being modified, in the specified language from the specified country, using the default character set or a character set selected from Specified Character Set
2	>		INCLUDE	DTID 1201 “Language of Value”	1	U
3		HAS CONCEPT MOD	CODE	EV (121050, DCM, "Equivalent Meaning of Concept Name")	1-n	MC	XOR Row 1
4	>		INCLUDE	DTID 1201 “Language of Value”	1	U

Note

A coded equivalent meaning for the Concept Name can also be included using the Attribute Equivalent Code Sequence (0008,0121) in the Concept Name Code Sequence (0040,A043) (see Section 8.9 “Equivalent Code Sequence” in PS3.3 ), though the equivalent code(s) in the Equivalent Code Sequence (0008,0121) need not be the same as those in TID 1210.

TID 1211 Equivalent Meaning(s) of Value

Defines a mechanism for specifying one or more equivalent meanings for the Value of the parent Content Item.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1211. Equivalent Meaning(s) of Value

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1		HAS CONCEPT MOD	TEXT	EV (121051, DCM, "Equivalent Meaning of Value")	1-n	MC	XOR Row 3	Plain text equivalent of code meaning of the value of the Content Item being modified, in the specified language from the specified country, using the default character set or a character set selected from Specified Character Set
2	>		INCLUDE	DTID 1201 “Language of Value”	1	U
3		HAS CONCEPT MOD	CODE	EV (121051, DCM, "Equivalent Meaning of Value")	1-n	MC	XOR Row 1
4	>		INCLUDE	DTID 1201 “Language of Value”	1	U

Note

For example, to describe a longer, more meaningful equivalent (in the same language) for a procedure code than is defined in a Coding Scheme:

CODE: (121023, DCM, "Procedure Code") = (50291CC, ICD10PCS, "IMAGING:CNS:CT:SELLA:LOWOSMOLAR:IT, U, E:2PLANE3D")

> HAS CONCEPT MOD TEXT: (121051, DCM, "Equivalent meaning of value") = "imaging study central nervous system of the sella turcica/pituitary gland with low osmolar contrast intrathecal, unenhanced and enhanced, in two planes with 3D reconstructions"
For example, to specify a concept name and value in both French and English in Canada:

CODE:(91723000, SCT, "Anatomical structure") = (76752008, SCT, "Breast")

> HAS CONCEPT MOD CODE: (121048, DCM, "Language of name and value") = (en-CA, RFC5646, "English, Canada")

> HAS CONCEPT MOD CODE: (121050, DCM, "Equivalent meaning of concept name") = (91723000, SCT, Structure de l'anatomie")

>> HAS CONCEPT MOD CODE: (121047, DCM, " Langue de la valeur ") = (fr-CA, RFC5646, " Français, Canadien ")

> HAS CONCEPT MOD CODE: (121051, DCM, "Equivalent meaning of value") = (76752008, SCT, "Sein")

>> HAS CONCEPT MOD CODE: (121047, DCM, " Langue de la valeur ") = (fr-CA, RFC5646, " Français, Candie ")
3. A coded equivalent meaning for the Concept Value of a CODE Content Item can also be included using the Attribute Equivalent Code Sequence (0008,0121) in the Concept Code Sequence (0040, A168) (see Section 8.9 “Equivalent Code Sequence” in PS3.3 ).

TID 1350 Negation Modifier, Presence of Finding

Concept Name Modifier for negation of the presence of a finding represented by a post-coordinated concept.

Note

For example, negation modifier applied to "distention" in the post-coordinated structure:

CODE: "anatomic location" = "bile duct"

> HAS PROPERTY CODE: "morphology" = "distention"

>> HAS CONCEPT MOD CODE: "presence of property" = "absent"

means: "bile duct distention not present"
The presence-negation modifier modifies the entire post-coordinated concept, not just the Source Content Item of the HAS CONCEPT MOD relationship. The entire branch of the tree from the Content Item is included in the post-coordinated structure that is negated.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1350. Negation Modifier, Presence of Finding

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1		HAS CONCEPT MOD	CODE	EV (121052, DCM, "Presence of property")	1	M		DCID 240 “Present-Absent”

TID 1400 Linear Measurement

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1400. Linear Measurement

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			NUM	DCID 7470 “Linear Measurement”	1	M		UNITS = DCID 7460 “Linear Measurement Unit”
2	>	INFERRED FROM	SCOORD	EV (121055, DCM, "Path")	1	UC	XOR Row 5	GRAPHIC TYPE = {POLYLINE, CIRCLE, ELLIPSE}
3	>>	R-SELECTED FROM	IMAGE		1	MC	XOR Row 4
4	>>	SELECTED FROM	IMAGE		1	MC	XOR Row 3
5	>	INFERRED FROM	SCOORD	EV (121230, DCM, "Path Vertex")	2-n	UC	XOR Row 2	GRAPHIC TYPE = {POINT}
6	>>	R-SELECTED FROM	IMAGE		1	MC	XOR Row 7
7	>>	SELECTED FROM	IMAGE		1	MC	XOR Row 6
8	>	HAS OBS CONTEXT	INCLUDE	DTID 4108 “Tracking Identifier”	1	U

Content Item Descriptions

Row 2	Path shall represent the measured path or a projection of the measured path in the image. The Graphic Type (0070,0023) of the Path SCOORD shall be: an open POLYLINE with two different points (to measure length, diameter, distance, proximity, etc), a CIRCLE or ELLIPSE (to measure circumference) or an open or closed POLYLINE (closed polygon) to measure path length (open) or perimeter (closed).
Row 5	A measured path that traverses two or more images (e.g., the ends of the path are in different cross-sectional plane images) shall be identified by vertices along the path. The Path Vertices shall be ordered by the order of their SCOORD Content Items to identify the measured path. The Graphic Type (0070,0023) of each SCOORD shall be POINT

TID 1401 Area Measurement

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1401. Area Measurement

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			NUM	DCID 7471 “Area Measurement”	1	M		Value shall be > 0 UNITS = DCID 7461 “Area Measurement Unit”
2	>	INFERRED FROM	SCOORD	EV (121056, DCM, "Area Outline")	1	MC	IF concept name of Row 1 = (131184002, SCT, "Area of defined region"), and IFF Row 5 or 6 not present.	GRAPHIC TYPE = not {MULTIPOINT}
3	>>	R-SELECTED FROM	IMAGE		1	MC	XOR Row 4
4	>>	SELECTED FROM	IMAGE		1	MC	XOR Row 3
5	>	INFERRED FROM	IMAGE	EV (121214, DCM, "Referenced Segmentation Frame")	1	MC	IF concept name of Row 1 = (131184002, SCT, "Area of defined region"), and IFF Row 2 or 6 not present.	Reference shall be to a Segmentation Image, with a single value specified in Referenced Frame Number
6	>	R-INFERRED FROM	IMAGE		1	MC	IF concept name of Row 1 = (131184002, SCT, "Area of defined region"), and IFF Row 2 or 5 not present.	Reference shall be to a Segmentation Image, with a single value specified in Referenced Frame Number
7	>	HAS PROPERTIES	CODE	EV (370129005, SCT, "Measurement Method")	1	U		DCID 7473 “General Area Calculation Method”
8	>	HAS OBS CONTEXT	INCLUDE	DTID 4108 “Tracking Identifier”	1	U

Content Item Descriptions

Row 2

A Graphic Type of POINT implies that the object is a single pixel and the object's area is the area of the pixel. Otherwise the type shall be a closed POLYLINE (start and end point the same) or a CIRCLE or an ELLIPSE.

Rows 5, 6

Referenced Frame Number (0008,1160) is an Attribute of the IMAGE Content Item.

If the Referenced Segmentation SOP Instance has Segmentation Type (0062,0001) value BINARY, it identifies the area of defined (measured) region by pixel values in the referenced frame with value 1. For Segmentation Type value FRACTIONAL, the area is computed by an implementation dependent method.

Frame number shall be specified even if the Segmentation SOP Instance has only a single frame.

Row 8

The values of (112039, DCM, "Tracking Identifier") and (112040, DCM, "Tracking Unique Identifier"), if present, shall match the corresponding values of Tracking ID (0062,0020) and Tracking UID (0062,0021), if present, in the corresponding Segment of any Segmentation instance referenced in Row 5.

TID 1402 Volume Measurement

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1402. Volume Measurement

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			NUM	DCID 7472 “Volume Measurement”	1	M		Value shall be > 0 UNITS = DCID 7462 “Volume Measurement Unit”
2	>	INFERRED FROM	SCOORD	EV (121057, DCM, "Perimeter Outline")	1-n	UC	XOR Rows 5, 6	GRAPHIC TYPE = not {MULTIPOINT}
3	>>	R-SELECTED FROM	IMAGE		1	MC	XOR Row 4
4	>>	SELECTED FROM	IMAGE		1	MC	XOR Row 3
5	>	INFERRED FROM	IMAGE	EV (121191, DCM, "Referenced Segment")	1	UC	XOR Rows 2, 6	Reference shall be to a Segmentation Image, with a value specified in Referenced Segment Number
6	>	R-INFERRED FROM	IMAGE		1	UC	XOR Rows 2, 5	Reference shall be to a Segmentation Image, with a value specified in Referenced Segment Number
7	>	HAS PROPERTIES	CODE	EV (370129005, SCT, "Measurement Method")	1	U		DCID 7474 “General Volume Calculation Method”
8	>	HAS OBS CONTEXT	INCLUDE	DTID 4108 “Tracking Identifier”	1	U

Content Item Descriptions

Row 2

The two dimensional perimeter of the volume's intersection with or projection into the image. A Graphic Type of POINT implies that the volume's intersection or projection in a plane is a single pixel. A single pixel projection perimeter cannot cause a volume calculation to become 0.

Otherwise the type shall be a closed POLYLINE (start and end point the same) or a CIRCLE or an ELLIPSE.

Rows 5, 6

Referenced Segment Number (0062,000B) is an Attribute of the IMAGE Content Item.

If the Referenced Segmentation SOP Instance has Segmentation Type (0062,0001) value BINARY, it identifies the defined (measured) volume by pixel/voxel values in the frames of the referenced segment with value 1. For Segmentation Type value FRACTIONAL, the volume is computed by an implementation dependent method.

Segment number shall be specified even if the Segmentation SOP Instance has only a single segment.

Row 8

TID 1404 Numeric Measurement

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1404. Numeric Measurement

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			NUM		1	M		UNITS = DCID 82 “Measurement Unit”
2	>	INFERRED FROM	SCOORD		1-n	UC	XOR Rows 5, 6
3	>>	R-SELECTED FROM	IMAGE		1	MC	XOR Row 4
4	>>	SELECTED FROM	IMAGE		1	MC	XOR Row 3
5	>	R-INFERRED FROM	IMAGE	BCID 7003 “Diagnostic Imaging Report Purpose of Reference”	1-n	UC	XOR Rows 2, 6
6	>	INFERRED FROM	IMAGE	BCID 7003 “Diagnostic Imaging Report Purpose of Reference”	1-n	UC	XOR Rows 2, 5
7	>	HAS OBS CONTEXT	INCLUDE	DTID 4108 “Tracking Identifier”	1	U

Content Item Descriptions

Row 2	The SCOORD may indicate the points or area where the measurement was taken (e.g., a POINT showing the pixel location of a density measurement, or an open POLYLINE of three points showing the calculation of an angle).
Rows 3, 5	Valid only in IODs that permit relationships by-reference.

TID 1406 Three Dimensional Linear Measurement

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1406. Three Dimensional Linear Measurement

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			NUM	DCID 7470 “Linear Measurement”	1	M	UNITS = DCID 7460 “Linear Measurement Unit”
2	>	INFERRED FROM	SCOORD3D	EV (121055, DCM, "Path")	1	M	GRAPHIC TYPE = {POLYLINE, ELLIPSE, POLYGON}
3	>	HAS OBS CONTEXT	INCLUDE	DTID 4108 “Tracking Identifier”	1	U

Content Item Descriptions

Row 2

Path shall represent the measured path in a reference coordinate space. The Graphic Type (0070,0023) of the Path SCOORD3D shall be:

an open POLYLINE with two or more different (x,y,z) triplets (to measure length, diameter, distance, proximity, etc.),
an ELLIPSE (to measure circumference) or
a closed POLYGON to measure perimeter, where the (x,y,z) triplets are coplanar.

TID 1410 Planar ROI Measurements and Qualitative Evaluations

This Template provides a general structure to report measurements for some metric, e.g., density, flow, or concentration, and/or qualitative evaluations, over a planar region of interest in an image. The ROI may be specified by an SCOORD on an image, by a Segmentation Image, by an SCOORD3D defining an area relative to a 3D Frame of Reference, or by a reference to an ROI defined in a radiotherapy Structure Set.

Table TID 1410. Parameters

$Measurement	Coded term or Context Group for Concept Name of measurement
$Units	Units for the measurement
$ModType	Modifier Name for Concept Name of measurement
$ModValue	Modifier Value for Concept Name of measurement
$Method	Value for Measurement Method
$Derivation	Value for Measurement Derivation
$TargetSite	Value for Anatomic Location of measurement
$TargetSiteMod	Modifier Value for Anatomic Location of measurement
$Equation	Coded term or Context Group for the equation or table from which the measurement was derived or computed
$RefAuthority	Bibliographic reference or authority for statistical properties of a reference population
$RangeAuthority	Bibliographic reference or authority for the normal range of the measurement
$DerivationParameter	Coded term or Context Group for Concept Name of a derivation parameter
$DerivationParameterUnits	Units of derivation parameter
$QualType	Evaluations encoded with code or text responses
$QualValue	Value of evaluations encoded with code responses
$QualModType	Modifier Name of evaluations encoded with code or text responses
$QualModValue	Modifier Value of evaluations encoded with code or text responses
$FindingCategory	Category of the finding
$FindingType	Type of the finding
$TrackingID	Value for Tracking Identifier
$TrackingUID	Value for Tracking Unique Identifier

Type:: Extensible
Order:: Non-Significant
Root:: No

Table TID 1410. Planar ROI Measurements and Qualitative Evaluations

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CONTAINER	EV (125007, DCM, "Measurement Group")	1	M
1b	>	HAS OBS CONTEXT	TEXT	EV (C67447, NCIt, "Activity Session")	1	U
2	>	HAS OBS CONTEXT	TEXT	DT (112039, DCM, "Tracking Identifier")	1	U		$TrackingID
3	>	HAS OBS CONTEXT	UIDREF	EV (112040, DCM, "Tracking Unique Identifier")	1	U		$TrackingUID
3a	>	CONTAINS	CODE	EV (276214006, SCT, "Finding category")	1	U		$FindingCategory
3b	>	CONTAINS	CODE	EV (121071, DCM, "Finding")	1	U		$FindingType
3c	>	CONTAINS	CODE	EV (130400, DCM, "Geometric purpose of region")	1	U		BCID 219 “Geometry Graphical Representation”
4	>	HAS OBS CONTEXT	INCLUDE	DTID 1502 “Time Point Context”	1	U
5	>	CONTAINS	SCOORD	EV (111030, DCM, "Image Region")	1	MC	XOR Rows 7, 7b, 8b	GRAPHIC TYPE = not {MULTIPOINT}
6	>>	SELECTED FROM	IMAGE		1	M
7	>	CONTAINS	IMAGE	EV (121214, DCM, "Referenced Segmentation Frame")	1	MC	XOR Rows 5, 7b, 8b	Reference shall be to a Segmentation Image, with a single value specified in Referenced Segment Number (0062,000B). For references to tiled Segmentation Images, one or more values shall be specified in Referenced Frame Number (0008,1160), unless all frames in the referenced Segmentation Image are selected and there is only a single Segment, in which case Referenced Frame Number (0008,1160) will be absent. The referenced tiles shall all be in the same plane. For references to non-tiled Segmentation Images, a single value shall be specified in Referenced Frame Number (0008,1160), unless there is only one frame in the referenced Segmentation Image, in which case Referenced Frame Number (0008,1160) will be absent.
7b	>	CONTAINS	SCOORD3D	EV (111030, DCM, "Image Region")	1	MC	XOR Rows 5, 7, 8b	GRAPHIC TYPE = not {MULTIPOINT, POLYLINE or ELLIPSOID}
8	>	CONTAINS	IMAGE	EV (121233, DCM, "Source image for segmentation")	1	MC	IFF Row 7
8b	>	CONTAINS	COMPOSITE	EV (130488, DCM, "Region in Space")	1	MC	XOR Rows 5, 7, 7b	Reference shall be to an Instance of the RT Structure Set Storage SOP Class.
8c	>>	HAS PROPERTIES	TEXT	EV (130489, DCM, "Referenced Region of Interest Identifier")	1	M		Shall be the value of ROI Number (3006,0022) within the single referenced Item of Structure Set ROI Sequence (3006,0020) of the referenced Instance of the RT Structure Set Storage SOP Class.
9	>	CONTAINS	IMAGE	EV (121200, DCM, "Illustration of ROI")	1	U
9b	>	CONTAINS	IMAGE	EV (130401, DCM, "Visual explanation")	1-n	U
10	>	CONTAINS	COMPOSITE	EV (126100, DCM, "Real World Value Map used for measurement")	1	U		SOP Class UID shall be Real World Value Mapping Storage ("1.2.840.10008.5.1.4.1.1.67")
11	>	CONTAINS	INCLUDE	DTID 1419 “ROI Measurements”	1	U		$Measurement = $Measurement $Units = $Units $ModType = $ModType $ModValue = $ModValue $Method = $Method $Derivation = $Derivation $TargetSite = $TargetSite $TargetSiteMod = $TargetSiteMod $Equation = $Equation $RefAuthority = $RefAuthority $RangeAuthority = $RangeAuthority $DerivationParameter = $DerivationParameter $DerivationParameterUnits = $DerivationParameterUnits
12	>	CONTAINS	CODE	$QualType	1-n	U		$QualValue
12b	>>	HAS CONCEPT MOD	CODE	$QualModType	1-n	U		$QualModValue
13	>	CONTAINS	TEXT	$QualType	1-n	U

Content Item Descriptions

Row 1b	Identifies the session during which the measurements were made. The NCI Thesaurus definition is "time, period, or term devoted to some activity".
Rows 2, 3	The Tracking Identifier and Tracking Unique Identifier are defined as a text label or unique identifier (respectively) used for tracking a finding or feature, potentially across multiple reporting objects, over time. As such, they are distinct from the Observation UID (0040,A171), which is unique identifier of the specific Content Item and its subsidiary Content Items that constitute an individual observation, and would be different for different observations on different occasions of the same finding or feature. The values of these Content Items shall match the corresponding values of Tracking ID (0062,0020) and Tracking UID (0062,0021), if present, in the corresponding Segment of any Segmentation instance referenced in Row 7.
Rows 3a, 3b	The category and type of the finding describe whatever entity (finding or feature) is identified by Rows 2 and 3. E.g., a finding might be a lesion, a tumor, or a reference region (as distinct from its anatomical location, which is encoded in a different Content Item (Finding Site). When spatial localization is by reference to a Segmentation, the category and type may correspond to the values of Segmented Property Category Code Sequence (0062,0003) and Segmented Property Type Code Sequence (0062,000F), respectively. See also CID 7150 “Segmentation Property Category”.
Row 5	To describe an infinitely small area, such as the center of a lesion, a Graphic Type of POINT may be used.
Row 6	(260753009, SCT, "Source") may be used as a generic Concept Name when there is a desire to avoid having an anonymous (unnamed) Content Item.
Row 7	Referenced Frame Number (0008,1160) and Referenced Segment Number (0062,000B) are Attributes of the IMAGE Content Item. If the Referenced Segmentation SOP Instance has Segmentation Type (0062,0001) value BINARY, it identifies the area of defined (measured) region of interest by pixel values in the referenced frame with value 1. For Segmentation Type value FRACTIONAL, the area is computed by an implementation dependent method. Referenced Frame Number (0008,1160) may reference multiple frames in the same plane for tiled Segmentation Images (such as segmentations of Whole Slide Microscopy images).
Row 7b	The area may be defined independently of an image by reference to 3D coordinates in any type of DICOM Reference Coordinate System, whether it be patient-relative (Patient Based Coordinate System), volume-relative (including acquired and presentation state volumes), or whole slide relative (Slide Coordinate System).
Row 8	Identifies the source image that was segmented to identify the ROI, and whose properties are described in this container.
Rows 8b, 8c	A reference to a single ROI that defines a planar ROI, within an RT Structure Set.
Row 9	This referenced image may contain a "screen shot" illustrating a rendered version of the ROI.
Row 9b	This referenced image may contain a visual explanation of how an algorithm produces its results, and may be a "screen shot" of the explanation already superimposed on the source image (e.g., a "heat map"), or a parametric map intended to be superimposed on the source image by the receiving application. The type of image and the type of visual explanation is described in the referenced image's own metadata. More than one referenced image may be present, if there is more than one type of visual explanation, or it needs to span more than one single-frame image.
Row 10	The reference to an RWV in Row 10 allows measurements to be made in units that differ from the stored pixel values in the images referenced elsewhere in the Template. E.g., for a PET SUVbw measurement, the mapping from activity/concentration units in the referenced image that was used (and which may be reused for measurements in the future) may be encoded in a referenced RWV instance. This reference applies to any measurements in included Templates, unless overridden).
Row 11	Measurements may be omitted, for example if it is desired to describe only the location of a finding or to provide categorical information about it.
Rows 12, 12b, 13	Allows encoding a flat list of name-value pairs that are coded questions with coded or text answers, for example, to record categorical observations related to the subject of the measurement group. A single level of coded modifiers may be present.

TID 1411 Volumetric ROI Measurements and Qualitative Evaluations

This Template provides a general structure to report measurements for some metric, e.g., density, flow, or concentration, and/or qualitative evaluations, over a volumetric region of interest in a set of images or a Frame of Reference. The volumetric ROI may be specified by a set of SCOORDs on an image set representing a volume, by a volumetric Segmentation Image, by a volume defined in a Surface Segmentation, by a set of SCOORD3Ds defining a volume relative to a 3D Frame of Reference, or by a reference to an ROI defined in a radiotherapy Structure Set.

Table TID 1411. Parameters

$Measurement	Coded term or Context Group for Concept Name of measurement
$Units	Units for the measurement
$ModType	Modifier Name for Concept Name of measurement
$ModValue	Modifier Value for Concept Name of measurement
$Method	Value for Measurement Method
$Derivation	Value for Measurement Derivation
$TargetSite	Value for Anatomic Location of measurement
$TargetSiteMod	Modifier Value for Anatomic Location of measurement
$Equation	Coded term or Context Group for the equation or table from which the measurement was derived or computed
$RefAuthority	Bibliographic reference or authority for statistical properties of a reference population
$RangeAuthority	Bibliographic reference or authority for the normal range of the measurement
$DerivationParameter	Coded term or Context Group for Concept Name of a derivation parameter
$DerivationParameterUnits	Units of derivation parameter
$QualType	Evaluations encoded with code or text responses
$QualValue	Value of evaluations encoded with code responses
$QualModType	Modifier Name of evaluations encoded with code or text responses
$QualModValue	Modifier Value of evaluations encoded with code or text responses
$FindingCategory	Category of the finding
$FindingType	Type of the finding
$TrackingID	Value for Tracking Identifier
$TrackingUID	Value for Tracking Unique Identifier

Type:: Extensible
Order:: Non-Significant
Root:: No

Table TID 1411. Volumetric ROI Measurements and Qualitative Evaluations

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CONTAINER	EV (125007, DCM, "Measurement Group")	1	M
1b	>	HAS OBS CONTEXT	TEXT	EV (C67447, NCIt, "Activity Session")	1	U
2	>	HAS OBS CONTEXT	TEXT	DT (112039, DCM, "Tracking Identifier")	1	U		$TrackingID
3	>	HAS OBS CONTEXT	UIDREF	EV (112040, DCM, "Tracking Unique Identifier")	1	U		$TrackingUID
3a	>	CONTAINS	CODE	EV (276214006, SCT, "Finding category")	1	U		$FindingCategory
3b	>	CONTAINS	CODE	EV (121071, DCM, "Finding")	1	U		$FindingType
3c	>	CONTAINS	CODE	EV (130400, DCM, "Geometric purpose of region")	1	U		BCID 219 “Geometry Graphical Representation”
4	>	HAS OBS CONTEXT	INCLUDE	DTID 1502 “Time Point Context”	1	U
5	>	CONTAINS	SCOORD	EV (111030, DCM, "Image Region")	1-n	MC	XOR Rows 7, 10, 12b	GRAPHIC TYPE = not {MULTIPOINT}
6	>>	SELECTED FROM	IMAGE		1	M
7	>	CONTAINS	IMAGE	EV (121191, DCM, "Referenced Segment")	1	MC	XOR Rows 5, 10, 12b	Reference shall be to a Segmentation Image or Surface Segmentation object, with a single value specified in Referenced Segment Number
10	>	CONTAINS	SCOORD3D	EV (121231, DCM, "Volume Surface")	1-n	MC	XOR Rows 5, 7, 12b	If one item, GRAPHIC TYPE = {ELLIPSOID or POINT} If more than one item, GRAPHIC TYPE = {POLYGON or ELLIPSE}
11	>	CONTAINS	IMAGE	EV (121233, DCM, "Source image for segmentation")	1-n	MC	XOR Row 12 and IFF (Row 7 or Row 10)
12	>	CONTAINS	UIDREF	EV (121232, DCM, "Source series for segmentation")	1	MC	XOR Row 11 and IFF (Row 7 or Row 10)
12b	>	CONTAINS	COMPOSITE	EV (130488, DCM, "Region in Space")	1	MC	XOR Rows 5, 7, 10	Reference shall be to an Instance of the RT Structure Set Storage SOP Class.
12c	>>	HAS PROPERTIES	TEXT	EV (130489, DCM, "Referenced Region of Interest Identifier")	1	M		Shall be the value of ROI Number (3006,0022) within the single referenced Item of Structure Set ROI Sequence (3006,0020) of the referenced Instance of the RT Structure Set Storage SOP Class.
13	>	CONTAINS	IMAGE	EV (121200, DCM, "Illustration of ROI")	1-n	U
13b	>	CONTAINS	IMAGE	EV (130401, DCM, "Visual explanation")	1-n	U
14	>	CONTAINS	COMPOSITE	EV (126100, DCM, "Real World Value Map used for measurement")	1	U		SOP Class UID shall be Real World Value Mapping Storage ("1.2.840.10008.5.1.4.1.1.67")
15	>	CONTAINS	INCLUDE	DTID 1419 “ROI Measurements”	1	U		$Measurement = $Measurement $Units = $Units $ModType = $ModType $ModValue = $ModValue $Method = $Method $Derivation = $Derivation $TargetSite = $TargetSite $TargetSiteMod = $TargetSiteMod $Equation = $Equation $RefAuthority = $RefAuthority $RangeAuthority = $RangeAuthority $DerivationParameter = $DerivationParameter $DerivationParameterUnits = $DerivationParameterUnits
16	>	CONTAINS	CODE	$QualType	1-n	U		$QualValue
16b	>>	HAS CONCEPT MOD	CODE	$QualModType	1-n	U		$QualModValue
17	>	CONTAINS	TEXT	$QualType	1-n	U

Content Item Descriptions

Row 1b	Identifies the session during which the measurements were made. The NCI Thesaurus definition is "time, period, or term devoted to some activity".
Rows 2, 3	The Tracking Identifier and Tracking Unique Identifier are defined as a text label or unique identifier (respectively) used for tracking a finding or feature, potentially across multiple reporting objects, over time. As such, they are distinct from the Observation UID (0040,A171), which is unique identifier of the specific Content Item and its subsidiary Content Items that constitute an individual observation, and would be different for different observations on different occasions of the same finding or feature. The values of these Content Items shall match the corresponding values of Tracking ID (0062,0020) and Tracking UID (0062,0021), if present, in the corresponding Segment of any Segmentation instance referenced in Row 7.
Rows 3a, 3b	The type and category of the finding describe whatever entity (finding or feature) is identified by Rows 2 and 3. E.g., a finding might be a lesion, a tumor, or a reference region (as distinct from its anatomical location, which is encoded in a different Content Item (Finding Site). When spatial localization is by reference to a Segmentation, the category and type may correspond to the values of Segmented Property Category Code Sequence (0062,0003) and Segmented Property Type Code Sequence (0062,000F), respectively. See also CID 7150 “Segmentation Property Category”.
Row 5	Even though the coordinates are image-relative, not every image slice within the spatial extent of the ROI is required to be encoded. That is, the ROI may be more coarsely sampled than the image slices, and may be irregularly sampled, and the omission of a contour on a slice does not mean that it is omitted from the ROI. For example, a user may not draw an outline on every slice. However, failure to include every intermediate slice does give rise to this potential ambiguity, and is discouraged.
Rows 5, 7, 10	A single invocation of TID 1411 defines the entire spatial extent defined of a single ROI. A single structure with multiple fragments disconnected in spatial extent needs to be described as separate ROIs, in separate invocations of TID 1411, with different Tracking Identifiers and Tracking Unique Identifiers, but the same Finding.
Rows 5, 10	To describe an infinitely small volume, such as the center of a lesion, a Graphic Type of POINT may be used.
Row 6	(260753009, SCT, "Source") may be used as a generic Concept Name when there is a desire to avoid having an anonymous (unnamed) Content Item.
Rows 6, 7	Referenced Segment Number (0062,000B) is an Attribute of the IMAGE Content Item, and shall be present with a single value. If the Referenced SOP Instance is a Segmentation Image, it shall have a defined Frame of Reference. If it has Segmentation Type (0062,0001) value BINARY, it identifies the volume of defined (measured) region of interest by voxel values in the referenced segment with value 1. If it has Segmentation Type value FRACTIONAL, the volume is defined by an implementation dependent method. The extent, sampling rate and orientation of the Segmentation are not required to match that of corresponding image slices (if any), identified in Row 11 or referenced from the Segmentation. If the referenced SOP Instance is a Surface Segmentation, the referenced segment shall constitute a finite volume. It identifies the volume of the defined (measured) region of interest by the interior of the finite volume. Segment number shall be specified even if the Segmentation SOP Instance has only a single segment.
Row 10	Either a single item describing a closed volumetric surface, or multiple items describing a set of parallel closed coplanar areas (contours) is specified. The sampling rate and orientation of the contours is not required to match that of any image slices (if any), nor are the in-plane or cross-plane sampling rates required to be regular.
Row 11	Identifies the source images that were segmented to identify the ROI, when, for example a subset of images in a series was used.
Row 12	Identifies the source series of images that were segmented to identify the ROI, when, for example an entire set of images in a series was used.
Rows 12b, 12c	A reference to a single ROI that defines a volumetric ROI, within an RT Structure Set.
Row 13	These referenced images may contain "screen shot" illustrating rendered versions of the ROI.
Row 13b	This referenced image may contain a visual explanation of how an algorithm produces its results, and may be a "screen shot" of the explanation already superimposed on the source image (e.g., a "heat map"), or a parametric map intended to be superimposed on the source image by the receiving application. The type of image and the type of visual explanation is described in the referenced image's own metadata. More than one referenced image may be present, if there is more than one type of visual explanation, or it needs to span more than one single-frame image.
Row 14	The reference to an RWV in Row 14 allows measurements to be made in units that differ from the stored pixel values in the images referenced elsewhere in the Template. E.g., for a PET SUVbw measurement, the mapping from activity/concentration units in the referenced image that was used (and which may be reused for measurements in the future) may be encoded in a referenced RWV instance. This reference applies to any measurements in included Templates, unless overridden).
Row 15	Measurements may be omitted, for example if it is desired to describe only the location of a finding or to provide categorical information about it.
Rows 16, 16b, 17	Allows encoding a flat list of name-value pairs that are coded questions with coded or text answers, for example, to record categorical observations related to the subject of the measurement group. A single level of coded modifiers may be present.

TID 1419 ROI Measurements

This Template encodes measurements for some metric, e.g., density, flow, or concentration.

Table TID 1419. Parameters

$Measurement	Coded term or Context Group for Concept Name of measurement
$Units	Units for the measurement
$ModType	Modifier Name for Concept Name of measurement
$ModValue	Modifier Value for Concept Name of measurement
$Method	Value for Measurement Method
$Derivation	Value for Measurement Derivation
$TargetSite	Value(s) for Anatomic Location of measurement
$TargetSiteMod	Modifier Value for Anatomic Location of measurement
$Equation	Coded term or Context Group for the equation or table from which the measurement was derived or computed
$RefAuthority	Bibliographic reference or authority for statistical properties of a reference population
$RangeAuthority	Bibliographic reference or authority for the normal range of the measurement
$DerivationParameter	Coded term or Context Group for Concept Name of a derivation parameter
$DerivationParameterUnits	Units of derivation parameter

Type:: Extensible
Order:: Non-Significant
Root:: No

Table TID 1419. ROI Measurements

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1		HAS CONCEPT MOD	CODE	EV (370129005, SCT, "Measurement Method")	1	U		$Method
2		HAS CONCEPT MOD	CODE	EV (363698007, SCT, "Finding Site")	1-n	U		$TargetSite
3	>	HAS CONCEPT MOD	CODE	EV (272741003, SCT, "Laterality")	1	U		DCID 244 “Laterality”
4	>	HAS CONCEPT MOD	CODE	DT (106233006, SCT, "Topographical modifier")	1	U		$TargetSiteMod
4b		HAS CONCEPT MOD	INCLUDE	DTID 4019 “Algorithm Identification”	1	U
5			NUM	$Measurement	1-n	M		UNITS = $Units
6	>	HAS CONCEPT MOD	CODE	$ModType	1-n	U		$ModValue
7	>	HAS CONCEPT MOD	CODE	EV (370129005, SCT, "Measurement Method")	1	U		$Method
8	>	HAS CONCEPT MOD	CODE	EV (121401, DCM, "Derivation")	1	U		$Derivation
9	>	HAS CONCEPT MOD	CODE	EV (363698007, SCT, "Finding Site")	1-n	U		$TargetSite
10	>>	HAS CONCEPT MOD	CODE	EV (272741003, SCT, "Laterality")	1	U		DCID 244 “Laterality”
11	>>	HAS CONCEPT MOD	CODE	DT (106233006, SCT, "Topographical modifier")	1	U		$TargetSiteMod
12	>	HAS PROPERTIES	INCLUDE	DTID 310 “Measurement Properties”	1	U		$RefAuthority = $RefAuthority $RangeAuthority = $RangeAuthority
13	>	INFERRED FROM	NUM	$DerivationParameter	1-n	UC	XOR Row 14	$DerivationParameterUnits
14	>	R-INFERRED FROM	NUM	$DerivationParameter	1-n	UC	XOR Row 13	$DerivationParameterUnits
14b	>	INFERRED FROM	CODE	$DerivationParameter	1-n	U
14c	>	INFERRED FROM	TEXT	$DerivationParameter	1-n	U
15	>	INFERRED FROM	INCLUDE	DTID 315 “Equation or Table”	1	UC	XOR Row 16	$Equation = $Equation
16	>	INFERRED FROM	TEXT	DCID 228 “Equation or Table”	1	UC	XOR Row 15
17	>		INCLUDE	DTID 1000 “Quotation”	1	U
18	>	HAS CONCEPT MOD	TEXT	EV (121050, DCM, "Equivalent Meaning of Concept Name")	1	U
19	>	CONTAINS	COMPOSITE	EV (126100, DCM, "Real World Value Map used for measurement")	1	U		SOP Class UID shall be Real World Value Mapping Storage ("1.2.840.10008.5.1.4.1.1.67")
20	>	HAS CONCEPT MOD	INCLUDE	DTID 4019 “Algorithm Identification”	1	U

Content Item Descriptions

Rows 2, 9	Finding site may be multiple when a region of interest spans multiple anatomical locations and there is not a single pre-coordinated code describing the combination of locations. E.g., when a maligant, inflammatory or traumatic process spans actual or defined anatomical boundaries. There is no requirement that the multiple locations be contiguous.
Row 4b	Describes the algorithm that applies to all measurements in Row 5, unless overridden within the individual measurement at Row 20.
Row 5	Specifies the metric for which measurements are reported, e.g., density, flow, or concentration. This metric is computed at each sample point (e.g., pixel or voxel) in an ROI (defined in the invoking Template), but those individual point measurements are not encoded. Instead, just the summary measurements for the ROI are encoded, and the means of computing a single value is defined in Row 8 Derivation (e.g., mean).
Rows 1, 2, 3, 4, 6, 7, 8, 9, 10, 11	The HAS CONCEPT MOD items allow the explicit definition of terms for post-coordination of the measurement concept name. Additional post-coordinated modifier terms may be included in a SOP Instance based on this Template, in accordance with section 6.2.4, or as defined by Templates that invoke this Template and explicitly define additional post-coordinated modifiers.
Rows 13, 14	The INFERRED FROM items allow the specification (by-value or by-reference) of numeric values that were used in the derivation of the numeric measurement of Row 1. The nature of the inference is not explicitly conveyed; it may be implicit in the Concept Names of the measurements. Inference by-reference is valid only in SOP Classes that permit the INFERRED FROM relationship by-reference.
Row 18	Equivalent Meaning of Concept Name allows the creating application to specify the preferred composed concept name representing the measurement and the associated post-coordinated concept modifiers. The concept modifiers may include those specified in this Template, in a Template that invokes this Template, or at the option of the creating application in accordance with section 6.2.4. This composed concept name may be rendered by a display application.
Row 19	The reference to an RWV in Row 19 allows measurements to be made in units that differ from the stored pixel values in the images referenced in the parent Template. E.g., for a PET SUVbw measurement, the mapping from activity/concentration units in the referenced image that was used (and which may be reused for measurements in the future) may be encoded in a referenced RWV instance. This reference overrides any reference in an including Template (such as for a Measurement Group).

TID 1420 Measurements Derived From Multiple ROI Measurements

This Template encodes measurements for some metric, e.g., density, flow, or concentration, which are acquired over some defined sampling (e.g., over successive time slots in a dynamic contrast enhanced acquisition), or of some comparison between different ROIs.

Table TID 1420. Parameters

$Measurement	Coded term or Context Group for Concept Name of measurement
$MeasurementUnits	Units for the measurement
$ModType	Modifier Name for Concept Name of measurement
$ModValue	Modifier Value for Concept Name of measurement
$Method	Value for Measurement Method
$Derivation	Value for Measurement Derivation
$TargetSite	Value for Anatomic Location of measurement
$TargetSiteMod	Modifier Value for Anatomic Location of measurement
$Equation	Coded term or Context Group for the equation or table from which the measurement was derived or computed
$RefAuthority	Bibliographic reference or authority for statistical properties of a reference population
$RangeAuthority	Bibliographic reference or authority for the normal range of the measurement
$StatisticalRefAuthority	Bibliographic reference or authority for statistical properties of a reference population
$StatisticalRangeAuthority	Bibliographic reference or authority for the normal range of the measurement
$DerivationParameter	Coded term or Context Group for Concept Name of a derivation parameter
$DerivationParameterUnits	Units of derivation parameter

Type:: Extensible
Order:: Non-Significant
Root:: No

Table TID 1420. Measurements Derived From Multiple ROI Measurements

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			NUM	DCID 7465 “Measurement Derived From Multiple ROI Measurements”	1-n	M
1b	>	HAS CONCEPT MOD	INCLUDE	DTID 4019 “Algorithm Identification”	1	U
2	>	R-INFERRED FROM	INCLUDE	DTID 1410 “Planar ROI Measurements and Qualitative Evaluations”	1-n	MC	XOR Row 3	$Measurement = $Measurement $Units = $MeasurementUnits $ModType = $ModType $ModValue = $ModValue $Method = $Method $Derivation = $Derivation $TargetSite = $TargetSite $TargetSiteMod = $TargetSiteMod $Equation = $Equation $RefAuthority = $RefAuthority $RangeAuthority = $RangeAuthority $DerivationParameter = $DerivationParameter $DerivationParameterUnits = $DerivationParameterUnits
3	>	R-INFERRED FROM	INCLUDE	DTID 1411 “Volumetric ROI Measurements and Qualitative Evaluations”	1-n	MC	XOR Row 2	$Measurement = $Measurement $Units = $MeasurementUnits $ModType = $ModType $ModValue = $ModValue $Method = $Method $Derivation = $Derivation $TargetSite = $TargetSite $TargetSiteMod = $TargetSiteMod $Equation = $Equation $RefAuthority = $RefAuthority $RangeAuthority = $RangeAuthority $DerivationParameter = $DerivationParameter $DerivationParameterUnits = $DerivationParameterUnits
4	>	HAS PROPERTIES	INCLUDE	DTID 310 “Measurement Properties”	1	U		$RefAuthority = $RefAuthority $RangeAuthority = $RangeAuthority

Content Item Descriptions

Row 1	Specifies the type of derived measurement reported, e.g., the mean of the individual ROI mean density values, or a similarity measure of the number of pixels or voxels in the ROIs. Note that the units may be different from the units in the ROI measurements
Row 1b	Describes the algorithm used to produced the derived measurement, as opposed to the referenced measurements from which this measurement was derived.
Rows 2, 3	The measurement values of each ROI that contributes to the derived measurement, e.g., the mean density within an ROI, the number of pixels or voxels in an ROI. These are specified by reference, so as to not have to repeat the ROI information when it contributes to multiple derived measurements (e.g., if both mean and SD of ROI mean density values were specified).

TID 1500 Measurement Report

This Root Template encodes a list of Measurement Groups each containing lists of measurements, together with any derived measurements.

Each Measurement Group is identified by Tracking ID and UIDs.

An image library is available to describe characteristics of the images referenced by the measurements, if any.

Type:: Extensible
Order:: Non-Significant
Root:: Yes

Table TID 1500. Measurement Report

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CONTAINER	DCID 7021 “Measurement Report Document Title”	1	M
2	>	HAS CONCEPT MOD	INCLUDE	DTID 1204 “Language of Content Item and Descendants”	1	U
3	>	HAS OBS CONTEXT	INCLUDE	DTID 1001 “Observation Context”	1	M
4	>	HAS CONCEPT MOD	CODE	EV (121058, DCM, "Procedure reported")	1-n	U		BCID 100 “Quantitative Diagnostic Imaging Procedure”
5	>	CONTAINS	INCLUDE	DTID 1600 “Image Library”	1	U
6	>	CONTAINS	CONTAINER	EV (126010, DCM, "Imaging Measurements")	1	MC	IF Row 10 and Row 12 are absent
6b	>>	HAS CONCEPT MOD	INCLUDE	DTID 4019 “Algorithm Identification”	1	U
7	>>	CONTAINS	INCLUDE	DTID 1410 “Planar ROI Measurements and Qualitative Evaluations”	1-n	U		$Measurement = BCID 218 “Quantitative Image Feature” $Units = BCID 7181 “Abstract Multi-dimensional Image Model Component Unit” $Derivation = BCID 7464 “General Region of Interest Measurement Modifier” $Method = BCID 6147 “Response Criteria” $QualModType = BCID 210 “Qualitative Evaluation Modifier Type” $QualModValue = BCID 211 “Qualitative Evaluation Modifier Value”
8	>>	CONTAINS	INCLUDE	DTID 1411 “Volumetric ROI Measurements and Qualitative Evaluations”	1-n	U		$Measurement = BCID 218 “Quantitative Image Feature” $Units = BCID 7181 “Abstract Multi-dimensional Image Model Component Unit” $Derivation = BCID 7464 “General Region of Interest Measurement Modifier” $Method = BCID 6147 “Response Criteria” $QualModType = BCID 210 “Qualitative Evaluation Modifier Type” $QualModValue = BCID 211 “Qualitative Evaluation Modifier Value”
9	>>	CONTAINS	INCLUDE	DTID 1501 “Measurement and Qualitative Evaluation Group”	1-n	U		$Measurement = BCID 218 “Quantitative Image Feature” $ImagePurpose = BCID 7551 “Generic Purpose of Reference to Images and Coordinates in Measurement” $Units = BCID 7181 “Abstract Multi-dimensional Image Model Component Unit” $Derivation = BCID 7464 “General Region of Interest Measurement Modifier” $Method = BCID 6147 “Response Criteria” $QualModType = BCID 210 “Qualitative Evaluation Modifier Type” $QualModValue = BCID 211 “Qualitative Evaluation Modifier Value”
10	>	CONTAINS	CONTAINER	EV (126011, DCM, "Derived Imaging Measurements")	1	MC	IF Row 6 and Row 12 are absent
10b	>>	HAS CONCEPT MOD	INCLUDE	DTID 4019 “Algorithm Identification”	1	U
11	>>	CONTAINS	INCLUDE	DTID 1420 “Measurements Derived From Multiple ROI Measurements”	1-n	U
12	>	CONTAINS	CONTAINER	EV (C0034375, UMLS, "Qualitative Evaluations")	1	MC	IF Row 6 and Row 10 are absent
12b	>>	HAS CONCEPT MOD	INCLUDE	DTID 4019 “Algorithm Identification”	1	U
13	>>	CONTAINS	CODE		1-n	U
13b	>>>	HAS CONCEPT MOD	CODE	BCID 210 “Qualitative Evaluation Modifier Type”	1-n	U		BCID 211 “Qualitative Evaluation Modifier Value”
14	>>	CONTAINS	TEXT		1-n	U

Content Item Descriptions

Row 5	The Image Library provides potentially relevant characteristics of images associated with the measurements. There is no requirement to include all, or any, of the images referenced in the ROIs and measurements elsewhere in this template. The template may also include images that are associated with, but not directly referenced in, the ROIs and measurements. The Image Library is not replicating the content of the SOP Instance Reference Macro.
Rows 6, 10, 12	The conditions require that at least one of the "heading" containers be present, though any of them may be present but empty.
Row 6b, 10b, 12b	Describes the algorithm that applies to all observations within the container, unless overridden at the group or individual observation level.
Rows 7, 8, 9	The baseline Context Group allows for generic intensity, size, texture and other feature measurements, regardless of the geometry of the ROI (e.g., linear distance can be measured on volumes, or volume can be estimated from a linear distance), and being baseline, do not constrain the invoker from using other appropriate concepts specific to the application. Different measurements of the same real-world lesion made using different types of measurements (different templates) can be correlated by a shared value of Tracking Unique Identifier. See also Section RRR.5 “Measurement Report SR Document Volumetric ROI with RECIST Linear Distance Specified by Coordinates on CT Example” in PS3.17 .
Row 7	Planar ROI measurements are those defined on a single plane by a segmentation reference or planar spatial coordinates.
Row 8	Volumetric ROI measurements are those defined on a volume by raster or surface segmentation references or a set of 2D or 3D spatial coordinates.
Row 9	Generic measurements include those specified on an image as a whole or by unconstrained graphic coordinates. These may be used for such things as whole image scores or quality measures, and for linear distance measurements, such as for RECIST or WHO tumor treatment response criteria evaluation, or angle measurements. A Measurement Group is used to contain one or more individual measurements that are invocations of TID 300, consistent with TIDs 1410 and 1411, which both already have Measurement Group containers as their roots.
Rows 12, 13, 13b, 14	These Content Items allow encoding a flat list of name-value pairs that are coded questions with coded or text answers, for example, to record categorical observations related to the entire subject of the report rather than specific measurement groups. A single level of coded modifiers may be present, such as to post-coordinate the laterality if the parent concept involves an anatomic part.

TID 1501 Measurement and Qualitative Evaluation Group

This Template groups measurements and/or qualitative evaluations into a Measurement Group.

Each Measurement Group is identified by Tracking ID and UIDs, and may be described as having being made at a particular time point.

Measurement groups may contain various common measurement modifiers that are shared by all measurements in the group, such as method and finding site.

Table TID 1501. Parameters

Parameter Name	Parameter Usage
$Measurement	Coded term or Context Group for Concept Name of measurement
$Units	Measurement Unit
$ModType	Modifier Name for Concept Name of measurement
$ModValue	Modifier Value for Concept Name of measurement
$Method	Value for Measurement Method
$Derivation	Value for Measurement Derivation
$TargetSite	Value(s) for Anatomic Location of measurement
$TargetSiteMod	Modifier Value for Anatomic Location of measurement
$Equation	Coded term or Context Group for the equation or table from which the measurement was derived or computed
$ImagePurpose	Purpose of Reference for an image used as a source of the measurement
$WavePurpose	Purpose of Reference for a waveform used as a source of the measurement
$RefAuthority	Bibliographic reference or authority for statistical properties of a reference population
$RangeAuthority	Bibliographic reference or authority for the normal range of the measurement
$DerivationParameter	Coded term or Context Group for Concept Name of a derivation parameter
$DerivationParameterUnits	Units of derivation parameter
$QualType	Evaluations encoded with code or text responses
$QualValue	Value of evaluations encoded with code responses
$QualModType	Modifier Name of evaluations encoded with code or text responses
$QualModValue	Modifier Value of evaluations encoded with code or text responses
$FindingCategory	Category of the finding
$FindingType	Type of the finding
$TrackingID	Value for Tracking Identifier
$TrackingUID	Value for Tracking Unique Identifier

Type:: Extensible
Order:: Non-Significant
Root:: No

Table TID 1501. Measurement and Qualitative Evaluation Group

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1		CONTAINS	CONTAINER	EV (125007, DCM, "Measurement Group")	1	M
1b	>	HAS OBS CONTEXT	TEXT	EV (C67447, NCIt, "Activity Session")	1	U
2	>	HAS OBS CONTEXT	TEXT	DT (112039, DCM, "Tracking Identifier")	1	U	$TrackingID
3	>	HAS OBS CONTEXT	UIDREF	EV (112040, DCM, "Tracking Unique Identifier")	1	U	$TrackingUID
3a	>	CONTAINS	CODE	EV (276214006, SCT, "Finding category")	1	U	$FindingCategory
3b	>	CONTAINS	CODE	EV (121071, DCM, "Finding")	1	U	$FindingType
4	>	HAS OBS CONTEXT	INCLUDE	DTID 1502 “Time Point Context”	1	U
5	>	HAS CONCEPT MOD	CODE	EV (370129005, SCT, "Measurement Method")	1	U	$Method
6	>	HAS CONCEPT MOD	CODE	EV (363698007, SCT, "Finding Site")	1-n	U	$TargetSite
7	>>	HAS CONCEPT MOD	CODE	EV (272741003, SCT, "Laterality")	1	U	DCID 244 “Laterality”
8	>>	HAS CONCEPT MOD	CODE	DT (106233006, SCT, "Topographical modifier")	1	U	$TargetSiteMod
9	>	CONTAINS	COMPOSITE	EV (126100, DCM, "Real World Value Map used for measurement")	1	U	SOP Class UID shall be Real World Value Mapping Storage ("1.2.840.10008.5.1.4.1.1.67")
9b	>	HAS CONCEPT MOD	INCLUDE	DTID 4019 “Algorithm Identification”	1	U
9c	>	CONTAINS	IMAGE	EV (121200, DCM, "Illustration of ROI")	1	U
9d	>	CONTAINS	IMAGE	EV (130401, DCM, "Visual explanation")	1-n	U
10	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1-n	U	$Measurement = $Measurement $Units = $Units $ModType = $ModType $ModValue = $ModValue $Method = $Method $Derivation = $Derivation $TargetSite = $TargetSite $TargetSiteMod = $TargetSiteMod $Equation = $Equation $ImagePurpose = $ImagePurpose $WavePurpose = $WavePurpose $RefAuthority = $RefAuthority $RangeAuthority = $RangeAuthority $DerivationParameter = $DerivationParameter $DerivationParameterUnits = $DerivationParameterUnits
10b	>	CONTAINS	IMAGE	$ImagePurpose	1-n	U
10c	>	CONTAINS	SCOORD	$ImagePurpose	1-n	U
10d	>>	SELECTED FROM	IMAGE		1	M
10e	>	CONTAINS	SCOORD3D	$ImagePurpose	1-n	U
10f	>	CONTAINS	WAVEFORM	$WavePurpose	1-n	U
10g	>	CONTAINS	TCOORD	$WavePurpose	1-n	U
10h	>>	SELECTED FROM	WAVEFORM		1	M
11	>	CONTAINS	CODE	$QualType	1-n	U	$QualValue
11b	>>	HAS CONCEPT MOD	CODE	$QualModType	1-n	U	$QualModValue
12	>	CONTAINS	TEXT	$QualType	1-n	U

Content Item Descriptions

Row 1b	Identifies the session during which the measurements were made. The NCI Thesaurus definition is "time, period, or term devoted to some activity".
Rows 2, 3, 10	The included TID 300 contains an optional inclusion of TID 1408 Tracking Identifier as a child of the NUM measurement, which in turns allows for either or both Tracking Identifier and Tracking Unique Identifier Content Items; the intent of Rows 2 and 3 is not to send these Content Items twice, but rather to factor them out into a common location for multiple measurements, and to be consistent with TID 1410 and TID 1411.
Rows 3a, 3b	The category and type of the finding describe whatever entity (finding or feature) is identified by Rows 2 and 3. E.g., a finding might be a lesion, a tumor, or a reference region (as distinct from its anatomical location, which is encoded in a different Content Item (Finding Site).
Row 6	Finding site may be multiple when a region of interest spans multiple anatomical locations and there is not a single pre-coordinated code describing the combination of locations. E.g., when a maligant, inflammatory or traumatic process spans actual or defined anatomical boundaries. There is no requirement that the multiple locations be contiguous.
Row 9	The reference to an RWV in Row 9 allows measurements to be made in units that differ from the stored pixel values in the images referenced elsewhere in the Template. E.g., for a PET SUVbw measurement, the mapping from activity/concentration units in the referenced image that was used (and which may be reused for measurements in the future) may be encoded in a referenced RWV instance. This reference applies to any measurements in included Templates, unless overridden).
Row 9b	Describes the algorithm that applies to all measurements in TID 300 Row 1, unless overridden within the individual measurement at TID 300 Row 19.
Row 9c	This referenced image may contain a "screen shot" illustrating a rendered version of the ROI.
Row 9d	This referenced image may contain a visual explanation of how an algorithm produces its results, and may be a "screen shot" of the explanation already superimposed on the source image (e.g., a "heat map"), or a parametric map intended to be superimposed on the source image by the receiving application. The type of image and the type of visual explanation is described in the referenced image's own metadata. More than one referenced image may be present, if there is more than one type of visual explanation, or it needs to span more than one single-frame image.
Row 10	(260753009, SCT, "Source") may be specified for $ImagePurpose or $WavePurpose as a generic Concept Name when there is a desire to avoid having an anonymous (unnamed) Content Item.
Rows 10b, 10c, 10d, 10e, 10f, 10g, 10h	Coordinates, image or waveform references that are the subject of this measurement group instead of, or in addition to, coordinate, image or waveform references associated with measurements in Row 10. Note that if an ROI is defined, other templates may be used, such as TID 1410 Planar ROI Measurements and Qualitative Evaluations.
Rows 11, 11b, 12	Allows encoding a flat list of name-value pairs that are coded questions with coded or text answers, for example, to record categorical observations related to the subject of the measurement group. A single level of coded modifiers may be present.

TID 1502 Time Point Context

This Template describes information about the time point, for example, at which a measurement was obtained.

Type:: Extensible
Order:: Non-Significant
Root:: No

Table TID 1502. Time Point Context

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1		HAS OBS CONTEXT	TEXT	EV (126070, DCM, "Subject Time Point Identifier")	1	U
2		HAS OBS CONTEXT	TEXT	EV (126071, DCM, "Protocol Time Point Identifier")	1	U
3		HAS OBS CONTEXT	TEXT	EV (C2348792, UMLS, "Time Point")	1	M
4		HAS OBS CONTEXT	CODE	EV (126072, DCM, "Time Point Type")	1-n	U	BCID 6146 “Time Point Type”
5		HAS OBS CONTEXT	NUM	EV (126073, DCM, "Time Point Order")	1	U	UNITS = EV (1, UCUM, "no units")
6		HAS OBS CONTEXT	NUM	EV (128740, DCM, "Longitudinal Temporal Offset from Event")	1	U	UNITS = DT (d, UCUM, "days")
7	>	HAS CONCEPT MOD	CODE	EV (128741, DCM, "Longitudinal Temporal Event Type")	1	M	DCID 280 “Longitudinal Temporal Event Type”

Content Item Descriptions

Row 1	Usually the same value as the Clinical Trial Time Point ID (0012,0050) Attribute in the Clinical Trial Study Module, though not confined to clinical trial use. May or may not be human readable, and not required to be a DICOM UID.
Row 2	All of the subjects within a treatment protocol that are examined at a particular scheduled time point (e.g., "baseline", "pre-treatment", "first post-treatment") will have the same Protocol Time Point Identifier, but different Subject Time Point Identifiers. However, in different protocols, the Protocol Time Point Identifiers for the same conceptual "time point" will be different. E.g., the "baseline" time point will have different Protocol Time Point Identifiers in different protocols. May or may not be human readable, and not required to be a DICOM UID.
Row 3	Typically a short pre-defined label that has the same scope as Protocol Time Point Identifier (i.e., same conceptual time point within a treatment protocol) but is human-readable and understandable, e.g., "BASELINE" or "TP0", "TP1", etc. Usually the same value as Clinical Trial Time Point Description (0012,0051) Attribute in the Clinical Trial Study Module, though not confined to clinical trial use. The Concept Name is selected as (C2348792, UMLS, "Time Point") (which is (C68568, NCIt, "Time Point"), defined as "a specific point in the time continuum, including those established relative to an event") in order to be compatible with external terminologies.
Row 4	More than one type is permitted, e.g., a time point may be "posttreatment" as well as "unscheduled" or "nadir", etc.
Row 5	The order is expected to be monotonically increasing within a particular scope of usage, but is not required to start at 0 or 1, nor required to increase in increments of 1 or even the same increment (e.g., to allow for retrospective insertion of unscheduled time points). In clinical usage, the Time Point Order would be expected to be temporally increasing, but in a clinical trial may be a randomized reading order rather than a temporal order.
Rows 6, 7	Longitudinal temporal information may be inherited from Longitudinal Temporal Offset from Event (0012,0052) and Longitudinal Temporal Event Type (0012,0053) in the PS3.3 Section C.7.2.3 Clinical Trial Study Module, or may be specified or overridden within this template (e.g., if different measurements in the same SR Instance were measured on different time points).

TID 1600 Image Library

The Image Library contains references to images and selected attributes describing them that facilitate analysis without having to retrieve the entire set of referenced images.

Type:: Extensible
Order:: Non-Significant
Root:: No

Table TID 1600. Image Library

	NL	Rel with Parent	VT	Concept Name	VM	Req Type
1			CONTAINER	EV (111028, DCM, "Image Library")	1	M
2	>	CONTAINS	CONTAINER	EV (126200, DCM, "Image Library Group")	1-n	U
3	>>	HAS ACQ CONTEXT	INCLUDE	DTID 1602 “Image Library Entry Descriptors”	1	U
4	>>	CONTAINS	INCLUDE	DTID 1601 “Image Library Entry”	1-n	U

Row 3

These Image Library Entry Descriptors apply to all Image Library Entries in this Image Library Group.

TID 1601 Image Library Entry

Each instance of the Image Library Entry Template contains the Image SOP Class and Instance UIDs, and selected attributes for an image that facilitate analysis without having to retrieve the entire set of referenced images.

Type:: Extensible
Order:: Non-Significant
Root:: No

Table TID 1601. Image Library Entry

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			IMAGE		1	M
2	>	HAS ACQ CONTEXT	INCLUDE	DTID 1602 “Image Library Entry Descriptors”	1	U

Row 2

These Image Library Entry Descriptors apply to the IMAGE in Row 1 and override descriptors in Row 3 of Section TID 1600 in case of conflict.

TID 1602 Image Library Entry Descriptors

This Template contains selected attributes for an image or group of images. The descriptive information may be copied from images or derived.

Type:: Extensible
Order:: Non-Significant
Root:: No

Table TID 1602. Image Library Entry Descriptors

	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1	HAS ACQ CONTEXT	CODE	EV (121139, DCM, "Modality")	1	U		DCID 29 “Acquisition Modality”
2	HAS ACQ CONTEXT	CODE	EV (123014, DCM, "Target Region")	1	U		DCID 4031 “Common Anatomic Region”
3	HAS ACQ CONTEXT	CODE	EV (111027, DCM, "Image Laterality")	1	U		DCID 244 “Laterality”
4	HAS ACQ CONTEXT	DATE	EV (111060, DCM, "Study Date")	1	U
5	HAS ACQ CONTEXT	TIME	EV (111061, DCM, "Study Time")	1	U
6	HAS ACQ CONTEXT	DATE	EV (111018, DCM, "Content Date")	1	U
7	HAS ACQ CONTEXT	TIME	EV (111019, DCM, "Content Time")	1	U
8	HAS ACQ CONTEXT	DATE	EV (126201, DCM, "Acquisition Date")	1	U
9	HAS ACQ CONTEXT	TIME	EV (126202, DCM, "Acquisition Time")	1	U
10	HAS ACQ CONTEXT	UIDREF	EV (112227, DCM, "Frame of Reference UID")	1	U
11	HAS ACQ CONTEXT	NUM	EV (110910, DCM, "Pixel Data Rows")	1	U		UNITS = EV ({pixels}, UCUM, "pixels")
12	HAS ACQ CONTEXT	NUM	EV (110911, DCM, "Pixel Data Columns")	1	U		UNITS = EV ({pixels}, UCUM, "pixels")
13	HAS ACQ CONTEXT	INCLUDE	DTID 1603 “Image Library Entry Descriptors for Projection Radiography”	1	MC	IFF Row 1 is present with a value of "CR", "DX", "IO", "MG, "PX", "RF", "RG" or "XA"
14	HAS ACQ CONTEXT	INCLUDE	DTID 1604 “Image Library Entry Descriptors for Cross-Sectional Modalities”	1	MC	IFF Row 1 is present with a value of "CT", "MR" or "PT"
15	HAS ACQ CONTEXT	INCLUDE	DTID 1605 “Image Library Entry Descriptors for CT”	1	MC	IFF Row 1 is present with a value of "CT"
16	HAS ACQ CONTEXT	INCLUDE	DTID 1606 “Image Library Entry Descriptors for MR”	1	MC	IFF Row 1 is present with a value of "MR"
17	HAS ACQ CONTEXT	INCLUDE	DTID 1607 “Image Library Entry Descriptors for PET”	1	MC	IFF Row 1 is present with a value of "PT"

Content Item Descriptions

Row 2

The value of Anatomic Region Sequence (0008,2218) in the Image IOD, or a code derived from Body Part Examined (0018,0015) using the mapping described in Annex L.

TID 1603 Image Library Entry Descriptors for Projection Radiography

This Template contains selected attributes for a projection radiography image or group of such images. The descriptive information may be copied from images or derived.

Type:: Extensible
Order:: Non-Significant
Root:: No

Table TID 1603. Image Library Entry Descriptors for Projection Radiography

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1		HAS ACQ CONTEXT	CODE	EV (111031, DCM, "Image View")	1	U
2	>	HAS CONCEPT MOD	CODE	EV (111032, DCM, "Image View Modifier")	1-n	U
3		HAS ACQ CONTEXT	TEXT	EV (111044, DCM, "Patient Orientation Row")	1	U
4		HAS ACQ CONTEXT	TEXT	EV (111043, DCM, "Patient Orientation Column")	1	U
5		HAS ACQ CONTEXT	NUM	EV (111026, DCM, "Horizontal Pixel Spacing")	1	U	UNITS = EV (mm, UCUM, "millimeter")
6		HAS ACQ CONTEXT	NUM	EV (111066, DCM, "Vertical Pixel Spacing")	1	U	UNITS = EV (mm, UCUM, "millimeter")
7		HAS ACQ CONTEXT	NUM	EV (112011, DCM, "Positioner Primary Angle")	1	U	UNITS = EV (deg, UCUM, "deg")
8		HAS ACQ CONTEXT	NUM	EV (112012, DCM, "Positioner Secondary Angle")	1	U	UNITS = EV (deg, UCUM, "deg")

Content Item Descriptions

Rows 3, 4	First (row) and second (column) components of Patient Orientation (0020,0020) in the Image IOD. See Section C.7.6.1.1.1 “Patient Orientation” in PS3.3 .
Row 5	The second component of Imager Pixel Spacing (0018,1164) in the Image IOD. See Section C.8.11.4 “DX Detector Module” in PS3.3 .
Row 6	The first component of Imager Pixel Spacing (0018,1164) in the Image IOD. See Section C.8.11.4 “DX Detector Module” in PS3.3 .

TID 1604 Image Library Entry Descriptors for Cross-Sectional Modalities

This Template contains selected attributes for a cross-sectional image or group of such images. The descriptive information may be copied from images or derived.

Type:: Extensible
Order:: Non-Significant
Root:: No

Table TID 1604. Image Library Entry Descriptors for Cross-Sectional Modalities

	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1	HAS ACQ CONTEXT	NUM	EV (111026, DCM, "Horizontal Pixel Spacing")	1	U	UNITS = EV (mm, UCUM, "millimeter")
2	HAS ACQ CONTEXT	NUM	EV (111066, DCM, "Vertical Pixel Spacing")	1	U	UNITS = EV (mm, UCUM, "millimeter")
3	HAS ACQ CONTEXT	NUM	EV (112226, DCM, "Spacing between slices")	1	U	UNITS = EV (mm, UCUM, "millimeter")
4	HAS ACQ CONTEXT	NUM	EV (112225, DCM, "Slice Thickness")	1	U	UNITS = EV (mm, UCUM, "millimeter")
5	HAS ACQ CONTEXT	NUM	EV (110901, DCM, "Image Position (Patient) X")	1	U	UNITS = EV (mm, UCUM, "millimeter")
6	HAS ACQ CONTEXT	NUM	EV (110902, DCM, "Image Position (Patient) Y")	1	U	UNITS = EV (mm, UCUM, "millimeter")
7	HAS ACQ CONTEXT	NUM	EV (110903, DCM, "Image Position (Patient) Z")	1	U	UNITS = EV (mm, UCUM, "millimeter")
8	HAS ACQ CONTEXT	NUM	EV (110904, DCM, "Image Orientation (Patient) Row X")	1	U	UNITS = EV ({-1:1}, UCUM, "{-1:1}")
9	HAS ACQ CONTEXT	NUM	EV (110905, DCM, "Image Orientation (Patient) Row Y")	1	U	UNITS = EV ({-1:1}, UCUM, "{-1:1}")
10	HAS ACQ CONTEXT	NUM	EV (110906, DCM, "Image Orientation (Patient) Row Z")	1	U	UNITS = EV ({-1:1}, UCUM, "{-1:1}")
11	HAS ACQ CONTEXT	NUM	EV (110907, DCM, "Image Orientation (Patient) Column X")	1	U	UNITS = EV ({-1:1}, UCUM, "{-1:1}")
12	HAS ACQ CONTEXT	NUM	EV (110908, DCM, "Image Orientation (Patient) Column Y")	1	U	UNITS = EV ({-1:1}, UCUM, "{-1:1}")
13	HAS ACQ CONTEXT	NUM	EV (110909, DCM, "Image Orientation (Patient) Column Z")	1	U	UNITS = EV ({-1:1}, UCUM, "{-1:1}")

Content Item Descriptions

Row 1	The second component of Pixel Spacing (0028,0030) in the Image IOD. See Section 10.7.1.1 “Pixel Spacing” in PS3.3 and Section C.7.6.2 “Image Plane Module” in PS3.3 .
Row 2	The first component of Pixel Spacing (0028,0030) in the Image IOD. See Section 10.7.1.1 “Pixel Spacing” in PS3.3 and Section C.7.6.2 “Image Plane Module” in PS3.3 .

TID 1605 Image Library Entry Descriptors for CT

This Template contains selected attributes for a CT image or group of such images. The descriptive information may be copied from images or derived.

Type:: Extensible
Order:: Non-Significant
Root:: No

Table TID 1605. Image Library Entry Descriptors for CT

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1		HAS ACQ CONTEXT	CODE	EV (113820, DCM, "CT Acquisition Type")	1	U		DCID 10013 “CT Acquisition Type”
2		HAS ACQ CONTEXT	CODE	EV (113961, DCM, "Reconstruction Algorithm")	1	U		DCID 10033 “CT Reconstruction Algorithm”

Content Item Descriptions

Row 1	A code derived from the Value of Acquisition Type (0018,9302) in the Image IOD. See Section C.8.15.3.2 “CT Acquisition Type Macro” in PS3.3 .
Row 2	A code derived from the Value of Reconstruction Algorithm (0018,9315) in the Image IOD. See Section C.8.15.3.7 “CT Reconstruction Macro” in PS3.3 .

TID 1606 Image Library Entry Descriptors for MR

This Template contains selected attributes for a MR image or group of such images. The descriptive information may be copied from images or derived. Specialized coded Content Items allow more precise description of imaging sequences used for interpretation of multiparametric prostate MRI.

Type:: Extensible
Order:: Non-Significant
Root:: No

Table TID 1606. Image Library Entry Descriptors for MR

	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1	HAS ACQ CONTEXT	TEXT	EV (128230, DCM, "Pulse Sequence Name")	1	U
2	HAS ACQ CONTEXT	NUM	EV (130542, DCM, "Magnetic field strength")	1	U	UNITS = (T, UCUM, "Tesla")
3	HAS ACQ CONTEXT	NUM	EV (RID10813, RADLEX, "MR coil")	1-n	U	DCID 6349 “MR Coil Type”
4	HAS ACQ CONTEXT	NUM	EV (110852, DCM, "MR signal intensity")	1	U	BCID 6311 “MR Signal Intensity”
5	HAS ACQ CONTEXT	NUM	EV (130546, DCM, "Cross-sectional scan plane orientation")	1	U	BCID 6312 “Cross-sectional Scan Plane Orientation”
6	HAS ACQ CONTEXT	NUM	EV (113240, DCM, "Source image diffusion b-value")	1-n	U	UNITS = (s/mm2, UCUM, "s/mm2")
7	HAS ACQ CONTEXT	INCLUDE	DTID 1608 “Image Library Entry Descriptors for Prostate Multiparametric MR”	1	U

Content Item Descriptions

Row 1	The value of Pulse Sequence Name (0018,9005) or Sequence Name (0018,0024) in the Image IOD. See Section C.8.13.4 “MR Pulse Sequence Module” in PS3.3 .
Row 6	Multiple values may apply when entry descriptor corresponds to a parametric map such as Apparent Diffusion Coefficient (ADC) map, which utilizes multiple b-values from a Diffusion-Weighted acquisition.

TID 1607 Image Library Entry Descriptors for PET

This Template contains selected attributes for a PET image or group of such images. The descriptive information may be copied from images or derived.

Note

The content of this Template is similar to that in TID 15101 NM/PET Protocol Context, but is in the form of an SR Template rather than a Protocol Context Template, and the Content Items are not nested as modifiers. There is also some similarity to TID 3307 NM/PET Perfusion Measurement Group.

Type:: Extensible
Order:: Non-Significant
Root:: No

Table TID 1607. Image Library Entry Descriptors for PET

	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1	HAS ACQ CONTEXT	CODE	EV (89457008, SCT, "Radionuclide")	1	U		DCID 4020 “PET Radionuclide”
2	HAS ACQ CONTEXT	CODE	EV (349358000, SCT, "Radiopharmaceutical agent")	1	U		DCID 4021 “PET Radiopharmaceutical”
3	HAS ACQ CONTEXT	NUM	EV (304283002, SCT, "Half-life of radiopharmaceutical")	1	U		UNITS = EV (s, UCUM, "s")
3b	HAS ACQ CONTEXT	TEXT	EV (121022, DCM, "Accession Number")	1	U
4	HAS ACQ CONTEXT	DATETIME	EV (123003, DCM, "Radiopharmaceutical Start DateTime")	1	U
5	HAS ACQ CONTEXT	DATETIME	EV (123004, DCM, "Radiopharmaceutical Stop DateTime")	1	U
6	HAS ACQ CONTEXT	NUM	EV (123005, DCM, "Radiopharmaceutical Volume")	1	U		UNITS = DT (cm3, UCUM, "cm3")
7	HAS ACQ CONTEXT	NUM	EV (123006, DCM, "Radionuclide Total Dose")	1	U		UNITS = DT (Bq, UCUM, "Bq")
8	HAS ACQ CONTEXT	NUM	EV (123007, DCM, "Radiopharmaceutical Specific Activity")	1	U		UNITS = DT (Bq/mol, UCUM, "Bq/mol")
9	HAS ACQ CONTEXT	CODE	EV (410675002, SCT, "Route of Administration")	1	U		BCID 11 “Administration Route”
10	HAS ACQ CONTEXT	NUM	EV (123009, DCM, "Radionuclide Syringe Counts")	1	U		UNITS = DT ({counts}/s, UCUM, "counts/s")
11	HAS ACQ CONTEXT	NUM	EV (123010, DCM, "Radionuclide Residual Syringe Counts")	1	U		UNITS = DT ({counts}/s, UCUM, "counts/s")
12	HAS ACQ CONTEXT	NUM	EV (126203, DCM, "PET Radionuclide Incubation Time")	1	U		UNITS = EV (min, UCUM, "min")
13	HAS ACQ CONTEXT	NUM	EV (14749-6, LN, "Glucose")	1	U		UNITS = EV (mmol/l, UCUM, "mmol/l")
14	HAS ACQ CONTEXT	DATE	EV (127857, DCM, "Glucose Measurement Date")	1	MC	IF Row 13 Glucose is present and does not contain Observation DateTime (0040,A032).
15	HAS ACQ CONTEXT	TIME	EV (127858, DCM, "Glucose Measurement Time")	1	MC	IF Row 13 Glucose is present and does not contain Observation DateTime (0040,A032).

Content Item Descriptions

Row 3	Half-life of radiopharmaceutical	The units for half life are chosen to be seconds, to match the units used for Radionuclide Half Life (0018,1075). See Section C.8.9.2 “PET Isotope Module” in PS3.3 .
Row 14	Glucose Measurement Date	In an earlier edition of the Standard, an incorrect DCM code was used for this concept, which was already assigned as (109081, DCM, "Prospective gating").
Row 15	Glucose Measurement Time	In an earlier edition of the Standard, an incorrect DCM code was used for this concept, which was already assigned as (109082, DCM, "Retrospective gating").

TID 1608 Image Library Entry Descriptors for Prostate Multiparametric MR

This Template includes attributes for image library entries that define the type of the sequence, as needed for PI-RADS interpretation of multiparametric MRI, specify most important sequence-specific attributes, and provide a location for reporting prostate imaging and sequence-specific technical characteristics of the acquisition.

Note

A descriptor specific to prostate MRI and PI-RADS is provided to record Prostate DCE temporal resolution. This term follows the conventions used in the PI-RADS guidelines.

Type:: Extensible
Order:: Non-Significant
Root:: No

Table TID 1608. Image Library Entry Descriptors for Prostate Multiparametric MR

	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1	HAS ACQ CONTEXT	TEXT	EV (130544, DCM, "Endorectal coil type")	1	U
2	HAS ACQ CONTEXT	CODE	EV (130545, DCM, "Inflatable endorectal coil fill substance")	1	U	DCID 6350 “Endorectal Coil Fill Substance”
3	HAS ACQ CONTEXT	NUM	EV (130547, DCM, "Dynamic contrast-enhanced temporal resolution")	1-n	U	UNITS = (s, UCUM, "second")

TID 1700 Generic Blood Lab Measurements

The Generic Blood Lab Measurements Template provides for the recording of measurements made on a blood sample that is not specific to a particular clinical application. The type and anatomic source of the blood is recorded as acquisition context. The results from the blood chemistry measurement system are quoted; the measurement names may be pre-coordinated with the type or source of the blood, or generic measurement names may be reported. In the latter case, the full measurement concept name may be effectively post-coordinated using the recorded acquisition context.

Table TID 1700. Parameters

Parameter Name	Parameter Usage
$Measurement	Measurement.
$Units	Measurement units.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1700. Generic Blood Lab Measurements

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CONTAINER	EV (122125, DCM, "Blood lab measurements")	1	M
2	>	HAS ACQ CONTEXT	DATETIME	EV (111469, DCM, "Sampling DateTime")	1	M
3	>	HAS ACQ CONTEXT	CODE	EV (371439000, SCT, "Specimen Type")	1	M	DCID 3520 “Blood Source Type”
4	>	HAS ACQ CONTEXT	CODE	EV (363704007, SCT, "Procedure site")	1	M	BCID 3630 “Cardiovascular Anatomic Location”
5	>		INCLUDE	DTID 1000 “Quotation”	1	U
6	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1-n	M	$Measurement = $Measurement $Units = $Units

TID 1701 Imaging Study Quality

This template provides the mechanism to describe image quality both at the study and individual series level, following a specific quality control standard.

Table TID 1701. Parameters

Parameter Name	Parameter Usage
$ImageQualityControlStandard	Value for Quality Control Standard.
$StudyQualityFindings	Value for Study Quality Findings.
$SeriesQualityFindings	Value for Series Quality Findings.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 1701. Imaging Study Quality

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CONTAINER	EV (130549, DCM, "Imaging Study Quality")	1	M
2	>	CONTAINS	CODE	EV (111050, DCM, "Quality Assessment")	1	M		DCID 6044 “Image Quality Assessment Type”
3	>>	HAS PROPERTIES	CODE	EV (111051, DCM, "Quality Control Standard")	1	M		$ImageQualityControlStandard Defaults to BCID 6326 “Image Quality Control Standard”
4	>	CONTAINS	CODE	EV (111052, DCM, "Quality Finding")	1-n	U		$StudyQualityFindings
5	>	CONTAINS	CONTAINER	EV (130550, DCM, "Imaging Series Quality")	1-n	U
6	>>	CONTAINS	UIDREF	EV (112002, DCM, "Series Instance UID")	1-n	M
7	>>	CONTAINS	CODE	EV (111050, DCM, "Quality Assessment")	1	MC	At least one of Rows 7, 9, 10 shall be present	DCID 6044 “Image Quality Assessment Type”
8	>>>	HAS PROPERTIES	CODE	EV (111051, DCM, "Quality Control Standard")	1	M		$ImageQualityControlStandard Defaults to BCID 6326 “Image Quality Control Standard”
9	>>	CONTAINS	CODE	EV (111052, DCM, "Quality Finding")	1-n	MC	At least one of Rows 7, 9, 10 shall be present	$SeriesQualityFindings
10	>>	CONTAINS	NUM	EV (111029, DCM, "Image Quality Rating")	1-n	MC	At least one of Rows 7, 9, 10 shall be present	UNITS = EV (%, UCUM, "Percent") Value = 0 - 100

Content Item Descriptions

Row 6

Defines the series to which the assessments apply.

Diagnostic Imaging Report Templates

TID 2000 Basic Diagnostic Imaging Report

Basic report Template for general diagnostic imaging interpretation reports.

Can only be instantiated at the root node and cannot be included in other Templates.

Type:: Non-Extensible
Order:: Significant
Root:: Yes

Table TID 2000. Basic Diagnostic Imaging Report

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CONTAINER	BCID 7000 “Diagnostic Imaging Report Document Title”	1	M
2	>	HAS CONCEPT MOD	CODE	EV (121058, DCM, "Procedure reported")	1-n	U
3	>	HAS CONCEPT MOD	CODE	EV (122142, DCM, "Acquisition Device Type")	1-n	U	DCID 29 “Acquisition Modality”
4	>	HAS CONCEPT MOD	CODE	EV (123014, DCM, "Target Region")	1-n	U
5	>	HAS CONCEPT MOD	INCLUDE	DTID 1204 “Language of Content Item and Descendants”	1	M
6	>	HAS CONCEPT MOD	INCLUDE	DTID 1210 “Equivalent Meaning(s) of Concept Name”	1-n	U
7	>	HAS OBS CONTEXT	INCLUDE	DTID 1001 “Observation Context”	1	M
8	>	CONTAINS	CONTAINER	BCID 7001 “Diagnostic Imaging Report Heading”	1-n	U
9	>>	HAS OBS CONTEXT	INCLUDE	DTID 1001 “Observation Context”	1	U
10	>>		INCLUDE	DTID 2002 “Report Narrative”	1	M

No Content Items other than those defined in Observation Context TID 1001 “Observation Context” may be the target of a HAS OBS CONTEXT relationship when TID 2000 “Basic Diagnostic Imaging Report” is invoked.

Content Item Descriptions

Rows 2, 3, 4

The content of Rows 2, 3, and 4 shall not be inconsistent with the meaning of the report title of Row 1. If the report title does not include the concepts of the procedure type, modality, or target site (e.g., the generic "Diagnostic Imaging Report"), these rows may provide post-coordination of those concepts. If the report title does include such concepts (e.g., "CT Head Report"), they may be encoded duplicatively to support report categorization and search.

TID 2001 Basic Diagnostic Imaging Report Observations

Individual numeric or image observations that may be useful for inclusion as individual findings or as the source of inferences in a report.

Type:: Non-Extensible
Order:: Significant
Root:: No

Table TID 2001. Basic Diagnostic Imaging Report Observations

	VT	Concept Name	VM	Req Type	Condition
1	IMAGE	BCID 7003 “Diagnostic Imaging Report Purpose of Reference”	1	MC	XOR Rows 2, 3, 4, 5.
2	INCLUDE	DTID 1400 “Linear Measurement”	1	MC	XOR Rows 1, 3, 4, 5. Shall not be present if the NUM value type is not supported by the IOD.
3	INCLUDE	DTID 1401 “Area Measurement”	1	MC	XOR Rows 1, 2, 4, 5. Shall not be present if the NUM value type is not supported by the IOD.
4	INCLUDE	DTID 1402 “Volume Measurement”	1	MC	XOR Rows 1, 2, 3, 5. Shall not be present if the NUM value type is not supported by the IOD.
5	INCLUDE	DTID 1404 “Numeric Measurement”	1	MC	XOR Rows 1, 2, 3, 4. Shall not be present if the NUM value type is not supported by the IOD.

TID 2002 Report Narrative

The Report Narrative allows recording of text, code, and numeric observations. The order of Content Items in the Template is not significant; the order of Content Items in a SOP Instance may be significant to the narrative flow of the report.

Type:: Non-Extensible
Order:: Non-Significant
Root:: No

Table TID 2002. Report Narrative

	NL	Rel with Parent	VT	Concept Name	VM	Req Type
1		CONTAINS	CODE	BCID 7002 “Diagnostic Imaging Report Element”	1-n	U
2	>	INFERRED FROM	INCLUDE	DTID 2001 “Basic Diagnostic Imaging Report Observations”	1-n	U
3		CONTAINS	TEXT	BCID 7002 “Diagnostic Imaging Report Element”	1-n	U
4	>	INFERRED FROM	INCLUDE	DTID 2001 “Basic Diagnostic Imaging Report Observations”	1-n	U
5		CONTAINS	INCLUDE	DTID 2001 “Basic Diagnostic Imaging Report Observations”	1-n	U

TID 2005 Transcribed Diagnostic Imaging Report

Basic report Template for general diagnostic imaging interpretation reports produced in a dictation/transcription workflow. SR documents encoded using this Template are intended to be transformable to HL7 Clinical Document Architecture format (see Section X.3 “Transcribed Diagnostic Imaging CDA Instance Content” in PS3.17 and Annexes in PS3.20).

This Template can be instantiated only at the root node, and cannot be included in other Templates.

Observation Context shall be inherited from outside the Structured Report Content Tree, and shall not be changed within the Content Tree. To satisfy the requirement that Observer Context is inherited, either or both the Author Observer Sequence (0040,A078) or the Verifying Observer Sequence (0040,A073) from the SR Document General Module must be present in the SOP Instance.

Note

See Section C.17.5 “Observation Context Encoding” in PS3.3 .

Type:: Non-Extensible
Order:: Significant
Root:: Yes

Table TID 2005. Transcribed Diagnostic Imaging Report

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CONTAINER	BCID 7000 “Diagnostic Imaging Report Document Title”	1	M
2	>	HAS CONCEPT MOD	CODE	EV (121058, DCM, "Procedure reported")	1-n	U
3	>	HAS CONCEPT MOD	CODE	EV (122142, DCM, "Acquisition Device Type")	1-n	U	DCID 29 “Acquisition Modality”
4	>	HAS CONCEPT MOD	CODE	EV (123014, DCM, "Target Region")	1-n	U
5	>	HAS CONCEPT MOD	CODE	EV (121049, DCM, "Language of Content Item and Descendants")	1	M	DCID 5000 “Language”
6	>	CONTAINS	CONTAINER	BCID 7001 “Diagnostic Imaging Report Heading”	1-n	M
7	>>	CONTAINS	TEXT	BCID 7002 “Diagnostic Imaging Report Element”	1	U
8	>	CONTAINS	CONTAINER	EV (55113-5, LN, "Key Images")	1-n	U
9	>>	CONTAINS	TEXT	EV (113012, DCM, "Key Object Description")	1	U
10	>>	CONTAINS	IMAGE		1-n	M

Content Item Descriptions

Rows 2, 3, 4	The content of Rows 2, 3, and 4 shall not be inconsistent with the meaning of the report title of Row 1. If the report title does not include the concepts of the procedure type, modality, or target site (e.g., the generic "Diagnostic Imaging Report"), these rows may provide post-coordination of those concepts. If the report title does include such concepts (e.g., "CT Head Report"), they may be encoded duplicatively to support report categorization and search.
Row 6	CONTAINER Concept Name may be absent.
Row 10	IMAGE Concept Name shall be absent. Purpose of reference is not specified.

TID 2006 Imaging Report With Conditional Radiation Exposure and Protection Information

This Template is used for general imaging reports for both radiation producing and non-radiation producing modalities.

For radiation producing modalities, radiation exposure and protection information is required, such as to support nationally-specific legal or standard requirements.

It contains mandatory sections, each of which may appear only once in objects instantiated from the Template, including the medical content of the report that comprises relevant medical history data, information on the current request (i.e., clinical question that is expected to be answered by the requested procedure), impressions on the current imaging procedure that has been performed, and radiation exposure and protection information.

This Template is a specialization of TID 2000 “Basic Diagnostic Imaging Report”, in that it uses the same structure of headings and content, but mandates the presence and order of specific headings, and extends the subordinate content with specific Content Items.

Type:: Non-Extensible
Order:: Non-Significant
Root:: Yes

Table TID 2006. Imaging Report With Conditional Radiation Exposure and Protection Information

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition
1			CONTAINER	BCID 7000 “Diagnostic Imaging Report Document Title”	1	M
2	>	HAS CONCEPT MOD	CODE	EV (121058, DCM, "Procedure reported")	1-n	U
3	>	HAS CONCEPT MOD	INCLUDE	DTID 1204 “Language of Content Item and Descendants”	1	M
4	>	HAS CONCEPT MOD	INCLUDE	DTID 1210 “Equivalent Meaning(s) of Concept Name”	1-n	U
5	>	HAS OBS CONTEXT	INCLUDE	DTID 1001 “Observation Context”	1	M
6	>	CONTAINS	CONTAINER	EV (55111-9, LN, "Current Procedure Descriptions")	1	M
7	>>		INCLUDE	DTID 2007 “Imaging Procedure Description”	1	M
8	>	CONTAINS	CONTAINER	EV (55114-3, LN, "Prior Procedure Descriptions")	1-n	MC	IF relevant prior procedures have been performed.
9	>>		INCLUDE	DTID 2007 “Imaging Procedure Description”	1	M
10	>	CONTAINS	CONTAINER	EV (11329-0, LN, "History")	1	M
11	>>	HAS OBS CONTEXT	INCLUDE	DTID 1001 “Observation Context”	1	U
12	>>		INCLUDE	DTID 2002 “Report Narrative”	1	M
13	>	CONTAINS	CONTAINER	EV (55115-0, LN, "Request")	1	M
14	>>	HAS OBS CONTEXT	INCLUDE	DTID 1001 “Observation Context”	1	U
15	>>		INCLUDE	DTID 2002 “Report Narrative”	1	M
16	>	CONTAINS	CONTAINER	EV (19005-8, LN, "Impressions")	1	M
17	>>	HAS OBS CONTEXT	INCLUDE	DTID 1001 “Observation Context”	1	U
18	>>		INCLUDE	DTID 2002 “Report Narrative”	1	M
19	>	CONTAINS	INCLUDE	DTID 2008 “Radiation Exposure and Protection Information”	1	MC	IF the current procedure exposes the patient to ionizing radiation.
20	>	CONTAINS	CONTAINER	BCID 7001 “Diagnostic Imaging Report Heading”	1-n	U
21	>>	HAS OBS CONTEXT	INCLUDE	DTID 1001 “Observation Context”	1	U
22	>>		INCLUDE	DTID 2002 “Report Narrative”	1	M

No Content Items other than those defined in TID 1001 “Observation Context” may be the target of a HAS OBS CONTEXT relationship when TID 2006 “Imaging Report With Conditional Radiation Exposure and Protection Information” is invoked.

Content Item Descriptions

Row 2

Even though this information is related to the content of Row 6 in TID 2007 “Imaging Procedure Description”, it is present here for consistency with other report Templates.

Rows 5, 6

Information on at least one of the following person observers is mandatory:

1) "Performing Physician"

2) "Performing Technologist".

(For those person observers, requirement types as specified in TID 1003 “Person Observer Identifying Attributes” apply. That means that "Person Observer Name" is the only mandatory Content Item).

Row 20

Each heading (concept code from CID 7001 “Diagnostic Imaging Report Heading”) may appear only once, and may not repeat the headings (concept codes) used when instantiating any other rows of this Template.

TID 2007 Imaging Procedure Description

Contains information related to the procedure.

Type:: Extensible
Order:: Non-Significant
Root:: No

Table TID 2007. Imaging Procedure Description

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1		HAS OBS CONTEXT	INCLUDE	DTID 1001 “Observation Context”	1	U
2		CONTAINS	TEXT	EV (123014, DCM, "Target Region")	1	MC	XOR with Row 3
3		CONTAINS	CODE	EV (123014, DCM, "Target Region")	1	MC	XOR with Row 2	DCID 4028 “Craniofacial Anatomic Region” DCID 4030 “CT, MR and PET Anatomy Imaged” DCID 4031 “Common Anatomic Region”
4	>	HAS CONCEPT MOD	CODE	EV (122142, DCM, "Acquisition Device Type")	1-n	U		DCID 29 “Acquisition Modality”
5		CONTAINS	TEXT	EV (121065, DCM, "Procedure Description")	1	M
6		CONTAINS	DATE	EV (111060, DCM, "Study Date")	1	M		Shall be equal to the Study Date (0020,0020) in the General Study Module in the images to which this report applies.
7		CONTAINS	TIME	EV (111061, DCM, "Study Time")	1	U		If present, shall be equal to the Study Time (0020,0030) in the General Study Module in the images to which this report applies.
8		CONTAINS	COMPOSITE	EV (113701, DCM, "X-Ray Radiation Dose Report")	1-n	U

TID 2008 Radiation Exposure and Protection Information

Contains information related to the radiation exposure and protection of the patient, as is required by national legal requirements or standards.

Other information about the current procedure is described in TID 2006 “Imaging Report With Conditional Radiation Exposure and Protection Information” and not repeated here.

Type:: Extensible
Order:: Non-Significant
Root:: No

Table TID 2008. Radiation Exposure and Protection Information

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CONTAINER	EV (73569-6, LN, "Radiation Exposure and Protection Information")	1	M
2	>	HAS OBS CONTEXT	INCLUDE	DTID 1001 “Observation Context”	1	U
3	>	CONTAINS	CODE	EV (364320009, SCT, "Pregnancy observable")	1	MC	IF female patient of child-bearing age	DCID 6096 “Pregnancy Status”
4	>	CONTAINS	TEXT	EV (18785-6, LN, "Indications for Procedure")	1	M
5	>	CONTAINS	PNAME	EV (113850, DCM, "Irradiation Authorizing")	1	M
6	>	CONTAINS	TEXT	EV (113921, DCM, "Radiation Exposure")	1	MC	IFF ionizing radiation is applied in the context of the current procedure
7	>	CONTAINS	TEXT	EV (440252007, SCT, "Administration of radiopharmaceutical")	1	MC	IFF radioactive substance is administered in the context of the current procedure

Content Item Descriptions

Row 5

The clinician responsible for determining that the irradiating procedure was appropriate for the indications.

Row 6

A textual, human-readable description of the radiation exposure is all that is required by this Template (such as is sufficient to comply with, for example, German law). Detailed specification of exposure is out of the scope of this Template. Such information may be given in a separate SR instances such as described in TID 10001 “Projection X-Ray Radiation Dose” or TID 10011 “CT Radiation Dose”, and referenced from TID 2007 “Imaging Procedure Description”.

TID 2010 Key Object Selection

The Key Object Selection Template is intended for flagging one or more significant images, waveforms, or other composite SOP Instances. Key Object Selection contains:

coded document title stating the reason for significance of the referenced objects in the Key Object Selection,
optional free form text comment in an explicitly identified language, and
optional identification of the observer (device or person) that created the Key Object Selection.

Note

For instance, when this Template is used to identify images rejected for quality reasons, the device or person performing the quality assessment is identified in observation context items (invoked through TID 1002 “Observer Context”). The reason for rejection can be included both as a code used as a concept modifier for the document title, and as text description.
The order of object references may be significant, e.g., when the title concept is "For Conference".
Instances referenced in a Key Object Selection Document may be securely referenced by Digital Signature or MAC mechanisms within the SR Document General Module (see PS3.3).

The Template can only be instantiated at the root node and cannot be included in other Templates. The Template is not extensible; that is, no other Content Items may be added to this Template, or the Templates that are included, recursively.

Type:: Non-Extensible
Order:: Non-Significant
Root:: Yes

Table TID 2010. Key Object Selection

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CONTAINER	DCID 7010 “Key Object Selection Document Title”	1	M
2	>	HAS CONCEPT MOD	CODE	EV (113011, DCM, "Document Title Modifier")	1-n	U
3	>	HAS CONCEPT MOD	CODE	EV (113011, DCM, "Document Title Modifier")	1	UC	IF Row 1 Concept Name = (113001, DCM, "Rejected for Quality Reasons") or (113010, DCM, "Quality Issue")	DCID 7011 “Rejected for Quality Reason”
4	>	HAS CONCEPT MOD	CODE	EV (113011, DCM, "Document Title Modifier")	1	MC	IF Row 1 Concept Name = (113013, DCM, "Best In Set")	DCID 7012 “Best in Set”
5	>	HAS CONCEPT MOD	INCLUDE	DTID 1204 “Language of Content Item and Descendants”	1	U
6	>	HAS OBS CONTEXT	INCLUDE	DTID 1002 “Observer Context”	1-n	U
7	>	CONTAINS	TEXT	EV (113012, DCM, "Key Object Description")	1	U
8	>	CONTAINS	IMAGE		1-n	MC	At least one of Rows 8, 9 and 10 shall be present
9	>	CONTAINS	WAVEFORM		1-n	MC	At least one of Rows 8, 9 and 10 shall be present
10	>	CONTAINS	COMPOSITE		1-n	MC	At least one of Rows 8, 9 and 10 shall be present

Content Item Descriptions

Rows 8, 9, 10

Purpose of reference shall not be present.

Optometry and Ophthalmology Templates

TID 2020 Spectacle Prescription Report

The Spectacle Prescription Report is a structured report used to represent the prescription for a patient. Usually a prescription is for both eyes, but sometimes just one. The Spectacle Prescription Report defines a refractive correction relative to which visual acuity may be measured subjectively, and thus may be referenced by a Visual Acuity Measurements Storage SOP Instance.

Type:: Extensible
Order:: Significant
Root:: Yes

Table TID 2020. Spectacle Prescription Report

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CONTAINER	EV (111671, DCM, "Spectacle Prescription Report")	1	M
2	>	CONTAINS	CONTAINER	EV (111688, DCM, "Right Eye Rx")	1	UC	IF Right Spectacle Lens is prescribed
3	>>	CONTAINS	INCLUDE	DTID 2021 “Template for Spectacle Prescription Details”	1	M
4	>	CONTAINS	CONTAINER	EV (111689, DCM, "Left Eye Rx")	1	UC	IF Left Spectacle Lens is prescribed
5	>>	CONTAINS	INCLUDE	DTID 2021 “Template for Spectacle Prescription Details”	1	M
6	>	CONTAINS	NUM	EV (111679, DCM, "Distance Pupillary Distance")	1	U		UNITS = EV (mm, UCUM, "mm")
7	>	CONTAINS	NUM	EV (111680, DCM, "Near Pupillary Distance")	1	U		UNITS = EV (mm, UCUM, "mm")
8	>	CONTAINS	TEXT	EV (121106, DCM, "Comment")	1	U

TID 2021 Template for Spectacle Prescription Details

Type:: Extensible
Order:: Significant
Root:: No

Table TID 2021. Spectacle Prescription Details

	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1	CONTAINS	NUM	EV (251795007, SCT, "Sphere")	1	M		UNITS = EV ([diop], UCUM, "diopters")
2	CONTAINS	NUM	EV (251797004, SCT, "Cylinder Power")	1	UC	IF Cylinder is prescribed	UNITS = EV ([diop], UCUM, "diopters")
3	CONTAINS	NUM	EV (251799001, SCT, "Axis")	1	MC	IF Row 2 is present	UNITS = EV (deg, UCUM, "degrees")
4	CONTAINS	NUM	EV (111672, DCM, "Add Near")	1	UC	IF Add Near is prescribed	UNITS = EV ([diop], UCUM, "diopters")
5	CONTAINS	NUM	EV (111673, DCM, "Add Intermediate")	1	UC	IF Add Intermediate is prescribed	UNITS = EV ([diop], UCUM, "diopters")
6	CONTAINS	NUM	EV (111674, DCM, "Add Other")	1	UC	IF Add Other is prescribed	UNITS = EV ([diop], UCUM, "diopters")
7	CONTAINS	NUM	EV (111675, DCM, "Horizontal Prism Power")	1	UC	IF Horizontal Prism is prescribed	UNITS = EV ([p'diop], UCUM, "prism diopters")
8	CONTAINS	CODE	EV (111676, DCM, "Horizontal Prism Base")	1	MC	IF Row 7 is present	DCID 4214 “Ophthalmic Horizontal Direction”
9	CONTAINS	NUM	EV (111677, DCM, "Vertical Prism Power")	1	UC	IF Vertical Prism is prescribed	UNITS = EV ([p'diop], UCUM, "prism diopters")
10	CONTAINS	CODE	EV (111678, DCM, "Vertical Prism Base")	1	MC	IF Row 9 is present	DCID 4215 “Ophthalmic Vertical Direction”
11	CONTAINS	NUM	EV (415813002, SCT, "Vertex distance")	1	U		UNITS = EV (mm, UCUM, "mm")

TID 2100 Macular Grid Thickness and Volume Report

The Macular Grid Thickness and Volume Report is a structured report encoding the macular grid thickness and volume values derived from ophthalmic images, such as ophthalmic OPT images. This may encode measurements of either or both eyes.

The macular grid conveyed by this report is based upon the grid employed by the Early Treatment of Diabetic Retinopathy Study (ETDRS) to measure area and proximity of macular edema to the anatomic center (fovea) of the macula. See ETDRS Report Number 10.

Type:: Extensible
Order:: Significant
Root:: Yes

Table TID 2100. Macular Grid Thickness and Volume Report

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CONTAINER	EV (111690, DCM, "Macular Grid Thickness and Volume Report")	1	M
2	>	HAS CONCEPT MOD	INCLUDE	DTID 1204 “Language of Content Item and Descendants”	1	M
3	>	HAS OBS CONTEXT	INCLUDE	DTID 1001 “Observation Context”	1	M
4	>	CONTAINS	INCLUDE	DTID 2101 “Macular Grid Thickness and Volume Measurement”	1	MC	IF Row 5 is absent.	$Laterality = EV (24028007, SCT, "Right")
5	>	CONTAINS	INCLUDE	DTID 2101 “Macular Grid Thickness and Volume Measurement”	1	MC	IF Row 4 is absent.	$Laterality = EV (7771000, SCT, "Left")

TID 2101 Macular Grid Thickness and Volume Measurement

This Template encodes the macular grid thickness and volume measurements for a single eye.

Table TID 2101. Parameters

Parameter Name	Parameter Usage
$Laterality	Which eye

Type:: Extensible
Order:: Significant
Root:: No

Table TID 2101. Macular Grid Thickness and Volume Measurement

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CONTAINER	EV (59776-5, LN, "Findings")	1	M
2	>	HAS CONCEPT MOD	CODE	EV (363698007, SCT, "Finding Site")	1	M	EV (81745001, SCT, "Eye")
3	>>	HAS CONCEPT MOD	CODE	EV (272741003, SCT, "Laterality")	1	M	$Laterality
4	>	CONTAINS	NUM	EV (57108-3, LN, "Macular Grid.Center Point Thickness")	1	M	UNITS = EV (um, UCUM, "micrometer")
5	>	CONTAINS	NUM	EV (57109-1, LN, "Macular Grid.Center Subfield Thickness")	1	M	UNITS = EV (um, UCUM, "micrometer")
6	>	CONTAINS	NUM	EV (57110-9, LN, "Macular Grid.Inner Superior Subfield Thickness")	1	M	UNITS = EV (um, UCUM, "micrometer")
7	>	CONTAINS	NUM	EV (57111-7, LN, "Macular Grid.Inner Nasal Subfield Thickness")	1	M	UNITS = EV (um, UCUM, "micrometer")
8	>	CONTAINS	NUM	EV (57112-5, LN, "Macular Grid.Inner Inferior Subfield Thickness")	1	M	UNITS = EV (um, UCUM, "micrometer")
9	>	CONTAINS	NUM	EV (57113-3, LN, "Macular Grid.Inner Temporal Subfield Thickness")	1	M	UNITS = EV (um, UCUM, "micrometer")
10	>	CONTAINS	NUM	EV (57114-1, LN, "Macular Grid.Outer Superior Subfield Thickness")	1	M	UNITS = EV (um, UCUM, "micrometer")
11	>	CONTAINS	NUM	EV (57115-8, LN, "Macular Grid.Outer Nasal Subfield Thickness")	1	M	UNITS = EV (um, UCUM, "micrometer")
12	>	CONTAINS	NUM	EV (57116-6, LN, "Macular Grid.Outer Inferior Subfield Thickness")	1	M	UNITS = EV (um, UCUM, "micrometer")
13	>	CONTAINS	NUM	EV (57117-4, LN, "Macular Grid.Outer Temporal Subfield Thickness")	1	M	UNITS = EV (um, UCUM, "micrometer")
14	>	CONTAINS	NUM	EV (57118-2, LN, "Macular Grid.Total Volume")	1	M	UNITS = EV (mm3, UCUM, "mm3")
15	>	CONTAINS	NUM	EV (111691, DCM, "Number of Images Used for Macular Measurements")	1	M	UNITS = EV ({images}, UCUM, "images")
16	>	CONTAINS	NUM	EV (111692, DCM, "Number of Samples Used per Image")	1	M	UNITS = EV ({samples}, UCUM, "samples")
17	>	CONTAINS	NUM	EV (111693, DCM, "Analysis Quality Rating")	1	M	UNITS = EV ({0:100}, UCUM, "range:0:100") Value = 0 - 100
18	>>	HAS OBS CONTEXT	INCLUDE	DTID 2102 “Quality Rating Identification”	1	M
19	>	CONTAINS	NUM	EV (111694, DCM, "Image Set Quality Rating")	1	M	UNITS = EV ({0:100}, UCUM, "range:0:100") Value = 0 - 100
20	>>	HAS OBS CONTEXT	INCLUDE	DTID 2102 “Quality Rating Identification”	1	M
21	>	CONTAINS	NUM	EV (111029, DCM, "Image Quality Rating")	1-n	U	UNITS = EV ({0:100}, UCUM, "range:0:100") Value = 0 - 100
22	>>	INFERRED FROM	IMAGE		1	M
23	>>	HAS OBS CONTEXT	INCLUDE	DTID 2102 “Quality Rating Identification”	1	M
24	>	CONTAINS	CODE	EV (111696, DCM, "Visual Fixation Quality During Acquisition")	1	U	DCID 4220 “Visual Fixation Quality During Acquisition”
25	>>	HAS CONCEPT MOD	CODE	EV (111697, DCM, "Visual Fixation Quality Problem")	1-n	U	DCID 4221 “Visual Fixation Quality Problem”
26	>	CONTAINS	CODE	EV (111698, DCM, "Ophthalmic Macular Grid Problem")	1-n	U	DCID 4222 “Ophthalmic Macular Grid Problem”
27	>	CONTAINS	TEXT	EV (121106, DCM, "Comment")	1	U

Content Item Descriptions

Row 22

No purpose of reference is specified.

TID 2102 Quality Rating Identification

This Template specifies the algorithm (and parameters) used to create a quality rating for an image or image set.

It is expected that the identified algorithm will create a consistent quality rating when analyzing a given image. If the algorithm allows change to its parameters that would alter the quality rating created, the specific parameters used should be specified.

Type:: Non-Extensible
Order:: Significant
Root:: No

Table TID 2102. Quality Rating Identification

	VT	Concept Name	VM	Req Type
1	TEXT	EV (111001, DCM, "Algorithm Name")	1	M
2	TEXT	EV (111003, DCM, "Algorithm Version")	1	M
3	TEXT	EV (122405, DCM, "Algorithm Manufacturer")	1	M
4	TEXT	EV (111002, DCM, "Algorithm Parameters")	1-n	U

TID 2120 Ophthalmology Measurements Group

This Template is a proper subset of TID 1501, with some optional extensions, and may be processed by a receiving application in the same way. The parameters used in this Template are identical to those parameters as used in TID 1501. However, this Template is specialized for ophthalmology (finding site "Eye") , and makes mandatory a Content Item for each measuement or finding concept specified in the invoking Template in the Context Groups invoked for the $Measurement parameter (TID 1501 has no mandatory content).

Table TID 2120. Parameters

Parameter Name	Parameter Usage
$TargetSiteMod	Value for Anatomic Location of measurement
$Method	Value for Measurement Method
$Measurement	Coded term or Context Group for Concept Name of mandatory measurements
$OptMeasure	Coded term or Context Group for Concept Name of optional measurements
$TableName	Coded term for Concept Name of a table of measurements

Type:: Extensible
Order:: Non-Significant
Root:: No

Table TID 2120. Ophthalmology Measurements Group

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1		CONTAINS	CONTAINER	EV (125007, DCM, "Measurement Group")	1	M
2	>	HAS CONCEPT MOD	CODE	EV (363698007, SCT, "Finding Site")	1	M		EV (81745001, SCT, "Eye")
3	>>	HAS CONCEPT MOD	CODE	EV (272741003, SCT, "Laterality")	1	M		DCID 247 “Laterality Left-Right Only”
4	>>	HAS CONCEPT MOD	CODE	EV (106233006, SCT, "Topographical modifier")	1	MC	IFF Template is invoked with a non-empty $TargetSiteMod parameter	$TargetSiteMod
5	>	HAS CONCEPT MOD	CODE	EV (370129005, SCT, "Measurement Method")	1	MC	IFF Template is invoked with a non-empty $Method parameter	$Method
6	>	HAS OBS CONTEXT	CODE	EV (418775008, SCT, "Finding Method")	1	MC	IFF measurements made with ROI or sector grid positioned differently from prior analyses	EV (131247, DCM, "Repositioned ROI or grid")
7	>	HAS OBS CONTEXT	INCLUDE	DTID 4108 “Tracking Identifier”	1	U
8	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1-n	MC	IFF Template is invoked with a non-empty $Measurement parameter (see Content Item Description)	$Measurement = $Measurement
9	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1-n	U		$Measurement = $OptMeasure
10	>	CONTAINS	TABLE	$TableName	1	U
11	>	CONTAINS	IMAGE	EV (121112, DCM, "Source of Measurement")	1-n	U
12	>	CONTAINS	NUM	EV (111694, DCM, "Image Set Quality Rating")	1	UC	XOR Row 13	UNITS = EV ({0:100}, UCUM, "range:0:100") Value = 0 - 100
13	>	CONTAINS	CODE	EV (111101, DCM, "Image Quality")	1	UC	XOR Row 12	BCID 3114 “Study Quality”
14	>	CONTAINS	IMAGE	EV (130401, DCM, "Visual explanation")	1	U
15	>	CONTAINS	COMPOSITE	EV (130401, DCM, "Visual explanation")	1	U
16	>	CONTAINS	TEXT	EV (121106, DCM, "Comment")	1	U

Content Item Descriptions

Row 8	Mandatory numeric findings of the measurement group. Each Concept specified in the Value Set Constraints (i.e., as specified in the invoking Template $Measurement parameter) shall be encoded in a NUM Content Item. Thus if there are eight concepts in the specified Context Group, eight NUM Content Items in accordance with TID 300 will be present. Note that the NUM Content Item allows an absent value with an associated reason code per CID 42, e.g., (114007, DCM, "Measurement not attempted"). TID 300 “Measurement” defines an optional capability to specify properties of a measurement via TID 310 “Measurement Properties”. TID 310 supports properties such as normality, statistical properties (through subsidiary TID 311), normal ranges (subsidiary TID 312) , level of significance and more. Normality flags are highly useful and commonly provided by implementations.
Row 9	Optional numeric measurements of the measurement group.
Row 10	Optional table of numeric measurements of the measurement group.
Row 11	Reference to the original image(s) , e.g., Ophthalmic Tomography, that provided the data analyzed to produce the measurements in this group.
Rows 12, 13	A numeric (row 12) or categorical (row 13) rating of the quality of the source images for the purpose of producing the measurements in this group.
Rows 14, 15	May be a reference to a Secondary Capture Image (row 14) or Encapsulated PDF (row 15) rendering of the set of measurements and findings encoded in this Measurement Group, and possibly additional data.

TID 2121 Visual Field Key Measurements

Type:: Extensible
Order:: Non-Significant
Root:: Yes

Table TID 2121. Visual Field Key Measurements

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CONTAINER	EV (131240, DCM, "Visual Field Key Measurements")	1	M
2	>	HAS CONCEPT MOD	INCLUDE	DTID 1204 “Language of Content Item and Descendants”	1	U
3	>	HAS OBS CONTEXT	INCLUDE	DTID 1002 “Observer Context”	1-n	U
4	>	HAS OBS CONTEXT	INCLUDE	DTID 4019 “Algorithm Identification”	1	U
5	>	CONTAINS	CONTAINER	EV (125007, DCM, "Measurement Group")	1-n	M
6	>>	HAS CONCEPT MOD	CODE	EV (363698007, SCT, "Finding Site")	1	M		EV (81745001, SCT, "Eye")
7	>>>	HAS CONCEPT MOD	CODE	EV (272741003, SCT, "Laterality")	1	M		DCID 247 “Laterality Left-Right Only”
8	>>	HAS CONCEPT MOD	CODE	EV (370129005, SCT, "Measurement Method")	1	M		DCID 4250 “Visual Field Static Perimetry Test Pattern”
9	>>	HAS ACQ CONTEXT	CODE	EV (246501002, SCT, "Technique")	1	M		DCID 4251 “Visual Field Static Perimetry Test Strategy”
10	>>	HAS OBS CONTEXT	INCLUDE	DTID 4108 “Tracking Identifier”	1	U
11	>>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M		$Measurement = EV (131248, DCM, "Visual Field Global Deviation from Normal") $Units = EV (dB, UCUM, "dB")
12	>>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M		$Measurement = EV (131249, DCM, "Visual Field Localized Deviation From Normal") $Units = EV (dB, UCUM, "dB")
13	>>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U		$Measurement = BCID 4280 “Visual Field Measurements”
14	>>	CONTAINS	INCLUDE	DTID 314 “Ratio”	1	MC	IF Row 15 not present	$Measurement = EV (131250, DCM, "Fixation false positive ratio") $NumUnits = EV ({false positives}, UCUM, "false positives") $DenomUnits = EV ({trials}, UCUM, "trials")
15	>>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	MC	IF Row 14 not present	$Measurement = EV (131251, DCM, "Fixation false positive percent") $Units = EV (%, UCUM, "%")
16	>>	CONTAINS	INCLUDE	DTID 314 “Ratio”	1	MC	IF Row 17 not present	$Measurement = EV (131252, DCM, "Fixation false negative ratio") $NumUnits = EV ({false negatives}, UCUM, "false negatives") $DenomUnits = EV ({trials}, UCUM, "trials")
17	>>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	MC	IF Row 16 not present	$Measurement = EV (131253, DCM, "Fixation false negative percent") $Units = EV (%, UCUM, "%")
18	>>	CONTAINS	INCLUDE	DTID 314 “Ratio”	1	M		$Measurement = EV (131254, DCM, "Fixation losses ratio") $NumUnits = EV ({fixation losses}, UCUM, "fixation losses") $DenomUnits = EV ({trials}, UCUM, "trials")
19	>>	CONTAINS	CODE	EV (111855, DCM, "Glaucoma Hemifield Test Analysis")	1	U		DCID 4254 “Visual Field Static Perimetry Test Analysis Result”
20	>>	CONTAINS	COMPOSITE	EV (121112, DCM, "Source of Measurement")	1	U
21	>>	CONTAINS	IMAGE	EV (130401, DCM, "Visual explanation")	1	U
22	>>	CONTAINS	COMPOSITE	EV (130401, DCM, "Visual explanation")	1	U
23	>>	CONTAINS	TEXT	EV (121106, DCM, "Comment")	1	U

Content Item Descriptions

Row 5	For example, the Measurement Group CONTAINER may be instantiated once for each eye, or multiple times for a trend series for a single eye.
Row 20	May be a reference to an Ophthalmic Visual Field Static Perimetry Measurements SOP Instance.
Rows 21, 22	May be a reference to a Secondary Capture Image (row 21) or Encapsulated PDF (row 22) rendering of the set of measurements and findings encoded in this Measurement Group, and possibly additional data.

TID 2122 Optic Disc Key Measurements

Type:: Extensible
Order:: Non-Significant
Root:: Yes

Table TID 2122. Optic Disc Key Measurements

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CONTAINER	EV (131241, DCM, "Optic Disc Key Measurements")	1	M
2	>	HAS CONCEPT MOD	INCLUDE	DTID 1204 “Language of Content Item and Descendants”	1	U
3	>	HAS OBS CONTEXT	INCLUDE	DTID 1002 “Observer Context”	1-n	U
4	>	HAS OBS CONTEXT	INCLUDE	DTID 4019 “Algorithm Identification”	1	M
5	>	CONTAINS	INCLUDE	DTID 2120 “Ophthalmology Measurements Group”	1-n	M	$Measurement = DCID 4281 “Optic Disc Key Measurements”

Content Item Descriptions

Row 5

For example, TID 2120 may be invoked once for each eye, or multiple times for a trend series for a single eye.

TID 2123 Circumpapillary Retinal Nerve Fiber Layer Key Measurements

Type:: Extensible
Order:: Non-Significant
Root:: Yes

Table TID 2123. Circumpapillary Retinal Nerve Fiber Layer Key Measurements

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CONTAINER	EV (131242, DCM, "Circumpapillary Retinal Nerve Fiber Layer Key Measurements")	1	M
2	>	HAS CONCEPT MOD	INCLUDE	DTID 1204 “Language of Content Item and Descendants”	1	U
3	>	HAS OBS CONTEXT	INCLUDE	DTID 1002 “Observer Context”	1-n	U
4	>	HAS OBS CONTEXT	INCLUDE	DTID 4019 “Algorithm Identification”	1	M
5	>	CONTAINS	INCLUDE	DTID 2120 “Ophthalmology Measurements Group”	1-n	U		$Method = DCID 4282 “Retinal Sector Methods” $Measurement = EV (131274, DCM, "Retinal ROI width") $OptMeasurement = DCID 4283 “RNFL Sector Measurements”
6	>	CONTAINS	INCLUDE	DTID 2120 “Ophthalmology Measurements Group”	1-n	U		$Method = EV (131308, DCM, "RNFL Clockface Method") $Measurement = DCID 4284 “RNFL Clockface Measurements”
7	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	MC	IFF RNFL thickness measurements made on both eyes	$Measurement = EV (131273, DCM, "Retinal nerve fiber layer symmetry") $Units =(%, UCUM, "%")

Content Item Descriptions

Row 5

For example, TID 2120 may be invoked once for each eye, or multiple times for a trend series for a single eye.

Applications also use various approaches to identifying different sectors of the retina when measuring the RNFL thickness. The sector definition used is specified by a concept from CID 4282 “Retinal Sector Methods”. Measurements that match the sector names defined by the method may be selected from CID 4283 “RNFL Sector Measurements” to be included in the key measurements.

Receiving applications are cautioned about comparing or aggregating measurements from measurement groups with different ROI areas or sector methods.

TID 2124 Macular Thickness Key Measurements

The macular grid used for the measurements of this template is based upon the grid employed by the Early Treatment of Diabetic Retinopathy Study (ETDRS) to measure area and proximity of macular edema to the anatomic center (fovea) of the macula. See [ETDRS Report Number 10].

Type:: Extensible
Order:: Non-Significant
Root:: Yes

Table TID 2124. Macular Thickness Key Measurements

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CONTAINER	EV (131243, DCM, "Macular Thickness Key Measurements")	1	M
2	>	HAS CONCEPT MOD	INCLUDE	DTID 1204 “Language of Content Item and Descendants”	1	U
3	>	HAS OBS CONTEXT	INCLUDE	DTID 1002 “Observer Context”	1-n	U
4	>	HAS OBS CONTEXT	INCLUDE	DTID 4019 “Algorithm Identification”	1	M
5	>	CONTAINS	INCLUDE	DTID 2120 “Ophthalmology Measurements Group”	1-n	M	$Measurement = DCID 4285 “Macular Thickness Key Measurements”

Content Item Descriptions

Row 5

For example, TID 2120 may be invoked once for each eye, or multiple times for a trend series for a single eye.

TID 2125 Ganglion Cell Key Measurements

Type:: Extensible
Order:: Non-Significant
Root:: Yes

Table TID 2125. Ganglion Cell Key Measurements

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CONTAINER	EV (131244, DCM, "Ganglion Cell Key Measurements")	1	M
2	>	HAS CONCEPT MOD	INCLUDE	DTID 1204 “Language of Content Item and Descendants”	1	U
3	>	HAS OBS CONTEXT	INCLUDE	DTID 1002 “Observer Context”	1-n	U
4	>	HAS OBS CONTEXT	INCLUDE	DTID 4019 “Algorithm Identification”	1	M
5	>	CONTAINS	INCLUDE	DTID 2120 “Ophthalmology Measurements Group”	1-n	M	$TargetSiteMod= DCID 4286 “Ganglion Cell Measurement Extent” $Method = DCID 4289 “Ganglion Cell Sector Methods” $Measurement = DCID 4287 “Ganglion Cell Key Measurements” $OptMeasure = DCID 4288 “Ganglion Cell Sector Measurements” $TableName = DT (131298, DCM, "Average ganglion cell thickness in posterior pole grid")

Content Item Descriptions

Row 5

For example, TID 2120 may be invoked once for each eye, or multiple times for a trend series for a single eye.

Methods to measure the Ganglion Cell thickness vary widely. This template requires the SOP Instance creator application to specify which other cell layers, if any, are measured with the Ganglion Cell Layer proper (using a concept from CID 4286 “Ganglion Cell Measurement Extent”).

Applications also use various methods to identify different sectors of the retina when measuring the Ganglion Cell thickness. The sector definition used is specified by a concept from CID 4289 “Ganglion Cell Sector Methods”. Measurements matching the sector names defined by the method may be selected from CID 4288 “Ganglion Cell Sector Measurements”. If the sector method uses a rectangular or elliptical ROI, the sector measurements should include both the ROI width and height.

If optional measurements using (131298, DCM, "Average ganglion cell thickness in posterior pole grid") are present, the SOP Class of the instance must support the TABLE Content Item Value Type (e.g., the Extensible SR Storage SOP Class).

Receiving applications are cautioned about comparing or aggregating measurements from measurement groups with different measurement extents or sector methods.

TID 2126 Endothelial Cell Count Key Measurements

Type:: Extensible
Order:: Non-Significant
Root:: Yes

Table TID 2126. Endothelial Cell Count Key Measurements

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CONTAINER	EV (131245, DCM, "Endothelial Cell Count Key Measurements")	1	M
2	>	HAS CONCEPT MOD	INCLUDE	DTID 1204 “Language of Content Item and Descendants”	1	U
3	>	HAS OBS CONTEXT	INCLUDE	DTID 1002 “Observer Context”	1-n	U
4	>	HAS OBS CONTEXT	INCLUDE	DTID 4019 “Algorithm Identification”	1	M
5	>	CONTAINS	INCLUDE	DTID 2120 “Ophthalmology Measurements Group”	1-n	M	$Measurement = DCID 4290 “Endothelial Cell Count Measurements”

Content Item Descriptions

Row 5

For example, TID 2120 may be invoked once for each eye, or multiple times for a trend series for a single eye.

TID 2127 Ophthalmic Image ROI Measurements

Type:: Extensible
Order:: Non-Significant
Root:: Yes

Table TID 2127. Ophthalmic Image ROI Measurements

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CONTAINER	EV (131246, DCM, "Ophthalmic Image ROI Measurements")	1	M
2	>	HAS CONCEPT MOD	INCLUDE	DTID 1204 “Language of Content Item and Descendants”	1	U
3	>	HAS OBS CONTEXT	INCLUDE	DTID 1002 “Observer Context”	1-n	U
4	>	HAS OBS CONTEXT	INCLUDE	DTID 4019 “Algorithm Identification”	1	U
5	>	CONTAINS	INCLUDE	DTID 2120 “Ophthalmology Measurements Group”	1-n	M	$OptMeasure = DCID 4291 “Ophthalmic Image ROI Measurements”

Content Item Descriptions

Row 5

For example, TID 2120 may be invoked once for each eye, or multiple times for a trend series for a single eye, or multiple times for different classes of measurements.

No mandatory key measurements are specified. Creating applications may include any measurements or findings.

Procedure Log IOD Templates

TID 3001 Procedure Log

The Procedure Log Template is intended for the representation of reports or logs of time-stamped events occurring during an image-guided interventional or other procedure.

This Template does not require a particular ordering of the subsidiary Content Items.

Note

The Procedure Log IOD (PS3.3) requires ordering by Observation DateTime; thus log entries of different types (i.e., specified by different Rows in the Template) may appear in any order.
While this Template is extensible, the Procedure Log IOD forbids Container Content Items subsidiary to the top level Container.

Type:: Extensible
Order:: Non-Significant
Root:: Yes

Table TID 3001. Procedure Log

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CONTAINER	DCID 3400 “Procedure Log Title”	1	M
2	>		INCLUDE	DTID 1002 “Observer Context”	1-n	M
3	>		INCLUDE	DTID 3601 “Procedure Context”	1	M
4	>	HAS ACQ CONTEXT	TEXT	EV (121121, DCM, "Room identification")	1	U
5	>	HAS ACQ CONTEXT	TEXT	EV (121122, DCM, "Equipment identification")	1-n	U
6	>	CONTAINS	TEXT	DCID 3401 “Log Note Type”	1-n	U
7	>>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U
8	>	CONTAINS	CODE	EV (121123, DCM, "Patient Status or Event")	1-n	U	DCID 3402 “Patient Status and Event”
9	>>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U
10	>	CONTAINS	PNAME	DCID 3404 “Staff Action”	1-n	U
11	>>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U
12	>	CONTAINS	TEXT	DCID 3427 “Equipment Event”	1-n	U	Equipment identifier
13	>>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U
14	>	CONTAINS	INCLUDE	DTID 3100 “Procedure Action”	1-n	U
15	>	CONTAINS	INCLUDE	DTID 3101 “Image Acquisition”	1-n	U
16	>	CONTAINS	INCLUDE	DTID 3102 “Waveform Acquisition”	1-n	U
17	>	CONTAINS	INCLUDE	DTID 3103 “Referenced Object”	1-n	U
18	>	CONTAINS	INCLUDE	DTID 3104 “Consumables”	1-n	U
19	>	CONTAINS	INCLUDE	DTID 3105 “Lesion Identification and Properties”	1-n	U
20	>	CONTAINS	INCLUDE	DTID 3106 “Drugs/Contrast Administered”	1-n	U
21	>	CONTAINS	INCLUDE	DTID 3107 “Device Used”	1-n	U
22	>	CONTAINS	INCLUDE	DTID 3108 “Intervention”	1-n	U
23	>	CONTAINS	CODE	EV (116224001, SCT, "Complication of Procedure")	1-n	U	DCID 3413 “Adverse Outcome”
24	>>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U
25	>	CONTAINS	INCLUDE	DTID 3109 “Measurements”	1-n	U
26	>	CONTAINS	INCLUDE	DTID 3110 “Impressions or Findings”	1-n	U
27	>	CONTAINS	INCLUDE	DTID 3111 “Percutaneous Entry”	1-n	U
28	>	CONTAINS	INCLUDE	DTID 3112 “Specimen Obtained”	1-n	U
29	>	CONTAINS	INCLUDE	DTID 3113 “Patient Support”	1-n	U
30	>	CONTAINS	INCLUDE	DTID 3114 “Patient Assessment”	1-n	U
31	>	CONTAINS	INCLUDE	DTID 3115 “ECG ST Assessment”	1-n	U

Content Item Descriptions

Row 2	Includes TID 1002 “Observer Context”, which shall be used to record the identity of the person responsible for recording the log, as well as all other participants in the procedure, even though these personnel may not technically be "observers" of the Procedure Log. As participants in the procedure, they are potential sources for events and observations recorded in the Log. TID 1002 “Observer Context” allows the specification of the person's role in the organization (e.g., physician, nurse), as well as the role in the procedure (e.g., circulating, performing, etc.).
Row 5	Shall be used to record the identity of the major equipment used in the procedure.
Row 6	May be used to record any event not covered by a specific log entry Template.

TID 3010 Log Entry Qualifiers

The Log Entry Qualifiers Template provides a common means for adding additional description to a procedure log Content Item. It allows identification of a source for the procedure log entry (other than the recording observer for the log as a whole), a free text comment, a link to a particular Procedure Action item, a link to a particular lesion, or the date/time of recording (if different than the time of the event occurrence recorded in the Observation DateTime of the parent Content Item).

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3010. Log Entry Qualifiers

	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1		INCLUDE	DTID 1000 “Quotation”	1	U
2	HAS PROPERTIES	TEXT	EV (121106, DCM, "Comment")	1	U
3	HAS OBS CONTEXT	TEXT	EV (121124, DCM, "Procedure Action ID")	1-n	U
4	HAS OBS CONTEXT	TEXT	EV (121151, DCM, "Lesion Identifier")	1-n	U	Up to 3 numeric characters
5	HAS OBS CONTEXT	DATETIME	EV (121125, DCM, "DateTime of Recording of Log Entry")	1	U
6	INFERRED FROM	IMAGE		1-n	U
7	INFERRED FROM	WAVEFORM		1-n	U
8	INFERRED FROM	COMPOSITE		1-n	U
9	HAS OBS CONTEXT	CODE	EV (121135, DCM, "Observation DateTime Qualifier")	1	U	DCID 3430 “DateTime Qualifier”

Content Item Descriptions

Row 3	Procedure Action ID allows linking recorded events to a particular action, step, or phase of a procedure. See description for TID 3100 “Procedure Action”.
Row 4	Lesion Identifier is specified as a numeric text string, and allows linking recorded events to the diagnosis or therapy of particular lesion. See description for TID 3105 “Lesion Identification and Properties”.

TID 3100 Procedure Action

The Procedure Action Template is intended for the recording of the beginning or end of procedure steps or action items in a procedure. The level of granularity of the recorded events is not specified, and may vary between institutions, or even be at multiple levels within a single procedure log. There is no requirement for the real-world procedure step or action item recorded with this Template to end before another one begins; there may be overlapping or simultaneous procedure steps or action items.

This log entry Template may be used to record the start or stop of timers.

Other recorded events in the procedure may be linked to a particular step or action item by Procedure Action ID (see TID 3010 “Log Entry Qualifiers”).

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3100. Procedure Action

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CODE	DCID 3421 “Procedure Action”	1	M		BCID 3405 “Procedure Action Value”
2	>	HAS PROPERTIES	TEXT	EV (121124, DCM, "Procedure Action ID")	1	M
3	>	HAS PROPERTIES	PNAME	BCID 7453 “Performing Role”	1-n	U
4	>	HAS PROPERTIES	NUM	EV (121128, DCM, "Procedure Action Duration")	1	U
5	>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U
6	>	HAS PROPERTIES	UIDREF	EV (121126, DCM, "Performed Procedure Step SOP Instance UID")	1	MC	IFF a Performed Procedure Step SOP Class is used to provide status of the Procedure Step
7	>	HAS PROPERTIES	UIDREF	EV (121127, DCM, "Performed Procedure Step SOP Class UID")	1	MC	IFF a Performed Procedure Step SOP Class is used to provide status of the Procedure Step

Content Item Descriptions

Row 2	The value of the Procedure Action ID shall be uniquely associated with the step or action within the context of the Study, and may be used to associate various Procedure Log entries with the step or action.
Row 3	May be used to record the identity of staff roles for the purpose of this Procedure Action, which may differ from their roles in the procedure as a whole.

TID 3101 Image Acquisition

The Image Acquisition Template allows recording of the essential parameters of a digital image acquired during the procedure.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3101. Image Acquisition

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			IMAGE	EV (121138, DCM, "Image Acquired")	1	M
2	>	HAS ACQ CONTEXT	UIDREF	EV (112002, DCM, "Series Instance UID")	1	M
3	>	HAS ACQ CONTEXT	CODE	EV (121139, DCM, "Modality")	1	M	DCID 29 “Acquisition Modality” A code derived from the Value of Modality (0008,0060).
4	>	HAS PROPERTIES	NUM	EV (121140, DCM, "Number of Frames")	1	U
5	>	HAS PROPERTIES	TEXT	EV (121141, DCM, "Image Type")	1	U	From Referenced Image SOP Instance (0008,0008)
6	>	HAS ACQ CONTEXT	NUM	EV (112011, DCM, "Positioner Primary Angle")	1	U	UNITS = EV (deg, UCUM, "deg")
7	>	HAS ACQ CONTEXT	NUM	EV (112012, DCM, "Positioner Secondary Angle")	1	U	UNITS = EV (deg, UCUM, "deg")
8	>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U

TID 3102 Waveform Acquisition

The Waveform Acquisition Template allows recording of the essential parameters of a digital waveform acquired during the procedure.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3102. Waveform Acquisition

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			WAVEFORM	EV (121143, DCM, "Waveform Acquired")	1	M
2	>	HAS ACQ CONTEXT	CODE	EV (121139, DCM, "Modality")	1	M	DCID 29 “Acquisition Modality” A code derived from the Value of Modality (0008,0060).
3	>	HAS ACQ CONTEXT	NUM	EV (121142, DCM, "Acquisition Duration")	1	U
4	>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U

TID 3103 Referenced Object

The Referenced Object Template allows reference to measurement or report objects, such as prior medical reports, laboratory results, hemodynamic measurement reports, or quantitative analysis reports.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3103. Referenced Object

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			COMPOSITE	BCID 3407 “Object Reference Purpose”	1	M
2	>	HAS PROPERTIES	CODE	EV (121144, DCM, "Document Title")	1	MC	IFF Row 1 references an SR object	Root node concept of referenced SR object
3	>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U

TID 3104 Consumables

The Consumables Template allows recording of devices (e.g., catheters or stents), drugs, or contrast agents accessed in a procedure. This Content Item is directed towards inventory control and billing. The actual clinical use of the particular consumable is recorded using TID 3106 “Drugs/Contrast Administered” or TID 3107 “Device Used”.

This Template allows recording both consumable retrieval from, and return to, inventory or stock, and disposal of used material. The quantity involved in each recorded transaction may be specified.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3104. Consumables

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CODE	DCID 3408 “Consumable Action”	1	M	Vendor or local bar coded values
2	>	HAS PROPERTIES	TEXT	DCID 3426 “Consumables Parameter”	1-n	U
3	>	HAS PROPERTIES	NUM	EV (121146, DCM, "Quantity of Material")	1	U
4	>	HAS PROPERTIES	CODE	EV (121147, DCM, "Billing Code")	1	U	local billing codes
5	>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U

TID 3105 Lesion Identification and Properties

The Lesion Identification and Properties Template allows recording the identification of each lesion addressed in a procedure. The lesion identifier may be used to relate diagnostic or therapeutic actions with their target lesion (see Row 4 in TID 3010 “Log Entry Qualifiers”). This Content Item may include the initial visually estimated measurements of stenosis or TIMI flow; measured values from a quantitative measurement report may be referenced indirectly (through TID 3103 “Referenced Object”), or by quotation (TID 3109 “Measurements”). Subsequent (e.g., post-intervention) stenosis measurements may be encoded using TID 3109 “Measurements”, with the Lesion Identifier conveyed through its subsidiary TID 3010 “Log Entry Qualifiers” Template.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3105. Lesion Identification and Properties

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			TEXT	EV (121151, DCM, "Lesion Identifier")	1	M		Up to 3 numeric characters
2	>	HAS PROPERTIES	CODE	EV (363698007, SCT, "Finding Site")	1	M		DCID 3604 “Arterial Lesion Location”
3	>>	HAS CONCEPT MOD	CODE	EV (106233006, SCT, "Topographical modifier")	1	U		DCID 3019 “Cardiovascular Anatomic Structure Modifier”
4	>	HAS PROPERTIES	CODE	EV (121153, DCM, "Lesion Risk")	1	U		DCID 3418 “Lesion Risk”
5	>	HAS PROPERTIES	NUM	EV (408715008, SCT, "Lumen Diameter Stenosis")	1	U		UNITS = EV (%, UCUM, "%")
6	>>	HAS CONCEPT MOD	CODE	EV (129085009, SCT, "Catheterization Procedure Phase")	1	M		EV (128955008, SCT, "Baseline Phase")
7	>>	HAS CONCEPT MOD	CODE	EV (121401, DCM, "Derivation")	1	U		DCID 3745 “Calculation Method”
8	>	HAS PROPERTIES	CODE	EV (122109, DCM, "Baseline TIMI Flow")	1	UC	IFF Row 2 specifies a coronary artery	DCID 3713 “TIMI Flow Characteristic”
9	>	HAS PROPERTIES	CODE	EV (122131, DCM, "Degree of Thrombus")	1	U		DCID 3714 “Thrombus”
10	>	HAS PROPERTIES	CODE	EV (129737002, SCT, "Lesion Margin Characteristics")	1	U		DCID 3715 “Lesion Margin”
11	>	HAS PROPERTIES	CODE	EV (122134, DCM, "Vessel Morphology")	1-n	U		DCID 3712 “Vessel Descriptor”
12	>	HAS PROPERTIES	CODE	EV (122132, DCM, "Severity of Calcification")	1	U		DCID 3716 “Severity”
13	>	HAS PROPERTIES	IMAGE	DT (121080, DCM, "Best illustration of finding")	1	U
14	>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U

Content Item Descriptions

Row 1

Lesion Identifier is specified as a numeric text string in order to facilitate transcoding to DICOM Attribute (0018,3105) Lesion Number and to formats for outcomes registries, such as the ACC National Cardiovascular Data Registry™.

TID 3106 Drugs/Contrast Administered

The Drugs/Contrast Administered Template allows the recording of the start or end of that type of event, together with its parameters. If start and end are represented by a single log entry (e.g., for an injection), the concept name "Drug/contrast administered" shall be used.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3106. Drugs/Contrast Administered

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CODE	DCID 3409 “Drug/Contrast Administration”	1	M	BCID 10 “Interventional Drug” or BCID 12 “Imaging Contrast Agent”
2	>	HAS PROPERTIES	TEXT	EV (121145, DCM, "Description of Material")	1	U
3	>	HAS PROPERTIES	CODE	EV (410675002, SCT, "Route of administration")	1	U	BCID 11 “Administration Route”
4	>	HAS PROPERTIES	NUM	DCID 3410 “Drug/Contrast Numeric Parameter”	1-n	U
5	>	HAS PROPERTIES	PNAME	EV (121152, DCM, "Person administering drug/contrast")	1	U
6	>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U

TID 3107 Device Used

The Device Used Template allows recording of the use of interventional diagnostic and therapeutic devices.

The identification of one device used to deploy another device (e.g., a balloon catheter to deploy a stent) may be described with two entries, with one identified as a deployment device in the Concept Modifier of Row 6 of this Template, and linked by the same Procedure Action ID in the Log Entry Qualifiers of the included TID 3010 “Log Entry Qualifiers”.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3107. Device Used

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CODE	DCID 3422 “Device Use Action”	1	M	BCID 3429 “Catheterization Device”
2	>	HAS PROPERTIES	CODE	EV (121150, DCM, "Device Code")	1-n	U	Vendor or local bar coded values
3	>	HAS PROPERTIES	TEXT	EV (121145, DCM, "Description of Material")	1	U
4	>	HAS PROPERTIES	NUM	DCID 3423 “Numeric Device Characteristic”	1-n	U
5	>	HAS PROPERTIES	CODE	EV (363704007, SCT, "Procedure site")	1	U	BCID 3630 “Cardiovascular Anatomic Location”
6	>	HAS CONCEPT MOD	CODE	EV (363703001, SCT, "Has Intent")	1	U	DT (121155, DCM, "Deployment")
7	>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U

TID 3108 Intervention

The Intervention Template allows recording of interventions, including atherectomy, angioplasty, stent placement, brachytherapy, etc. The record may include reference to an image that documents the intervention.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3108. Intervention

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CODE	EV (122090, DCM, "Intervention Action")	1	M		DCID 3412 “Intervention Action/Status”
2	>	HAS PROPERTIES	CODE	EV (363704007, SCT, "Procedure site")	1	M		DCID 3604 “Arterial Lesion Location”
3	>>	HAS CONCEPT MOD	CODE	EV (106233006, SCT, "Topographical modifier")	1	U		DCID 3019 “Cardiovascular Anatomic Structure Modifier”
4	>	HAS PROPERTIES	TEXT	EV (121154, DCM, "Intervention attempt identifier")	1	M		Up to 3 numeric characters
5	>	HAS PROPERTIES	CODE	EV (116682006, SCT, "Uses Equipment")	1-n	U		BCID 3411 “Intracoronary Device”
6	>>	HAS CONCEPT MOD	CODE	EV (122111, DCM, "Primary Intervention Device")	1	MC	IF Device is Primary for this Lesion	DCID 230 “Yes-No”
7	>	HAS PROPERTIES	NUM	DCID 3425 “Intervention Parameter”	1-n	U
8	>	HAS PROPERTIES	IMAGE	BCID 7003 “Diagnostic Imaging Report Purpose of Reference”	1	U
9	>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U

Content Item Descriptions

Row 4

Intervention attempt Identifier is specified as a numeric text string, and shall be treated as the ordinal of the recorded attempted intervention within this procedure (i.e., "1" for the first attempted intervention, "2" for the second, etc.).

TID 3109 Measurements

The Measurements Template allows recording of significant measurements, such as vital signs, laboratory results, hemodynamic measurements, or quantitative analysis measurements. These measurements are often quoted from another source, which would be documented in the included TID 3010 “Log Entry Qualifiers”.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3109. Measurements

	NL	Rel with Parent	VT	Concept Name	VM	Req Type
1			NUM		1	U
2	>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U
3	>	HAS PROPERTIES	INCLUDE	DTID 310 “Measurement Properties”	1	U
4			CODE		1	U
5	>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U

TID 3110 Impressions or Findings

The Impressions or Findings Template allows the recording of unconfirmed (provisional) impressions or findings noted during the procedure. It is not intended to convey the Cath Lab Clinical Report (the formal report from the performing physician), although it may be used (like any Procedure Log entry) for the subsequent construction of the Cath Lab Clinical Report.

A finding that is supported by a specific image frame may reference that image in the INFERRED FROM / IMAGE row of the included TID 3010 “Log Entry Qualifiers” Template.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3110. Impressions or Findings

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CODE	EV (121071, DCM, "Finding")	1	U	BCID 3728 “Cath Finding”
2	>	HAS PROPERTIES	CODE	EV (246112005, SCT, "Severity")	1	U	DCID 3716 “Severity”
3	>	HAS PROPERTIES	CODE	EV (363698007, SCT, "Finding Site")	1	U
4	>>	HAS CONCEPT MOD	CODE	EV (106233006, SCT, "Topographical modifier")	1	U	DCID 3019 “Cardiovascular Anatomic Structure Modifier”
5	>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U
6			TEXT	BCID 3419 “Finding Title”	1	U
7	>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U

Content Item Descriptions

Row 3

Finding Site has no Baseline Context ID specified. Typically terms would be drawn from coronary segments, other arterial segments, myocardial segments, etc.

TID 3111 Percutaneous Entry

The Percutaneous Entry Template allows recording of the opening or closing of invasive access ports.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3111. Percutaneous Entry

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CODE	EV (121156, DCM, "Percutaneous Entry Action")	1	M	DCID 3403 “Percutaneous Entry”
2	>	HAS CONCEPT MOD	CODE	EV (272741003, SCT, "Laterality")	1	U	DCID 244 “Laterality”
3	>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U

TID 3112 Specimen Obtained

The Specimen Obtained Template allows recording of obtaining a specimen, and the identifiers for that specimen. This is particularly designed for blood samples that will be analyzed for blood oxygen-related measurements. The analysis of the sample may be recorded in one or more log entries using TID 3109 “Measurements”, or in a separate Structured Report SOP Instance referenced by a log entry using TID 3103 “Referenced Object”.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3112. Specimen Obtained

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CODE	EV (121123, DCM, "Patient Status or Event")	1	M		DCID 3515 “Specimen Collection”
2	>	HAS ACQ CONTEXT	CODE	EV (371439000, SCT, "Specimen Type")	1	UC	IFF specimen is blood sample	DCID 3520 “Blood Source Type”
3	>	HAS ACQ CONTEXT	CODE	EV (363704007, SCT, "Procedure site")	1	U		BCID 3630 “Cardiovascular Anatomic Location”
4	>	HAS PROPERTIES	INCLUDE	DTID 1009 “Subject Context, Specimen”	1	U

TID 3113 Patient Support

The Patient Support Template allows recording of the use of various support technologies, including oxygen, ventilation, pacing, etc.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3113. Patient Support

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CODE	DCID 3530 “Oxygen Administration Action”	1	U		DCID 3531 “Oxygen Administration”
2	>	HAS PROPERTIES	NUM	EV (121160, DCM, "Oxygen Administration Rate")	1	MC	IFF Row 1 Concept is (121161, DCM, "Begin Oxygen Administration")	UNITS = DT (l/min, UCUM, "l/min")
3	>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U
4			CODE	DCID 3550 “Circulatory Support Action”	1	U		DCID 3553 “Circulatory Support”
5	>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U
6			CODE	DCID 3551 “Ventilation Action”	1	U		DCID 3554 “Ventilation”
7	>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U
8			CODE	DCID 3552 “Pacing Action”	1	U		DCID 3555 “Pacing”
9	>		INCLUDE	DTID 3010 “Log Entry Qualifiers”	1	U

TID 3114 Patient Assessment

The Patient Assessment Template allows recording of the assessment of the patient's cardiovascular, neurological, and/or respiratory condition. A particular use of this Template is for "vital signs", which are a specific subset of mandatory patient assessment measurements.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3114. Patient Assessment

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CODE	EV (121123, DCM, "Patient Status or Event")	1	M		DT (121165, DCM, "Patient Assessment Performed") DT (61746007, SCT, "Observation of Vital Signs")
2	>	HAS PROPERTIES	INCLUDE	DTID 300 “Measurement”	1	MC	IF Row 1 value = (61746007, SCT, "Observation of Vital Signs")	$Measurement = EV (271649006, SCT, "Systolic blood pressure") $Units = DCID 3500 “Pressure Unit” $Method = BCID 3560 “Blood Pressure Method”
3	>	HAS PROPERTIES	INCLUDE	DTID 300 “Measurement”	1	MC	IF Row 1 value = (61746007, SCT, "Observation of Vital Signs")	$Measurement = EV (271650006, SCT, "Diastolic blood pressure") $Units = DCID 3500 “Pressure Unit”
4	>	HAS PROPERTIES	INCLUDE	DTID 300 “Measurement”	1	MC	IF Row 1 value = (61746007, SCT, "Observation of Vital Signs")	$Measurement = EV (8867-4, LN, "Heart rate") $Units = EV ({H.B.}/min, UCUM, "BPM")
5	>	HAS PROPERTIES	INCLUDE	DTID 300 “Measurement”	1	MC	IF Row 1 value = (61746007, SCT, "Observation of Vital Signs")	$Measurement = EV (8310-5, LN, "Body temperature") $Units = EV (Cel, UCUM, "C")
6	>	HAS PROPERTIES	INCLUDE	DTID 300 “Measurement”	1	MC	IF Row 1 value = (61746007, SCT, "Observation of Vital Signs")	$Measurement = DCID 3526 “Blood Gas Saturation” $Units = EV (%, UCUM, "%")
7	>	HAS PROPERTIES	INCLUDE	DTID 300 “Measurement”	1	MC	IF Row 1 value = (61746007, SCT, "Observation of Vital Signs")	$Measurement = EV (86290005, SCT, "Respiration rate") $Units = EV (/min, UCUM, "breaths/min")
8	>	HAS PROPERTIES	INCLUDE	DTID 300 “Measurement”	1-n	MC	IF Row 1 value = (61746007, SCT, "Observation of Vital Signs")	$Measurement = EV (122195, DCM, "Pulse Strength") $Method = BCID 3442 “Peripheral Pulse Method” $TargetSite = BCID 3440 “Peripheral Pulse Location” $Units = DT ({0:4}, UCUM, "range 0:4")
9	>	HAS PROPERTIES	INCLUDE	DTID 300 “Measurement”	1	MC	IF Row 1 value = (61746007, SCT, "Observation of Vital Signs")	$Measurement = EV (225908003, SCT, "Pain Score") $Units = DT ({1:10}, UCUM, "range 1:10")
10	>	HAS PROPERTIES	CODE	DT (8884-9, LN, "Cardiac Rhythm")	1	U		BCID 3415 “Cardiac Rhythm”
11	>	HAS PROPERTIES	CODE	DT (9304-7, LN, "Respiration Rhythm")	1	U		BCID 3416 “Respiration Rhythm”
12	>	HAS PROPERTIES	CODE	DT (364062005, SCT, "Respiration Assessment")	1	U		BCID 3448 “Airway Assessment”
13	>	HAS PROPERTIES	CODE	DT (364528001, SCT, "Skin condition")	1-n	U		BCID 3446 “Skin Condition”
14	>	HAS PROPERTIES	CODE	DT (363871006, SCT, "Patient mental state assessment")	1	U
15	>	HAS PROPERTIES	TEXT	BCID 3441 “Patient Assessment”	1-n	U

Content Item Descriptions

Row 8	Pulse Strength allows the assessment of the patient's pulse at multiple locations using the Topographical concept modifier. It may also be used for a single pulse strength measurement from an unspecified location, as is typical of vital signs assessments.
Row 16	Allows free text description of patient assessments that are not expressible by coded entries of Rows 10, 11, 12, 13, 14.

TID 3115 ECG ST Assessment

The ECG ST Assessment Template allows recording of the assessment of changes in the patient ECG relative to baseline.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3115. ECG ST Assessment

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CODE	EV (121123, DCM, "Patient Status or Event")	1	M	DT (258181008, SCT, "ECG Analysis")
2	>	HAS PROPERTIES	NUM	DT (122099, DCM, "ST change from baseline")	1-n	M	UNITS = EV (uV, UCUM, "uV")
3	>>	HAS CONCEPT MOD	CODE	DT (122148, DCM, "Lead ID")	1	M	BCID 3001 “ECG Lead”

Quantitative Ventricular Analysis Report SR IOD Templates

The Templates that comprise the Quantitative Ventricular Analysis SR are interconnected as in Figure A-3:

Figure A-3. Quantitative Ventricular Analysis Report SR IOD Template Structure

TID 3202 Quantitative Ventricular Analysis Report

The Quantitative Ventricular Analysis Report Template provides a CONTAINER with a structure for reporting the result of the ventricular analysis.

Type:: Extensible
Order:: Significant
Root:: Yes

Table TID 3202. Quantitative Ventricular Analysis Report

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CONTAINER	EV (122292, DCM, "Quantitative Ventriculography Report")	1	M
2	>	HAS CONCEPT MOD	INCLUDE	DTID 1204 “Language of Content Item and Descendants”	1	M
3	>	HAS OBS CONTEXT	INCLUDE	DTID 1002 “Observer Context”	1-n	M
4	>	CONTAINS	INCLUDE	DTID 3602 “Cardiovascular Patient Characteristics”	1	U
5	>	CONTAINS	CONTAINER	EV (122144, DCM, "Quantitative Analysis")	1-n	M
6	>>	HAS OBS CONTEXT	INCLUDE	DTID 1002 “Observer Context”	1-n	U
7	>>	HAS OBS CONTEXT	TEXT	EV (111001, DCM, "Algorithm Name")	1	M
8	>>	HAS OBS CONTEXT	TEXT	EV (111003, DCM, "Algorithm Version")	1	M
9	>>	HAS OBS CONTEXT	TEXT	EV (122405, DCM, "Algorithm Manufacturer")	1	M
10	>>	CONTAINS	IMAGE	EV (121112, DCM, "Source of Measurement")	1-n	M
11	>>>	HAS CONCEPT MOD	CODE	EV (246092007, SCT, "Cardiac Phase")	1	M		DCID 12233 “Cardiac Phase”
12	>>>	HAS CONCEPT MOD	CODE	EV (111031, DCM, "Image View")	1	MC	If Biplane Analysis	DCID 3466 “Plane Identification”
13	>>	HAS ACQ CONTEXT	INCLUDE	DTID 3205 “Calibration”	1-2	U	VM = 1: Single plane analysis, VM = 2: Biplane analysis	$CalibrationPlane = DCID 3466 “Plane Identification”
14	>>	HAS ACQ CONTEXT	INCLUDE	DTID 3520 “Hemodynamic Clinical Context”	1	U
15	>>	CONTAINS	INCLUDE	DTID 3206 “VA Main Results”	1	M
16	>>	CONTAINS	INCLUDE	DTID 3207 “AA Main Results”	1	U
17	>>	CONTAINS	INCLUDE	DTID 3208 “Frame-to-Frame Results”	1	U
18	>>	CONTAINS	INCLUDE	DTID 3209 “Centerline Wall Motion”	1-2	U	VM = 1: Single plane analysis, VM = 2: Biplane analysis
19	>>	CONTAINS	INCLUDE	DTID 3210 “Radial Based Wall Motion”	1-2	U	VM = 1: Single plane analysis, VM = 2: Biplane analysis
20	>>	CONTAINS	INCLUDE	DTID 3211 “Landmark Based Wall Motion”	1-2	U	VM = 1: Single plane analysis, VM = 2: Biplane analysis

Content Item Descriptions

Row 7	Identifies the Ventricular Analysis program
Row 8	Identifies the Ventricular Analysis program version
Row 9	Identifies the Ventricular Analysis program manufacturer
Row 10	Identifies the ES and ED images on which the analysis is based, for frame by frame analysis the analyzed image are specified in the frame by frame results (3208) Template

TID 3205 Calibration

The Calibration Template consists of a CONTAINER, with a structure for reporting of the calibration of images used in the analysis.

Table TID 3205. Parameters

Parameter Name	Parameter Usage
$CalibrationPlane	XA Imaging plane

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3205. Calibration

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CONTAINER	EV (122505, DCM, "Calibration")	1	M
2	>	HAS CONCEPT MOD	CODE	EV (111031, DCM, "Image View")	1	U		$CalibrationPlane
3	>	HAS OBS CONTEXT	TEXT	EV (111001, DCM, "Algorithm Name")	1	MC	IF different from Analysis program specified in the invoking Template
4	>	HAS OBS CONTEXT	TEXT	EV (111003, DCM, "Algorithm Version")	1	MC	IF different from Analysis program specified in the invoking Template
5	>	HAS OBS CONTEXT	TEXT	EV (122405, DCM, "Algorithm Manufacturer")	1	MC	IF different from Analysis program specified in the invoking Template
6	>	CONTAINS	CODE	EV (122422, DCM, "Calibration Method")	1	M		DCID 3452 “Calibration Method”
7	>	CONTAINS	CODE	EV (122421, DCM, "Calibration Object")	1	MC	IF Row 6 value specifies Calibration Object Used	DCID 3451 “Calibration Object”
8	>	CONTAINS	NUM	EV (122423, DCM, "Calibration Object Size")	1	MC	IF Row 6 value specifies Calibration Object Used	DCID 3510 “Catheter Size Unit”
9	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M		$Measurement = EV (111026, DCM, "Horizontal Pixel Spacing") $Units = DT (mm/{pixel}, UCUM, "mm/pixel") $ImagePurpose = EV (121112, DCM, "Source of Measurement")
10	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M		$Measurement = EV (111066, DCM, "Vertical Pixel Spacing") $Units = DT (mm/{pixel}, UCUM, "mm/pixel") $ImagePurpose = EV (121112, DCM, "Source of Measurement")
11	>	CONTAINS	IMAGE		1	U

Content Item Descriptions

Row 3	Identifies the Calibration program
Row 4	Identifies the Calibration program version
Row 5	Identifies the Calibration program manufacturer
Row 7	Besides a Sphere and a Catheter, a Distance can be identified as a Calibration Object. In this case a distance measurement of a known dimension of the object is used to calculate the pixel size.
Row 8	The catheter size units is also used to specify the size of other calibration objects (e.g., sphere)
Rows 9, 10	Spacing in the patient body. Point to a single frame containing the image used for calibration if applicable, the actual measurements may be indicated by a SCOORD (see TID 320 “Image or Spatial Coordinates”, Row 3)
Row 11	Secondary Capture image with calibration position. No purpose of reference is specified.

TID 3206 VA Main Results

The VA Main Results Template consists of a CONTAINER with a structure for reporting the main ventricular analysis measurements.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3206. VA Main Results

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CONTAINER	EV (59776-5, LN, "Findings")	1	M
2	>	HAS CONCEPT MOD	CODE	EV (363698007, SCT, "Finding Site")	1	M	DCID 3462 “Chamber Identification”
3	>	CONTAINS	CODE	EV (122429, DCM, "Volume Method")	1	M	DCID 3453 “Cardiac Volume Method”
4	>	CONTAINS	NUM	EV (122435, DCM, "Regression Volume Exponent")	1	U	Unit = DT (1, UCUM, "no units")
5	>	CONTAINS	NUM	EV (122431, DCM, "Regression Slope ED")	1	U	Unit = DT ({ratio}, UCUM, "ratio")
6	>	CONTAINS	NUM	EV (122432, DCM, "Regression Offset ED")	1	U	Unit = DT (ml, UCUM, "ml")
7	>	CONTAINS	NUM	EV (122433, DCM, "Regression Slope ES")	1	U	Unit = DT ({ratio}, UCUM, "ratio")
8	>	CONTAINS	NUM	EV (122434, DCM, "Regression Offset ES")	1	U	Unit = DT (ml, UCUM, "ml")
9	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = DCID 3467 “Ejection Fraction” $Units = DT (%, UCUM, "%")
10	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = DCID 3468 “ED Volume” $Units = DT (ml, UCUM, "ml")
11	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = DCID 3469 “ES Volume” $Units = DT (ml, UCUM, "ml")
12	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (90096001, SCT, "Stroke Volume") $Units = DT (ml, UCUM, "ml")
13	>	CONTAINS	NUM	EV (8867-4, LN, "Heart Rate")	1	U	Unit = DT ({H.B.}/min, UCUM, "BPM")
14	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = DCID 3468 “ED Volume” $ModType = EV (121425, DCM, "Index") $ModValue = DCID 3455 “Index Method” $Units = DT (ml/m2, UCUM, "ml/m2")
15	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = DCID 3468 “ED Volume” $ModType = EV (121425, DCM, "Index") $ModValue = EV (29463-7, LN, "Patient Weight") $Units = DT (ml/kg, UCUM, "ml/kg")
16	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = DCID 3469 “ES Volume” $ModType = EV (121425, DCM, "Index") $ModValue = DCID 3455 “Index Method” $Units = DT (ml/m2, UCUM, "ml/m2")
17	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = DCID 3469 “ES Volume” $ModType = EV (121425, DCM, "Index") $ModValue = EV (29463-7, LN, "Patient Weight") $Units = DT (ml/kg, UCUM, "ml/kg")
18	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (90096001, SCT, "Stroke Volume") $ModType = EV (121425, DCM, "Index") $ModValue = DCID 3455 “Index Method” $Units = DT (ml/m2, UCUM, "ml/m2")
19	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (90096001, SCT, "Stroke Volume") $ModType = EV (121425, DCM, "Index") $ModValue = EV (29463-7, LN, "Patient Weight") $Units = DT (ml/kg, UCUM, "ml/kg")
20	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (82799009, SCT, "Cardiac Output") $Units = DT (l/min, UCUM, "l/min")
21	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (54993008, SCT, "Cardiac Index") $ModType = EV (121425, DCM, "Index") $ModValue = DCID 3455 “Index Method” $Units = DT (l/min/m2, UCUM, "l/min/m2")
22	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (122445, DCM, "Wall Thickness") $Units = DT (mm, UCUM, "mm")
23	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (122446, DCM, "Wall Volume") $Units = DT (ml, UCUM, "ml")
24	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (122447, DCM, "Wall Mass") $Units = DT (g, UCUM, "gram")
25	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (122447, DCM, "Wall Mass") $ModType = EV (121425, DCM, "Index") $ModValue = DCID 3455 “Index Method” $Units = DT (g/m2, UCUM, "gram/m2")
26	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (122447, DCM, "Wall Mass") $ModType = EV (121425, DCM, "Index") $ModValue = EV (29463-7, LN, "Patient Weight") $Units = DT (g/kg, UCUM, "gram/kg")
27	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (122448, DCM, "Wall Stress") $Units = DT (dyn/cm2, UCUM, "dynes/cm2")
28	>	CONTAINS	IMAGE		1-n	U

Content Item Descriptions

Row 28

Secondary Capture image with ED and/or ES contours. No purpose of reference is specified.

TID 3207 AA Main Results

The AA Main Results Template consists of a CONTAINER with a structure for reporting the main atrial analysis measurements.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3207. AA Main Results

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CONTAINER	EV (59776-5, LN, "Findings")	1	M
2	>	HAS CONCEPT MOD	CODE	EV (363698007, SCT, "Finding Site")	1	M	DCID 3462 “Chamber Identification”
3	>	CONTAINS	CODE	EV (122429, DCM, "Volume Method")	1	M	DCID 3453 “Cardiac Volume Method”
4	>	CONTAINS	NUM	EV (122435, DCM, "Regression Volume Exponent")	1	U	Unit = DT (1, UCUM, "no units")
5	>	CONTAINS	NUM	EV (122431, DCM, "Regression Slope ED")	1	U	Unit = DT ({ratio}, UCUM, "ratio")
6	>	CONTAINS	NUM	EV (122432, DCM, "Regression Offset ED")	1	U	Unit = DT (ml, UCUM, "ml")
7	>	CONTAINS	NUM	EV (122433, DCM, "Regression Slope ES")	1	U	Unit = DT ({ratio}, UCUM, "ratio")
8	>	CONTAINS	NUM	EV (122434, DCM, "Regression Offset ES")	1	U	Unit = DT (ml, UCUM, "ml")
9	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = DCID 3468 “ED Volume” $Units = DT (ml, UCUM, "ml")
10	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = DCID 3469 “ES Volume” $Units = DT (ml, UCUM, "ml")
11	>	CONTAINS	IMAGE		1-n	U

Content Item Descriptions

Row 11

Secondary Capture image with ED and/or ES contours. No purpose of reference is specified.

TID 3208 Frame-to-Frame Results

The Frame-to-Frame Result Template consists of a CONTAINER providing measurements derived from the angiographic images on frame-by-frame basis.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3208. Frame-To-Frame Result

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CONTAINER	EV (59776-5, LN, "Findings")	1	M
2	>	HAS CONCEPT MOD	CODE	EV (111004, DCM, "Analysis Performed")	1	M		EV (122499, DCM, "Frame to Frame Analysis")
3	>	CONTAINS	IMAGE	EV (121112, DCM, "Source of Measurement")	1-2	M	VM = 1: Single plane analysis, VM = 2: Biplane analysis
4	>	CONTAINS	CODE	EV (122429, DCM, "Volume Method")	1	M		DCID 3453 “Cardiac Volume Method”
5	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1-n	M		$Measurement = DCID 3471 “Estimated Volume” $TargetSite = DCID 3462 “Chamber Identification” $Units = DT (ml, UCUM, "ml")
6	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1-n	U		$Measurement = EV (122445, DCM, "Wall Thickness") $Units = DT (mm, UCUM, "mm")
7	>	CONTAINS	IMAGE		1-n	U

Content Item Descriptions

Row 3	Identifies each frame analyzed, using the multi-valued Referenced Frame Number (0008,1160) Attribute of the IMAGE Content Item.
Rows 5, 6	Includes one measurement for each frame referenced in Row 3.
Row 7	Secondary Capture image with ventricular contours. No purpose of reference is specified.

TID 3209 Centerline Wall Motion

The Centerline Wall Motion Template consists of a CONTAINER providing measurements of the centerline wall motion.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3209. Centerline Wall Motion

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CONTAINER	EV (59776-5, LN, "Findings")	1	M
2	>	HAS CONCEPT MOD	CODE	EV (111004, DCM, "Analysis Performed")	1	M	EV (122449, DCM, "Centerline Wall Motion Analysis")
3	>>	HAS CONCEPT MOD	CODE	EV (122410, DCM, "Contour Realignment")	1	M	DCID 3458 “Contour Realignment”
4	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	100	M	$Measurement = EV (122450, DCM, "Normalized Chord Length") $Units = DT (%, UCUM, "%")
5	>	CONTAINS	NUM	EV (122411, DCM, "Threshold Value")	1	M	Values shall be 1, 2 or 3 UNITS = EV ({sd}, UCUM, "Standard Deviations")
6	>	CONTAINS	CONTAINER	EV (122451, DCM, "Abnormal Region")	1-6	U
7	>>	CONTAINS	CODE	EV (60797005, SCT, "Cardiac Wall Motion")	1	M	DCID 3703 “Wall Motion”
8	>>	CONTAINS	CODE	EV (255593009, SCT, "Circumferential Extent")	1	U	DCID 3460 “Circumferential Extent”
9	>>	CONTAINS	NUM	EV (122452, DCM, "First Chord of Abnormal Region")	1	M	Unit = DT (1, UCUM, "no units")
10	>>	CONTAINS	NUM	EV (122453, DCM, "Last Chord of Abnormal Region")	1	M	Unit = DT (1, UCUM, "no units")
11	>	CONTAINS	CONTAINER	EV (122417, DCM, "Regional Abnormal Wall Motion")	1-4	U
12	>>	HAS CONCEPT MOD	CODE	EV (363698007, SCT, "Finding Site")	1	M	DCID 3461 “Regional Extent”
13	>>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = EV (122459, DCM, "Territory Region Severity") $ModType = EV (60797005, SCT, "Cardiac Wall Motion") $ModValue = DCID 3703 “Wall Motion” $Units = DT ({sd}, UCUM, "Standard Deviations")
14	>>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = EV (122461, DCM, "Opposite Region Severity") $ModType = EV (60797005, SCT, "Cardiac Wall Motion") $ModValue = DCID 3703 “Wall Motion” $Units = DT ({sd}, UCUM, "Standard Deviations")
15	>	CONTAINS	IMAGE		1	U

Content Item Descriptions

Row 4	Normalized lengths of the chords determined between ED and ES contour. The measurement Template allows the specification of the statistical properties of the normal population and of the chord measurement relative to the population.
Row 8	If the Circumferential Extent is not specified no limitations to the boundaries for regions are assumed.
Row 11	The Regional Abnormal Wall Motion container holds the information on the severity of the decreased or increased wall motion of the 4 predefined regions as described in [Sheehan, 1986].
Row 12	The name of the region with an abnormal ventricular wall motion as described in [Sheehan, 1986].
Row 13	The severity of the wall motion abnormality expressed in Standard Deviations above or below normal in the territory region as described in [Sheehan, 1986].
Row 14	The severity of the wall motion abnormality expressed in Standard Deviations above or below normal in the opposite region as described in [Sheehan, 1986].
Row 15	Secondary Capture image with centerline analysis result. No purpose of reference is specified.

TID 3210 Radial Based Wall Motion

The Radial Based Wall Motion Template consists of a CONTAINER providing measurements of the radial based wall motion.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3210. Radial Based Wall Motion

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CONTAINER	EV (59776-5, LN, "Findings")	1	M
2	>	HAS CONCEPT MOD	CODE	EV (111004, DCM, "Analysis Performed")	1	M	EV (122493, DCM, "Radial Based Wall Motion Analysis")
3	>>	HAS CONCEPT MOD	CODE	EV (122410, DCM, "Contour Realignment")	1	M	DCID 3458 “Contour Realignment”
4	>	CONTAINS	CONTAINER	EV (59776-5, LN, "Findings")	1-n	M
5	>>	HAS CONCEPT MOD	CODE	EV (363698007, SCT, "Finding Site")	1	M	DCID 3718 “Myocardial Wall Segments in Projection”
6	>>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = EV (122495, DCM, "Regional Contribution to Ejection Fraction") $Units = DT (%, UCUM, "%")
7	>>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1-n	U	$Measurement = EV (122496, DCM, "Radial Shortening") $Units = DT (%, UCUM, "%")
8	>	CONTAINS	IMAGE		1	U

Content Item Descriptions

Row 6	The CREF values of the 6 regions determined for the radial based wall motion
Row 7	The shortening of the measured radials within the region
Row 8	Secondary Capture image with radial based analysis result. No purpose of reference is specified.

TID 3211 Landmark Based Wall Motion

The Landmark Based Wall Motion Template consists of a CONTAINER providing measurements of the landmark based wall motion.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3211. Landmark Based Wall Motion

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CONTAINER	EV (59776-5, LN, "Findings")	1	M
2	>	HAS CONCEPT MOD	CODE	EV (111004, DCM, "Analysis Performed")	1	M	EV (122497, DCM, "Landmark Based Wall Motion Analysis")
3	>>	HAS CONCEPT MOD	CODE	EV (122410, DCM, "Contour Realignment")	1	M	DCID 3458 “Contour Realignment”
4	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1-n	M	$Measurement = EV (122498, DCM, "Slice Contribution to Ejection Fraction") $Units = DT (%, UCUM, "%")
5	>	CONTAINS	CONTAINER	EV (59776-5, LN, "Findings")	5	M
6	>>	HAS CONCEPT MOD	CODE	EV (363698007, SCT, "Finding Site")	1	M	DCID 3718 “Myocardial Wall Segments in Projection”
7	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = EV (122495, DCM, "Regional Contribution to Ejection Fraction") $Units = DT (%, UCUM, "%")
8	>	CONTAINS	IMAGE		1	U

Content Item Descriptions

Row 8

Secondary Capture image with Landmark Based Analysis result. No purpose of reference is specified.

Quantitative Arterial Analysis Report SR IOD Templates

The Templates that comprise the Quantitative Arterial Analysis SR are interconnected as in Figure A-4:

Figure A-4. Quantitative Arterial Analysis Report SR IOD Template Structure

TID 3213 Quantitative Arterial Analysis

The Quantitative Arterial Analysis Template consists of a CONTAINER with a structure for reporting the result of the quantitative arterial analysis process.

Type:: Extensible
Order:: Significant
Root:: Yes

Table TID 3213. Quantitative Arterial Analysis

	NL	Rel with Parent	VT	Concept Name	VM	Req Type
1			CONTAINER	EV (122291, DCM, "Quantitative Arteriography Report")	1	M
2	>	HAS CONCEPT MOD	INCLUDE	DTID 1204 “Language of Content Item and Descendants”	1	M
3	>	HAS OBS CONTEXT	INCLUDE	DTID 1002 “Observer Context”	1-n	M
4	>	CONTAINS	INCLUDE	DTID 3602 “Cardiovascular Patient Characteristics”	1	U
5	>	HAS OBS CONTEXT	TEXT	EV (111001, DCM, "Algorithm Name")	1	M
6	>	HAS OBS CONTEXT	TEXT	EV (111003, DCM, "Algorithm Version")	1	M
7	>	HAS OBS CONTEXT	TEXT	EV (122405, DCM, "Algorithm Manufacturer")	1	M
8	>	CONTAINS	INCLUDE	DTID 3214 “Analyzed Segment”	1-n	M

Content Item Descriptions

Row 5	Identifies the Arterial Analysis program
Row 6	Identifies the Arterial Analysis program version
Row 7	Identifies the Arterial Analysis program manufacturer

TID 3214 Analyzed Segment

The Analyzed Segment Template consists of a CONTAINER providing quantitative arterial analysis measurements derived from the angiographic images.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3214. Analyzed Segment

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CONTAINER	EV (59776-5, LN, "Findings")	1	M
2	>	HAS CONCEPT MOD	CODE	EV (363698007, SCT, "Finding Site")	1	M	DCID 3604 “Arterial Lesion Location”
3	>	CONTAINS	IMAGE	EV (121112, DCM, "Source of Measurement")	1	M
4	>	CONTAINS	INCLUDE	DTID 3205 “Calibration”	1	M
5	>	HAS ACQ CONTEXT	INCLUDE	DTID 3520 “Hemodynamic Clinical Context”	1	U
6	>	HAS ACQ CONTEXT	CODE	EV (129085009, SCT, "Catheterization Procedure Phase")	1	U	DCID 3651 “Hemodynamic Measurement Phase”
7	>	CONTAINS	SCOORD	EV (122507, DCM, "Left Contour")	1	M	GRAPHIC TYPE = {POLYLINE}
8	>>	R-SELECTED FROM	IMAGE		1	M	Must reference Row 3
9	>	CONTAINS	SCOORD	EV (122508, DCM, "Right Contour")	1	M	GRAPHIC TYPE = {POLYLINE}
10	>>	R-SELECTED FROM	IMAGE		1	M	Must reference Row 3
11	>	CONTAINS	INCLUDE	DTID 3219 “Segment Values”	1	M
12	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = EV (397413000, SCT, "Vessel Luminal Diameter") $Derivation = EV (255605001, SCT, "Minimum") $Units = DT (mm, UCUM, "mm")
13	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = EV (397413000, SCT, "Vessel Luminal Diameter") $Derivation = EV (56851009, SCT, "Maximum") $Units = DT (mm, UCUM, "mm")
14	>	CONTAINS	CONTAINER	EV (122509, DCM, "Diameter Graph")	1	U
15	>>	CONTAINS	NUM	EV (122511, DCM, "Graph Increment")	1	M	Value = 1 UNITS = DT ({pixels}, UCUM, "pixels")
16	>>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1-n	M	$Measurement = EV (397413000, SCT, "Vessel Luminal Diameter") $Units = DT (mm, UCUM, "mm")
17	>	CONTAINS	NUM	EV (122382, DCM, "Site of Luminal Minimum")	1	U	UNITS = DT ({pixels}, UCUM, "pixels")
18	>	CONTAINS	NUM	EV (122516, DCM, "Site of Luminal Maximum")	1	U	UNITS = DT ({pixels}, UCUM, "pixels")
19	>	CONTAINS	INCLUDE	DTID 3215 “Angiographic Lesion Analysis”	1-n	U
20	>	CONTAINS	INCLUDE	DTID 3217 “Sub-segmental Data”	1-n	U
21	>	CONTAINS	IMAGE		1	U

Content Item Descriptions

Row 1	Observation DateTime (0040,A032) of container needs to be flagged with the time of the analysis
Row 7	Numeric coordinates (x,y) identifying the contour points from proximal to distal of left contour. Left is relative to the direction of the blood flow.
Row 9	Numeric coordinates (x,y) identifying the contour points from proximal to distal of right contour. Right is relative to the direction of the blood flow.
Rows 12, 13	Positions are relative to the midpoint between the first left and right contour points and measured along the midline between the left and right contour.
Row 14	The X-axis represents the pixel points of the midline of the vessel from proximal to distal. The points on the midline are not necessarily equidistant.
Row 16	For each point of the midline of the vessel a measurement value for the diameter is calculated.
Rows 17, 18	The positions in the graph are related to the points on the midline of the vessel.
Row 21	Secondary Capture image with Arterial Analysis contour. No purpose of reference is specified.

Definition of Left and Right defined by the direction of the blood flow as in Figure A-4b:

Figure A-4b. Direction of Blood Flow

TID 3215 Angiographic Lesion Analysis

The Angiographic Lesion Analysis Template consists of a CONTAINER providing quantitative arterial analysis measurements derived for an obstruction in a total analyzed segment.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3215. Angiographic Lesion Analysis

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CONTAINER	EV (300577008, SCT, "Lesion Finding")	1	M
2	>	CONTAINS	TEXT	EV (121151, DCM, "Lesion Identifier")	1	M
3	>>	HAS PROPERTIES	CODE	EV (363698007, SCT, "Finding Site")	1	M	DCID 3604 “Arterial Lesion Location”
4	>>>	HAS CONCEPT MOD	CODE	EV (106233006, SCT, "Topographical modifier")	1	U	DCID 3019 “Cardiovascular Anatomic Structure Modifier”
5	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = EV (397413000, SCT, "Vessel Luminal Diameter") $Derivation = EV (255605001, SCT, "Minimum") $Units = DT (mm, UCUM, "mm")
6	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1-n	U	$Measurement = EV (397415007, SCT, "Vessel Lumen Cross-Sectional Area") $Method = DCID 3470 “Vessel Lumen Cross-sectional Area Calculation Method” $Derivation = EV (255605001, SCT, "Minimum") $Units = DT (mm2, UCUM, "mm2")
7	>	CONTAINS	CODE	EV (122430, DCM, "Reference Method")	1	M	DCID 3465 “QA Reference Method”
8	>	CONTAINS	CONTAINER	EV (122438, DCM, "Reference Points")	1	U
9	>>	CONTAINS	NUM	EV (122337, DCM, "Relative Position")	1-n	M	UNITS = DT (mm, UCUM, "mm")
10	>>>	HAS PROPERTIES	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (397413000, SCT, "Vessel Luminal Diameter") $Units = DT (mm, UCUM, "mm")
11	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = EV (397413000, SCT, "Vessel Luminal Diameter") $TargetSite = (122382, DCM, "Site of Luminal Minimum") $Units = DT (mm, UCUM, "mm")
12	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (397415007, SCT, "Vessel Lumen Cross-Sectional Area") $Derivation = EV (122404, DCM, "Reconstructed") $TargetSite = (122382, DCM, "Site of Luminal Minimum") $Units = DT (mm2, UCUM, "mm2")
13	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = EV (397413000, SCT, "Vessel Luminal Diameter") $Derivation = EV (258090004, SCT, "Calculated") $TargetSite = EV (122481, DCM, "Contour Start") $Units = DT (mm, UCUM, "mm")
14	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = EV (397413000, SCT, "Vessel Luminal Diameter") $Derivation = EV (258090004, SCT, "Calculated") $TargetSite = EV (122482, DCM, "Contour End") $Units = DT (mm, UCUM, "mm")
15	>	CONTAINS	INCLUDE	DTID 3218 “Position in Arterial Segment”	1	M
16	>	CONTAINS	CONTAINER	EV (122517, DCM, "Densitometric Luminal Cross-sectional Area Graph")	1	U
17	>>	CONTAINS	NUM	EV (122511, DCM, "Graph Increment")	1	M	Value = 1 UNITS = DT ({pixels}, UCUM, "pixels")
18	>>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1-n	M	$Measurement = EV (397415007, SCT, "Vessel Lumen Cross-Sectional Area") $Units = (mm2, UCUM, "mm2")
19	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (397415007, SCT, "Vessel Lumen Cross-Sectional Area") $Derivation = EV (258090004, SCT, "Calculated") $Method = EV (122474, DCM, "Densitometric method") $TargetSite = EV (122481, DCM, "Contour Start") $Units = (mm2, UCUM, "mm2")
20	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (397415007, SCT, "Vessel Lumen Cross-Sectional Area") $Derivation = EV (258090004, SCT, "Calculated") $Method = EV (122474, DCM, "Densitometric method") $TargetSite = EV (122482, DCM, "Contour End") $Units = (mm2, UCUM, "mm2")
21	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = EV (408716009, SCT, "Stenotic Lesion Length") $Units = DT (mm, UCUM, "mm")
22	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = EV (408715008, SCT, "Lumen Diameter Stenosis") $Units = DT (%, UCUM, "%")
23	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1-n	U	$Measurement = EV (408714007, SCT, "Lumen Area Stenosis") $Method = DCID 3470 “Vessel Lumen Cross-sectional Area Calculation Method” $Units = DT (%, UCUM, "%")
24	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1-n	U	$Measurement = EV (122372, DCM, "Lumen Volume") $Method = DCID 3470 “Vessel Lumen Cross-sectional Area Calculation Method” $Units = DT (mm3, UCUM, "mm3")
25	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (122542, DCM, "Plaque Area") $Units = DT (mm2, UCUM, "mm2")
26	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (122376, DCM, "Total Plaque Volume") $Units = DT (mm3, UCUM, "mm3")
27	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (122544, DCM, "Diameter Symmetry") $Units = DT ({ratio}, UCUM, "ratio")
28	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (122545, DCM, "Area Symmetry") $Units = DT ({ratio}, UCUM, "ratio")
29	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (122546, DCM, "Inflow Angle") $Units = DT (deg, UCUM, "deg")
30	>	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (122547, DCM, "Outflow Angle") $Units = DT (deg, UCUM, "deg")
31	>	CONTAINS	INCLUDE	DTID 3216 “Stenotic Flow Reserve”	1	U
32	>	CONTAINS	IMAGE		1	U

Content Item Descriptions

Row 8	Set of user defined reference position for method that requires local reference position.
Row 9	Distance of local reference position from an arbitrary landmark.
Row 10	Diameter at a local reference position.
Row 11	The reference diameter for the arterial lesion calculated with the applicable reference method
Row 12	The reference area for the arterial lesion calculated with the applicable reference method
Row 13	The diameter measurement at the start of the reconstruction line in the diameter graph (TID 3214 “Analyzed Segment” Row 14)
Row 14	The diameter measurement at the end of the reconstruction line in the diameter graph (TID 3214 “Analyzed Segment” Row 14)
Row 15	The positions of the lesion, borders of the lesion, etc.
Row 16	The graph with the calculated cross sectional area results based on the densitometric method
Row 18	The cross sectional area measurements calculated based on the densitometric method
Row 19	The cross sectional area measurement at the start of the reconstruction line in the area graph
Row 20	The cross sectional area measurement at the end of the reconstruction line in the area graph
Row 21	Measured along the midline of the left and right contour
Row 22	The diameter stenosis is calculated as follows: (Reference Luminal Diameter - Minimum Luminal Diameter / Reference Luminal Diameter) * 100%
Row 23	The circular and the densitometric area stenosis are calculated respectively as: (Reference Vessel Lumen Cross-Sectional Area - Minimum Luminal Circular Area / Reference Vessel Lumen Cross-Sectional Area) * 100%(Reference Vessel Lumen Cross-Sectional Area - Minimum Luminal Densitometric Area / Reference Vessel Lumen Cross-Sectional Area) * 100%
Row 24	Estimated lumen volume between proximal border and distal border of lesion (TID 3218 “Position in Arterial Segment”, Row 1 and Row 2)
Row 32	Secondary Capture image with obstruction analysis contour. No purpose of reference is specified.

TID 3216 Stenotic Flow Reserve

The Stenotic Flow Reserve Template consists of a CONTAINER providing quantitative arterial analysis measurements derived for an obstruction in a total analyzed segment.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3216. Stenotic Flow Reserve

	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = EV (122548, DCM, "Stenotic Flow Reserve") $Units = DT ({ratio}, UCUM, "ratio")
2	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = EV (122549, DCM, "Poiseuille Resistance") $Units = DT (mm[Hg].s/cm, UCUM, "mmHG.s/cm")
3	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = EV (122550, DCM, "Turbulence Resistance") $Units = DT (mm[Hg].s2/cm2, UCUM, "mmHG.s2/cm2")
4	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = EV (122555, DCM, "Estimated Normal Flow") $Units = DT (ml/s, UCUM, "ml/s")
5	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (122551, DCM, "Pressure Drop at SFR") $Units = DT (mm[Hg], UCUM, "mmHg")
6	CONTAINS	IMAGE		1	U

Content Item Descriptions

Row 6

Secondary Capture image with SFR analysis contour. No purpose of reference is specified.

TID 3217 Sub-segmental Data

The Sub-segmental Data Template consists of a CONTAINER providing quantitative arterial analysis measurements derived for a sub-segment in a total analyzed segment.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3217. Sub-Segmental Data

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CONTAINER	EV (59776-5, LN, "Findings")	1	M
2	>	HAS CONCEPT MOD	CODE	EV (363698007, SCT, "Finding Site")	1	M	DCID 3604 “Arterial Lesion Location”
3	>>	HAS CONCEPT MOD	CODE	EV (106233006, SCT, "Topographical modifier")	1	U	DCID 3019 “Cardiovascular Anatomic Structure Modifier”
4	>	CONTAINS	CODE	EV (122554, DCM, "Segmentation Method")	1	M	DCID 3456 “Sub-segment Method”
5	>	CONTAINS	INCLUDE	DTID 3219 “Segment Values”	1	U
6	>	CONTAINS	INCLUDE	DTID 3218 “Position in Arterial Segment”	1	M
7	>	CONTAINS	IMAGE		1	U

Content Item Descriptions

Row 7

Secondary Capture image with obstruction analysis contour. No purpose of reference is specified.

TID 3218 Position in Arterial Segment

The Position in Arterial Segment Template consists of the position Content Items common for the Angiographic Lesion Analysis and Sub-Segmental Data.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3218. Position in Arterial Segment

	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M		$Measurement = EV (122528, DCM, "Position of Proximal Border") $Units = DT (mm, UCUM, "mm")
2	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M		$Measurement = EV (122529, DCM, "Position of Distal Border") $Units = DT (mm, UCUM, "mm")
3	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M		$Measurement = EV (122382, DCM, "Site of Luminal Minimum") $Units = DT (mm, UCUM, "mm")
4	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M		$Measurement = EV (122516, DCM, "Site of Luminal Maximum") $Units = DT (mm, UCUM, "mm")
5	CONTAINS	NUM	EV (122528, DCM, "Position of Proximal Border")	1	UC	IFF TID 3214 “Analyzed Segment” Row 14 is present	UNITS = DT ({pixels}, UCUM, "pixels")
6	CONTAINS	NUM	EV (122529, DCM, "Position of Distal Border")	1	UC	IFF TID 3214 “Analyzed Segment” Row 14 is present	UNITS = DT ({pixels}, UCUM, "pixels")
7	CONTAINS	NUM	EV (122382, DCM, "Site of Luminal Minimum")	1	UC	IFF TID 3214 “Analyzed Segment” Row 14 is present	UNITS = DT ({pixels}, UCUM, "pixels")
8	CONTAINS	NUM	EV (122516, DCM, "Site of Luminal Maximum")	1	UC	IFF TID 3214 “Analyzed Segment” Row 14 is present	UNITS = DT ({pixels}, UCUM, "pixels")

Content Item Descriptions

Rows 1, 2, 3, 4	Positions are relative to the midpoint of the first left and right contour points and measured along the midline of the left and right contour
Rows 5, 6, 7, 8	The positions are relative to the measurement locations of the Diameter Graph of TID 3214 “Analyzed Segment” Row 14.

TID 3219 Segment Values

The Segment Values Template consists of Content Items providing quantitative arterial analysis measurements for a total analyzed segment or sub segment.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3219. Segment Values

	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = EV (122510, DCM, "Length Luminal Segment") $Units = DT (mm, UCUM, "mm")
2	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = EV (397413000, SCT, "Vessel Luminal Diameter") $Derivation = EV (255605001, SCT, "Minimum") $Units = DT (mm, UCUM, "mm")
3	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = EV (397413000, SCT, "Vessel Luminal Diameter") $Derivation = EV (56851009, SCT, "Maximum") $Units = DT (mm, UCUM, "mm")
4	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	M	$Measurement = EV (397413000, SCT, "Vessel Luminal Diameter") $Derivation = EV (373098007, SCT, "Mean") $Units = DT (mm, UCUM, "mm")
5	CONTAINS	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (397413000, SCT, "Vessel Luminal Diameter") $Derivation = EV (386136009, SCT, "Standard Deviation") $Units = DT (mm, UCUM, "mm")

Content Item Descriptions

Row 1

Measured along the midline of the left and right contour.

IVUS Report Templates

The Templates that comprise the IVUS Report within the Evidence Report IOD are interconnected as shown in Figure A-5.

Figure A-5. IVUS Report Template Hierarchy

TID 3250 IVUS Report

The IVUS Report Template is the root structure for the representation of IVUS measurements acquired during a catheterization procedure.

Type:: Extensible
Order:: Significant
Root:: Yes

Table TID 3250. IVUS Report

	NL	Rel with Parent	VT	Concept Name	VM	Req Type
1			CONTAINER	EV (122325, DCM, "IVUS Report")	1	M
2	>	HAS CONCEPT MOD	INCLUDE	DTID 1204 “Language of Content Item and Descendants”	1	M
3	>	HAS OBS CONTEXT	INCLUDE	DTID 1002 “Observer Context”	1-n	U
4	>		INCLUDE	DTID 3601 “Procedure Context”	1	U
5	>	CONTAINS	INCLUDE	DTID 3602 “Cardiovascular Patient Characteristics”	1	U
6	>	CONTAINS	CONTAINER	EV (111028, DCM, "Image Library")	1	U
7	>>	CONTAINS	IMAGE		1-n	U
8	>	CONTAINS	INCLUDE	DTID 3251 “IVUS Vessel”	1-n	M

Content Item Descriptions

Row 7

No purpose of reference is specified.

TID 3251 IVUS Vessel

The IVUS Vessel Template provides a structure for grouping one or more lesions analyzed and/or treated during a single phase of a catheterization procedure, according to vessel (or arterial location).

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3251. IVUS Vessel

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CONTAINER	EV (59776-5, LN, "Findings")	1	M
2	>	HAS CONCEPT MOD	CODE	EV (363698007, SCT, "Finding Site")	1	U		DCID 3604 “Arterial Lesion Location”
3	>>	HAS CONCEPT MOD	CODE	EV (106233006, SCT, "Topographical modifier")	1	U		DCID 3019 “Cardiovascular Anatomic Structure Modifier”
4	>>	HAS CONCEPT MOD	CODE	EV (272741003, SCT, "Laterality")	1	UC	IFF anatomy has laterality	DCID 244 “Laterality”
5	>	HAS ACQ CONTEXT	CODE	EV (129085009, SCT, "Catheterization Procedure Phase")	1	U		DCID 3480 “IVUS Procedure Phase”
6	>	CONTAINS	CODE	EV (122134, DCM, "Vessel Morphology")	1-n	U		CID 3712 “Vessel Descriptor”
7	>	CONTAINS	INCLUDE	DTID 3819 “Common Findings”	1-n	U
8	>	CONTAINS	CODE	EV (115, NCDR [2.0b], "Dissection in segment")	1	U		DCID 230 “Yes-No”
9	>	CONTAINS	INCLUDE	DTID 3252 “IVUS Lesion”	1-n	U

TID 3252 IVUS Lesion

The IVUS Lesion Template provides a structure for grouping measurements and observations made on a single lesion during an Intravascular Ultrasound Procedure.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3252. IVUS Lesion

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Condition	Value Set Constraint
1			CONTAINER	EV (300577008, SCT, "Lesion Finding")	1	M
2	>	HAS OBS CONTEXT	TEXT	EV (121151, DCM, "Lesion Identifier")	1	M		Up to 3 numeric characters
3	>>	HAS CONCEPT MOD	CODE	EV (363698007, SCT, "Finding Site")	1-n	U		DCID 3604 “Arterial Lesion Location”
4	>>>	HAS CONCEPT MOD	CODE	EV (106233006, SCT, "Topographical modifier")	1	U		DCID 3019 “Cardiovascular Anatomic Structure Modifier”
5	>	HAS ACQ CONTEXT	INCLUDE	DTID 3107 “Device Used”	1-n	U
6	>	CONTAINS	INCLUDE	DTID 3253 “IVUS Measurements”	1	MC	One or both of Rows 6 & 7 must be present
7	>	CONTAINS	INCLUDE	DTID 3254 “IVUS Qualitative Assessments”	1	MC	One or both of Rows 6 & 7 must be present
8	>	CONTAINS	INCLUDE	DTID 3819 “Common Findings”	1-n	U

Content Item Descriptions

Row 2	Lesion Identifier is specified as a numeric text string in order to facilitate trans-coding to DICOM Attribute (0018,3105) Lesion Number and to formats for outcomes registries, such as the ACC National Cardiovascular Data Registry™. Note Also see TID 3105 “Lesion Identification and Properties”.
Row 3	Finding site may span multiple segments with the proximal and distal extent specified by separate items. These may not be totally contained with the segment specified at the Vessel level.

TID 3253 IVUS Measurements

The IVUS measurements Template groups together simple distance, area and angle measurements, along with derived measurements that made during an IVUS procedure. Refer to the " ACC Clinical Expert Consensus Document on Standards for Acquisition, measurement and Reporting of Intravascular Ultrasound Studies (IVUS) "for more information.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3253. IVUS Measurements

	VT	Concept Name	VM	Req Type	Value Set Constraint
1	INCLUDE	DTID 300 “Measurement”	1-n	U	$Measurement = DCID 3481 “IVUS Distance Measurement” $Units = EV (mm, UCUM, "mm") $Derivation = DCID 3488 “Min/Max/Mean” $TargetSite = BCID 3486 “Vascular Measurement Site”
2	INCLUDE	DTID 300 “Measurement”	1-n	U	$Measurement = DCID 3482 “IVUS Area Measurement” $Units = EV (mm2, UCUM, "mm2") $Derivation = DCID 3488 “Min/Max/Mean” $TargetSite = BCID 3486 “Vascular Measurement Site”
3	INCLUDE	DTID 300 “Measurement”	1-n	U	$Measurement = DCID 3483 “IVUS Longitudinal Measurement” $Units = EV (mm, UCUM, "mm")
4	INCLUDE	DTID 300 “Measurement”	1-n	U	$Measurement = EV (122355, DCM, "Arc of Calcium") $Units = EV (deg, UCUM, "degrees") $TargetSite = BCID 3486 “Vascular Measurement Site”
5	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (408714007, SCT, "Lumen Area Stenosis") $Units = EV (%, UCUM, "%")
6	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (122354, DCM, "Plaque Burden") $Units = EV (%, UCUM, "%") $TargetSite = BCID 3486 “Vascular Measurement Site”
7	INCLUDE	DTID 300 “Measurement”	1-n	U	$Measurement = DCID 3484 “IVUS Index/Ratio” $Units = EV ({ratio}, UCUM, "ratio") $TargetSite = BCID 3486 “Vascular Measurement Site”
8	INCLUDE	DTID 3255 “IVUS Volume Measurement”	1-n	U
9	INCLUDE	DTID 300 “Measurement”	1	U	$Measurement = EV (122339, DCM, "Stent Volume Obstruction") $Units = EV (%, UCUM, "%")

TID 3254 IVUS Qualitative Assessments

The IVUS Qualitative Assessments Template groups together the qualitative properties of a lesion that are observed during an IVUS procedure. Refer to the "ACC Clinical Expert Consensus Document on Standards for Acquisition, measurement and Reporting of Intravascular Ultrasound Studies (IVUS) " for more information.

Type:: Extensible
Order:: Significant
Root:: No

Table TID 3254. IVUS Qualitative Assessments

	NL	Rel with Parent	VT	Concept Name	VM	Req Type	Value Set Constraint
1			CODE	EV (122133, DCM, "Lesion Morphology")	1-n	U	DCID 3491 “IVUS Lesion Morphology”
2			CODE	EV (121071, DCM, "Finding")	1-n	U	DCID 3494 “IVUS Non Morphological Finding”
3	>		INCLUDE	DTID 1350 “Negation Modifier, Presence of Finding”	1	U
4			CODE	EV (121071, DCM, "Finding")	1	U	EV (710864009, SCT, "Arterial Dissection")
5	>	HAS CONCEPT MOD	CODE	EV (122387, DCM, "Dissection Classification")	1	U	DCID 3492 “Vascular Dissection Classification”
6	>		INCLUDE	DTID 1350 “Negation Modifier, Presence of Finding”	1	U
7			CODE	EV (122391, DCM, "Relative Stenosis Severity")	1	U	DCID 3493 “IVUS Relative Stenosis Severity”
8			CODE	EV (108, NCDR [2.0b], "Previously Dilated Lesion")	1	U	DCID 3750 “Previously Dilated Lesion”
9			CODE	EV (121071, DCM, "Finding")	1	U	EV (122393, DCM, "Restenotic Lesion")
10	>		INCLUDE	DTID 1350 “Negation Modifier, Presence of Finding”	1	U
11			CODE	EV (111009, DCM, "Calcification Type")	1	U	DCID 3489 “Calcium Distribution”