MediaWiki API result

{
    "batchcomplete": "",
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "31": {
                "pageid": 31,
                "ns": 0,
                "title": "Vol1Profiles",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "__NOTOC__\n=Volume 1 - Profiles=\n\n=10 Anatomic Pathology Structured Report (APSR) Profile=\n\nThis content profile describes an\nanatomic pathology structured report (APSR) as a digital document to be shared or\nexchanged between pathology laboratories and other care providers and\ninstitutions. \n\nAnatomic pathology structured reports\ndocument the findings on specimens removed from patients for diagnostic or\ntherapeutic reasons. This information can be used for patient care, clinical\nresearch and epidemiology. Standardizing and computerizing anatomic pathology\nreports is necessary to improve the quality of reporting and to facilitate the\nexchange and reuse of the content of these reports.\n\nThis content profile describes a digital\nanatomic pathology report shared in a human-readable format, which may include\nimages, and which also contains findings and observations in a machine-readable\nformat, to facilitate the integration of these into the database of a consumer\nsystem, and to enable the application of automated reasoning to this content.\n\nThe scope of this IHE content profile covers all fields\nof anatomic pathology (cancers, benign neoplasms as well as non-neoplastic\nconditions) as well as cytopathology.\n\nGoldsmith J.D. et al. <ref>Goldsmith, J.D., et al., \u201cReporting\nguidelines for clinical laboratory reports in surgical pathology\u201d Arch Pathol\nLab Med, 2008. 132(10): p. 1608-16</ref> is the first source of specification for\nthis content profile. This article delineates the required, preferred, and\noptional elements which should be included in any report of surgical pathology.\n\nThis source is complemented by the \n\u201cCancer Checklists\u201d produced by the College of American Pathologists <ref>http://www.cap.org/web/oracle/webcenter/portalapp/pagehierarchy/cancer_protocol_templates.jspx?_adf.ctrl-state=e1f4ltym4_4&_afrLoop=275425457234715#!</ref>, and by\nthe \u201ccomptes rendus d\u2019anatomopathologie : donn\u00e9es minimales \u00e0 renseigner pour\nune tumeur primitive\u201d produced by the French society of pathology (SFP <ref> http://www.sfpathol.org</ref>)\nfor the French cancer institute (INCa <ref>http://www.e-cancer.fr</ref>), and by the German \"Guideline Pathology / Neuropathology\" (formerly TM-30) of the Sector Committee Pathology for the implementation of DIN EN ISO/EC 17020. \n\nThis profile has also benefited from the\nguidance on cancer AP reports provided by the North-American Association of\nCentral Cancer Registries; some of the example snippets captured in the profile\nleverage the NAACCR Standards for Cancer Registries, Volume V, Pathology\nLaboratory Electronic Reporting.\n\n== 10.1 APSR Actors/Transactions ==\n\nThis\nsection defines the actors, transactions, and/or content modules in this\nprofile. General definitions of actors are given in the Technical Frameworks\nGeneral Introduction Appendix A published [http://ihe.net/Technical_Frameworks/#GenIntro here]. \n\nFigure 10.1-1\nshows the actors directly involved in the APSR Profile and the direction that\nthe content that is exchanged. \n\nA product implementation using this profile must group actors from this profile\nwith actors from a workflow or transport profile to be functional. The grouping\nof the content module described in this profile to specific actors is described\nin more detail in the \u201cRequired Actor Groupings\u201d section below.\n\n[[File:Fig.4.1.-1.jpg]]\n\n'''Figure 10.1-1: APSR Actor Diagram'''\n\n\nTable 10.1-1 lists the content module(s)\ndefined in the APSR profile. To claim support with this profile, an actor shall\nsupport all required content modules (labeled \u201cR\u201d) and may support optional\ncontent modules (labeled \u201cO\u201d). \n\n\n'''Table 10.1-1: APSR Profile - Actors and Content Modules'''\n{| class=\"hl7table\"\n!Actors !! Content Modules !! Optionality !! Reference\n|-\n|Content \nCreator\n||\nAnatomic Pathology Structured Report\n1.3.6.1.4.1.19376.1.8.1.1.1\n|| R\n||PaLM TF-3: 6.3.1.2\n|-\n|Content \nConsumer\n||\nAnatomic Pathology Structured Report\n1.3.6.1.4.1.19376.1.8.1.1.1\n|| R\n||PaLM TF-3: 6.3.1.2\n|-\n|}\n\n=== 10.1.1 Actor Descriptions and Actor Profile Requirements===\n\nMost requirements are documented in\nContent Modules (Volume 3). This section documents any additional requirements\non profile\u2019s actors.\n\n==10.2 APSR Actor Options==\n\nOptions that may be selected for each\nactor in this profile are listed in the table 10.2-1. These options are further\ndetailed in PCC Technical Framework Volume 2 as indicated in the rightmost\ncolumn.\n\n'''Table 10.2-1  Anatomic Pathology Structured Report - Actors and Options'''\n\n{| class=\"hl7table\"\n!Actor !! Option Name !! Reference\n|-\n|Content \nCreator\n||''None''\n|| \n|-\n|Content \nConsumer\n||''View Option (1)''\n''Document Import Option (1)''\n\n''Section Import Option (1)''\n||PCC TF-2:3.1.1\nPCC TF-2:3.1.2\n\nPCC TF-2:3.1.3\n|-\n|}\nNote 1: The Content Consumer shall support at least one of these options.\n\n==10.3 APSR Required Actor Groupings ==\n\nAn actor from this profile (Column 1)\nshall implement all of the required transactions and/or content modules in this\nprofile in addition to all of the transactions required for the grouped\nactor (Column 2). \n\nIn some cases, required groupings are\ndefined as at least one of an enumerated set of possible actors; this is\ndesignated by merging column one into a single cell spanning multiple potential\ngrouped actors. Notes are used to highlight this situation.\n\nSection 10.5 describes some optional\ngroupings that may be of interest for security considerations and section 10.6\ndescribes some optional groupings in other related profiles.\n\n'''Table 10.3-1: Anatomic Pathology Structured Report - Required Actor Groupings'''\n{| class=\"hl7table\"\n!APSR Actor !! Actor to be grouped with !! Reference !! Content Bindings Reference\n|-\n|Content \nCreator\n||\nITI XDS.b\nDocument Source\n\nOR \n\nITI XDM Portable Media Creator\n\nOR\n\nITI XDR Document\nSource\n\nOR\n\nITI MHD Document Source\n|| \nITI TF-1:10\n\n\nITI TF-1:16\n\n \nITI TF-1:15\n\n\n\nITI TF-1:33\n|| \n|-\n|Content \nConsumer\n||\nITI XDS.b Document Consumer\n\nOR \n\nITI XDM Portable Media Consumer\n\nOR\n\nITI XDR Document\nRecipient\n\nOR\n\nITI MHD Document Consumer\n||\nITI TF-1:10\n\n\n \nITI TF-1:16\n\n\n\nITI TF-1:15\n\n\nITI TF-1:33\n|| \n|-\n|}\nNote 1: Each actor of APSR SHALL be grouped with at least one of the ITI actors listed in its table row.\n\n==10.4 APSR Overview==\n\n===10.4.1 Concepts===\n\nThis content profile represents a common\ndigital document model applicable to any structured report for surgical\npathology in all fields of anatomic pathology (cancers, benign neoplasms, non-neoplastic\nconditions) as well as for cytopathology.\n\nThis common model is composed of a header conveying\nthe context of care (patient, care providers, pathologists, laboratories,\norder, act documented \u2026) and a body. The body organizes the human-readable\ncontent of the report in a number of sections. Each section may also provide\nmachine-readable content in a repeatable \u201centry\u201d embedded in the section.  This common model defines the order of\nappearance, cardinalities and internal structure of each section, and of each\nentry embedded in each section. \n\nFigure 10.4.1-1 shows this general model\napplicable to any pathology digital report.\n\n[[File:10.4.1-1_APSR2layout.png]]\n\n'''Figure 10.4.1-1: Common model for a digital anatomic pathology structured report'''\n\n''Note 1: The only section that is mandatory is the Diagnostic Conclusion section.''\n\n=== 10.4.2 Use Cases ===\n==== 10.4.2.1 Use Case #1: Single Report ====\nAnatomic pathology order fulfilled by a pathology laboratory produces a report.\n\n=====10.4.2.1.1 Single Report Use Case Description=====\nDr. Eva Surgeon, PhD, takes a ultrasound guided core biopsy from a breast tumor from patient Eve Onewoman, born on Sept 21 1971, requests the procedure \u201cbreast core biopsy specimen - pathological examination\u201d and sends the specimen to the anatomic pathology laboratory of the Cancer Institute.\nOne specimen (five cores) is accessioned by the anatomic pathology laboratory under the accession number A710240008. The staff performs a macroscopic examination of the specimen; gross imaging is performed if needed. The specimen with the specimen ID A710240008_A is processed for microscopic examination and other special ancillary techniques or tissue banking if needed. During the imaging interpretation process, microscopic imaging is performed if needed. At the end of the interpretation process of the macroscopic and microscopic observations and some ancillary techniques, done by the pathologists Dr. Marcel Pathologist, PhD, and Dr. Jonas Jones, M.D., Dr. Marcel Pathologist queries the Content Creator application for the appropriate APSR template, fills the form, binds some relevant images and/or regions of interest to specific observations, validates and signs the digital report.\n\n=====10.4.2.1.2 Single Report Process Flow=====\n\n[[File:Flow_case_1.png|600px]]\n\n=====10.4.2.1.3 Single Report Text Example=====\nMacroscopic observation\n\nA. \"RIGHT BREAST FIVE CORES 8-9:00\" (ULTRASOUND GUIDED NEEDLE CORE BIOPSY):\n\nMicroscopic observation\n\nINVASIVE ADENOCARCINOMA OF THE BREAST.<br/>\nICD-O-3-CLASSIFICATION: C50.3 M8500/33<br/>\nHISTOLOGIC TYPE: DUCTAL.<br/>\nNOTTINGHAM COMBINED HISTOLOGIC GRADE: 1 OF 3.<br/>\nTUBULE FORMATION SCORE: 2.\nNUCLEAR PLEOMORPHISM SCORE: 2.\nMITOTIC RATE SCORE: 1.\n\nIN-SITU CARCINOMA: EQUIVOCAL.\n\nBREAST CANCER BIOMARKER STUDIES:<br/> \nPARAFFIN BLOCK NUMBER: A1.<br/>\nER INTERPRETATION: POSITIVE ESTROGEN RECEPTOR ACTIVITY (ALLRED SCORE = 8, Percentage of positive cells = 85%, Staining Intensity score = 3).<br/>\nPR INTERPRETATION: POSITIVE PROGESTERONE RECEPTOR ACTIVITY (ALLRED SCORE = 8).<br/>\nDAKO EGFR PHARMDX IMMUNOHISTOCHEMISTRY: NEGATIVE (0) FOR EXPRESSION OF\nEPIDERMAL GROWTH FACTOR RECEPTOR.<br/>\nHER2/NEU IMMUNOHISTOCHEMISTRY: AMBIGUOUS(2+) FOR OVEREXPRESSION OF HER2/NEU\nONCOPROTEIN.<br/>\nHER2/NEU FISH RESULT: NEGATIVE FOR AMPLIFICATION OF HER2/NEU.<br/>\n\n\nDiagnostic conclusion\n\nA. \"RIGHT BREAST FIVE CORES 8-9:00\" (ULTRASOUND GUIDED NEEDLE CORE BIOPSY):\n\nINVASIVE ADENOCARCINOMA OF THE BREAST.<br/>\nICD-O-3-CLASSIFICATION: C50.3 M8500/33<br/>\nHISTOLOGIC TYPE: DUCTAL.<br/>\nNOTTINGHAM COMBINED HISTOLOGIC GRADE: 1 OF 3.<br/>\nTUBULE FORMATION SCORE: 2.\nNUCLEAR PLEOMORPHISM SCORE: 2.\nMITOTIC RATE SCORE: 1.\n\nIN-SITU CARCINOMA: EQUIVOCAL.\n\nBREAST CANCER BIOMARKER STUDIES:<br/> \nPARAFFIN BLOCK NUMBER: A1.<br/>\nER INTERPRETATION: POSITIVE ESTROGEN RECEPTOR ACTIVITY (ALLRED SCORE = 8, Percentage of positive cells = 85%, Staining Intensity score = 3).<br/>\nPR INTERPRETATION: POSITIVE PROGESTERONE RECEPTOR ACTIVITY (ALLRED SCORE = 8).<br/>\nDAKO EGFR PHARMDX IMMUNOHISTOCHEMISTRY: NEGATIVE (0) FOR EXPRESSION OF\nEPIDERMAL GROWTH FACTOR RECEPTOR.<br/>\nHER2/NEU IMMUNOHISTOCHEMISTRY: AMBIGUOUS(2+) FOR OVEREXPRESSION OF HER2/NEU\nONCOPROTEIN.<br/>\nHER2/NEU FISH RESULT: NEGATIVE FOR AMPLIFICATION OF HER2/NEU.<br/>\n\n\nProcedure steps:\n\nRIGHT BREAST FIVE CORES 8-9:00\" (ULTRASOUND GUIDED NEEDLE CORE BIOPSY)\nPARAFFIN BLOCK NUMBER: A1.:FOUR SECTIONS FOR EACH STAIN:\n\nRIGHT BREAST FIVE CORES 8-9:00\n\nPARAFFIN BLOCK NUMBER: A1\n\nslide from block A1 HE stained\n\nslide from block A1 ER Immunohistochemistry\n\nslide from block A1 PR Immunohistochemistry\n\nslide from block A1 EGFR (PharmDX) Immunohistochemistry\n\nslide from block A1 HER2 Immunohistochemistry\n\nslide block from A1 HER2 FISH\n\n====10.4.2.2 Use Case #2: Multi-step Report====\n\nReporting includes multiple successive steps.\n\n=====10.4.2.2.1 Multi-step Report Use Case Description=====\n\nA surgeon removes a breast tumor from a patient, requests the procedure \u201cbreast surgical specimen - frozen sections & pathological examination\u201d, and  \u201cbreast surgical specimen - pathological examination\u201d and sends the specimen(s) to the anatomic pathology laboratory. \n\nSpecimens are accessioned by the anatomic pathology department. The staff performs a macroscopic examination of the specimens, gross imaging is performed if needed. The specimens are processed for intraoperative observation if needed, and tissue banking if needed (e.g., for research purpose). During the imaging interpretation process of frozen sections, microscopic imaging is performed if needed. At the end of the interpretation process, the pathologist queries the Content Creator for the appropriate APSR template, fills the intraoperative observation section, binds some relevant images and/or regions of interest to specific observation(s) if needed, validates and signs (i.e., legally authenticates) the preliminary APSR.\n\nThe day after, the specimen(s) are processed for microscopic examination and other special ancillary techniques if needed. During the imaging interpretation process, microscopic imaging is performed if needed. At the end of the interpretation process, pathologist queries the Content Creator for the preliminary APSR, fills the form, binds some relevant images and/or regions of interest to specific observation(s), validates and signs (i.e., legally authenticates) the final APSR.\n\n=====10.4.2.2.2 Multi-step Report Process Flow=====\n\n[[File:Flow_Case_2.png|600px]]\n\n==10.5 APSR Security Considerations==\n\nSee PaLM TF-1: Appendix A.\n\n==10.6 APSR Cross Profile Considerations==\n\nIntentionally left blank"
                    }
                ]
            },
            "34": {
                "pageid": 34,
                "ns": 0,
                "title": "Vol3ContentModules",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "__NOTOC__\n= Volume 3 \u2013 Content Modules =\n\n= 1 Introduction =\nThe content of this entire section is identical to Section 1 of [http://www.ihe.net/uploadedFiles/Documents/PaLM/IHE_PaLM_TF_Vol3.pdf PaLM: TF-3].\n\n== 1.1 Overview of the Anatomic Pathology Technical Framework ==\nIntegrating the Healthcare Enterprise (IHE) is an international initiative to promote the use of standards to achieve interoperability among health information technology (HIT) systems and effective use of electronic health records (EHRs). IHE provides a forum for care providers, HIT experts and other stakeholders in several clinical and operational domains to reach consensus on standards-based solutions to critical interoperability issues. \nThe primary output of IHE is system implementation guides, called IHE Profiles. IHE publishes each profile through a well-defined process of public review and trial implementation and gathers profiles that have reached final text status into an IHE Technical Framework, of which this volume is a part.\nFor more general information regarding IHE, refer to [http://ihe.net IHE International website]. It is strongly recommended that, prior to reading this volume, the reader familiarizes themselves with the concepts defined in the [https://www.ihe.net/resources/technical_frameworks/#GenIntro IHE Technical Frameworks General Introduction].\n\n== 1.2 Intended Audience ==\nThe intended audience of IHE Technical Frameworks Volume 3 is:\n* IT departments of healthcare institutions \n* Technical staff of vendors participating in the IHE initiative\n* Experts involved in standards development\n\n== 1.3 Overview of Technical Framework Volume 3 ==\nVolume 3 is comprised of several distinct sections:  \n* Section 1 provides background and reference material.\n* Section 2 presents the conventions used in this volume to define the content modules.\n* Section 3 provides an overview of Content Modules and the terminology used.\n* Section 4 is reserved for domain unique Content Module specifications.\n* Section 5 lists the namespaces and identifiers defined or referenced and the vocabularies defined or referenced herein.\n* Section 6 defines the PaLM domain\u2019s HL7&reg; <ref>HL7 is the registered trademark of Health Level Seven International.</ref> V3 CDA Content Modules in detail.\n* Section 7 defines the PaLM domain\u2019s DICOM&reg; <ref>DICOM is the registered trademark of the National Electrical Manufacturers Association for its standards publications relating to digital communications of medical information.</ref> content modules in detail.\n* Section 8 defines other types of content modules.\nThe appendices in Volume 3 provide clarification of technical details of the IHE data model and transactions. A glossary of terms and acronyms used in the IHE Technical Framework, including those from relevant standards, is provided in the [https://www.ihe.net/resources/technical_frameworks/#GenIntro IHE Technical Frameworks General Introduction]. Due to the length of the document, some domains may divide Volume 3 into smaller volumes labeled 3a, 3b, etc. In this case, the Volume 3 appendices are gathered in Volume 3x. Code and message samples may also be stored on the IHE ftp server. In this case, explicit links to the ftp server will be provided in the transaction text.\n\n== 1.4 Comment Process ==\nIHE International welcomes comments on this document and the IHE initiative. Comments on the IHE initiative can be submitted by sending an email to the co-chairs and secretary of the Pathology and Laboratory Medicine domain committees at palm@ihe.net. Comments on this document can be submitted at https://www.ihe.net/PaLM_Public_Comments/.\n\n== 1.5 Copyright Licenses ==\nIHE International hereby grants to each Member Organization, and to any other user of these documents, an irrevocable, worldwide, perpetual, royalty-free, nontransferable, nonexclusive, non-sublicensable license under its copyrights in any IHE profiles and Technical Framework documents, as well as any additional copyrighted materials that will be owned by IHE International and will be made available for use by Member Organizations, to reproduce and distribute (in any and all print, electronic or other means of reproduction, storage or transmission) such IHE Technical Documents. \nThe licenses covered by this Copyright License are only to those copyrights owned or controlled by IHE International itself. If parts of the Technical Framework are included in products that also include materials owned or controlled by other parties, licenses to use those products are beyond the scope of this IHE document and would have to be obtained from that other party.\n=== 1.5.1 Copyright of Base Standards ===\nIHE technical documents refer to and make use of a number of standards developed and published by several standards development organizations. All rights for their respective base standards are reserved by these organizations. This agreement does not supersede any copyright provisions applicable to such base standards.\nHealth Level Seven, Inc. has granted permission to IHE to reproduce tables from the HL7 standard. The HL7 tables in this document are copyrighted by Health Level Seven, Inc. All rights reserved. Material drawn from these documents is credited where used.\n\n== 1.6 Trademark ==\nIHE\u00ae and the IHE logo are trademarks of the Healthcare Information Management Systems Society in the United States and trademarks of IHE Europe in the European Community. They may only be used with the written consent of the IHE International Board Operations Committee, which may be given to a Member Organization in broad terms for any use that is consistent with the IHE mission and operating principles.\n\n== 1.7\tDisclaimer Regarding Patent Rights ==\nAttention is called to the possibility that implementation of the specifications in this document may require use of subject matter covered by patent rights. By publication of this document, no position is taken with respect to the existence or validity of any patent rights in connection therewith. IHE International is not responsible for identifying Necessary Patent Claims for which a license may be required, for conducting inquiries into the legal validity or scope of Patents Claims or determining whether any licensing terms or conditions provided in connection with submission of a Letter of Assurance, if any, or in any licensing agreements are reasonable or non-discriminatory. Users of the specifications in this document are expressly advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further information about the IHE International patent disclosure process including links to forms for making disclosures is available [http://www.ihe.net/Patent_Disclosure_Process here]. Please address questions about the patent disclosure process to the secretary of the IHE International Board: secretary@ihe.net \n\n== 1.8 History of Document Changes ==\nContent Modules for the APSR Profile:\n\n*Reconfiguration of the Document content module\n*Reconfiguration of the Procedure step section content module\n*Introduction of the Additional Specified Observation section content module\n*Reconfiguration of the entry content modules \"Problem organizer\", \"Specimen procedure steps\", and \"Update information organizer\"\n*Introduction of child element content modules \"X-specimen identified\", \"UICC/AJCC-TNM observation\", \"ICD-O-3 observation\", \"Assessment scales observation\", \"Pertinent insurance information\".\n*Renewal and completion of value sets.\n\nTransformation of a real-world use case into a valid APSR xml instance.\n\nFinalization of the supplement for trial implementation publication.\n\n= 2 Conventions =\nThis document has adopted the following conventions for representing the framework concepts and specifying how the standards upon which the IHE Technical Framework is based shall be applied.\n\n== 2.1 Content Module Modeling and Profiling Conventions ==\nIn order to maintain consistent documentation, modeling methods for IHE content modules and profiling conventions for frequently used standards are maintained as an appendix in the [https://www.ihe.net/resources/technical_frameworks/#GenIntro IHE Technical Frameworks General Introduction]. Methods described include the standards conventions DICOM, HL7 v2.x, HL7 Clinical Document Architecture (CDA) Documents, etc. These conventions are critical to understanding this volume and should be reviewed prior to reading this text.\n\n== 2.2 Additional Standards Profiling Conventions ==\nThis section defines profiling conventions for standards which are not described in the IHE Technical Frameworks General Introduction.<br/>\nNot Applicable.\n\n= 3 Content Modules Overview and Terminology =\nIn the future, an appendix to the IHE Technical Frameworks General Introduction will provide an overview of Content Modules. In the interim, information may be available [http://wiki.ihe.net/index.php?title=Profiles here].<br/>\nThe Pathology and Laboratory Medicine content modules are listed in the table below:<br/>\n'''Table 3-1: Pathology and Laboratory Medicine Content Modules'''\n{| class=\"hl7table\"\n!Content Module Acronym !! Type of Content Modules !! Semantic !! Status\n|-\n|XD-LAB || CDA R2 medical document || Clinical Laboratory Structured Report || Final Text\n|-\n|APSR || CDA R2 medical document || Anatomic Pathology Structured Report || Trial Implementation\n|-\n|}\n\n= 4 IHE Pathology and Laboratory Medicine Bindings =\n== 4.1 Medical Document Binding to XDS, XDM and XDR ==\nThe bindings of the content modules of the PaLM domain leverage the bindings specified by the Patient Care Coordination domain, in [http://www.ihe.net/uploadedFiles/Documents/PCC/IHE_PCC_TF_Vol2.pdf PCC TF Volume 2], section 4, with the addition of the constraints specified below.\n=== 4.1.1 XDSDocumentEntry Metadata ===\n==== 4.1.1.1 XDSDocumentEntry.eventCodeList ====\n<syntaxhighlight lang=\"xml\">\nAppend this paragraph at the end of the section.</syntaxhighlight>\nFor the APSR content module, The XDSDocumentEntry.eventCodeList provides a means to index anatomic pathology reports by reportable conditions (e.g., certain types of tumors\u2026) so as to facilitate later queries in a registry of shared clinical documents. The conclusions coded in the entry element of the Diagnostic Conclusion section are good candidates for this metadata.\n\n==== 4.1.1.2 XDSDocumentEntry.formatCode ====\n<syntaxhighlight lang=\"xml\">\nAppend this paragraph at the end of the section.</syntaxhighlight>\nFor the APSR content module, The XDSDocumentEntry.formatCode SHALL be urn:ihe:palm:apsr:2016<br/>\nThe associated codingScheme SHALL be 1.3.6.1.4.1.19376.1.2.3\n\n==== 4.1.1.3 XDSDocumentEntry.parentDocumentRelationship ====\n<syntaxhighlight lang=\"xml\">\nAppend this paragraph at the end of the section.</syntaxhighlight>\nFor the APSR content module XDSDocumentEntry.parentDocumentRelationship is constrained to the \"'''RPLC'''\" value. When there is a parent document the current document is a new version of the parent document, replacing it.\n\n* Note 1: A non-final anatomic pathology report published in an XDS infrastructure will likely be replaced afterwards by the final report. When this event occurs, the Content Creator Actor SHALL apply the following rules:\n** ClinicalDocument/setId SHALL have the same value in the new report as in the replaced report.\n** ClinicalDocument/versionNumber SHALL be incremented in the replacing report (i.e. the final one).\n** ClinicalDocument/relatedDocument@typeCode attribute SHALL be valued \u201dRPLC\u201d\n** ClinicalDocument/relatedDocument/parentDocument/id in the new report SHALL be equal to ClinicalDocument/ id of the replaced document.\nThe Document Source Actor SHALL apply the following rules on XDSDocumentEntry metadata:\n* The final report SHALL be associated with the previously published one, using RPLC relationship and the previous report SHALL be \u201cDeprecated\u201d as described in ITI TF-2:4.1.6.1.\n** Note 2: A non-final report can also be replaced by a more recent, albeit still non-final report. The rules above also apply in this case.\n** Note 3: A final report can also be replaced by a corrective final report. The rules above also apply in this case.\n** Note 4: A new version of a report SHOULD have an Update Organizer <entry> in its Diagnostic Conclusion <section> carrying information about what has been changed in comparison with the immediate previous report, and what is the clinical significance of that change.\n\n= 5 Namespaces and Vocabularies =\n\n== 5.1 OID tree of PAT TF ==\n\n1.3.6.1.4.1.19376.1.81.3.6.1.4.1.19376.1.8 is the OID of the former IHE Anatomic Pathology  domain, whereas 1.3.6.1.4.1.19376.1.81.3.6.1.4.1.19376.1.3 is the OID for PaLM domain :\n\nAll exchangeable objects specified by these domains are identified by OIDs built on these roots: \n\n\nBranch 1.3.6.1.4.1.19376.1.8.1 is dedicated to CDA Content Modules created by the AP domain\t\n\t\n        Sub-branch 1.3.6.1.4.1.19376.1.8.1.1 is the OID of the generic Document Content Module\t\t\n        Sub-branch 1.3.6.1.4.1.19376.1.8.1.2 is dedicated to Section Content Modules\n        Sub-branch 1.3.6.1.4.1.19376.1.8.1.3 is dedicated to Entry Content Modules.\n        Sub-branch 1.3.6.1.4.1.19376.1.8.1.3.6 is the OID of the Problem Organizer\n        Sub-branch 1.3.6.1.4.1.19376.1.8.1.4 is dedicated to Element Content Modules\t\n        Sub-branch 1.3.6.1.4.1.19376.1.8.1.4.9 is the OID of the generic anatomic pathology (AP) observation template\n\t\t\n \t\t\nBranch 1.3.6.1.4.1.19376.1.8.2 is dedicated to terminologies defined by AP domain\n\n        Sub-branch 1.3.6.1.4.1.19376.1.8.2.1 is dedicated to PathLex, BUT THIS TEMPORARY VOCABULARY IS NO LONGER USED\t\t\n\nBranch 1.3.6.1.4.1.19376.1.8.5 is dedicated to Value Sets defined by AP domain.\n\nBranch 1.3.6.1.4.1.19376.1.3.10 is dedicated to Templates newly defined by PaLM domain.\t\n\n        Sub-branch 1.3.6.1.4.1.19376.1.3.10.1 is dedicated to CDA Document Level Templates\n        Sub-branch 1.3.6.1.4.1.19376.1.3.10.2 is dedicated to CDA Header Level Templates\n        Sub-branch 1.3.6.1.4.1.19376.1.3.10.3 is dedicated to CDA Section Level Templates\n        Sub-branch 1.3.6.1.4.1.19376.1.3.10.4 is dedicated to CDA Entry Level Templates\n        Sub-branch 1.3.6.1.4.1.19376.1.3.10.9 is dedicated to CDA Template Fragments/Supporting Templates\n\nBranch 1.3.6.1.4.1.19376.1.3.11 is dedicated to Value Sets newly defined by PaLM domain.\t\t\n\nBranch 1.3.6.1.4.1.19376.1.8.9 is used to identify instances in the examples of AP content built by the PaLM domain.\t\n\n\nNotes on other IHE OIDs used in the AP domain: \t\t\t\t\n\nBranch 1.3.6.1.4.1.19376.1.3.4 is used to identify instances in the examples of AP content built by XD-LAB in the PaLM domain.\n\n== 5.2 Terminologies and controlled coded vocabularies ==\n\nThis section lists the terminologies and the coded vocabularies referenced by this Volume 3.\n\n'''Table 5.2-1  Anatomic Pathology Terminologies and Coded Vocabularies'''\n\n{|class=\"hl7table\"\n!codeSystem!!codeSystemName and Description!!Owner\n|- valign=top\n|2.16.840.1.113883.6.1\n|LOINC<br/>''Logical Observation Identifier Names and Codes''\n|Regenstrief Institute\n\n|- valign=top\n|2.16.840.1.113883.6.8\n|UCUM<br/>''Unified Code for Units of Measure''\n|Regenstrief Institute, and the UCUM Organization\n\n|- valign=top\n|2.16.840.1.113883.6.96\n|SNOMED-CT<br/>''Systematized Nomenclature of Medicine \u2013 Clinical Terms''\n|IHTSDO/Snomed International\n\n|- valign=top\n|1.3.6.1.4.1.19376.1.5.3.2\n|IHEActCode<br/>''Vocabulary defined by IHE PCC in PCC TF-2:5.1.2, used for representing annotation comments in the report''\n|IHE PCC \n\n|- valign=top\n|2.16.840.1.113883.5.4\n|Act Code<br/>''Codesystem for Acts''\n|HL7 International\n\n|- valign=top\n|2.16.840.1.113883.5.6\n|ActClass<br/>''Codesystem for Act Classes''\n|HL7 International\n\n|- valign=top\n|2.16.840.1.113883.5.1052\n|Act Site<br/>''Codesystem for Act Sites''\n|HL7 International\n\n|- valign=top\n|2.16.840.1.113883.5.1065\n|ProcedureMethod<br/>''Codesystem for Procedure Methods''\n|HL7 International\n\n|- valign=top\n|2.16.840.1.113883.5.111\n|Role Code<br/>''Codesystem for Role Codes''\n|HL7 International\n\n|- valign=top\n|2.16.840.1.113883.5.129\n|SpecimenType<br/>''Codesystem for Specimen Types''\n|HL7 \n\n|- valign=top\n|2.16.840.1.113883.5.83\n|ObservationInterpretation<br/>''One or more codes specifying a rough qualitative interpretation of the observation, such as \"normal\", \"abnormal\", \"below normal\", \"change up\", \"resistant\", \"susceptible\", etc.'' \n|HL7 International\n\n|- valign=top\n|2.16.840.1.113883.5.84\n|ObservationMethod<br/>''A code system that provides additional detail about the means or technique used to ascertain the observation''\n|HL7 International\n\n|- valign=top\n|2.16.840.1.113883.6.3\n|ICD-10<br/>''International Classification of Diseases revision 10''\n|WHO\n\n|- valign=top\n|2.16.840.1.113883.6.43.1\n|ICD-O-3<br/>''International Classification of Diseases for Oncology, 3rd edition, revision 1, 2013''\n|WHO\n\n|- valign=top\n| 1.2.840.10008.2.16.4\n|DICOM controlled vocabulary<br/>''The meanings of codes defined in DICOM, either explicitly or by reference to another part of DICOM or an external reference document or standard <ref>DICOM controlled vocabulary http://nema.org/dicom/dicm]</ref>''\n|DICOM\n\n|- valign=top\n|2.16.840.1.113883.15.16\n|TNM 8th edition<br/>''Internationally agreed-upon standards to describe and categorize cancer stages and progression <ref name=\"uicctnm\">UICC TNM http://www.uicc.org/resources/tnm</ref>''\n|Union for International Cancer Control (UICC) & American Joint Committee on Cancer (AJCC)\n\n|- valign=top\n|2.16.840.1.113883.15.6\n|TNM 7th edition<br/>''Internationally agreed-upon standards to describe and categorize cancer stages and progression <ref name=\"uicctnm\">UICC TNM http://www.uicc.org/resources/tnm</ref>''\n|Union for International Cancer Control (UICC) & American Joint Committee on Cancer (AJCC)\n\n|- valign=top\n|2.16.840.1.113883.15.7\n|TNM 6th edition<br/>''Internationally agreed-upon standards to describe and categorize cancer stages and progression <ref name=\"uicctnm\"/>''\n|Union for International Cancer Control (UICC) & American Joint Committee on Cancer (AJCC)\n\n|- valign=top\n|2.16.840.1.113883.15.8\n|TNM 5th edition<br/>''Internationally agreed-upon standards to describe and categorize cancer stages and progression <ref name=\"uicctnm\"/>''\n|Union for International Cancer Control (UICC) & American Joint Committee on Cancer (AJCC)\n\n|- valign=top\n|2.16.840.1.113883.6.4\n|ICD-10-PCS<br/>''International Classification of Diseases, 10th Revision, Procedure Coding System (ICD-10-PCS)''\n|WHO\n\n|- valign=top\n|1.2.276.0.76.5.464\n|OPS 2017<br/>''Code lists to describe and categorize surgeries and procedures, adapted from WHO ICPM for Germany''\n|DIMDI / (WHO)\n\n|- valign=top\n|2.16.840.1.113883.6.174\n|OMIM<br/>''Code lists to describe and categorize human genes. OMIM is a comprehensive, authoritative compendium of human genes and genetic phenotypes that is freely available and updated daily.''<ref> OMIM Johns Hopkins University School of Medicine  http://www.omim.org</ref>\n|OMIM Johns Hopkins University School of Medicine\n\n|- valign=top\n|1.2.276.0.76.3.1.131.1.5.1\n|DKG Coding Scheme<br/>''Internationally agreed-upon code lists to describe and categorize cancer grading systems, adapted for Germany <ref>Coding Schemes German Cancer Society http://wiki.hl7.de/index.php?title=cdaonk:OID-Konzept</ref>''\n|DKG (Deutsche Krebsgesellschaft)\n\n|- valign=top\n|1.2.276.0.76.5.336\n|Grading / Differentiation scheme<br/>''Code lists to describe and categorize Tumor grading according ICD-O-3, adapted for Germany'' \n||HL7 Germany\n\n|- valign=top\n|1.2.276.0.76.5.401\n|Localization scheme for distant metastases<br/>''Code lists to describe and categorize localization of metastases according UICC, adapted for Germany'' \n|HL7 Germany\n|}\n\n== 5.3 Value Sets ==\n\n\nThe value sets defined or referenced by this Volume 3 of the IHE PaLM TF Suppl. are listed and specified in Appendix A of this Volume.\n\n==5.4 Namespaces==\n\n===5.4.1 Namespace protecting extensions to the CDA schema===\n\nThere is currently one single extension to the CDA.xsd schema used in PaLM TF-3. This extension has been created by former IHE LAB and is protected by this particular namespace in document instances: '' xmlns:lab=\"urn:oid:1.3.6.1.4.1.19376.1.3.2\"''\n\n==5.5 References to Content Modules built outside of IHE PaLM TF==\nThe Content Modules specified in this Volume 3 of the PaLM TF leverage a number of Content Modules (currently CDA templates) produced and maintained by other groups, including other domains of IHE. Table 5.5-1 lists them.\n\n'''Table 5.5-1  External Content Modules referenced by PaLM TF-3'''\n\n{| class=\"hl7table\"\n!templateId !! Standard !!Definition!! Source of Specification\n|-\n|1.3.6.1.4.1.19376.1.5.3.1.3.1||CDA R2\n||Reason for referral\n||IHE PCC TF-2:6.3.3.1.2\n\n|-\n|1.3.6.1.4.1.19376.1.5.3.1.3.4\n||CDA R2||History of present illness\n||IHE PCC TF-2:6.3.3.2.1\n\n|-\n|1.3.6.1.4.1.19376.1.5.3.1.3.6\n||CDA R2||Active Problems\n||IHE PCC TF-2:6.3.3.2.3\n\n|-\n|1.3.6.1.4.1.19376.1.5.3.1.4.2\n||CDA R2||Comment\n||IHE PCC TF-2:6.3.4.6\n\n|}\n\n== 5.6 IHE code and formatCode for Anatomic Pathology Document Template ==\n<syntaxhighlight lang=\"xml\">\nMerge the content of this section into the current section 5.1.1 of PaLM TF volume 3.\n</syntaxhighlight>\nAny AP structured report SHALL be associated with the metadata typeCode = \u201c60568-3\u201d, which is the LOINC code for \u201cPathology Synoptic report\u201d.\n\nThe table below lists the format codes, template identifiers and media types used by the IHE Profiles specified in the PaLM Technical Framework. \nNote that the code system for these codes is 1.3.6.1.4.1.19376.1.2.3 as assigned by the ITI Domain for codes used for the purposes of cross-enterprise document sharing (XDS). For more information see [http://wiki.ihe.net/index.php?title=XDS_Coding_System_%281.3.6.1.4.1.19376.1.2.3%29 XDS Coding System (1.3.6.1.4.1.19376.1.2.3)]. \n<br/>\n{| class=\"hl7table\"\n!Profile !! formatCode !! Media Type !! Template ID\n|-\n|XD-LAB || urn:ihe:lab:xd-lab:2008 || text/xml || 1.3.6.1.4.1.19376.1.3.3 \n|-\n|APSR || urn:ihe:palm:apsr:2016 || text/xml || 1.3.6.1.4.1.19376.1.8.1.1.1\n|}\n\n<div class=\"landscape\">\n\n=6 PaLM HL7 CDA Content Modules=\n\n==6.1 Conventions==\n\n* HL7 CDA conventions are defined in the [https://www.ihe.net/resources/technical_frameworks/#GenIntro IHE Technical Frameworks General Introduction Appendix E] \n\n* In all Content Modules specified in this section, the abbreviation \u201c'''AP'''\u201d stands for \u201cAnatomic Pathology\u201d.\n\n==6.2 Folder Modules==\nIntentionally left blank\n\n==6.3 Content Modules==\nThis section defines each IHE Pathology and Laboratory Medicine Content Module in detail, specifying the standards used and the information defined.\n\n===6.3.1 CDA Document Content Modules===\nAll persons (including the patient) and organizations mentioned in the CDA Document Content Modules SHALL include the elements ''name'', ''addr'' and ''telecom''.\n\n====6.3.1.1 Clinical Laboratory Report Content Module 1.3.6.1.4.1.19376.1.3.3====\n<syntaxhighlight lang=\"xml\">Section unchanged, as in PaLM TF-3</syntaxhighlight>\n\n====6.3.1.2 Anatomic Pathology Structured Report Content Module 1.3.6.1.4.1.19376.1.8.1.1.1====\nThis Content Integration Profile describes a surgical pathology report as an electronic document to be published towards a document sharing resource such as an Electronic Health Record (EHR) or Personal Health Record (PHR) shared by a community of care providers, using one of the document sharing profiles defined in ITI-TF. <br/>\nSuch an electronic document contains the set of releasable results produced by an surgical pathology laboratory in fulfillment of an Order or an Order Group for a patient. The report is shared in a human-readable format. In addition, this electronic anatomic pathology report SHALL contain diagnostic conclusions in a machine-readable format, to facilitate the integration of these observations in the database of a consumer system. <br/>\nThis Document Content Module defines the base set of constraints that apply to all AP structured reports, related to any kind of lesion or diagnostic problem (cancers, benign neoplasms as well as non-neoplastic conditions) as well as for Cytopathology. <br/> \nIn other words, this is the generic template for any AP structured report.<br/> <br/>\nThis document content module is identified by templateId 1.3.6.1.4.1.19376.1.8.1.1.1. <br/>\nThe body of this Document Content Module specifies a common hierarchy of sections and entries depicted by figure 10.4.1-1 in Volume 1. The only mandatory section is the Diagnostic Conclusion Section. And the only mandatory entry is the Problem Organizer Entry below this section. <br/><br/> \n\nThe specification of this Document Content Module is built and published on Art-Decor [https://art-decor.org/art-decor/decor-project--psr- Pathology Structured Reporting], including schematron rules, code systems and value sets.\n\n{{:1.3.6.1.4.1.19376.1.8.1.1.1/dynamic}}\n\n=====6.3.1.2.1 General constraints that apply to APSR=====\n*When a section has a text element and one or more entry element, the content coded for machine-processing in the entries SHALL be completely transcribed into human-readable content in the text element. \n*Conversely the text element MAY contain pieces of information, which are not available in machine-readable format in any entry element of the section.\n*Information that is sent SHALL clearly identify distinctions between:\n\n'''None'''\n\nIt is known with complete confidence that there are none. This indicates that the sender knows that there is no relevant information of this kind that can be sent.\n\n'''None Known'''\n\nNone known at this time, but it is not known with complete confidence that none exist. \n\n'''Asked but unknown'''\n\nThe information was requested but could not be obtained. Used mainly in the context where an observation was made but the result could not be determined.\n\n'''Unknown'''\n\nThe information is not known, or is otherwise unavailable.\n\n'''Other, not specified'''\n\nThe actual value does not belong to the assigned value set and is not reported at all by the author.\n\n'''Other, specify'''\n\nThe actual value does not belong to the assigned value set and the author of the report provides this ''foreign'' value anyway. \n\n'''Not applicable'''\n\nNo proper value is applicable in this context. \n\nSections that are required to be present but have no information should use one of the above phrases where appropriate in the ''text'' element. \n\nStructural elements that are required but have no information shall provide a \u201cnullFlavor\u201d attribute coding the reason why the information is missing.\n\n{| class=\"hl7table\"\n!Situation !! nullFlavor !!HL7 Definition\n|-\n|Asked but unknown||ASKU\n||Information was sought but not found \n\n|-\n|Unknown\n||UNK||A proper value is applicable, but not known\n\n|-\n|Other, not specified\n||OTH||The actual value is not an element in the value domain of a variable. (e.g., concept not provided by required code system).\n\n|-\n|Not applicable\n||NA||No proper value is applicable in this context\n\n|-\n|Temporarily not available\n||NAV||Information is not available at this time but it is expected that it will be available later.\n|}\n\n\nThe two situations \u201cNone\u201d and \u201cNone known\u201d represent effective values, which are part of the related value sets.\n\nThe situation \u201cOther, specify\u201d can be handled in two ways in a coded data element:\n*Leaving empty the ''code'' attribute and providing the non-coded answer in the ''originalText'' attribute. \n*Providing a value coded from a different coding scheme, when the coding strength of the element is \u201cCWE\u201d (coded with extensions). The attributes ''code'', ''displayName'', ''codeSystem'' and ''codeSystemName'' then describe the foreign code.\n\nFor ancillary techniques, the situation \u201c not performed\u201d or \u201cnone performed\u201d  is represented by nullFlavor = NAV.\n\n\n=====6.3.1.2.2 Common structure for CDA APSR=====\n\nFigure 6.3.1.2.2-1 describes the high-level view of the structure of the Problem Organizer Entry, which is common to the first six CDA APSR 2.0 sections. \n\n\n[[File:6.2.1.3-1-FO_ProblemOrganizerEntry.png]]\n\n'''Figure 6.3.1.2.2-1  Structure of machine-readable content for the first 6 sections of APSR 2.0 CDA R2 Document Template'''\n\nNote 1:\tIn order to facilitate a further de-identification process of CDA AP reports for some secondary use (biosurveillance, epidemiology\u2026) the producer of an APSR SHOULD avoid populating any patient identification data (name, sex, birthdate, address \u2026) into the body of the report (neither <entry> elements nor <text> elements). The appropriate location for patient identification data is the CDA header exclusively.\n\nNote 2:\tThe AP sections are those shown on figure 10.4.1-1 of Volume 1. \n\nNote 3:\tPossible sub sections are shown on figure 10.4.1-1 of Volume 1.\n\n\nFigure 6.3.1.2.2-2 shows the common structure of the Procedure Step Content Module specified here, too. \n\n[[File:6.2.1.3-2-FO_ProcedureStep.png]]\n\n'''Figure 6.3.1.2.2-2  Structure of machine-readable content for the Procedure Step section of APSR 2.0 CDA R2 Document Template'''\n\n===6.3.2 CDA Header Content Modules===\n\n====6.3.2.1 <Specimen Collector in Header> - Header Content Module \u2013 1.3.6.1.4.1.19376.1.8.1.4.1====\n\n=====6.3.2.1.1 Definition and purpose=====\n\nThis Content Module is usable only in the CDA header. \n\nThis Content Module is used only in the situation where the specimen was not collected by the ordering physician. (See use cases in volume 1)\n\n=====6.3.2.1.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.8.1.4.1/dynamic}}\n\n====6.3.2.2 <Content Validator> - Header Content Module \u2013 1.3.6.1.4.1.19376.1.8.1.4.3====\n\n=====6.3.2.2.1 Definition and purpose=====\n\nThis Content Module is usable only in the CDA header. \n\nIt describes a pathologist having verified the content of the report, using the element authenticator. This element authenticator is used when the pathologist having verified the content of the report is distinct from the pathologist assuming the legal responsibility for this report, described in the legalAuthenticator element.\n\nThe report MAY have zero or more Content Validators.\n\n=====6.3.2.2.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.8.1.4.3/dynamic}}\n\n\n====6.3.2.3 <Participant Pertinent Insurance Information> - Header Content Module - 1.3.6.1.4.1.19376.1.3.10.2.5====\n\n=====6.3.2.3.1 Definition and purpose=====\n\nThis participant is carrying key information of the insurance status of the patient, as it may be requested for example, by cancer registries. It is used in a header only. It is not intended to provide the whole information about payment details.\n\n=====6.3.2.3.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.3.10.2.5/dynamic}}\n\n===6.3.3 CDA Section Content Modules===\n\n====6.3.3.1 <Clinical Information> - Section Content Module - 1.3.6.1.4.1.19376.1.8.1.2.1====\n\n=====6.3.3.1.1 Definition and Purpose=====\n\nThe Clinical Information section contains the information provided by the ordering physician: Clinical history, preoperative diagnosis, postoperative diagnosis, reason for anatomic pathology procedure, clinical laboratory data, specimen collection procedure including target site, performer, specimen type, specimen(s) clinical description, and tumor site in case of a cancer. The only entry for this section is the Problem Organizer Entry module.\n\n=====6.3.3.1.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.8.1.2.1/dynamic}}\n\n====6.3.3.2 <Intraoperative Observation>- Section Content Module - 1.3.6.1.4.1.19376.1.8.1.2.2====\n\n=====6.3.3.2.1 Definition and Purpose=====\n\nThe Intraoperative Observation section contains an intraoperative diagnosis for each specimen examined, the specimen identification and description, intraoperative observation procedure description (frozen section, gross examination, intraoperative cytology) and derived specimen dissected for other ancillary procedures (flow cytometry, cytogenetics, molecular studies, and electron microscopy). The only entry for this section is the Problem Organizer Entry module.\n\n=====6.3.3.2.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.8.1.2.2/dynamic}}\n\n====6.3.3.3 <Macroscopic Observation> -  Section Content Module - 1.3.6.1.4.1.19376.1.8.1.2.3====\n\n=====6.3.3.3.1 Definition and Purpose=====\n\nThe Macroscopic Observation section contains the description of the specimen(s) received or obtained by the laboratory (specimen type and state), the gross observation, links to gross images, if taken, processing information and tissue disposition (representative sampling and tissue submitted for additional studies or sent to biorepository. The only entry for this section is the Problem Organizer Entry module.\n\n=====6.3.3.3.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.8.1.2.3/dynamic}}\n\n====6.3.3.4 <Microscopic Observation> - Section Content Module - 1.3.6.1.4.1.19376.1.8.1.2.4====\n\n=====6.3.3.4.1 Definition and Purpose=====\n\nThe Microscopic Observation section contains optionally the histopathologic findings of the case and many laboratories use this section to record the results of histochemical and immunohistochemical stains. The only entry for this section is the Problem Organizer Entry module.\n\n=====6.3.3.4.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.8.1.2.4/dynamic}}\n\n====6.3.3.5 <Additional Specified Observation> - Section Content Module - 1.3.6.1.4.1.19376.1.3.10.3.1====\n\n=====6.3.3.5.1 Definition and Purpose=====\n\nThe Additional Specified Observation section includes additional pathologic finding(s) and the results of ancillary studies with non-morphological methods (e.g., flow cytometry, cytogenetics, molecular pathology, etc.) and may include diagrams and still images or virtual slides, if taken. Further CDA content section modules as subsections are allowed. The only entry for this section is the Problem Organizer Entry module.\n\n=====6.3.3.5.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.3.10.3.1/dynamic}}\n\n====6.3.3.6 <Diagnostic Conclusion> - Section Content Module - 1.3.6.1.4.1.19376.1.8.1.2.5====\n\n=====6.3.3.6.1 Definition and Purpose=====\n\nThe Diagnostic Conclusion section contains diagnoses on all specimens that are delivered to the pathology department from one operation or patient visit to a single clinician on a particular day. The diagnoses for each specimen sample or group of specimen samples are reported separately. This section may include diagrams and still images or virtual slides, if taken. In case of cancer, this section may also include a cancer checklist. The only mandatory entry for this section is the Problem Organizer Entry module, additionally the Update Organizer Entry module MAY be used.\n\n=====6.3.3.6.2 Specification and Example=====\n\n\n{{:1.3.6.1.4.1.19376.1.8.1.2.5/dynamic}}\n\n====6.3.3.7 <Procedure Steps> - Section Content Module - 1.3.6.1.4.1.19376.1.8.1.2.6====\n\n=====6.3.3.7.1 Definition and Purpose=====\n\nThe Procedure steps section contains the description of tissue sampling and dissection: representative specimens and derived specimens dissected for other ancillary procedures (flow cytometry, cytogenetics, molecular studies, electron microscopy, etc.) or biorepository. The only entry for this section is the Specimen Procedure Steps Entry module.\n\n=====6.3.3.7.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.8.1.2.6/dynamic}}\n\n===6.3.4 CDA Entry Content Modules===\n\n====6.3.4.1 Common Specification for all APSR Entry Content Modules====\n\nThe unique <entry> Content Module available in all the sections except Procedure Steps <section> of the APSR template is the Problem Organizer <entry>. \n\nThe unique <entry> Content Module available in Procedure Steps <section> of the APSR template is Specimen Procedure Step <entry>.\n\nThe Update Information Organizer <entry>  Content Module is only available in Diagnostic Conclusion <section> of the APSR template.\n\nEach <entry> Content Module carries machine-readable data related to one Problem on one specimen or on a group of specimens observed for this section.\n\nEach <entry> Content Module is repeatable below its section, so as to support the use cases where a section reports on more than one problem on one specimen or one group of specimens.\n\n====6.3.4.2 <Problem Organizer> - Entry Content Module \u2013 1.3.6.1.4.1.19376.1.8.1.3.6====\n\n=====6.3.4.2.1 Definition and purpose=====\n\nThis Content Module is usable as only <entry> within any Section module except Procedure steps <section>.\n\nThe problem organizer groups the battery of observations together with embedded images performed to investigate on a single problem identified on a specimen or on a group of specimens. If a Problem cannot be addressed specifically the Problem organizer allows also the grouping around one specimen. The problem type is coded by using a component with a generic CDA observation, not to confuse with the series of AP and other observations organized by this Organizer content module.\n\n=====6.3.4.2.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.8.1.3.6/dynamic}}\n\n====6.3.4.3 <Specimen Procedure Step> - Entry Content Module - 1.3.6.1.4.1.19376.1.3.10.4.1====\n\n=====6.3.4.3.1 Definition and purpose=====\nThe Specimen Procedure Step <entry> Content Module contains in machine-readable form all the data concerning one specimen or a group of specimens together with its container(s). It is usable within a Procedure Steps <section> Content Module only.\nThis Content Module structures the machine-readable data, which characterize the specimens and the procedures of their collection and processing (identifiers and types, status, time intervals, performers, approach site, target site, etc.). <br/>\nBy referencing the child procedure ID via an entryRelationship the entry is used in an iterative manner for each single step of specimen collection and processing, which results in derived (child) specimen. <br/>\nThe resulting specimen is the participant in the procedure according to the CDA-RIM (fig. 6.2.5.3.2-1) with the typeCode=\"PRD\", and the ParticipantRole.classCode=\"SPEC\". The specimen ID is the ParticipantRole.ID.<br/>\nAdditives to the specimen (e.g., fixatives) MAY be additional participants with the typeCode=\"CSM\" and the ParticipantRole.classCode=\"ADTV\". <br/>\nEach specimen is put in or on an appropriate container. The container is described through one or more EntryRelationship(s) to one or more Supply whose product is the container and possible container components (see this volume,  6.3.6.4).<br/>\nThe specimen reception in laboratory may be expressed through another EntryRelationship of typeCode \"COMP\", introducing the \"specimen received\" Act. <br/>\nIn case the procedure step produces a child specimen, the parent specimen is the specimen on which the procedure is performed. Thus the parent specimen is represented by a Specimen participation to the procedure. In this case, Specimen.SpecimenRole.Id is the id of the parent specimen. These parent specimens might be multiple, for instance in the case of TMA; therefore, cardinalities of Specimen are [0..*]<br/>\nSpecimen and their containers carry IDs as well as further attributes, which are defined in the HL7 Specimen DAM <ref>HL7 DAM Specimen Release 1 http://www.hl7.org/implement/standards/product_brief.cfm?product_id=394</ref>. \n\n\n[[File:6.2.6.4.1-1_container_6.jpg|700px]]\n\n'''Figure 6.3.4.3.1-1 CDA-R-MIM of the Specimen Procedure Steps <entry>'''\n\nAccording to the CDA RIM in the Content Module further supporting Content Modules for Participant, and Playing Entity are needed, which have the OIDs 1.3.6.1.4.1.19376.1.3.10.9.44,  1.3.6.1.4.1.19376.1.3.10.9.21). \n\nThe Code systems and Value sets MAY be organized organ-specific.\n\n=====6.3.4.3.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.3.10.4.1/dynamic}}\n\n'''Supportive template CDA Participant (Body) Procedure Steps APSR2 - 1.3.6.1.4.1.19376.1.3.10.9.44'''\n{{:1.3.6.1.4.1.19376.1.3.10.9.44/dynamic}}\n\n'''Supportive template CDA PlayingEntitySpecimen APSR2 - 1.3.6.1.4.1.19376.1.3.10.9.21'''\n{{:1.3.6.1.4.1.19376.1.3.10.9.21/dynamic}}\n\n====6.3.4.4 <Update Information Organizer> - Entry Content Module - 1.3.6.1.4.1.19376.1.3.10.4.5====\n\n=====6.3.4.4.1 Definition and purpose=====\nThis content module is usable in the Diagnostic Conclusion <section> only.\n\nIt is used in the situation where a new version of a report is replacing the previous one, as to indicate what sections and/or entries have been changed in comparison with the immediate previous version of the report.\n\n=====6.3.4.4.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.3.10.4.5/dynamic}}\n\n===6.3.5 CDA Child Element Content Modules===\n\nThis section specifies the Content Modules designed for child elements. A child element is a child of the CDA Section, or of the CDA Header, or an element nested at various depths below an CDA Entry, or an element appearing at some combination of these locations.\n\n====6.3.5.1 <Author> - Child Element Content Module \u2013 1.3.6.1.4.1.19376.1.8.1.4.2====\n\n=====6.3.5.1.1 Definition and purpose=====\n\nThis Content Module is usable in the CDA header, in a <section> and at various depths of an <entry>. \n\nIt describes an author having contributed to the document wholly or to a portion of it (e.g., a section, an observation, a group of observations).\n\nA given document or any delimited portion of it may have more than one author.\n\nAn author MAY be a person or a device (manufactured device or software system). In both cases the scoping organization MAY be described.\n\n=====6.3.5.1.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.8.1.4.2/dynamic}}\n\n====6.3.5.2 <Informant> - Child Element Content Module \u2013 1.3.6.1.4.1.19376.1.8.1.4.6====\n\n=====6.3.5.2.1 Definition and purpose=====\n\nThis Content Module is usable in the CDA header, in a <section> and within an <entry>. \n\nIt describes a person having provided some piece of relevant information for the document.\n\nA <ClinicalDocument> or a <section> or any kind of act below an <entry>, MAY have zero or more informant.\n\n=====6.3.5.2.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.8.1.4.6/dynamic}}\n\n====6.3.5.3 <Specimen Container in Specimen Procedure Step> - Child Element Content Module- 1.3.6.1.4.1.19376.1.3.10.9.22====\n\n=====6.3.5.3.1 Definition and purpose=====\n\nThis Supporting Content Module is usable in the Specimen Procedure Steps <entry> (see 6.2.6.4) and is repeatable within one procedure step for describing container components, too. It describes the properties of containers, in or on which the specimens are processed. The relations between container and specimen are described in the HL7 Specimen DAM.\n\n[http://www.hl7.org/implement/standards/product_brief.cfm?product_id=331 HL7 DAM Specimen Release 1].\n\nFor Anatomic Pathology the CDA Content Modules \"Material\" and \"ManufacturedMaterial\" were specialized to Supporting Templates CDA ManufacturedProduct APSR2 (1.3.6.1.4.1.19376.1.3.10.9.24) and CDA Material Container APSR2 (1.3.6.1.4.1.19376.1.3.10.9.23).\n\n=====6.3.5.3.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.22/dynamic}}\n\n'''Supportive Template CDA ManufacturedProduct APSR2 - 1.3.6.1.4.1.19376.1.3.10.9.24'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.24/dynamic}}\n\n'''Supportive Template CDA Material Container APSR2 - 1.3.6.1.4.1.19376.1.3.10.9.23'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.23/dynamic}}\n\n====6.3.5.4 <Additional participant in an entry> - Child Element Content Module- 1.3.6.1.4.1.19376.1.8.1.4.7====\n\n=====6.3.5.4.1 Definition and purpose=====\n\nThis Content Module is usable only within an <entry> element. \n\nAdditional participants MAY take part in any organizer as well as in any observation of an APSR. These participants MAY be any of these 4:\n*Validator: This is the same participation as Content Validator in the header of the report: a pathologist having verified the content (of this particular subset of results).  \n*Device: A device used to produce this particular subset of results.\n*Responsible: The director of a laboratory (described in a performer element at the same level) who produced this particular subset of results.\n*Transcriptionist: This is the same participation as dataEnterer in the header of the report: a staff who entered, possibly from dictation, this particular subset of results.\n\n=====6.3.5.4.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.8.1.4.7/dynamic}}\n\n====6.3.5.5 <Anatomic Pathology Observation> - Child Element Content Module \u2013 1.3.6.1.4.1.19376.1.8.1.4.9====\n\n=====6.3.5.5.1 Definition and purpose=====\n\nThis Content Module is usable within a Problem Organizer.\n\nThe \u201cAP Observation\u201d generic template is usable for all AP observations, including those on findings from ancillary\ntechniques.\n\nAn AP Observation has a status and an effective time, MAY describe various participants (persons, devices, organizations), MAY have a number of additional properties (method,\ninterpretation, text), and MAY contain embedded images, comments, and sub-observations, which are also AP observations. For coding an AP observations LOINC codes SHOULD be used. For measurement results the UCUM system SHOULD be used.\n\nEach kind of AP observation SHALL have one or more content modules \"X specimen identified\"\n\n=====6.3.5.5.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.8.1.4.9/dynamic}}\n\n====6.3.5.6 <Embedded Image> - Child Element Content Module \u2013 1.3.6.1.4.1.19376.1.8.1.4.10====\n\n=====6.3.5.6.1 Definition and purpose=====\n\nThis Content Module is usable within an <entry> element, in relationship with a\ndisplay anchor carried in the ''referencedObject'' attribute of a <renderMultimedia>\nelement in the <text> element of the <section> holding this <entry>.\n\n\nThe <observationMedia> element carries an image, embedded in B64. This element may be standalone, or encapsulated within a <regionOfInterest> element which defines an overlay\nshape to focus on a part of the image. \n\nThis <observationMedia> element embeds the image binary data, encoded in B64.\n\n=====6.3.5.6.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.8.1.4.10/dynamic}}\n\n====6.3.5.7 <X Specimen Identified> - Child Element Content Module -  1.3.6.1.4.1.19376.1.3.10.9.1 ====\n\n=====6.3.5.7.1 Definition and purpose=====\n\nThis Specimen Identification <entry> provides the machine-readable links between any type of procedure or observation or embedded image or containers to the specimen, on that this procedure is performed (parent specimen), or from which this observation or image is obtained.\nIt is required when more than one specimen is documented at this level.\nIt is only used in PaLM templates for Problem Organizer, Specimen Procedure Steps, Observations, Embedded images, and Containers in Specimen Procedure Steps.\n\n=====6.3.5.7.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.1/dynamic}}\n\n====6.3.5.8 <UICC/AJCC TNM Staging and Grading> - Child Element Content Module - 1.3.6.1.4.1.19376.1.3.10.4.2====\n\n=====6.3.5.8.1 Definition and purpose=====\nThe UICC/AJCC TNM <entry> Content Modul is a template for a complex structured observation usable in tumor pathology contexts. It contains in machine-readable form all the information concerning a TNM formula for a problem investigated. It is a constraint version of an AP Generic observation <entry> Content Module. It is usable within a Problem Organizer <entry> Content Module only.\n\nThis Content Module structures the machine-readable data, which characterize the staging and grading of a malignant tumor according the UICC/AJCC regulations for the TNM system. A series of supporting templates is used for all the detailed descriptions of the elements of the TNM system. Value sets are mentioned for the most recent UICC/AJCC 8th edition and its immediate predecessor 7th edition only.\n\n[[File:6.2.6.12.1-1mod.jpg]]\n\n'''Figure 6.3.5.8.1-1 CDA-R-MIM of the UICC/AJCC TNM <entry>'''\n\n=====6.3.5.8.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.3.10.4.2/dynamic}}\n\n'''Supportive Template TNM T-Observation - 1.3.6.1.4.1.19376.1.3.10.9.25'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.25/dynamic}}\n\n'''Supportive Template TNM N-Observation - 1.3.6.1.4.1.19376.1.3.10.9.26'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.26/dynamic}} \n\n'''Supportive Template TNM Number of Nodes - 1.3.6.1.4.1.19376.1.3.10.9.37'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.37/dynamic}}\n\n'''Supportive Template TNM M-Observation - 1.3.6.1.4.1.19376.1.3.10.9.27'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.27/dynamic}}\n\n'''Supportive Template TNM Grading - 1.3.6.1.4.1.19376.1.3.10.9.28'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.28/dynamic}}\n\n'''Supportive Template TNM R-Status - 1.3.6.1.4.1.19376.1.3.10.9.29'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.29/dynamic}}\n\n'''Supportive Template TNM a - 1.3.6.1.4.1.19376.1.3.10.9.30'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.30/dynamic}}\n\n'''Supportive Template TNM r - 1.3.6.1.4.1.19376.1.3.10.9.31'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.31/dynamic}}\n\n'''Supportive Template TNM y - 1.3.6.1.4.1.19376.1.3.10.9.32'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.32/dynamic}}\n\n'''Supportive Template TNM Serum Tumor Markers - 1.3.6.1.4.1.19376.1.3.10.9.33'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.33/dynamic}}\n\n'''Supportive Template TNM Lymphatic Invasion - 1.3.6.1.4.1.19376.1.3.10.9.34'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.34/dynamic}}\n\n'''Supportive Template TNM Venous Invasion - 1.3.6.1.4.1.19376.1.3.10.9.35'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.35/dynamic}}\n\n'''Supportive Template TNM Perineurial Invasion - 1.3.6.1.4.1.19376.1.3.10.9.36'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.36/dynamic}}\n\n====6.3.5.9 <ICD-O-3 Typing and Grading> - Child Element Content Module - 1.3.6.1.4.1.19376.1.3.10.4.3====\n\n=====6.3.5.9.1 Definition and purpose=====\nThe ICD-O-3 Typing and Grading<entry> Content Modul is a template for a complex observation usable in tumor pathology contexts. It contains in machine-readable form all the information concerning ICD-O-3 Typing and Grading for a problem investigated. It is a constraint version of an AP Generic observation <entry> Content Module. It is usable within a Problem Organizer <entry> Content Module only.\n\nThis Content Module structures the machine-readable data, which characterize the typing and grading of a tumor or a systemic malignancy according the WHO regulations for the ICD-O-3 system. The supporting template ICD-O-Behavior is to use for behavior classification (5th digit in morphology and behavior code list). The supporting template ICD-O-Differentiation is used for a more detailed descriptions (6th digit) of those elements of the ICD-O-3 system. \n\nMorphology and topography axes of ICD-O-3 are not combined to a singular, common code, but used simultaneously. A complete ICD-O-3 coding consists always of topography ''and'' morphology and behavior codes, displayed together in one line in the human readable section. Therefore, the topography axis of ICD-O-3 SHOULD be coded in a supportive template ICD-O-Topography, specialized from a generic observation, within the same Problem Organizer <entry> Content Module.\n\n[[File:6.2.6.13.1-1_neu4.jpg|600px|]]\n\n'''Figure 6.3.5.9.1-1 CDA-R-MIM of the ICD-O-3 <entry>'''\n\n=====6.3.5.9.2 Specification and Example=====\n\n{{:1.3.6.1.4.1.19376.1.3.10.4.3/dynamic}}\n\n\n'''Supportive Template ICD-O-Behavior - 1.3.6.1.4.1.19376.1.3.10.9.38'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.38/dynamic}}\n\n\n'''Supportive Template ICD-O-Differentiation - 1.3.6.1.4.1.19376.1.3.10.9.39'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.39/dynamic}}\n\n\n'''Supportive Template ICD-O-Topography - 1.3.6.1.4.1.19376.1.3.10.9.41'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.41/dynamic}}\n\n====6.3.5.10 <Assessment Scales for Scoring systems> - Child Element Content Module - 1.3.6.1.4.1.19376.1.3.10.4.4====\n\n=====6.3.5.10.1 Definition and purpose=====\nThe Assessment Scales <entry> Content Modul is a template for a complex observation, especially usable in tumor pathology contexts, within a Problem organizer or as sub-observation for grading observations. It contains in machine-readable form all the information concerning (semi)quantitative scoring systems often used for describing a tumor grading for a problem investigated. It is a constraint version of an AP Generic observation <entry> Content Module. It is usable within the ICD-O-3 Typing and Grading <entry> or within a Problem Organizer <entry> Content Module.\n\nThis Content Module structures the machine-readable data, which characterize the grading components of a tumor or a systemic disease according specific regulations. \n\n[[File:6.2.6.14.1-1_neu.jpg]]\n\n'''Figure 6.3.5.10.1-1 CDA-R-MIM of an Assessment Scales <entry>'''\n\n=====6.3.5.10.2 Specification and Example=====\n\n'''Assessment Scales Observation for Scoring Systems APSR2 - 1.3.6.1.4.1.19376.1.3.10.4.4'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.4.4/dynamic}}\n\n'''Supportive Template Assessment Scoring System - 1.3.6.1.4.1.19376.1.3.10.9.42'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.42/dynamic}} \n\n'''Supportive Template Assessment Scoring Item - 1.3.6.1.4.1.19376.1.3.10.9.43'''\n\n{{:1.3.6.1.4.1.19376.1.3.10.9.43/dynamic}}\n\n===6.3.6 External Content Modules referenced by APSR 2.0 ===\n\n=====6.3.6.1 Definition and purpose=====\nFor some of the templates described above supportive templates are used, defined and specified by XD-LAB or PCC. They are listed in table 5.5-1 (see above), and shown here for better understanding only.\n\n=====6.3.6.2 Specifications and Examples=====\n\n'''<IHE Reason for Referral Sub-Section> - Section Content Module - 1.3.6.1.4.1.19376.1.5.3.1.3.1'''\n{{:1.3.6.1.4.1.19376.1.5.3.1.3.1/dynamic}}\n\n'''<History of Present Illness Sub-Section> - Section Content Module - 1.3.6.1.4.1.19376.1.5.3.1.3.4'''\n{{:1.3.6.1.4.1.19376.1.5.3.1.3.4/static-2013-01-31T000000}}\n\n'''<CDA Active Problems Sub-Section> - Section Content Module - 1.3.6.1.4.1.19376.1.5.3.1.3.6'''\n{{:1.3.6.1.4.1.19376.1.5.3.1.3.6/dynamic}}\n\n'''<Specimen Received> - Child Element Content Module - 1.3.6.1.4.1.19376.1.3.1.3'''\n{{:1.3.6.1.4.1.19376.1.3.1.3/dynamic}}\n\n'''<Laboratory Observation> - Child Element Content Module - 1.3.6.1.4.1.19376.1.3.1.6'''\n{{:1.3.6.1.4.1.19376.1.3.1.6/dynamic}}\n\n'''<Human Patient (recordTarget)> - Child Element Content Module - 1.3.6.1.4.1.19376.1.3.3.1.1'''\n{{:1.3.6.1.4.1.19376.1.3.3.1.1/dynamic}}\n\n'''<Information Recipient> - Child Element Content Module - 1.3.6.1.4.1.19376.1.3.3.1.4'''\n{{:1.3.6.1.4.1.19376.1.3.3.1.4/dynamic}}\n\n'''<Ordering Provider> - Child Element Content Module - 1.3.6.1.4.1.19376.1.3.3.1.6'''\n{{:1.3.6.1.4.1.19376.1.3.3.1.6/dynamic}}\n\n'''<Laboratory Performer>  - Child Element Content Module - 1.3.6.1.4.1.19376.1.3.3.1.7'''\n{{:1.3.6.1.4.1.19376.1.3.3.1.7/dynamic}}\n\n'''<Legal Authenticator> - Child Element Content Module - 1.3.6.1.4.1.19376.1.3.10.2.4'''\n{{:1.3.6.1.4.1.19376.1.3.10.2.4/dynamic}}\n\n'''<Comment> - Child Element Content Module - 1.3.6.1.4.1.19376.1.5.3.1.4.2'''\n{{:1.3.6.1.4.1.19376.1.5.3.1.4.2/dynamic}}\n\n==6.4 Section not applicable==\n\n==6.5 <APSR> Value Sets==\n\nThere are both extensional and intensional value sets specifically used for APSR.\n\n===6.5.1 <Generic AP Observation Codes>  <1.3.6.1.4.1.19376.1.3.11.11>===\n\n{{:1.3.6.1.4.1.19376.1.3.11.11/dynamic}}\n\n===6.5.2 <Problem type>  <1.3.6.1.4.1.19376.1.3.11.7>===\n\n{{:1.3.6.1.4.1.19376.1.3.11.7/dynamic}}\n\n===6.5.3 <Container Entity Class Type>  <1.3.6.1.4.1.19376.1.3.11.8>===\n\n{{:1.3.6.1.4.1.19376.1.3.11.8/dynamic}}\n\n===6.5.4 <Procedure (target) site>  <1.3.6.1.4.1.19376.1.3.11.9>===\n\n{{:1.3.6.1.4.1.19376.1.3.11.9/dynamic}}\n\n===6.5.5 <Specimen collection and processing> <1.3.6.1.4.1.19376.1.3.11.10>===\n\n{{:1.3.6.1.4.1.19376.1.3.11.10/dynamic}} \n\n===6.5.6 <UICC/AJCC stage> <1.3.6.1.4.1.19376.1.3.11.46>===\n\n{{:1.3.6.1.4.1.19376.1.3.11.46/dynamic}}\n\n===6.5.7 <UICC/AJCC T category>  <1.3.6.1.4.1.19376.1.3.11.43>===\n\n{{:1.3.6.1.4.1.19376.1.3.11.43/dynamic}}\n\n===6.5.8 <UICC/AJCC T category (SCT)> <1.3.6.1.4.1.19376.1.3.11.12>===\n\n{{:1.3.6.1.4.1.19376.1.3.11.12/dynamic}}\n\n===6.5.9 <UICC/AJCC N category> <1.3.6.1.4.1.19376.1.3.11.44>===\n\n{{:1.3.6.1.4.1.19376.1.3.11.44/dynamic}}\n\n===6.5.10 <UICC/AJCC N category (SCT)> <1.3.6.1.4.1.19376.1.3.11.13>===\n\n{{:1.3.6.1.4.1.19376.1.3.11.13/dynamic}}\n\n===6.5.11 <UICC/AJCC M category> <1.3.6.1.4.1.19376.1.3.11.45>===\n\n{{:1.3.6.1.4.1.19376.1.3.11.45/dynamic}}\n\n===6.5.12 <UICC/AJCC M category (SCT)>  <1.3.6.1.4.1.19376.1.3.11.14>===\n\n{{:1.3.6.1.4.1.19376.1.3.11.14/dynamic}}\n\n===6.5.13 <UICC/AJCC C-Factor>  <1.3.6.1.4.1.19376.1.3.11.19>===\n\nThis value set has values from TNM 7th edition only. There is no C-Factor in the 8th edition.\n{{:1.3.6.1.4.1.19376.1.3.11.19/dynamic}}\n\n===6.5.14 <UICC/AJCC C-Factor (SCT)>  <1.3.6.1.4.1.19376.1.3.11.20>===\n\n{{:1.3.6.1.4.1.19376.1.3.11.20/dynamic}}\n\n===6.5.15 <UICC/AJCC Residual tumor (R) classification> <1.3.6.1.4.1.19376.1.3.11.21>===\n\n{{:1.3.6.1.4.1.19376.1.3.11.21/dynamic}}\n\n===6.5.16 <UICC/AJCC clinical/pathological> <1.3.6.1.4.1.19376.1.3.11.22>===\n\nThis value set has values from TNM 8th edition. There is no difference to 7th edition.\n{{:1.3.6.1.4.1.19376.1.3.11.22/dynamic}}\n\n===6.5.17 <UICC/AJCC Venous Invasion> <1.3.6.1.4.1.19376.1.3.11.23>===\n\nThis value set has values from TNM 8th edition. There is no difference to 7th edition.\n{{:1.3.6.1.4.1.19376.1.3.11.23/dynamic}}\n\n===6.5.18 <UICC/AJCC Lymphatic Invasion> <1.3.6.1.4.1.19376.1.3.11.24>===\n\nThis value set has values from TNM 8th edition. There is no difference to 7th edition.\n{{:1.3.6.1.4.1.19376.1.3.11.24/dynamic}}\n\n===6.5.19 <UICC/AJCC Perineurial Invasion> <1.3.6.1.4.1.19376.1.3.11.25>===\n\nThis value set has values from TNM 8th edition. There is no difference to 7th edition.\n{{:1.3.6.1.4.1.19376.1.3.11.25/dynamic}}\n\n===6.5.20 <UICC/AJCC Mucosa> <1.3.6.1.4.1.19376.1.3.11.26>===\n\n{{:1.3.6.1.4.1.19376.1.3.11.26/dynamic}}\n\n===6.5.21 <UICC/AJCC Submucosa> <1.3.6.1.4.1.19376.1.3.11.27>===\n\n{{:1.3.6.1.4.1.19376.1.3.11.27/dynamic}}\n\n===6.5.22 <UICC/AJCC Localization of distant metastases> <1.3.6.1.4.1.19376.1.3.11.28>===\n\nThis value set has values from TNM 8th edition. There is no difference to 7th edition.\n{{:1.3.6.1.4.1.19376.1.3.11.28/dynamic}}\n\n===6.5.23 <UICC/AJCC Grade 3 tiered> <1.3.6.1.4.1.19376.1.3.11.29>===\n\nThis value set has values from TNM 8th edition. There is no difference to 7th edition.\n{{:1.3.6.1.4.1.19376.1.3.11.29/dynamic}}\n\n===6.5.24 <UICC/AJCC Grade 2 tiered> <1.3.6.1.4.1.19376.1.3.11.30>===\n\nThis value set has values from TNM 8th edition. There is no difference to 7th edition.\n{{:1.3.6.1.4.1.19376.1.3.11.30/dynamic}}\n\n===6.5.25 UICC/AJCC Grade 4 tiered> <1.3.6.1.4.1.19376.1.3.11.31>===\n\nThis value set has values from TNM 8th edition. There is no difference to 7th edition.\n{{:1.3.6.1.4.1.19376.1.3.11.31/dynamic}}\n\n===6.5.26 <UICC/AJCC Tumor Serum Markers> <1.3.6.1.4.1.19376.1.3.11.32>===\n\nThis value set has values from TNM 8th edition. There is no difference to 7th edition.\n{{:1.3.6.1.4.1.19376.1.3.11.32/dynamic}}\n\n===6.5.27 <ICD-O-3 Morphology and Behavior> <1.3.6.1.4.1.19376.1.3.11.33>===\n\n{{:1.3.6.1.4.1.19376.1.3.11.33/dynamic}}\n\n===6.5.28 <ICD-O-3 Behavior> <1.3.6.1.4.1.19376.1.3.11.34>===\n\n{{:1.3.6.1.4.1.19376.1.3.11.34/dynamic}}\n\n===6.5.29 <ICD-O-3 Differentiation> <1.3.6.1.4.1.19376.1.3.11.35>===\n\n{{:1.3.6.1.4.1.19376.1.3.11.35/dynamic}}\n\n===6.5.30 <ICD-O-3 Topography> <1.3.6.1.4.1.19376.1.3.11.36>===\n\n{{:1.3.6.1.4.1.19376.1.3.11.36/dynamic}}\n\n===6.5.31 <UICC/AJCC Multiplicity> <1.3.6.1.4.1.19376.1.3.11.37>===\n\nThis value set has values from TNM 8th edition. There is no difference to 7th edition.\n{{:1.3.6.1.4.1.19376.1.3.11.37/dynamic}}\n\n===6.5.32 <UICC/AJCC Isolated Tumor Cells> <1.3.6.1.4.1.19376.1.3.11.38>===\n\nThis value set has values from TNM 8th edition. There is no difference to 7th edition.\n{{:1.3.6.1.4.1.19376.1.3.11.38/dynamic}}\n\n===6.5.33 <UICC/AJCC Recurrence> <1.3.6.1.4.1.19376.1.3.11.39>===\n\nThis value set has values from TNM 8th edition. There is no difference to 7th edition.\n{{:1.3.6.1.4.1.19376.1.3.11.39/dynamic}}\n\n===6.5.34 <UICC/AJCC Posttherapeutic> <1.3.6.1.4.1.19376.1.3.11.40>===\n\nThis value set has values from TNM 8th edition. There is no difference to 7th edition.\n{{:1.3.6.1.4.1.19376.1.3.11.40/dynamic}}\n\n===6.5.35 <UICC/AJCC Autopsy> <1.3.6.1.4.1.19376.1.3.11.41>===\n\nThis value set has values from TNM 8th edition. There is no difference to 7th edition.\n{{:1.3.6.1.4.1.19376.1.3.11.41/dynamic}}\n\n===6.5.36 <Clinical Significance> <1.3.6.1.4.1.19376.1.3.11.47>===\n{{:1.3.6.1.4.1.19376.1.3.11.47/dynamic}}\n\n</div>"
                    }
                ]
            }
        }
    }
}