{"text_format":"1","workbook":"xlsx","n_sheets":11,"sheets":["Cover","Background","Intro","TSR","TC - Traceability","FS-Doc","FS-Narr","FS-Types","FS-Auth","References","Change log"],"not_rendered":{"charts":0,"images":6,"macros":1,"external_links":5,"defined_names":39,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"Cover","index":0,"n_rows":47,"n_cols":4,"rows_kept":47,"cut":false,"hidden":false,"merged":[[40,1,40,3],[42,1,42,3],[43,1,43,3],[44,1,44,3],[46,1,46,3],[32,1,32,3],[33,1,33,3],[36,1,36,3],[37,1,37,3],[39,1,39,3],[29,1,29,3],[30,1,30,3],[3,1,3,4],[15,3,15,4],[27,1,27,3],[28,1,28,3],[16,3,16,4]]}
[null," "]
[]
[]
[null,"Authoring Systems"]
[null,"Conformance Test Specification"]
[]
[null,"Version 1.2"]
[null,"2020-03-31"]
[]
[null,"Approved for external use"]
[null,"Document ID: DH-3153:2020"]
[null,"Document owner: Director, Conformance and Assurance"]
[]
[null,"Product version history"]
[null,"Version","Date","Comments"]
[null,1,"Jun-17","First Release"]
[null,1.1000000000000001,"2017-12-21","Approved for release."]
[null,1.2,"2020-03-31","Release to align with Common Conformance Profile v1.7"]
[null,1.2,"2025-05-09","The spreadsheet presentation has been enhanced to align with current branding guidelines, however the content has not been changed."]
[]
[]
[null,"Transition of terms"]
[null,"Historical term","Current term"]
[null," National eHealth Transition Authority (NEHTA)"," The Australian Digital Health Agency (ADHA)"]
[null," Personally controlled electronic health record (PCEHR)","My Health Record (MHR)"]
[]
[]
[null,"Acknowledgements "]
[null,"The Australian Digital Health Agency is jointly funded by the Australian Government and all state and territory governments."]
[null,"IHTSDO (SNOMED CT)"]
[null,"This material includes SNOMED Clinical TermsTM (SNOMED CT®) which is used by permission of the International Health Terminology Standards Development Organisation (IHTSDO). All rights reserved. SNOMED CT® was originally created by The College of American Pathologists. “SNOMED” and “SNOMED CT” are registered trademarks of the IHTSDO."]
[]
[null,"HL7 International"]
[null,"This document includes excerpts of HL7TM International standards and other HL7 International material. HL7 International is the publisher and holder of copyright in the excerpts. The publication, reproduction and use of such excerpts is governed by the HL7 IP Policy (http://www.hl7.org/legal/ippolicy.cfm) and the HL7 International License Agreement. HL7 and CDA are trademarks of Health Level Seven International and are registered with the United States Patent and Trademark Office."]
[]
[]
[null,"Disclaimer"]
[null,"The Australian Digital Health Agency (“the Agency”) makes the information and other material (“Information”) in this document available in good faith but without any representation or warranty as to its accuracy or completeness. The Agency cannot accept any responsibility for the consequences of any use of the Information. As the Information is of a general nature only, it is up to any person using or relying on the Information to ensure that it is accurate, complete and suitable for the circumstances of its use."]
[]
[null,"Document control"]
[null,"This document is maintained in electronic form and is uncontrolled in printed form. It is the responsibility of the user to verify that this copy is the latest revision."]
[]
[null,"Copyright © 2025 Australian Digital Health Agency"]
[null,"This document contains information which is protected by copyright. All Rights Reserved. No part of this work may be reproduced or used in any form or by any means – graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systems – without the permission of the Australian Digital Health Agency. All copies of this document must include the copyright and other information contained on this page."]
[]
[]
[null,"Australian Digital Health Agency ABN 84 425 496 912, Level 25, 175 Liverpool Street, Sydney, NSW 2000\nTelephone 1300 901 001 or email help@digitalhealth.gov.au\nwww.digitalhealth.gov.au"]

{"sheet":"Background","index":1,"n_rows":80,"n_cols":5,"rows_kept":80,"cut":false,"hidden":false,"merged":[[27,1,27,2],[28,1,28,4],[3,4,5,4],[17,1,17,2],[21,1,21,2],[22,1,22,2],[23,1,23,2]]}
[]
[null,"Table of contents",null,"Document information"]
[1,"Purpose",null,"Owner:","Director, Conformance and Assurance"]
[2,"Guidance",null,"Contact for enquiries:","ADHA Help Centre\nt:  1300 901 001\ne:  help@digitialhealth.gov.au"]
[3,"Target audience"]
[4,"Authoring system requirements"]
[]
[]
[]
[1,"Purpose"]
[null,"The purpose of the Conformance Test Specification for Authoring Systems is to determine that:"]
[null,"a.      The authoring system creates clinical documents that conform to the requirements for all types of documents;"]
[null,"b.      The content of the clinical documents is an accurate reflection of the data entered into the authoring system; and"]
[null,"c.      The authoring system conforms to end-system behaviour requirements."]
[null,"Return to top"]
[]
[2,"Guidance"]
[null,"The development of the Conformance Test Specification for Authoring Systems was guided by a review of conformance errors made by software development organisations from 2012 to 2015 and found by NEHTA during conformance assessment.  The analysis was used to determine where test cases could be improved and clarified, and where coverage of the requirements could be improved. \n\nThis CTS is structured to provide a requirement-based testing resource to take advantage of scripted testing practices that are repeatable, have explicit trace back to requirements, and are reusable. This is to ensure that the conformance requirements of the test item have been addressed during testing and to determine whether the test item meets those conformance requirements. Importantly, an experience-based testing practice has been leveraged using metrics from previous conformance assessments to target explicit test cases against known defect types.\nThe worksheets in this CTS are structured as feature sets of conformance requirements identified for a specific purpose. For example: FS-Doc, which is a collection of test cases to assess the conformance of a clinical document; and FS-Auth, which is a collection of test cases to assess the conformance of a clinical document authoring system.\nLIMITATIONS: This current conformance test specification version excludes test scenarios. This is due to constraints of scope and time in the development and review processes. Scenario testing is a specification-based test technique that is planned to be included in future published versions as it is seen as a useful and logical next step in providing purposeful and usable test material."]
[null,"Return to top"]
[]
[3,"Target audience"]
[null,"There are two different audiences for the Conformance Test Specification for Authoring Systems: "]
[null,"a.      Developers and testers of healthcare software that create clinical documents; and "]
[null,"b.      Testers that do not have healthcare software but have a set of clinical documents created by other software systems. "]
[null,"Return to top"]
[]
[4,"Authoring system requirements"]
[null,"For each type of clinical document, the source of the requirements is the conformance profile for that type of document, in addition to the requirements in the technical specifications referenced by the conformance profile, etc. That is, the technical specifications exist in a hierarchy with the document-specific conformance profile (i.e. the conformance profile for a specific type of document) at the top of the hierarchy. When declaring conformance, a developer declares conformance to the document-specific conformance profile. Specifications at one level of the hierarchy may override specifications at a lower level of the hierarchy when there is a specific need to constrain a more general requirement. The following diagram provides an illustration of the hierarchy with blue shading used for specifications published by NEHTA and yellow shading used for specifications published by other organisations. Green shading indicates a specification or registry for a namespace relevant for clinical documents. Note that this is provided for illustrative purposes only, and does not show a complete list of specifications and registries.\n\n"]
[]
[null,"Return to top"]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[null,"Pass"]
[null,"Fail"]
[null,"N/A"]
[null,"TBD"]

{"sheet":"Intro","index":2,"n_rows":182,"n_cols":5,"rows_kept":182,"cut":false,"hidden":false,"merged":[[88,1,88,2],[37,1,37,2],[59,1,59,2],[72,1,72,2],[2,1,2,2],[11,1,11,2],[13,1,13,2],[14,1,14,2],[35,1,35,2],[36,1,36,2]]}
[null,null,null,"Document information"]
[null,"Introduction",null,"Owner:","Director, Conformance and Assurance"]
[null,"The information in this section will:\n1. help you determine what test material you need to apply - this will be based on the type of \"user\" you are.\n2. give you an overview of the individual worksheets and their structure (i.e. what the columns mean and how to record the Test Results; Pass, Fail, etc.).\n3. give instructions on saving test output and evidence for audit.   \n\nThis conformance test specification uses software testing concepts and terminology defined in these standards:\nISO/IEC/IEEE 29119-1 Software and systems engineering – Software testing – Part 1: Concepts and definitions\nISO/IEC/IEEE 29119-3 Software and systems engineering – Software testing – Part 3: Test documentation\n",null,"Contact for enquiries:","ADHA Help Centre\nt:  1300 901 001\ne:  help@digitalhealth.gov.au"]
[]
[null,"Table of contents"]
[1,"What test material do I need?"]
[2,"Worksheet Names"]
[3,"Worksheet Structure"]
[4,"Acronyms"]
[]
[1,"What test material do I need?"]
[null,"The type of user you are will determine which tests you need to apply.  This section defines the two possible target audiences of this test material, and gives instructions on which test cases need to be applied. "]
[null,"Table 1: What test material do I need?"]
[null,"USER 1:  I want to test my Authoring System and the clinical documents it creates."]
[null,"In this scenario, you have developed an Authoring System that creates clinical documents and you want to test its conformance to digital health requirements."]
[null,"Tests to apply regardless of the clinical document type(s) being authored:"]
[null,null,"From the Authoring Systems Conformance Test Specification:"]
[null,null,"Feature set: FS-Doc"]
[null,null,"Feature set: FS-Narr"]
[null,null,"Feature set: FS-Types"]
[null,null,"Feature set: FS-Auth"]
[]
[null,"You also need to apply additional tests  for the specific type of clinical document being authored, for example: "]
[null,null,"eHealth Diagnostic Imaging Report"]
[null,null,"eHealth Pathology Report"]
[null,null,"Discharge Summary"]
[null,null,"Shared Health Summary"]
[null,null,"CDA Packaging"]
[null,null,"Event Summary"]
[null,null,"eReferral"]
[null,null,"Specialist Letter"]
[null,null,"eHealth Prescription Record"]
[null,null,"eHealth Dispense Record"]
[null,"These are available in a conformance test specification for that type of document."]
[]
[null,"USER 2:  I want to test clinical documents created by another Authoring System."]
[null,"In this scenario, you have a clinical document - but no knowledge of the Authoring System which produced it - and you want to test its conformance to digital health requirements.  "]
[null,"Tests to apply regardless of the clinical document type(s):"]
[null,null,"From the Authoring Systems Conformance Test Specification:"]
[null,null,"Feature set: FS-Doc"]
[null,null,"Feature set: FS-Narr"]
[null,null,"Feature set: FS-Types"]
[]
[null,"You also need to apply additional tests for the specific type of clinical document, for example:"]
[null,null,"Conformance Test Specification for CDA Packaging"]
[null,null,"Diagnostic Imaging Report"]
[null,null,"Pathology Report"]
[null,null,"Discharge Summary"]
[null,null,"Shared Health Summary"]
[null,null,"Event Summary"]
[null,null,"eReferral"]
[null,null,"Specialist Letter"]
[null,null,"Prescription Record"]
[null,null,"Dispense Record"]
[null,"These are available in a conformance test specification for that type of document."]
[null,"Return to top"]
[]
[]
[2,"Worksheet Names"]
[null,"Table 2 describes the abbreviated name and purpose of each worksheet. "]
[null,"Table 2: Worksheet Names","`"]
[null,"WORKSHEET NAME","PURPOSE"]
[null,"TSR","Full name: Test Summary Report\nObjective: This worksheet has 2 parts:\nPart 1 is the area where you record details about the developer organisation and the software being tested.\nPart 2 is the area where the results of the testing will be automatically calculated using a Macro.  If you currently have Macros disabled, press <F9> to enable. \n\nIf the tester selects a TEST RESULT of N/A for one or more mandatory test cases - a warning will be displayed on the TSR page, because the only appropriate results for a mandatory test case are Pass or Fail.\n"]
[null,"TC-Traceability","Full name: Traceability Reference\nObjective: This worksheet contains a list of requirements and specifications that show requirements coverage.\n"]
[null,"FS-Doc","Full name: Clinical Documents\nObjective: To assess the conformance of a clinical document to the requirements for clinical documents, excluding the requirements for narrative blocks, data types, and data groups.\n"]
[null,"FS-Narr","Full name: Narrative Blocks\nObjective: To assess the conformance of a clinical document to the requirements for narrative blocks.\n"]
[null,"FS-Types","Full name: Data Types & Data Groups\nObjective: To assess the conformance of a clinical document to the requirements for complex data types, and data groups defined in the Australian CDA extensions.\n"]
[null,"FS-Auth","Full name: Authoring Systems \nObjective: To assess the conformance of a clinical document authoring system to the requirements that apply regardless of the type of document being authored.\n"]
[null,"Return to top"]
[]
[]
[3,"Worksheet Structure"]
[null,"Table 3 describes the column names which are used in the Feature Set worksheets."]
[null,"Table 3: Worksheet Structure"]
[null,"COLUMN NAME","DESCRIPTION"]
[null,"TEST SET ID","An identifier that groups a set of tests. This column can be used to filter the tests.\n"]
[null,"TEST CASE ID","A unique identifier that distinguishes each test case from the entire set of test specifications. \n"]
[null,"CONFORMANCE REQUIREMENT","Displays the requirement to be met by the software being tested.\n"]
[null,"PRIORITY","Specifies whether a test is mandatory, conditional, or optional.  This is done with the abbreviation:\nM for Mandatory \nC for Conditional\nO for Optional\n"]
[null,"STEP NO.","The individual test step number within a test case which has multiple steps.\n"]
[null,"TEST STEP","The evaluation required for applying the test case.\n"]
[null,"EXPECTED RESULT","The expected outcome of the Test Step.\n"]
[null,"TEST RESULT","Result of the test (Pass, Fail, N/A, or TBD). \n\nPass:  The software passed the test.\nFail:    The software failed the test.\nN/A:   Not applicable - the test is not applicable for the software being tested \n(i.e. the test may be for an optional requirement that is not implemented in the software, or \nthe test is conditional and the condition is not present).\nTBD:   To be determined - the test result is still to be determined.\n"]
[null,"TESTER COMMENTS","Comments in support of the test result.\n"]
[null,"Return to top"]
[]
[]
[4,"Acronyms"]
[null,"Table 4 lists acronyms and terms used in the CTS."]
[null,"Table 4: Acronyms"]
[null,"Acronym","Meaning"]
[null,"ABN","Australian Business Number"]
[null,"AS","authoring system"]
[null,"CAE-I","Care Agency Employee Identifier. (See also PAI)"]
[null,"CDA","Clinical Document Architecture"]
[null,"CIS","clinical information system"]
[null,"CR","conformance requirement"]
[null,"CSP","contracted service provider"]
[null,"CTS","conformance test specification"]
[null,"DVA","Department of Veterans’ Affairs"]
[null,"FS","Feature Set"]
[null,"HI","Healthcare Identifier"]
[null,"HPI","Healthcare Provider Identifier (O-Organisation, I-individual)"]
[null,"HTML","HyperText Markup Language"]
[null,"IG","implementation guide(s)"]
[null,"IHI","IHI – Individual Healthcare Identifier"]
[null,"ISO","International Standard for Organisation"]
[null,"Luhn algorithm","Mod10 checksum"]
[null,"MBS","Medicare Benefits Schedule"]
[null,"NEHTA","National E-Health Transition Authority"]
[null,"OID","object identifier"]
[null,"P2P","peer-to-peer"]
[null,"PAI","PCEHR Assigned Identifier (O-Organisation, D-Device, R-Repository, delegated-Delegated Repository). (See also CAE-I)"]
[null,"PBS","Pharmaceutical Benefits Schedule"]
[null,"PCEHR","Personally Controlled Electronic Health Record"]
[null,"PDF","Portable Document Format"]
[null,"RTF","Rich Text Format"]
[null,"SCS","structured content specification"]
[null,"SNOMED CT","Systemised Nomenclature of Medicine - Clinical Terminology"]
[null,"SNOMED CT-AU","Systemised Nomenclature of Medicine - Clinical Terminology (Australia)"]
[null,"TC","test case"]
[null,"TS","test set"]
[null,"UML","Unified Modelling Language"]
[null,"UUID","universally unique identifier"]
[null,"XML","Extensible Markup Language"]
[null,"XSL","Extensible Stylesheet Language"]
[null,"XSLT","Extensible Stylesheet Language Transformations"]
[null,"Return to top"]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[null,"Return to top"]
[null,"Pass"]
[null,"Fail"]
[null,"N/A"]
[null,"TBD"]

{"sheet":"TSR","index":3,"n_rows":23,"n_cols":9,"rows_kept":23,"cut":false,"hidden":false,"merged":[[22,1,23,3],[1,2,1,3],[3,1,3,2],[4,1,4,2],[5,1,5,2],[6,1,6,2],[7,1,7,2],[8,1,8,2],[9,1,9,2],[10,1,10,2],[11,1,11,2],[14,1,14,4]]}
[]
[null,null,"TEST SUMMARY REPORT\n"]
[]
[null,"Software developer organisation:",null,"Please complete"]
[null,"Software name:",null,"Please complete"]
[null,"Software version:",null,"Please complete"]
[null,"Software description:",null,"Please complete"]
[null,"Testing location address:",null,"Please complete"]
[null,"Date(s) of testing:",null,"Please complete"]
[null,"Name of person(s) conducting tests:",null,"Please complete"]
[null,"Operating System/Environment Configuration (name and version)",null,"Optional."]
[null,"Additional software tools and versions not subject to testing used \n(e.g. web browser)",null,"Optional."]
[null,null,null,null,null,null,null,null," "]
[]
[null,"THIS SECTION DOES NOT NEED TO BE FILLED IN - IT WILL BE AUTOMATICALLY CALCULATED USING A MACRO. PRESS <F9> IF YOU HAVE MACROS DISABLED."]
[null,null,"Test Case Worksheet ","% Success Rate","Number of \"N/A\" test results for mandatory tests"]
[null,1,"Tests for Clinical Documents (FS-Doc)",{"$f":"'FS-Doc'!J81","v":0},{"$f":"SUM('FS-Doc'!K:K)","v":{"$error":"#NAME?"}}]
[null,2,"Tests for Narratives (FS-Narr)",{"$f":"'FS-Narr'!J131","v":0},{"$f":"SUM('FS-Narr'!K:K)","v":{"$error":"#NAME?"}}]
[null,3,"Tests for Data Type and Groups (FS-Types)",{"$f":"'FS-Types'!J225","v":0},{"$f":"SUM('FS-Types'!K:K)","v":{"$error":"#NAME?"}}]
[null,4,"Tests for Authoring Systems (FS-Auth)",{"$f":"'FS-Auth'!J95","v":0},{"$f":"SUM('FS-Auth'!K:K)","v":{"$error":"#NAME?"}}]
[]
[]
[null,{"$f":"IF(OR(ISERROR(E17),ISERROR(E18)),\"WARNING: You must enable macros for this workbook.\",IF(SUM(E17:E20)>0,\"WARNING: A test result of N/A (not applicable) has been selected for one or more mandatory test cases. The only appropriate test results for a mandatory test are Pass or Fail. Please review and update the test results.\",\"\"))","v":"WARNING: You must enable macros for this workbook."}]

{"sheet":"TC - Traceability","index":4,"n_rows":335,"n_cols":15,"rows_kept":335,"cut":false,"hidden":false,"merged":[[174,11,175,11],[174,12,175,12],[171,13,173,13],[174,13,175,13],[171,9,173,9],[171,10,173,10],[174,9,175,9],[174,10,175,10],[171,11,173,11],[171,12,173,12],[266,4,267,4],[171,4,173,4],[171,6,173,6],[171,7,173,7],[171,8,173,8],[174,4,175,4],[176,4,177,4],[174,6,175,6],[174,7,175,7],[174,8,175,8]]}
[]
[null,"Traceability Reference","Related Specification","Conformance Requirement","Test Cases","Test Set Relevance","Test Case Exists?","Priority","Test Steps","FS-Doc","FS-Narr","FS-Types","FS-Auth","Notes"]
[null,"TR-ALL-001","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023706","TC-Doc-01","TS-GCD","P","M",1,"P",null,null,null,"Refers also to additional TCs in FS-Doc and FS-Auth"]
[null,"TR-ALL-002","NEHTACDAIG - CDA implementation guides","Section 1.8 Conformance","TC-Doc-02","TS-GCD","P","M",1,"P",null,null,null,"See also [NEHTA-1599:2014 ]"]
[null,"TR-ALL-003","NEHTACDAIG - CDA implementation guides","Section 1.8 Conformance","TC-Doc-03","TS-GCD","O","-",0,"P",null,null,null,"No Test Case required as tested in FS-Types"]
[null,"TR-ALL-004","NEHTACDAIG - CDA implementation guides","Section 1.8 Conformance","TC-Doc-04","TS-GCD","P","M",1,"P",null,null,null,"Refers also to additional TCs in FS-Types(Class) "]
[null,"TR-ALL-005","NEHTACDAIG - CDA implementation guides","Section 1.8 Conformance","TC-Doc-05","TS-GCD","P","M",2,"P"]
[null,"TR-ALL-006","NEHTACDAIG - CDA implementation guides","Section 1.8 Conformance","TC-Doc-06","TS-GCD","P","M",1,"P"]
[null,"TR-ALL-007","NEHTACDAIG - CDA implementation guides","Section 1.8 Conformance","TC-Doc-07","TS-GCD","O","-",0,"P",null,null,null,"No Additional Test Cases - See also [NEHTA-1136:2010]"]
[null,"TR-ALL-008","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 025254","TC-Doc-08","TS-GCD","P","M",1,"P"]
[null,"TR-ALL-009","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 4","TC-Doc-09","TS-GCD","P","M",1,"P"]
[null,"TR-ALL-010","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023707","TC-Doc-10","TS-Head","O","-",0,"P",null,null,null,"No Test Case required as tested in FS-Doc-01"]
[null,"TR-ALL-011","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023708","TC-Doc-11","TS-Head","P","M",1,"P"]
[null,"TR-ALL-012","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023709","TC-Doc-12","TS-Head","O","-",0,"P",null,null,null,"No Test Case required as tested in FS-Doc-05"]
[null,"TR-ALL-013","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 24","TC-Doc-13","TS-Head","O","-",0,"P",null,null,null,"No Test Case required as tested in FS-Doc-05"]
[null,"TR-ALL-014","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023728","TC-Doc-14","TS-Head","P","C",1,"P",null,null,null,null," "]
[null,"TR-ALL-015","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023734","TC-Doc-15","TS-Head","P","M",1,"P"]
[null,"TR-ALL-016","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023710","TC-Doc-22","TS-Head","P","M",1,"P"]
[null,"TR-ALL-017","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 024482","TC-Doc-16","TS-Level","P","C",1,"P"]
[null,"TR-ALL-018","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 024482","TC-Doc-17","TS-Level","P","C",1,"P"]
[null,"TR-ALL-019","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 024482","TC-Doc-18","TS-Level","P","C",1,"P"]
[null,"TR-ALL-020","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 024482","TC-Doc-19","TS-Level","P","C",1,"P"]
[null,"TR-ALL-021","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 024482","TC-Doc-20","TS-Level","P","C",2,"P"]
[null,"TR-ALL-022","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023723 ","TC-Doc-21","TS-Level","P","C",1,"P"]
[null,"TR-ALL-023","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023726","TC-Doc-23","TS-Body","P","C",2,"P"]
[null,"TR-ALL-024","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 025054","TC-Doc-24","TS-Body","P","C",1,"P",null,null,null,"See also [NEHTA-1199:2012]"]
[null,"TR-ALL-025","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 027731","TC-Doc-25","TS-Body","O","-",0,"P",null,null,null,"See also [NEHTA-1199:2012]"]
[null,"TR-ALL-026","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 26 (b)","TC-Doc-26","TS-Logo","P","C",1,"P"]
[null,"TR-ALL-027","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 26 (c)","TC-Doc-26","TS-Logo","P","C",1]
[null,"TR-ALL-028","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 26 (d)","TC-Doc-27","TS-Logo","P","C",1,"P"]
[null,"TR-ALL-029","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023722","TC-Doc-28","TS-Dext","P","C",4,"P",null,null,null,"Only 1 step marked conditional"]
[null,"TR-ALL-030","NEHTACDAIG - CDA implementation guides","Section 1.8 Conformance","TC-Doc-28","TS-Dext",null,null,null,null,null,null,null,"Refers also to FS-Types and FS-Narr as well as other FS-Doc tests"]
[null,"TR-ALL-031","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023724","TC-Doc-28","TS-Dext"]
[null,"TR-ALL-032","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023725","TC-Doc-29","TS-Dext","O","-",0,"P",null,null,null,"No Additional Test Cases"]
[null,"TR-ALL-033","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 64","TC-Doc-30","TS-Vers","P","M",1,"P"]
[null,"TR-ALL-034","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 65","TC-Doc-31","TS-Vers","P","M",1,"P"]
[null,"TR-ALL-035","HL7CDAR2 - HL7 Clinical Document Architecture, Release 2","4.2.3.1 ParentDocument","TC-Doc-32","TS-DocIdent","P","C",2,"P"]
[null,"TR-ALL-036","HL7CDAR2 - HL7 Clinical Document Architecture, Release 2","4.2.3.1 ParentDocument","TC-Doc-33","TS-DocIdent","P","C",1,"P"]
[null,"TR-ALL-037","NEHTACDAIG - CDA implementation guides","Section 8.2 id","TC-Doc-34","TS-DocIdent","P","C",1,"P"]
[null,"TR-ALL-038","HL7CDAR2 - HL7 Clinical Document Architecture, Release 2","4.2.3.1 ParentDocument","TC-Doc-35","TS-DocIdent","P","C",1,"P"]
[null,"TR-ALL-039","NEHTASCS","Appendix C. Information Model Specification Parts Legends","TC-Doc-36","TS-Dext","P","M",1,"P"]
[null,"TR-ALL-040","NEHTASCS","Appendix C. Data Group","TC-Doc-37","TS-GCD","P","M",1,"P"]
[null,"TR-ALL-041","HL7CDAR2 - HL7 Clinical Document Architecture, Release 2","4.2.1.1 ClinicalDocument.id","TC-Doc-38","TS-DocIdent","P","M",1,"P"]
[null,"TR-ALL-042","NEHTA-1199:2012 Clinical Documents - CDA Rendering Specification v1.0","CDA-RS 23","TC-Doc-39","TS-Head","P","O",1,"P"]
[null,"TR-ALL-043","NEHTA-0794:2011 Participation Data Specification","Section 2.49 Date of Birth is Calculated From Age\nSection 2.50 Date of Birth Accuracy Indicator\nSection 2.56 Age Accuracy Indicator","TC-Doc-40","TS-AdminObs","P","C",1,"P"]
[null,"TR-ALL-0321","NEHTACDAIG - CDA implementation guides","Section 2.2 Mapping Interpretation","TC-Doc-41","TS-Body","P","C",1,"P"]
[null,"TR-ALL-0322","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 027732","TC-Doc-42","TS-GCD","P","C",1,"P"]
[null,"TR-ALL-0323","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 027734","TC-Doc-43","TS-Body","O","-",0,"P",null,null,null,"See [DH-XXXX-XXX]"]
[null,"TR-ALL-0324","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 027735","TC-Doc-44","TS-Body","O","-",0,"P",null,null,null,"See [DH-XXXX-XXX]"]
[null,"TR-ALL-0325","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023727","TC-Doc-45","TS-GCD","O","-",0,"P",null,null,null,"No Test Case required as tested in FS-Doc, FS-Types, FS-Narr and FS-Auth: [NEHTA-1199:2012]"]
[null,"TR-ALL-044","NEHTACDAIG - CDA implementation guides","Section 1.8 Conformance ","TC-Narr-01","TS-Narr","O","-",0,null,"P",null,null,"No Test Case - this is the parent of all Narr"]
[null,"TR-ALL-045","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 025052","TC-Narr-02","TS-Narr","P","M",1,null,"P",null,null,"2 Requirements - One Test  - See also [NEHTA-0794:2011]"]
[null,"TR-ALL-046","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 025053","TC-Narr-02","TS-Narr"]
[null,"TR-ALL-047","NEHTACDAIG - CDA implementation guides","Appendix A. CDA Narratives","TC-Narr-03","TS-Narr","O","-",0,null,"P",null,null,"No Test Case required as tested in FS-Doc-01: [NEHTA-1599:2014]"]
[null,"TR-ALL-048","NEHTACDAIG - CDA implementation guides","Appendix A. CDA Narratives","TC-Narr-04","TS-Narr","O","-",0,null,"P",null,null,"No Test Case required as tested elsewhere in FS-Narr"]
[null,"TR-ALL-049","NEHTACDAIG - CDA implementation guides","Appendix A. CDA Narratives","TC-Narr-05","TS-Narr","O","-",0,null,"P",null,null,"No Test Case required as tested in FS-Doc [NEHTA-1599:2014] & elsewhere in FS-Narr"]
[null,"TR-ALL-050","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 024482","TC-Narr-06","TS-Narr","P","C",1,null,"P"]
[null,"TR-ALL-051","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 024482","TC-Narr-07","TS-Narr","P","C",1,null,"P"]
[null,"TR-ALL-052","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023706","TC-Narr-08","TS-Info","P","C",1,null,"P"]
[null,"TR-ALL-053","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 025053","TC-Narr-09","TS-Info","P","M",14,null,"P",null,null,"5/14 Steps Mandatory - Complex Test with many steps"]
[null,"TR-ALL-054","NEHTACDAIG - CDA implementation guides","Appendix A. CDA Narratives","TC-Narr-09","TS-Info"]
[null,"TR-ALL-055","NEHTACDAIG - CDA implementation guides","Appendix A. CDA Narratives","TC-Narr-10","TS-Info","P","O",1,null,"P",null,null,"See also [NEHTA-0794:2011]"]
[null,"TR-ALL-056","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 13","TC-Narr-11","TS-Auto","P","C",1,null,"P"]
[null,"TR-ALL-057","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 14 ","TC-Narr-12","TS-Auto","P","C",1,null,"P"]
[null,"TR-ALL-058","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 15 (a)","TC-Narr-13","TS-Auto","P","C",1,null,"P",null,null,"See also CDA-RS 49 (b)"]
[null,"TR-ALL-059","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 15 (b)","TC-Narr-14","TS-Auto","P","C",1,null,"P"]
[null,"TR-ALL-060","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 16 (a)","TC-Narr-15","TS-Auto","P","C",1,null,"P"]
[null,"TR-ALL-061","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 16 (b)","TC-Narr-16","TS-Auto","P","C",1,null,"P"]
[null,"TR-ALL-062","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 16 (c)","TC-Narr-17","TS-Auto","P","C",1,null,"P"]
[null,"TR-ALL-063","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 16 (d)","TC-Narr-18","TS-Auto","P","C",1,null,"P"]
[null,"TR-ALL-064","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 17 (a)","TC-Narr-19","TS-Auto","P","C",1,null,"P"]
[null,"TR-ALL-065","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 17 (b)","TC-Narr-20","TS-Auto","O","-",0,null,"P",null,null,"No Test Case required as tested with TC-Narr12 to 19"]
[null,"TR-ALL-066","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 49 (a)","TC-Narr-26","TS-Auto","P","O",1,null,"P"]
[null,"TR-ALL-067","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 49 (b)","TC-Narr-27","TS-Auto","P","C",1,null,"P"]
[null,"TR-ALL-068","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 18","TC-Narr-21","TS-Auto","P","C",1,null,"P"]
[null,"TR-ALL-069","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 19","TC-Narr-22","TS-Auto","P","C",1,null,"P"]
[null,"TR-ALL-070","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 20","TC-Narr-23","TS-Auto","P","C",1,null,"P"]
[null,"TR-ALL-071","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 21","TC-Narr-24","TS-Auto","P","O",1,null,"P"]
[null,"TR-ALL-072","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 22","TC-Narr-25","TS-Auto","P","C",1,null,"P"]
[null,"TR-ALL-073","HL7CDAR2 - HL7 Clinical Document Architecture, Release 2","Section 4.3.5.2","TC-Narr-93","TS-Auto","P","C",1,null,"P"]
[null,"TR-ALL-074","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 024482","TC-Narr-28","TS-Mark","P","C",1,null,"P",null,null,"See also [NEHTA-1199:2012]"]
[null,"TR-ALL-075","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 43","TC-Narr-29","TS-Mark","P","M",1,null,"P"]
[null,"TR-ALL-076","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 44","TC-Narr-30","TS-Mark","P","O",1,null,"P"]
[null,"TR-ALL-077","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 45","TC-Narr-31","TS-Mark","P","O",1,null,"P",null,null,"See also CDA-RS 43"]
[null,"TR-ALL-078","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 50","TC-Narr-32","TS-Mark","O","-",0,null,"P",null,null,"No Test Case required as tested in FS-Doc: [NEHTA-1599:2014]"]
[null,"TR-ALL-079","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 47 (a)","TC-Narr-33","TS-Mark","P","C",3,null,"P",null,null,"3 Requirements and 3 Steps. See also additional options [NEHTA-2065:2015]."]
[null,"TR-ALL-080","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 47 (b)","TC-Narr-33","TS-Mark"]
[null,"TR-ALL-081","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 50","TC-Narr-33","TS-Mark"]
[null,"TR-ALL-082","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 50","TC-Narr-34","TS-Mark","O","-",0,null,"P",null,null,"No Test Case required as tested in Narrative Block"]
[null,"TR-ALL-083","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 50","TC-Narr-35","TS-Mark","O","-",0,null,"P",null,null,"No Test Case required as tested in Narrative Block"]
[null,"TR-ALL-084","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 50","TC-Narr-36","TS-Mark","O","-",0,null,"P",null,null,"No Test Case required as tested in Narrative Block"]
[null,"TR-ALL-085","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 50","TC-Narr-37","TS-Mark","O","-",0,null,"P",null,null,"No Test Case required as tested in FS-Doc: [NEHTA-1599:2014 ]"]
[null,"TR-ALL-086","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 50","TC-Narr-38","TS-Mark","P","C",1,null,"P"]
[null,"TR-ALL-087","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 50","TC-Narr-39","TS-Mark","P","C",1,null,"P"]
[null,"TR-ALL-088","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 50","TC-Narr-40","TS-Mark","O","-",0,null,"P",null,null,"No Test Case required as tested in FS-Doc: [NEHTA-1599:2014 ]"]
[null,"TR-ALL-089","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 50","TC-Narr-41","TS-Mark","P","C",1,null,"P"]
[null,"TR-ALL-090","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 50","TC-Narr-42","TS-Mark","O","-",0,null,"P",null,null,"No Test Case required as tested in FS-Doc: [NEHTA-1599:2014 ]"]
[null,"TR-ALL-091","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 50","TC-Narr-43","TS-Mark","O","-",0,null,"P",null,null,"No Test Case required as tested in FS-Doc: [NEHTA-1599:2014 ]"]
[null,"TR-ALL-092","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 50","TC-Narr-44","TS-Mark","O","-",0,null,"P",null,null,"No Test Case required as tested in FS-Doc: [NEHTA-1599:2014 ]"]
[null,"TR-ALL-093","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 50","TC-Narr-45","TS-Mark","O","-",0,null,"P",null,null,"No Test Case required as tested in FS-Doc: [NEHTA-1599:2014 ]"]
[null,"TR-ALL-094","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 50","TC-Narr-46","TS-Mark","O","-",0,null,"P",null,null,"No Test Case required as tested in FS-Doc: [NEHTA-1599:2014 ]"]
[null,"TR-ALL-095","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 50","TC-Narr-47","TS-Mark","O","-",0,null,"P",null,null,"No Test Case required as tested in FS-Doc: [NEHTA-1599:2014 ]"]
[null,"TR-ALL-096","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 52 (a) ","TC-Narr-48","TS-Tab","O","-",0,null,"P",null,null,"No Test Case required as tested in Narrative Block"]
[null,"TR-ALL-097","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 52 (b) ","TC-Narr-49","TS-Tab","P","O",1,null,"P"]
[null,"TR-ALL-098","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 52 (c) ","TC-Narr-50","TS-Tab","P","C",2,null,"P",null,null,"2 Requirements - One Test Case"]
[null,"TR-ALL-099","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 52 (d) ","TC-Narr-50","TS-Tab"]
[null,"TR-ALL-100","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 52 (e) ","TC-Narr-51","TS-Tab","P","C",1,null,"P",null,null,"See also CDA-RS 52 (c)"]
[null,"TR-ALL-101","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 52 (f) ","TC-Narr-52","TS-Tab","O","-",0,null,"P",null,null,"No Test Case required as tested in Narrative Block"]
[null,"TR-ALL-102","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 52 (g) ","TC-Narr-53","TS-Tab","P","C",1,null,"P"]
[null,"TR-ALL-103","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 52 (h) ","TC-Narr-54","TS-Tab","O","-",0,null,"P",null,null,"No Test Case required as tested in Narrative Block"]
[null,"TR-ALL-104","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 52 (i) ","TC-Narr-55","TS-Tab","O","-",0,null,"P",null,null,"No Test Case required as tested in Narrative Block"]
[null,"TR-ALL-105","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 52 (j) ","TC-Narr-56","TS-Tab","O","-",0,null,"P",null,null,"No Test Case required as tested in Narrative Block"]
[null,"TR-ALL-106","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 52 (k) ","TC-Narr-57","TS-Tab","P","O",1,null,"P"]
[null,"TR-ALL-107","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 52 (l) ","TC-Narr-58","TS-Tab","O","-",0,null,"P",null,null,"No Test Case required as tested in Narrative Block"]
[null,"TR-ALL-108","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 52 (m) ","TC-Narr-59","TS-Tab","O","-",0,null,"P",null,null,"No Test Case required as tested in FS-Doc: [NEHTA-1599:2014 ]"]
[null,"TR-ALL-109","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 52 (n) ","TC-Narr-60","TS-Tab","P","C",1,null,"P"]
[null,"TR-ALL-110","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 52 (o) ","TC-Narr-61","TS-Tab","O","-",0,null,"P",null,null,"No Test Case required as tested in Narrative Block"]
[null,"TR-ALL-111","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 52 (p) ","TC-Narr-62","TS-Tab","P","C",1,null,"P"]
[null,"TR-ALL-112","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 54 (a) ","TC-Narr-63","TS-Style","O","-",0,null,"P",null,null,"No Test Case required as tested in Narr-64 onwards (TS-Style)"]
[null,"TR-ALL-113","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 54 (b), CDA-RS 55 (a-f), CDA-RS 56 (a-d), CDA-RS 57 (a-g)","TC-Narr-64","TS-Style","P","C",5,null,"P"]
[null,"TR-ALL-114","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 54 (c) ","TC-Narr-65","TS-Style","P","C",1,null,"P"]
[null,"TR-ALL-115","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 55 (f) ","TC-Narr-71","TS-Style","P","O",1,null,"P"]
[null,"TR-ALL-116","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 55 (g) ","TC-Narr-72","TS-Style","P","C",1,null,"P"]
[null,"TR-ALL-117","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 55 (h) ","TC-Narr-73","TS-Style","P","C",1,null,"P"]
[null,"TR-ALL-118","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 55 (i) ","TC-Narr-74","TS-Style","P","C",1,null,"P"]
[null,"TR-ALL-119","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 55 (j) ","TC-Narr-75","TS-Style","P","C",1,null,"P"]
[null,"TR-ALL-120","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 55 (k) ","TC-Narr-76","TS-Style","P","C",1,null,"P"]
[null,"TR-ALL-121","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023722 ","TC-Narr-88","TS-Ext","P","C",1,null,"P"]
[null,"TR-ALL-122","NEHTACDAIG - CDA implementation guides","Section 1.8 Conformance ","TC-Narr-88","TS-Ext"]
[null,"TR-ALL-123","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 50","TC-Narr-89","TS-Ref","P","C",1,null,"P",null,null,"See also [HL7CDAR2]"]
[null,"TR-ALL-124","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 53 (a)","TC-Narr-90","TS-Ref","O","-",0,null,"P",null,null,"5 Requirements & 0 Steps - Dependent on TC-Narr 89. "]
[null,"TR-ALL-125","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 53 (b)","TC-Narr-90","TS-Ref",null,null,null,null,null,null,null,"See also [NEHTA-2065:2015], mentioned as reference but not specified in TC-Narr 89"]
[null,"TR-ALL-126","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 53 (c)","TC-Narr-90","TS-Ref",null,null,null,null,null,null,null,"See also [DH-2481:2017]"]
[null,"TR-ALL-127","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 53 (d)","TC-Narr-90","TS-Ref"]
[null,"TR-ALL-128","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 53 (e)","TC-Narr-90","TS-Ref"]
[null,"TR-ALL-129","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 53 (h)","TC-Narr-91","TS-Ref","P","C",1,null,"P"]
[null,"TR-ALL-130","HL7CDAR2 - HL7 Clinical Document Architecture, Release 2","4.3.5.6 <renderMultiMedia>","TC-Narr-92","TS-Ref","P","M",2,null,"P"]
[null,"TR-ALL-131","OG1997","Universal Unique Identifier (UUID) ","TC-Types-105","TS-UID","P","M",1,null,null,"P"]
[null,"TR-ALL-132","ITU2004","Object Identifier (OID)","TC-Types-106","TS-UID","P","M",1,null,null,"P"]
[null,"TR-ALL-133","ITU2004","Object Identifier (OID)","TC-Types-107","TS-UID","P","M",1,null,null,"P"]
[null,"TR-ALL-134","ITU2004","UUID OID","TC-Types-108","TS-UID","P","M",1,null,null,"P"]
[null,"TR-ALL-135","OIDR2015","Australian Company Number (ACN) or Australian Business Number (ABN)","TC-Types-109","TS-UID","P","M",1,null,null,"P"]
[null,"TR-ALL-136","NEHTA-1136:2010 - Data Types in NEHTA Specifications","4.2 Boolean","TC-Types-01","TS-BSB","P","M",1,null,null,"P",null,"Refers to TS-BL"]
[null,"TR-ALL-137","NEHTA-1136:2010 - Data Types in NEHTA Specifications","5.1 EncapsulatedData","TC-Types-02","TS-BSB","P","M",1,null,null,"P",null,"Refers to TS-ED"]
[null,"TR-ALL-138","NEHTA-1136:2010 - Data Types in NEHTA Specifications","5.2 Text","TC-Types-03","TS-BSB","P","M",1,null,null,"P",null,"Refers to TS-ST"]
[null,"TR-ALL-139","NEHTA-1136:2010 - Data Types in NEHTA Specifications","6.1 CodeableText","TC-Types-04","TS-Coded","P","M",2,null,null,"P",null,"Refers to TS-CD"]
[null,"TR-ALL-140","DH-2481:2017 Clinical Documents - Common Conformance","CDA Level 3B","TC-Types-05","TS-Coded","P","C",1,null,null,"P",null,"2 Requirements - 1 Test Case"]
[null,"TR-ALL-141","ISO21090","7.5.2.1 Description","TC-Types-05","TS-Coded"]
[null,"TR-ALL-142","NEHTASCS","Codeable Text","TC-Types-06","TS-Coded","P","M",2,null,null,"P"]
[null,"TR-ALL-143","NEHTA-1136:2010 - Data Types in NEHTA Specifications","6.2 Coded Text","TC-Types-07","TS-Coded","P","M",2,null,null,"P",null,"2 steps - 1 Conditional and 1 Mandatory"]
[null,"TR-ALL-144","NEHTASCS","Coded Text","TC-Types-07","TS-Coded"]
[null,"TR-ALL-145","NEHTACDAIG - CDA implementation guides","Appendix A. CDA Narratives ","TC-Types-08","TS-Coded","P","M",1,null,null,"P"]
[null,"TR-ALL-146","NEHTACDAIG - CDA implementation guides","Section 1.8 Conformance","TC-Types-09","TS-Coded","O","-",0,null,null,"P",null,"No Additional Test Cases - See TC-Types 06"]
[null,"TR-ALL-147","NEHTA-1136:2010 - Data Types in NEHTA Specifications","7.1 Link","TC-Types-10","TS-IL","P","M",1,null,null,"P"]
[null,"TR-ALL-148","NEHTA-1136:2010 - Data Types in NEHTA Specifications","7.2 UniqueIdentifier","TC-Types-11","TS-IL","P","M",1,null,null,"P"]
[null,"TR-ALL-149","NEHTASCS","UniqueIdentifier","TC-Types-12","TS-IL","O","-",0,null,null,"P",null,"No Additional Test Cases"]
[null,"TR-ALL-150","NEHTA-1136:2010 - Data Types in NEHTA Specifications","8.1 Quantity","TC-Types-13","TS-Qualt","P","M",1,null,null,"P",null,"Refers to TS-PQ"]
[null,"TR-ALL-151","NEHTA-1136:2010 - Data Types in NEHTA Specifications","8.2 Integer","TC-Types-14","TS-Qualt","P","M",1,null,null,"P",null,"Refers to TS-INT"]
[null,"TR-ALL-152","NEHTA-1136:2010 - Data Types in NEHTA Specifications","8.3 Real","TC-Types-15","TS-Qualt","P","M",1,null,null,"P",null,"Refers to TS-REAL"]
[null,"TR-ALL-153","NEHTA-1136:2010 - Data Types in NEHTA Specifications","8.4 QuantityRatio","TC-Types-16","TS-Qualt","P","M",1,null,null,"P",null,"Refers to TS-RTO"]
[null,"TR-ALL-154","NEHTA-1136:2010 - Data Types in NEHTA Specifications","8.5 Duration","TC-Types-17","TS-Qualt","P","M",1,null,null,"P",null,"Refers to TS-PQ.TIME"]
[null,"TR-ALL-155","NEHTA-1136:2010 - Data Types in NEHTA Specifications","8.6 DateTime","TC-Types-18","TS-Qualt","P","M",1,null,null,"P",null,"Refers to TS-TS"]
[null,"TR-ALL-156","NEHTASCS","DateTime","TC-Types-19","TS-Qualt","O","-",0,null,null,"P",null,"No Additional Test Cases"]
[null,"TR-ALL-157","NEHTA-1136:2010 - Data Types in NEHTA Specifications","9.1 QuantityRange","TC-Types-21","TS-Cont","P","M",1,null,null,"P",null,"Refers to TS-IVL, TS-Qualt and TS-BTB"]
[null,"TR-ALL-158","NEHTA-1136:2010 - Data Types in NEHTA Specifications","9.2 TimeInterval","TC-Types-22","TS-Cont","P","M",1,null,null,"P",null,"Refers to TS-IVL, TS-Qualt and TS-BTB"]
[null,"TR-ALL-159","NEHTA-0794:2011 Participation Data Specification","Section 2.9 Entity Identifier","TC-Types-23","TS-EntId","P","M",2,null,null,"P",null,"Refers to TS-IL, TS-CD and TS-ST. See also NEHTACDAIG - CDA implementation guides"]
[null,"TR-ALL-160","NEHTACDAIG - CDA implementation guides","Section 8.4 Entity Identifier - id@root","TC-Types-24","TS-EntId","P","M",1,null,null,"P",null,"Refers to TS-UID"]
[null,"TR-ALL-161","NEHTACDAIG - CDA implementation guides","Section 8.4 Entity Identifier - id@root","TC-Types-25","TS-EntId","P","M",1,null,null,"P"]
[null,"TR-ALL-162","NEHTACDAIG - CDA implementation guides","Section 8.4 Entity Identifier - id@extention","TC-Types-26","TS-EntId","O","-",0,null,null,"P",null,"No Additional Test Cases. Refers to TS-II"]
[null,"TR-ALL-163","NEHTACDAIG - CDA implementation guides","Section 8.4 Entity Identifier - id@assigningauthorityname","TC-Types-27","TS-EntId","O","-",0,null,null,"P",null,"No Additional Test Cases. Refers to TS-II"]
[null,"TR-ALL-164","NEHTACDAIG - CDA implementation guides","Section 8.4 Entity Identifier - assigninggeographicArea","TC-Types-28","TS-EntId","P","M",1,null,null,"P"]
[null,"TR-ALL-165","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 027738","TC-Types-29","TS-EntId","P","C",1,null,null,"P",null,"Refers to TS-UID"]
[null,null,"DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 027736",null,"TS-EntId"]
[null,null,"DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 027737",null,"TS-EntId"]
[null,"TR-ALL-166","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 027789","TC-Types-30","TS-EntId","P","C",1,null,null,"P",null,"Refers to TS-UID"]
[null,"TR-ALL-167","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 027790",null,"TS-EntId"]
[null,null,"DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 027791","TC-Types-82","TS-EntId","P","C",1,null,null,"P",null,"Refers to TS-UID"]
[null,null,"DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 027792",null,"TS-EntId","P","M",1,null,null,"P",null,"Refers to TS-UID"]
[null,"TR-ALL-171","NEHTA-0794:2011 Participation Data Specification","Section 2.74 Entitlement","TC-Types-31","TS-EntIt","P","M",2,null,null,"P",null,"Refers to TS-IL, TS-Coded and TS-Cont"]
[null,"TR-ALL-172","NEHTA-0794:2011 Participation Data Specification","Section 2.76 Entitlement Type","TC-Types-32","TS-EntIt","P","M",1,null,null,"P",null,"Refers to TS-UID"]
[null,"TR-ALL-173","NEHTA-0794:2011 Participation Data Specification","Section 2.9 Entity Identifier - Participation Data Specification","TC-Types-33","TS-EntIt","P","M",1,null,null,"P"]
[null,"TR-ALL-174","NEHTACDAIG - CDA implementation guides","Medicare Number Used for an entitlement","TC-Types-34","TS-EntIt","P","M",1,null,null,"P",null,"See also Standards Australia Handbook 234-2012 - Section 7"]
[null,"TR-ALL-175","NEHTACDAIG - CDA implementation guides","Centrelink Customer Reference Number used for an entitlement","TC-Types-35","TS-EntIt","P","M",1,null,null,"P",null,"See also Standards Australia Handbook 234-2012 - Section 7"]
[null,"TR-ALL-176","NEHTACDAIG - CDA implementation guides","DVA file number used for an entitlement","TC-Types-36","TS-EntIt","P","M",1,null,null,"P",null,"See also Standards Australia Handbook 234-2012 - Section 7"]
[null,"TR-ALL-177","NEHTACDAIG - CDA implementation guides","Safety Net card number used for an entitlement","TC-Types-37","TS-EntIt","P","M",1,null,null,"P",null,"See also Standards Australia Handbook 234-2012 - Section 7"]
[null,"TR-ALL-178","NEHTACDAIG - CDA implementation guides","Medicare prescriber number used for an entitlement","TC-Types-38","TS-EntIt","P","M",1,null,null,"P",null,"See also Standards Australia Handbook 234-2012 - Section 7"]
[null,"TR-ALL-179","NEHTACDAIG - CDA implementation guides","Medicare pharmacy approval number used for an entitlement","TC-Types-39","TS-EntIt","P","M",1,null,null,"P",null,"See also Standards Australia Handbook 234-2012 - Section 7"]
[null,"TR-ALL-180","NEHTA-0794:2011 Participation Data Specification","Section 3.1 Address","TC-Types-40","TS-AddrDG","P","M",1,null,null,"P"]
[null,"TR-ALL-181","NEHTA-0794:2011 Participation Data Specification","Section 3.2 No Fixed Address Indicator","TC-Types-41","TS-AddrDG","P","M",1,null,null,"P"]
[null,"TR-ALL-182","NEHTA-0794:2011 Participation Data Specification","Section 3.4 International Address","TC-Types-42","TS-AddrDG","P","M",1,null,null,"P"]
[null,"TR-ALL-183","NEHTA-0794:2011 Participation Data Specification","Section 3.10 Australian Address","TC-Types-43","TS-AddrDG","P","M",1,null,null,"P"]
[null,"TR-ALL-184","NEHTA-0794:2011 Participation Data Specification","Section 3.11 Unstructured Australian Address Line","TC-Types-44","TS-AddrDG","P","O",1,null,null,"P"]
[null,"TR-ALL-185","NEHTA-0794:2011 Participation Data Specification","Section 3.21 Australian Lot Number","TC-Types-45","TS-AddrDG","P","O",1,null,null,"P"]
[null,"TR-ALL-186","NEHTA-0794:2011 Participation Data Specification","Section 3.30 Australian Suburb/Town/Locality","TC-Types-46","TS-AddrDG","P","O",1,null,null,"P",null,"2 Requirements - 1 Test Case"]
[null,"TR-ALL-187","NEHTA-0794:2011 Participation Data Specification","Section 3.31 Australian Suburb/Town/Locality Values","TC-Types-46","TS-AddrDG"]
[null,"TR-ALL-188","NEHTA-0794:2011 Participation Data Specification","Section 3.34 Australian Postcode","TC-Types-47","TS-AddrDG","P","O",1,null,null,"P",null,"2 Requirements - 1 Test Case"]
[null,"TR-ALL-189","NEHTA-0794:2011 Participation Data Specification","Section 3.35 Australian Postcode Values","TC-Types-47","TS-AddrDG"]
[null,"TR-ALL-190","ISO21090","7.1.4 Exceptional Value Detail","TC-Types-48","TS-NF","P","M",1,null,null,"P"]
[null,"TR-ALL-191","ISO21090","7.1.4 Null and NullFlavor","TC-Types-49","TS-NF","P","M",3,null,null,"P",null,"2 Requirements - 1 Test Case"]
[null,"TR-ALL-192","ISO21090","7.3.3.3.1 NullFlavor UNC","TC-Types-49","TS-NF"]
[null,"TR-ALL-193","ISO21090","7.3.4.5 Invariants","TC-Types-50","TS-BL","O","-",0,null,null,"P",null,"No Additional Test Cases required as tested in FS-Doc: [NEHTA-1599:2014 ]"]
[null,"TR-ALL-194","ISO21090","7.4.2.5 Invariants ","TC-Types-51","TS-ED","P","M",1,null,null,"P"]
[null,"TR-ALL-195","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 53 (i)","TC-Types-52","TS-ED","P","M",1,null,null,"P"]
[null,"TR-ALL-196","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 024631","TC-Types-53","TS-ED","P","C",1,null,null,"P",null," "]
[null,"TR-ALL-197","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 53 (j)","TC-Types-54","TS-ED","O","-",0,null,null,"P",null,"No Additional Test Cases required as tested in CTS for CDA Packaging [NEHTA-2065:2015]. \nAlso refer to CDA Package specification [NEHTA-1229:2011]"]
[null,"TR-ALL-198","ISO21090","7.4.2.3.5 mediaType","TC-Types-114","TS-ED","P","C",1,null,null,"P"]
[null,null,"DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 027766","TC-Types-119","TS-ED","P","C",1,null,null,"P"]
[null,null,"DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 027730","TC-Types-120","TS-ED","P","C",1,null,null,"P"]
[null,"TR-ALL-199","ISO21090","7.4.6.5 Invariants","TC-Types-55","TS-ST","P","M",1,null,null,"P"]
[null,"TR-ALL-200","ISO21090","7.4.6 ST (Character string)","TC-Types-56","TS-ST","P","M",1,null,null,"P",null,"See also [NEHTA-1199:2012]"]
[null,"TR-ALL-201","ISO21090","2.6 Concept Descriptor","TC-Types-57","TS-CD","P","M",1,null,null,"P"]
[null,"TR-ALL-202","ISO21090","7.5.2.6 Invariants ","TC-Types-58","TS-CD","P","M",1,null,null,"P"]
[null,"TR-ALL-203","ISO21090","7.5.2.4.1 code","TC-Types-59","TS-CD","P","M",1,null,null,"P"]
[null,"TR-ALL-204","ISO21090","7.5.2.1 nullFlavor ","TC-Types-60","TS-CD","P","M",1,null,null,"P"]
[null,"TR-ALL-205","ISO21090","7.5.2.4.2 codeSystem","TC-Types-61","TS-CD","P","M",1,null,null,"P"]
[null,"TR-ALL-206","ISO21090","7.5.2.4.2 codeSystem","TC-Types-62","TS-CD","P","M",1,null,null,"P"]
[null,"TR-ALL-207","ISO21090","7.5.2.4.4 codeSystemVersion ","TC-Types-63","TS-CD","P","C",1,null,null,"P"]
[null,"TR-ALL-208","ISO21090","7.5.2.4.3 codeSystemName","TC-Types-64","TS-CD","P","C",1,null,null,"P",null,"2 Requirements - 1 Test Case"]
[null,"TR-ALL-209","NEHTACDAIG - CDA implementation guides","Section 10 CodeSystem OIDs","TC-Types-64","TS-CD"]
[null,"TR-ALL-210","ISO21090","7.5.2.4.7 displayName","TC-Types-65","TS-CD","P","C",1,null,null,"P"]
[null,"TR-ALL-211","ISO21090","7.5.2.4.8 originalText","TC-Types-66","TS-CD","P","C",2,null,null,"P"]
[null,"TR-ALL-212","ISO21090","7.5.2.4.9 translation","TC-Types-67","TS-CD","P","C",2,null,null,"P"]
[null,"TR-ALL-213","ISO21090","7.5.2.4.8 originalText","TC-Types-67","TS-CD"]
[null,"TR-ALL-214","HL72004 - HL7 version 3 Standard: Data Types - Abstract Specification","2.6.8 Qualifier","TC-Types-68","TS-CD","P","C",3,null,null,"P"]
[null,"TR-ALL-215","ISO21090","7.6.2.5 Invariants","TC-Types-69","TS-Tel","P","M",1,null,null,"P",null,"No Additional Test Cases required as tested in FS-Doc: [NEHTA-1599:2014 ]"]
[null,"TR-ALL-216","ISO21090","7.6.2.1 Description","TC-Types-118","TS-Tel","P","M",1,null,null,"P"]
[null,"TR-ALL-217","ISO21090","7.6.7.5 Invariants","TC-Types-70","TS-II","P","M",1,null,null,"P"]
[null,"TR-ALL-218","ISO21090","7.6.7.3.1 root","TC-Types-71","TS-II","P","M",1,null,null,"P",null,"Refers to TS-UID"]
[null,"TR-ALL-219","NEHTACDAIG - CDA implementation guides","8.2 id","TC-Types-72","TS-II","P","M",1,null,null,"P"]
[null,"TR-ALL-220","ISO21090","7.6.7.3.1 root","TC-Types-73","TS-II","P","M",1,null,null,"P"]
[null,"TR-ALL-221","ISO21090","7.6.7.3.2 extension","TC-Types-74","TS-II","P","M",1,null,null,"P"]
[null,"TR-ALL-222","ISO21090","7.6.7.3.2 extension","TC-Types-75","TS-II","P","M",2,null,null,"P",null,"2 steps - 1 Conditional and 1 Mandatory"]
[null,"TR-ALL-223","HL72004 - HL7 version 3 Standard: Data Types - Abstract Specification","2.17 assigningAuthorityName","TC-Types-76","TS-II","P","C",1,null,null,"P"]
[null,"TR-ALL-224","Hl72015 - HL7 OID Registry","National healthcare identifier","TC-Types-77","TS-II","P","M",1,null,null,"P",null,"See also Use of HIs in Health Software Systems - Conformance Requirements [NEHTA-1732:2014]"]
[null,"TR-ALL-225","Hl72015 - HL7 OID Registry","PCEHR Assigned Identifier - Organisation","TC-Types-78","TS-II","P","C",1,null,null,"P",null,"See also Preparation Data Specification [NEHTA-0794:2011]"]
[null,"TR-ALL-226","Hl72015 - HL7 OID Registry","PCEHR Assigned Identifier - Care Agency Employee","TC-Types-111","TS-II","P","C",1,null,null,"P",null,"See also Preparation Data Specification [NEHTA-0794:2011]"]
[null,"TR-ALL-227","Hl72015 - HL7 OID Registry","PCEHR Assigned Identifier - Repository","TC-Types-79","TS-II","P","C",1,null,null,"P",null,"See also Preparation Data Specification [NEHTA-0794:2011]"]
[null,"TR-ALL-228","Hl72015 - HL7 OID Registry","PCEHR Assigned Identifier - Delegated Repository","TC-Types-80","TS-II","P","C",1,null,null,"P",null,"See also Preparation Data Specification [NEHTA-0794:2011]"]
[null,"TR-ALL-229","Hl72015 - HL7 OID Registry","PCEHR Assigned Identifier - Device ","TC-Types-81","TS-II","P","C",1,null,null,"P",null,"See also Preparation Data Specification [NEHTA-0794:2011]"]
[null,"TR-ALL-234","Hl72015 - HL7 OID Registry","Prescription Identifier scoped by an HPI-O","TC-Types-83","TS-II","P","C",5,null,null,"P"]
[null,"TR-ALL-235","Hl72015 - HL7 OID Registry","Dispense Record Identifier scoped by an HPI-O ","TC-Types-83","TS-II"]
[null,"TR-ALL-236","Hl72015 - HL7 OID Registry","HPI-O based Local Order Identifier ","TC-Types-83","TS-II"]
[null,"TR-ALL-237","Hl72015 - HL7 OID Registry","HPI-O based Accession Number","TC-Types-83","TS-II"]
[null,"TR-ALL-238","Hl72015 - HL7 OID Registry","HPI-O based Report Identifier","TC-Types-83","TS-II"]
[null,"TR-ALL-239","Hl72015 - HL7 OID Registry","Individual Medicare Card Number","TC-Types-84","TS-II","P","M",1,null,null,"P"]
[null,"TR-ALL-240","Hl72015 - HL7 OID Registry","Medicare Card Number","TC-Types-85","TS-II","P","M",1,null,null,"P"]
[null,"TR-ALL-241","AHW2015","Department of Veterans' Affairs File Number","TC-Types-86","TS-II","P","M",2,null,null,"P"]
[null,"TR-ALL-242","Hl72015 - HL7 OID Registry","Centrelink Customer Reference Number","TC-Types-87","TS-II","P","M",2,null,null,"P"]
[null,"TR-ALL-243","Hl72015 - HL7 OID Registry","Medicare Provider Number","TC-Types-88","TS-II","P","M",1,null,null,"P"]
[null,"TR-ALL-244","Hl72015 - HL7 OID Registry","Medicare Prescriber Number","TC-Types-89","TS-II","P","M",1,null,null,"P"]
[null,"TR-ALL-245","Hl72015 - HL7 OID Registry","Pharmacy Approval Number","TC-Types-90","TS-II","P","M",1,null,null,"P"]
[null,"TR-ALL-246","Hl72015 - HL7 OID Registry","NATA Lab Accreditation Number","TC-Types-91","TS-II","P","M",1,null,null,"P"]
[null,"TR-ALL-247","Hl72015 - HL7 OID Registry","Diagnostic Imaging Provider location specific practice number ","TC-Types-92","TS-II","P","M",1,null,null,"P"]
[null,"TR-ALL-248","ISO21090","7.8.9.3.2 unit","TC-Types-93","TS-PQ","P","M",1,null,null,"P"]
[null,"TR-ALL-249","ISO21090","7.8.9.5 Invariants","TC-Types-94","TS-PQ","P","M",1,null,null,"P",null,"See also [NEHTA-1599:2014]"]
[null,"TR-ALL-250","ISO21090","7.8.3.5 Invariants","TC-Types-95","TS-Int","P","M",1,null,null,"P"]
[null,"TR-ALL-251","ISO21090","7.8.7.6 Invariants","TC-Types-96","TS-REAL","P","M",1,null,null,"P"]
[null,"TR-ALL-252","ISO21090","7.8.8.4 Invariants","TC-Types-97","TS-RTO","P","M",1,null,null,"P",null,"See also [NEHTA-1599:2014]"]
[null,"TR-ALL-253","ISO21090","7.8.10.1 Description","TC-Types-98","TS-PQ.TIME","P","M",1,null,null,"P"]
[null,"TR-ALL-254","ISO21090","7.8.10.2 Invariants","TC-Types-98","TS-PQ.TIME"]
[null,"TR-ALL-255","ISO21090","7.8.13.3.1 value","TC-Types-99","TS-TS","P","M",2,null,null,"P"]
[null,"TR-ALL-256","ISO21090","7.8.13.5 Invariants","TC-Types-100","TS-TS","P","M",1,null,null,"P"]
[null,"TR-ALL-257","NEHTACDAIG - CDA implementation guides","Section 8.3 time","TC-Types-101","TS-TS","P","M",1,null,null,"P"]
[null,"TR-ALL-258","ISO21090","7.10.9.3.1 low","TC-Types-102","TS-IVL","P","M",1,null,null,"P"]
[null,"TR-ALL-259","ISO21090","7.10.9.3.3 high","TC-Types-103","TS-IVL","P","M",1,null,null,"P"]
[null,"TR-ALL-260","ISO21090","7.10.9.5 Invariants","TC-Types-104","TS-IVL","P","M",1,null,null,"P"]
[null,"TR-ALL-261","HL72013 as per the test cases","6.36.1 Observation.value","TC-Types-110","TS-Class","P","M",1,null,null,"P",null,"2 Requirements - 1 Test Case. See also [HL72013]"]
[null,"TR-ALL-262","HL72013 as per the test cases","6.5.4 Act.code",null,"TS-Class"]
[null,"TR-ALL-263","ISO21090","7.5.4.5 Invariants","TC-Types-115","TS-CS","P","M",1,null,null,"P"]
[null,"TR-ALL-264","ISO21090","7.5.4.3.1 code","TC-Types-116","TS-CS","P","M",1,null,null,"P"]
[null,"TR-ALL-265","ISO21090","7.5.4.3.1 code","TC-Types-117","TS-PIVL","P","M",1,null,null,"P"]
[null,"TR-ALL-328","ISO21090","7.9.6.5 Invariants","TC-Types-121","TS-SLIST","P","C",1,null,null,"P"]
[null,"TR-ALL-329","ISO21090","7.4.9.6 Invariants ","TC-Types-122","TS-ST","P","M",1]
[null,"TR-ALL-266","NEHTA-0794:2011 Participation Data Specification","Section 2.49 Date of Birth is Calculated from Age","TC-Auth-38","TS-Pers","P","M",1,null,null,null,"P"]
[null,"TR-ALL-267","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023873","TC-Auth-01","TS-Behav","P","C",1,null,null,null,"P","2 Requirements - 1 Test Case"]
[null,"TR-ALL-268","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023874","TC-Auth-01","TS-Behav"]
[null,"TR-ALL-269","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023730","TC-Auth-02.1","TS-Behav","P","C",5,null,null,null,"P","4 Requirements and 5 Steps"]
[null,"TR-ALL-270","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023732","TC-Auth-02.1","TS-Behav"]
[null,"TR-ALL-271","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023733","TC-Auth-02.1","TS-Behav"]
[null,"TR-ALL-272","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023877","TC-Auth-02.1","TS-Behav"]
[null,"TR-ALL-273","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023731","TC-Auth-02.2","TS-Behav","P","C",1,null,null,null,"P","2 Requirements - 1 Test Case"]
[null,"TR-ALL-274","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023732","TC-Auth-02.2","TS-Behav"]
[null,"TR-ALL-275","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023731","TC-Auth-02.3","TS-Behav","P","C",1,null,null,null,"P","2 Requirements - 1 Test Case"]
[null,"TR-ALL-276","DH-2481:2017 Clinical Documents - Common Conformance","Requirement - 023733","TC-Auth-02.3","TS-Behav"]
[null,"TR-ALL-277","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 3 (a)","TC-Auth-03","TS-Behav","P","M",1,null,null,null,"P"]
[null,"TR-ALL-278","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 2","TC-Auth-04","TS-Behav","P","M",2,null,null,null,"P","See also  Conformance Test Specification for CDA Rendering [NEHTA-2064:2016]"]
[null,"TR-ALL-279","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 67","TC-Auth-05","TS-Behav","P","M",2,null,null,null,"P","See also  Conformance Test Specification for CDA Rendering [NEHTA-2064:2016]"]
[null,"TR-ALL-280","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 3 (b)","TC-Auth-06","TS-Behav","P","C",1,null,null,null,"P","See also  Conformance Test Specification for CDA Rendering [NEHTA-2064:2016]"]
[null,"TR-ALL-281","HL7CDAR2 - HL7 Clinical Document Architecture, Release 2","1.3.2 CDA Conformance, Originator Responsibilities","TC-Auth-15","TS-Content","P","M",2,null,null,null,"P","2 steps:  1 Mandatory, 1 Conditional"]
[null,"TR-ALL-282","HL7CDAR2 - HL7 Clinical Document Architecture, Release 2","Section 4.3.5.2","TC-Auth-15","TS-Content"]
[null,"TR-ALL-283","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDR-RS 25","TC-Auth-17","TS-Content","O","-",0,null,null,null,"P","No Additional Test Cases"]
[null,"TR-ALL-284","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDR-RS 26 (a)","TC-Auth-18","TS-Content","P","C",1,null,null,null,"P"]
[null,"TR-ALL-285","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDR-RS 26 (c)","TC-Auth-19","TS-Content","O","-",0,null,null,null,"P","No Additional Test Cases Required - See FS-Doc"]
[null,"TR-ALL-286","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 46","TC-Auth-12","TS-Content","P","O",1,null,null,null,"P"]
[null,"TR-ALL-287","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 48","TC-Auth-13","TS-Content","P","O",1,null,null,null,"P"]
[null,"TR-ALL-288","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 52 (l)","TC-Auth-20","TS-Content","P","C",1,null,null,null,"P"]
[null,"TR-ALL-289","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 53 (f)","TC-Auth-08","TS-Content","P","C",1,null,null,null,"P"]
[null,"TR-ALL-290","NEHTA-1199:2012 Clinical Documents - CDA Rendering Spec","CDA-RS 53 (g)","TC-Auth-09","TS-Content","P","C",1,null,null,null,"P"]
[null,"TR-ALL-291","NEHTACDAIG - CDA implementation guides","Section 8.1 Code","TC-Auth-21","TS-Content","P","C",1,null,null,null,"P","See also Data Types in NEHTA Specifications [NEHTA-1136:2010]"]
[null,"TR-ALL-292","NEHTACDAIG - CDA implementation guides","Section 8.1 Code","TC-Auth-22","TS-Content","P","C",1,null,null,null,"P","See also Data Types in NEHTA Specifications [NEHTA-1136:2010]"]
[null,"TR-ALL-293","NEHTACDAIG - CDA implementation guides","Section 8.1 Code","TC-Auth-23","TS-Content","O","-",0,null,null,null,"P","No Additional Test Cases Required - See TC-Auth 10 & TS-Conc in FS-Types"]
[null,"TR-ALL-294","NEHTACDAIG - CDA implementation guides","Appendix A. CDA Narratives","TC-Auth-23","TS-Content"]
[null,"TR-ALL-295","NEHTACDAIG - CDA implementation guides","Section 8.1 Code","TC-Auth-24","TS-Content","P","C",2,null,null,null,"P","See also TC-Auth 22 & TS-Conc in FS-Types"]
[null,"TR-ALL-296","NEHTACDAIG - CDA implementation guides","Appendix A. CDA Narratives","TC-Auth-24","TS-Content"]
[null,"TR-ALL-297","HL72004 - HL7 version 3 Standard: Data Types - Abstract Specification","Section 2.36 Point in Time (TS)","TC-Auth-07","TS-Content","P","M",1,null,null,null,"P"]
[null,"TR-ALL-298","HL7CDAR2 - HL7 Clinical Document Architecture, Release 2","Section 4.2.3.1 Parent Document","TC-Auth-26","TS-Ident","P","C",1,null,null,null,"P"]
[null,"TR-ALL-299","HL7CDAR2 - HL7 Clinical Document Architecture, Release 2","Section 4.2.3.1 Parent Document","TC-Auth-27","TS-Ident","P","C",1,null,null,null,"P","See also [NEHTA-1599:2014]"]
[null,"TR-ALL-300","NEHTACDAIG - CDA implementation guides","Section 8.5 Person Name Usage","TC-Auth-28","TS-Pers","O","-",0,null,null,null,"P","No Additional Test Cases - Waiting on HL7"]
[null,"TR-ALL-301","NEHTA-0794:2011 Participation Data Specification","Section 2.27 Name Title","TC-Auth-29","TS-Pers","P","C",1,null,null,null,"P"]
[null,"TR-ALL-302","NEHTA-0794:2011 Participation Data Specification","Section 2.29 Family Name","TC-Auth-30","TS-Pers","P","M",3,null,null,null,"P","3 steps:  2 Mandatory, 1 Conditional - See also [NEHTA-1732:2014]"]
[null,"TR-ALL-303","NEHTA-0794:2011 Participation Data Specification","Section 2.30 Given Name","TC-Auth-31","TS-Pers","P","M",2,null,null,null,"P","2 steps:  1 Mandatory, 1 Optional"]
[null,"TR-ALL-304","NEHTA-0794:2011 Participation Data Specification","Section 2.31 Name Suffix","TC-Auth-32","TS-Pers","P","C",1,null,null,null,"P"]
[null,"TR-ALL-305","NEHTA-0794:2011 Participation Data Specification","Section 2.32 Name Suffix Values","TC-Auth-33","TS-Pers","P","O",1,null,null,null,"P"]
[null,"TR-ALL-306","NEHTA-0794:2011 Participation Data Specification","Section 2.34 Person Name Usage","TC-Auth-34","TS-Pers","P","C",1,null,null,null,"P"]
[null,"TR-ALL-307","NEHTA-0794:2011 Participation Data Specification","Section 2.45 Sex","TC-Auth-35","TS-Pers","P","M",1,null,null,null,"P"]
[null,"TR-ALL-308","NEHTA-0794:2011 Participation Data Specification","Section 2.47 Date of Birth Detail","TC-Auth-36","TS-Pers","O","-",0,null,null,null,"P","No Test Case - no mapping to CDA"]
[null,"TR-ALL-309","NEHTA-0794:2011 Participation Data Specification","Section 2.48 Date of Birth","TC-Auth-37","TS-Pers","P","M",1,null,null,null,"P"]
[null,"TR-ALL-310","NEHTA-0794:2011 Participation Data Specification","Section 2.49 Date of Birth is Calculated from Age","TC-Auth-38","TS-Pers","P","M",1,null,null,null,"P"]
[null,"TR-ALL-311","NEHTA-0794:2011 Participation Data Specification","Section 2.50 Date of Birth Accuracy Indicator","TC-Auth-39","TS-Pers","P","C",4,null,null,null,"P"]
[null,"TR-ALL-312","NEHTA-0794:2011 Participation Data Specification","Section 2.54 Age Detail","TC-Auth-40","TS-Pers","O","-",0,null,null,null,"P","No Test Case - no mapping to CDA"]
[null,"TR-ALL-313","NEHTA-0794:2011 Participation Data Specification","Section 2.56 Age Accuracy Indicator","TC-Auth-41","TS-Pers","P","C",1,null,null,null,"P"]
[null,"TR-ALL-314","NEHTA-0794:2011 Participation Data Specification","Section 2.61 Date of Death Accuracy Indicator","TC-Auth-42","TS-Pers","P","C",4,null,null,null,"P"]
[null,"TR-ALL-315","NEHTA-0794:2011 Participation Data Specification","Section 2.65 Source of Death Notification","TC-Auth-43","TS-Pers","P","C",1,null,null,null,"P"]
[null,"TR-ALL-316","NEHTA-0794:2011 Participation Data Specification","Section 2.70 State / Territory of Birth","TC-Auth-44","TS-Pers","P","C",1,null,null,null,"P"]
[null,"TR-ALL-317","NEHTA-0794:2011 Participation Data Specification","Section 2.72 Indigenous State","TC-Auth-45","TS-Pers","P","M",1,null,null,null,"P"]
[null,"TR-ALL-318","NEHTA-0794:2011 Participation Data Specification","Section 2.3 Role","TC-Auth-46","TS-Pers","P","C",1,null,null,null,"P"]
[null,"TR-ALL-319","NEHTA-0794:2011 Participation Data Specification","Section 2.40 Occupation","TC-Auth-47","TS-Pers","P","C",1,null,null,null,"P"]
[null,"TR-ALL-320","NEHTA-0794:2011 Participation Data Specification","Section 2.42 Position in Organisation","TC-Auth-48","TS-Pers","P","C",1,null,null,null,"P"]
[null,"TR-ALL-321","NEHTA-0794:2011 Participation Data Specification","Section 2.12 Electronic Communication Medium","TC-Auth-49","TS-eComm","P","C",1,null,null,null,"P"]
[null,"TR-ALL-322","NEHTA-0794:2011 Participation Data Specification","Section 2.14 Electronic Communication Usage Code ","TC-Auth-50","TS-eComm","P","C",1,null,null,null,"P"]
[null,"TR-ALL-323","NEHTA-0794:2011 Participation Data Specification","Section 2.16 Electronic Communication Address","TC-Auth-51","TS-eComm","P","C",1,null,null,null,"P"]
[null,"TR-ALL-324","NEHTA-0794:2011 Participation Data Specification","Section 3.1 Address","TC-Auth-52","TS-Addr","P","M",1,null,null,null,"P"]
[null,"TR-ALL-325","NEHTA-0794:2011 Participation Data Specification","Section 3.37 Address Purpose","TC-Auth-53","TS-Addr","P","M",1,null,null,null,"P"]
[null,"TR-ALL-326","NEHTACDAIG - CDA implementation guides","Section 8.6 Address","TC-Auth-54","TS-Addr","P","O",3,null,null,null,"P"]
[null,"TR-ALL-327","NEHTACDAIG - CDA implementation guides","Section 8.1 Code","TC-Auth-55","TS-Content","P","C",1,null,null,null,"P"]

{"sheet":"FS-Doc","index":5,"n_rows":81,"n_cols":11,"rows_kept":81,"cut":false,"hidden":false,"merged":[[66,2,67,2],[66,1,67,1],[2,5,3,5],[1,2,1,5],[0,2,0,5],[54,2,55,2],[0,0,0,1],[1,0,1,1],[2,0,2,1],[2,2,2,4],[3,0,3,1],[3,2,3,4]]}
["Feature set identifier:",null,"FS-Doc (Clinical Documents)"]
["Objective:",null,"To assess the conformance of a clinical document to the requirements for clinical documents, excluding the requirements for narrative blocks, data types and data groups."]
["Strategy:",null,"A clinical document to be tested may be obtained from any source, such as an authoring system operated by the tester, a database, or from another software system. The test sets are designed so a tester may assess the clinical document for conformance to the applicable requirements without needing any knowledge of the software that authored it. The test cases are written in a style that enables them to be automated wherever practical. \n\nSome conformance requirements are recommendations, indicated by the keywords SHOULD or SHOULD NOT. In general, the priority of the corresponding test case is 'optional' to indicate that it need only be applied if the developer of the authoring system claims to have implemented the recommended requirement.\n",null,null,"The following Test Sets have been defined:\n\nTS-GCD (General clinical document): derived from general requirements for a clinical document.\nTS-Head (CDA header): derived from general requirements for data elements in the header of a clinical document.\nTS-Level (Conformance level): derived from general requirements for the conformance level of a clinical document.\nTS-Body (CDA body): derived from general requirements for data elements in the body of a clinical document.\nTS-Logo (Logos): derived from requirements for the inclusion of a logo in a clinical document.\nTS-Dext (Document extensions): derived from requirements for the inclusion of extensions in a clinical document.\nTS-Vers (Version management): derived from requirements for a rendering system needed to render the clinical document.\nTS-DocIdent (Document identification, revisions & addenda): derived from requirements for document identification, revisions, and addenda.\nTS-AdminObs (Administrative Observations): derived from requirements for information in the administrative observations section."]
["Traceability:",null,"1. Clinical Documents - Common Conformance Profile [DH-2481:2017]\n2. HL7 Clinical Document Architecture, Release 2 [HL7CDAR2]\n3. CDA Rendering Specification [NEHTA-1199:2012]\n4. CDA implementation guides [NEHTACDAIG]\n5. PCEHR Document Exchange Service - Technical Service Specification v1.5.1 [NEHTA-1971:2014]\n6. Clinical Terminology - Guidance for Use in Healthcare Software [DH-2758:2018]\n7. Clinical Terminology Guidance for use of Medical Nomenclatures in Information Exchange [DH-2759:2018]"]
[]
["THIS HEADER CAN BE COLLAPSED BY CLICKING THE '-' SYMBOL ON THE LEFT."]
["TEST SET ID","TEST CASE ID","CONFORMANCE REQUIREMENT","PRIORITY\n(Mandatory, Optional, Conditional)","STEP NO.","TEST STEP","EXPECTED RESULT\n","TEST RESULT","TESTER COMMENTS","CALC.","MANDATORY AND N/A"]
["TS-GCD","START:  TS-GCD (General clinical document)"]
["TS-GCD","TC-Doc-01\n\n","023706 [DH-2481:2017]\nConformance to requirements specific for the type of clinical document\n\nA clinical document producing system SHALL conform to the requirements in the relevant structured content specification, the CDA implementation guide, the common conformance profile, and any specific conformance profile for the type of clinical document. Requirements in the specific conformance profile take precedence over requirements in the common conformance profile. Requirements in the common conformance profile take precedence over requirements in the structured content specification and the CDA implementation guide.\n\n","M",1,"For every data component in the clinical document: \n\nPass the test where the value is consistent with the definition of that data component.\nElse, Fail the test.\n\nNOTE TO TESTER: \nConformance to other aspects of this requirement is assessed by other test cases in the FS-Doc and FS-Narr feature sets.\n","Structured content for all data components in the clinical document is consistent with the appropriate specifications in the CDA Implementation guide.","TBD",null,{"$f":"IF(H9=\"\",\"0\",IF(H9=\"Pass\",1,IF(H9=\"Fail\",0,IF(H9=\"TBD\",0,IF(H9=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D9)=48,H9=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-GCD","TC-Doc-02\n\n","Section 1.8 Conformance [NEHTACDAIG]\nAny document that claims conformance to any derived conformance profile must meet these base requirements:\n\nIt SHALL be a valid HL7 CDA instance. \n\nIt SHALL be valid against the HL7 CDA Schema (once extensions have been removed; see W3C XML Schema).\n\nIt SHALL be valid against the Australian CDA schema extension [NEHTA-1599:2014 ] that accompanies this specification after any additional extension, not in the NEHTA extension namespace has been removed, along with any other CDA content not described by this implementation guide.\n\n","M",1,"Pass the test where:\na) the clinical document can be validated using the Australian CDA schema extension [NEHTA-1599:2014 ] using any software that is capable of performing XML schema validation; and\nb) the schema validation does not find any errors.\nElse, Fail the test.\n\nNOTE TO TESTER: \na)Validation to the Australian CDA schema extension may be performed using a digital health record template package as the template packages incorporate the Australian CDA schema extension. \nb) Other aspects of the requirement for a clinical document to be a valid HL7 CDA instance are assessed by other test cases in this conformance test specification.\n","Appropriate XML schema validation software confirms that the clinical document is valid against the Australian CDA schema extension. ","TBD",null,{"$f":"IF(H10=\"\",\"0\",IF(H10=\"Pass\",1,IF(H10=\"Fail\",0,IF(H10=\"TBD\",0,IF(H10=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D10)=48,H10=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-GCD","TC-Doc-03\n","Section 1.8 Conformance [NEHTACDAIG]\nAny document that claims conformance to any derived conformance profile must meet these base requirements:\n\nIt SHALL conform to the HL7 V3 R1 data type specification.\n",null,null,"No additional test case is needed as test cases derived from requirements for data types are included in the FS-Types feature set. \n"]
["TS-GCD","TC-Doc-04\n","Section 1.8 Conformance [NEHTACDAIG]\nAny document that claims conformance to any derived conformance profile must meet these base requirements:\n\nIt SHALL conform to the semantics of the RIM and Structural Vocabulary.\n","M",1,"Fail the test where any data element has an xsi:type attribute with a value that is inconsistent with the Reference Information Model specification for the data type;\nElse Pass the test.\n\nNOTE TO TESTER:\n For example, a data element of the name \"code\" has the \"CD\" data type which means it is an error for a \"code\" data element to have the \"ST\" data type.\n","For all data elements with an xsi:type attribute, the attribute has a value that is consistent with the Reference Information Model Specification for the data type.","TBD",null,{"$f":"IF(H12=\"\",\"0\",IF(H12=\"Pass\",1,IF(H12=\"Fail\",0,IF(H12=\"TBD\",0,IF(H12=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D12)=48,H12=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-GCD","TC-Doc-05\n","Section 1.8 Conformance [NEHTACDAIG]\nAny document that claims conformance to any derived conformance profile must meet these base requirements:\n\nIt SHALL use the mappings as they are stated in this document.\n\nNote: the document referenced by the requirement is the CDA implementation guide for the specific type of document.\n","M",1,"For every CDA schema data element in the clinical document:\nPass the step where the number of occurrences of the data element conforms to:\na) the cardinality listed in the mapping table; and\nb) any variations to the cardinality specified in the applicable conformance profile.\nElse, Fail the step.\n\nNOTE TO TESTER:\nThe Xpath for the CDA schema data element is listed in a mapping table column with the title 'CDA Schema Data Element', and the definition of the data component is in the mapping table column with the title 'Data Component Definition'. \nA clinical document may contain data elements not listed in the CDA implementation guide (e.g. they may be extensions). \nAny additional data elements are not examined in this test case.\n\n","All CDA schema data elements map as specified in the clinical document.","TBD",null,{"$f":"IF(H13=\"\",\"0\",IF(H13=\"Pass\",1,IF(H13=\"Fail\",0,IF(H13=\"TBD\",0,IF(H13=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D13)=48,H13=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-GCD",null,null,"M",2,"For every data element where there is a conformance requirement in the Vocab or Comments column of the mapping table:\nPass the step where the data element conforms to the requirement.\nElse, Fail the step.\n","All CDA schema data elements detailed in the comments column of the mapping table conform to the conformance requirements specified in the comments.","TBD",null,{"$f":"IF(H14=\"\",\"0\",IF(H14=\"Pass\",1,IF(H14=\"Fail\",0,IF(H14=\"TBD\",0,IF(H14=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D14)=48,H14=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-GCD","TC-Doc-06\n","Section 1.8 Conformance [NEHTACDAIG]\nAny document that claims conformance to any derived conformance profile must meet these base requirements:\n\nIt SHALL use all fixed values as specified in the mappings (e.g. @attribute=\"FIXED_VALUE\").\n","M",1,"Pass the test where, for every data element where the relevant CDA implementation guide specifies a fixed value, the data element in the clinical document contains the specified fixed value.\nElse, Fail the test.\n","All CDA implementation guide fixed value, specified data elements in the clinical document contain the appropriate specified fixed value. ","TBD",null,{"$f":"IF(H15=\"\",\"0\",IF(H15=\"Pass\",1,IF(H15=\"Fail\",0,IF(H15=\"TBD\",0,IF(H15=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D15)=48,H15=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-GCD","TC-Doc-07\n","Section 1.8 Conformance [NEHTACDAIG]\nAny document that claims conformance to any derived conformance profile must meet these base requirements:\n\nIt SHALL be valid against the additional conformance requirements that are established in this document (i.e. any use of the word “SHALL” in uppercase and bold typeface).\n\nThe document SHALL conform to the requirements specified in the CDA Rendering Specification.\n\nThe data as contained in the data types SHALL conform to the additional data type specification.\n",null,null,"No additional test case is needed as test cases derived from the conformance profiles for a specific type of document is listed in the worksheet for that type of document. \n\nThe CDA Rendering specifications contains requirements for authoring systems and the corresponding test cases are included in the FS-Doc, FS-Narr, FS-Types, and FS-Auth worksheets.\n\nTest cases derived from requirements in the additional data types specification are included in the FS-Types worksheet.\n"]
["TS-GCD","TC-Doc-08\n","025254 [DH-2481:2017]\nProhibit specific rendering of CDA content.\n\nClinical document producing systems SHALL NOT include any content that instructs or implies a specific rendering of the CDA content.\n\nNote: This explicitly includes the 'XML-stylesheet' processing instruction in CDA document XML content.","M",1,"Pass the test where the clinical document does not include any processing instructions that instruct or imply how to render the clinical content in the document.\nElse, Fail the test.\n\nNOTE TO TESTER: \nA processing Instruction allows an XML document to contain instructions for applications. The XML-stylesheet directive, which the XSLT processor correctly interprets is an example of a processing instruction. The XML-stylesheet directive allows an XSL stylesheet to be associated with an XML document without the need to actually change the XML element data. \n","The clinical document does NOT contain processing instructions that instruct or imply how to render the clinical content in the document.","TBD",null,{"$f":"IF(H17=\"\",\"0\",IF(H17=\"Pass\",1,IF(H17=\"Fail\",0,IF(H17=\"TBD\",0,IF(H17=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D17)=48,H17=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-GCD","TC-Doc-42","027732 [DH-2481:2017]\nIf the software has information in a form that may be used to populate an optional data component then the software SHALL allow the inclusion of that data component in a clinical document.\n\nAdditional Notes: The data component may be omitted from a clinical document if at least one of the following conditions is true:\n• The software does not have information for an optional data component;\n• The information is not in a form that may be used for the data component;\n• There is a clinical reason why supplying the data would be unsafe, misleading, or otherwise clinically inappropriate.","C",1,"CONDITION: The software system has information in a form that may be used to populate an optional data component and there is no clinical reason why the data should not be supplied.\n\nPass the test, where all information within the local system, which may be used to populate an optional data component, has been included in that data component in the clinical document.\nElse, Fail the test.\n\n","All information within the local system, which may be used to populate an optional data component, has been included in that data component in the clinical document.","TBD",null,{"$f":"IF(H18=\"\",\"0\",IF(H18=\"Pass\",1,IF(H18=\"Fail\",0,IF(H18=\"TBD\",0,IF(H18=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D18)=48,H18=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-GCD","TC-Doc-09\n","CDA-RS 4 [NEHTA-1199:2012]\nWhen using XML ID attributes in elements of the CDA document, Authoring Systems SHALL ensure that these XML ID attribute values are unique.\n","M",1,"Find all XML ID attributes in the clinical document.\n\nPass the test where there are no identical XML ID attributes.\nElse, Fail the test.\n\nNOTE TO TESTER: \nAn XML ID attribute is an attribute that is of the \"ID\" datatype defined in section 3.3.8 of the XML Schema Part 2: Datatypes Second Edition (https://www.w3.org/TR/XMLschema-2). The CDA schema also uses the name \"ID\" for every attribute of this type.\n","All XML ID attribute values in the clinical document are unique.","TBD",null,{"$f":"IF(H19=\"\",\"0\",IF(H19=\"Pass\",1,IF(H19=\"Fail\",0,IF(H19=\"TBD\",0,IF(H19=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D19)=48,H19=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-GCD","TC-Doc-37\n","Appendix C. Data Group [NEHTASCS]\nEvery instance of a data group SHALL have at least one child data component instantiated.\n\nNote: This requirement is generally listed in the Appendix C.2 \"The Structured Content Specification Metamodel\" of a Structured Content Specification but in some cases that section may be in Appendix B. In some old Structured Content Specifications the requirement may be worded differently or implied or stated in another section. For example in Shared Health Summary Structured Content Specification version 1.1 the definition of the Choice states that a member of a choice shall be present.\n","M",1,"Pass the test, where each Data Group included in the clinical document has at least one child data component.\nElse, Fail the test.\n\n\nNOTE TO TESTER: \nData group is described in SCS and CDA IG. If a data group is included in a clinical document then it must contain clinical information.\n","Each Data Group included in the clinical document contain clinical information with child data component.","TBD",null,{"$f":"IF(H20=\"\",\"0\",IF(H20=\"Pass\",1,IF(H20=\"Fail\",0,IF(H20=\"TBD\",0,IF(H20=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D20)=48,H20=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-GCD","TC-Doc-45\n","023727 [DH-2481:2017]\nConform to the authoring requirements from the CDA Rendering Specification.\n\nClinical document producing systems SHALL conform to the authoring requirements from the CDA Rendering Specification [NEHTA-1199:2012] for the creation of the clinical document.\n\nAdditional Notes: Note that some of the mandatory conformance requirements in the CDA Rendering Specification are context-specific. If that context does not apply then the corresponding mandatory requirement does not apply either. For example:\n• mandatory requirements that apply to automatically generated narratives do not apply to software that does not automatically generate narratives; and\n• some mandatory requirements that apply to a document body do not apply to software that generates clinical documents with an attachment rather than containing data within the document body.",null,null,"No additional test case is needed as the requirements derived from the CDA Rendering Specification [NEHTA-1199:2012] are tested in other test cases within this worksheet, as well as in the FS-Narr, FS-Types, and FS-Auth worksheets.\n\n\n\n"]
["TS-GCD","END:  TS-GCD (General clinical document)"]
["TS-Head","START:  TS-Head (CDA header)"]
["TS-Head","TC-Doc-11\n","023708 [DH-2481:2017]\nAll mandatory elements SHALL be present in a header.\n","M",1,"Using the mappings tables in the relevant CDA implementation guide, determine the header data elements with a minimum cardinality of 1 (e.g. \"1..1\" or \"1..*\").\n\nPass the test where, for each element listed, the data element is present in the clinical document. \nElse, Fail the test.\n\nNOTE TO TESTER: \nThe clinical document header is a set of data elements present in a clinical document before the body. Every clinical document has exactly one body, which is found in the ClinicalDocument/component/structuredBody.\n","ALL mandatory elements listed in the CDA header are contained in the clinical document.  ","TBD",null,{"$f":"IF(H24=\"\",\"0\",IF(H24=\"Pass\",1,IF(H24=\"Fail\",0,IF(H24=\"TBD\",0,IF(H24=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D24)=48,H24=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Head","TC-Doc-12\n","023709 [DH-2481:2017]\nAll logical header elements coded in the body SHALL be present.\n",null,null,"No additional test case is needed for this conformance requirement as TC-Doc-05 is sufficient."]
["TS-Head","TC-Doc-13\n","CDA-RS 24 [NEHTA-1199:2012]\nAuthoring Systems SHALL be aware that when a <title> header element is not provided, a CDA document title will be derived by compliant Rendering Systems based on other header elements.\n",null,null,"No additional test case is needed for this conformance requirement as TC-Doc-05 is sufficient."]
["TS-Head","TC-Doc-14\n","023728 [DH-2481:2017]\nIf the clinical document legalAuthenticator element is used in the clinical document, the person’s name and an entity identifier SHALL be included in the legalAuthenticator element, and the legalAuthenticator entity identifier value SHALL NOT be a NullFlavor.\n","C",1,"CONDITION: Clinical document under test contains the ClinicalDocument/legalAuthenticator element.\n\nPass the test where: \na) the legalAuthenticator name is present (i.e. ClinicalDocument/legalAuthenticator/assignedEntity/assignedPerson/<Person Name>); \nb) the legalAuthenticator entity identifier is present (i.e. ClinicalDocument/legalAuthenticator/assignedEntity/assignedPerson/<Entity Identifier>); and\nc) the value of the legalAuthenticator entity identifier is not a nullFlavor.\nElse, Fail the test.\n","ALL legalAuthenticator elements in the clinical document include the person's name and an entity identifier (which is not a nullFlavor). ","TBD",null,{"$f":"IF(H27=\"\",\"0\",IF(H27=\"Pass\",1,IF(H27=\"Fail\",0,IF(H27=\"TBD\",0,IF(H27=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D27)=48,H27=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Head","TC-Doc-15\n","023734 [DH-2481:2017]\nThe name and entity identifier of the custodian organisation SHALL be recorded in the clinical document and the custodian entity identifier value SHALL NOT be a NullFlavor.\n","M",1,"Pass the test where:\na) the custodian name is present (i.e. ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/name); \nb) the custodian entity identifier is present (i.e. ClinicalDocument/custodian/assignedCustodian/representedCustodianOrganization/<Entity Identifier>); and \nc) the value of the custodian entity identifier is not a nullFlavor.\nElse, Fail the test.\n","ALL custodian name elements in the clinical document include the custodian organisation's name and an entity identifier (which is not a nullFlavor). ","TBD",null,{"$f":"IF(H28=\"\",\"0\",IF(H28=\"Pass\",1,IF(H28=\"Fail\",0,IF(H28=\"TBD\",0,IF(H28=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D28)=48,H28=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Head","TC-Doc-39","CDA-RS 23 [NEHTA-1199:2012]\nAuthoring Systems SHOULD include a CDA document title in the <title> header element. This ensures that, when the document is rendered, an appropriate Author or episode-specific title is displayed to users.\n","O",1,"Mark the test N/A where the Authoring System does not create <title>header elements.\nPass the test where the ClinicalDocument title header element is present in clinical documents created by the authoring system and contains a value either specified by the clinical document author or else describes the type of healthcare episode. \nElse, Fail the test.\n","Title header element in clinical documents is created by the authoring system and contains a value specified by the clinical document author or describes the type of healthcare episode.","TBD",null,{"$f":"IF(H29=\"\",\"0\",IF(H29=\"Pass\",1,IF(H29=\"Fail\",0,IF(H29=\"TBD\",0,IF(H29=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D29)=48,H29=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Head","TC-Doc-22\n","023710 [DH-2481:2017]\nAny encoded content in the header SHALL support the terminology specified in the “Vocab” column of the CDA IGs.\n\nNote: this requirement applies to data elements containing a <code> element.\n","M",1,"Pass the test where, for every data element containing a <code> element where the mapping table Vocab column specifies a terminology:\na) the codeSystem attribute is present and has value for the specified terminology;\nb) the code attribute is present and has one of the values belonging to the specified terminology;\nc) if the displayName attribute is present then it has a value corresponding to the code; and\nd) if the codeSystemName attribute is present then it has a value specified for the code system.\nElse, Fail the test.\n\nNOTE TO TESTER: \nThis test case does not apply for a data element where the Vocab column states a specific terminology SHOULD be used.\n","<code> elements,  Vocab column specified have the appropriate code, codeSystem, display name and codeSystem Name attributes and values. ","TBD",null,{"$f":"IF(H30=\"\",\"0\",IF(H30=\"Pass\",1,IF(H30=\"Fail\",0,IF(H30=\"TBD\",0,IF(H30=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D30)=48,H30=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Head","END:  TS-Head (CDA header)"]
["TS-Level","START:  TS-Level (Conformance level)"]
["TS-Level","TC-Doc-16\n","024482 [DH-2481:2017]\nConformance level 1A.\n\nWith level 1A conformance a clinical document SHALL consist of: \nI. a CDA header; and\nii. a CDA body that only includes attachment references in the narrative block. \n\nThe body SHALL contain only one section <section>. \nThe narrative block SHALL contain only <renderMultimedia> elements which reference attachments contained in <observationMedia> entry elements that are contained in the same section. \nThe <observationMedia> element SHALL only reference local attachments that are part of the same CDA package. \nThe attachment SHALL be any of the approved file types (e.g. Adobe PDF format). \nThe same document MAY be included as multiple attachments with each of a different file type. \n\nNote: Attachments containing clinical information must be referenced from within an <observationMedia> in an <entry> (see the HL7 Clinical Document Architecture, Release 2 specification [HL7CDAR2]). As all clinical information is in attachments then at least one <observationMedia> must be present. Attachments to external objects (i.e. supporting documents) may also be present. The conformance levels that apply to each type of clinical document are specified in the separate clinical document conformance profiles. \n","C",1,"CONDITION: Conformance level 1A is claimed for the clinical document.\n\nPass the test where:\na) the clinical document body contains only one section <section>;\nb)  the <section> contains at least one narrative block <text>;\nc) the <section> contains at least <entry>;\nd) at least one <entry> element contains at least one <observationMedia>; and\ne) the <entry> elements contain only <observationMedia> and external objects.\nElse, Fail the test.\n\nNOTE TO TESTER: \nConformance of the header is done via other test cases, i) narrative block is via the FC-Narr feature set and ii) the attachment references from the <observationMedia> is via the FS-Types feature set. External objects are ExternalAct, ExternalDocument, ExternalObservation, and ExternalProcedure. The Conformance Test Specification for CDA Packaging [NEHTA-2065:2015] assesses conformance to the requirement that \"The <observationMedia> element SHALL only reference local attachments that are part of the same CDA package. The attachment SHALL be any of the approved file types (e.g. Adobe PDF format)\".","The clinical document header and body has the appropriate XML formats to meet conformance level 1A when claimed. \n\n","TBD",null,{"$f":"IF(H33=\"\",\"0\",IF(H33=\"Pass\",1,IF(H33=\"Fail\",0,IF(H33=\"TBD\",0,IF(H33=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D33)=48,H33=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Level","TC-Doc-17\n","024482 [DH-2481:2017]\nConformance level 1B.\n\nWith level 1B conformance a clinical document SHALL consist of:\ni. a CDA header format; and\nii. a CDA body format that includes at least one section which contains a narrative block. \n\nThe body SHALL contain at least one section <section> with a section label <title> and a narrative block <text>. \n\nThe narrative block SHALL contain human-readable mark-up content.\n","C",1,"CONDITION: Conformance level 1B is claimed for the clinical document.\n\nPass the test where:\na) the clinical document contains at least one section <section> containing a narrative block <text>; and\nb) any <section> containing a narrative block <text> also contains a <title>, and\nc) the narrative block contains human-readable mark-up content.\nElse, Fail the test\n\nNOTE TO TESTER: \nConformance of the header is assessed in other test cases and conformance of the narrative block is verified in the 'FC-Narr' feature set. A <section> may also contain <entry> elements.  \n","The clinical document header and body has the appropriate XML formats to meet conformance level 1B when claimed.\nThe narrative block contains human-readable mark-up content.\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D34)=48,H34=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Level","TC-Doc-18\n","024482 [DH-2481:2017]\nConformance level 2, 3A, and 3B.\n\nWith level 2 conformance, a clinical document SHALL consist of: \ni. a CDA header; \nii. a CDA body that contains mandatory sections; and \niii. mandatory sections, each containing a section label and a narrative block. \n\nThe body SHALL contain all sections that contain mandatory data elements (represented as narrative) as specified in the SCS and CDA IG. Each mandatory section in the body SHALL contain all mandatory elements specified as “CDA Body Level 2 Data Elements” in the CDA IG.\n","C",1,"CONDITION: Conformance level 2, 3A or 3B is claimed for the clinical document.\n\nPass the test where:\na) the CDA body includes every mandatory section specified in the relevant CDA implementation guide;\nb) each mandatory <section> contains a <title>; and\nc) each mandatory <section> contains all mandatory elements specified as “CDA Body Level 2 Data Elements” in the CDA implementation guide.\nElse, Fail the test.\n\nNOTE TO TESTER: Conformance of the header is assessed in other test cases. Conformance to the requirements for the narrative blocks is verified in the FS-Narr feature set. A <section> in a level 2 clinical document may also contain <entry> elements.  \n","The clinical document header and body has the appropriate XML formats to meet conformance level 2, 3A, or 3B when claimed.\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D35)=48,H35=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Level","TC-Doc-19\n","024482 [DH-2481:2017]\nConformance level 3A and 3B.\n\nRequirements are the same as Level 2. \nIn addition, each section in the body SHALL contain all mandatory elements specified as “CDA Body Level 3 Data Elements” in the CDA IGs. \n","C",1,"CONDITION: Conformance level 3A or 3B is claimed for the clinical document.\n\nPass the test where each section in the body contains the mandatory elements specified as “CDA Body Level 3 Data Elements” in the applicable CDA implementation guide. \nElse, Fail the test.\n","The clinical document section body has the appropriate CDA Body Level 3 Data Elements to meet conformance level 3A or 3B when claimed.\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D36)=48,H36=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Level","TC-Doc-20\n","024482 [DH-2481:2017]\nConformance level 3B.\n\nRequirements are the same as Level 3A. \nIn addition, each section’s encoded content SHALL use the clinical terminology (e.g. AMT and SNOMED CT-AU) and codes from the Pharmaceutical Benefits Schedule and the Medicare Benefits Schedule, as specified in the “Vocab” column of the CDA IGs. ","C",1,"CONDITION: Conformance level 3B is claimed for the clinical document.\n\nPass the step where, for every data element where the 'Vocab' column in the applicable CDA implementation guide states the use of Australian Medicines Terminology (AMT), SNOMED CT-AU, Pharmaceutical Benefits Schedule (PBS), or Medicare Benefits Schedule (MBS):\na) the data element includes the codeSystem for the specified terminology; and\nb) a primary or translation code attribute is present and has a value that is a member of the specified terminology; or\nc) nullFlavor \"OTH\" is present.\nElse, Fail the step. \n\nNOTE TO TESTER:\nThe terminology may be present as either the primary code or as a translation. The nullFlavor \"OTH\" is used when the specified terminology has no code corresponding to the concept selected by the user of the software. For AMT version 2 codeSystem=\"1.2.36.1.2001.1004.100\", for AMT version 3 codeSystem=\"2.16.840.1.113883.6.96\", for SNOMED CT-AU codeSystem=\"2.16.840.1.113883.6.96\", for PBS codeSystem=\"1.2.36.1.2001.1005.22\", and for MBS codeSystem=\"1.2.36.1.2001.1005.21\". \n","Each section's encoded content within the clinical document meets clinical terminology and codes for conformance level 3B requirements.\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D37)=48,H37=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Level",null,null,"C",2,"CONDITION: The 'Vocab' column in the applicable CDA implementation guide specifies a specific subset (a reference set) of the terminology and if a code is present.\n\nPass the step if the value of the code is a member of the specified reference set.\nElse, Fail the step.\n","Code values are members of specifically referenced subsets in the 'Vocab' column of the appropriate CDA implementation guide.  \n","TBD",null,0,{"$f":"IF(AND(BGCol(D38)=48,H38=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Level","TC-Doc-21\n","023723 [DH-2481:2017]\nA level 1B, 2, or 3A clinical document MAY include structured data with a higher level of conformance that is specified in the SCS and CDA IG.  If such data is included, it SHALL conform to the relevant requirements in the SCS and CDA IGs.\n","C",1,"CONDITION: Conformance level 1B, 2 or 3A is claimed for the clinical document and the body contains structured data that is mandatory to the higher level of conformance.\n\nList of all structured data elements that are present in the body section of the clinical document that is mandatory for the higher level of conformance.\n\n(Example: The clinical document conforms to level 1B and it contains elements that are mandatory for conformance levels 2 or 3A).\n\nPass the test where each of the structured data elements identified above passes the test cases in the FS-Types feature set and the TS-GCD, TS-Body and TS-Dext test sets of the FS-Doc feature set. \nElse Fail the test.\n","Structured data requiring a higher level of conformance meets appropriate 1B, 2, or 3A conformance levels.\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D39)=48,H39=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Level","END:  TS-Level (Conformance level)"]
["TS-Body","START:  TS-Body (CDA body)"]
["TS-Body","TC-Doc-23\n","023726 [DH-2481:2017]\nClinical document producing systems that insert AMT or SNOMED CT-AU terminology into a clinical document SHALL conform to the clinical terminology requirements in the relevant CDA IG.","C",1,"CONDITION: A data element contains an AMT or SNOMED CT-AU code.\n\nPass the step where, the data element passes the TS-CD test cases and the value domain is the reference set stated in the 'Vocab' column in the applicable CDA implementation guide.\nElse, Fail the step.\n","Data elements containing AMT or SNOMED CT-AU codes have code values from reference sets specified in the 'Vocab' column.","TBD",null,{"$f":"IF(H42=\"\",\"0\",IF(H42=\"Pass\",1,IF(H42=\"Fail\",0,IF(H42=\"TBD\",0,IF(H42=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D42)=48,H42=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Body","TC-Doc-24\n","025054 [DH-2481:2017]\nRequirements for title element\n\nIf a section contains a <text> element then the <title> element SHALL be included.\n\nNote: This overrides requirement CDA-RS 42 in the CDA Rendering Specification [NEHTA-1199:2012].\n","C",1,"CONDITION: The section contains a <text> element.\n\nPass the test if a <title> element is present,\nElse, Fail the test.","Each section with a <text> element contains a <title> element.","TBD",null,{"$f":"IF(H43=\"\",\"0\",IF(H43=\"Pass\",1,IF(H43=\"Fail\",0,IF(H43=\"TBD\",0,IF(H43=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D43)=48,H43=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Body","TC-Doc-25\n","027731 [DH-2481:2017]\nOmission of the section title\n\nIf a narrative is not included in a section, then the corresponding section title SHOULD NOT be included.\n\nNote: this overrides requirement CDA-RS 42 in the CDA Rendering Specification [NEHTA-1199:2012].\n\nAdditional Notes: The purpose of this requirement is to state that when there is no narrative block then the title for the narrative block should not be present.\n","O",1,"For every <section> element in the clinical document:\n\nPass the test where, if no <text> element or <section> element is present in the section, then no <title> is present in the section.\nElse, Fail the test.\n","No <title> is present in any <section> of the clinical document where there is neither narrative text or sub-section.","TBD",null,{"$f":"IF(H44=\"\",\"0\",IF(H44=\"Pass\",1,IF(H44=\"Fail\",0,IF(H44=\"TBD\",0,IF(H44=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D44)=48,H44=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Body","TC-Doc-41\n\n","Section 6.1 Subject of Care entitlements technical identifier [NEHTACDAIG]\nThe entitlement provides for the right of a participant to act in a given capacity (as defined by Entitlement Type) within a healthcare context. Each entitlement element SHALL be linked to the Record Target (Subject of Care). This is expressed as ext:coverage2/ext:entitlement/ext:participant/ext:participantRole/ext:id SHALL hold the same value as ClinicalDocument/recordTarget/patientRole/id.","C",1,"CONDITION: The Clinical Document contains at least one entitlement for Subject of Care.\n\nPass the test where the value of data element ClinicalDocument/recordTarget/patientRole/id is same as value of the ext:coverage2/ext:entitlement/ext:participant/ext:participantRole/ext:id data element\nElse, Fail the test\n","The value of  ext:coverage2/ext:entitlement/ext:participant/ext:participantRole/ext:id  is same as the value of ClinicalDocument/recordTarget/patientRole/id","TBD",null,{"$f":"IF(H45=\"\",\"0\",IF(H45=\"Pass\",1,IF(H45=\"Fail\",0,IF(H45=\"TBD\",0,IF(H45=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D45)=48,H45=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Body","TC-Doc-43\n\n","027734 [DH-2481:2017]\nThe requirements in Clinical Terminology - Guidance for Use in Healthcare Software [DH-2758:2018] SHOULD be adopted.\n",null,null,"No additional test case is needed as the test for the correct use of the clinical terminology is performed in the  Conformance Test Specification for Guidance for use of clinical terminology in Healthcare Software [DH-2758:2018].\n"]
["TS-Body","TC-Doc-44\n\n","027735 [DH-2481:2017]\nThe requirements in Clinical Terminology Guidance for use of Medical Nomenclatures in Information Exchange [DH-2759:2018] SHOULD be adopted.",null,null,"No additional test case is needed as the test for the correct use of the clinical terminology is performed in the  Conformance Test Specification for Guidance for use of medical nomenclatures in information exchange [DH-2759:2018].\n"]
["TS-Body","END:  TS-Body (CDA body)"]
["TS-Logo","START:  TS-Logo (Logos)"]
["TS-Logo","TC-Doc-26\n","CDA-RS 26 (b) [NEHTA-1199:2012]\nAuthoring Systems SHALL provide an <observationMedia> entry in the body of the CDA document to specify the image type and file name of the organisational logo in the CDA package.\n","C",1,"CONDITION: The Clinical Document contains an <observationMedia> element with an XML ID attribute with the value \"LOGO\".\n\nPass the test where the <observationMedia> contains a mediaType attribute whose value commence with \"image\" (e.g. \"image/gif\").\nElse, Fail the test\n","Any organisation logo used contains appropriate <observationMedia> entries included in the body of the clinical document, specifying the media type and file name of the organisational logo.\n\n","TBD",null,{"$f":"IF(H50=\"\",\"0\",IF(H50=\"Pass\",1,IF(H50=\"Fail\",0,IF(H50=\"TBD\",0,IF(H50=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D50)=48,H50=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Logo",null,"CDA-RS 26 (c) [NEHTA-1199:2012]\nAuthoring Systems SHALL ensure that the organisational logo’s associated <observationMedia> entry has an XML ID attribute with an assigned value of “LOGO”.\n","C",2,"CONDITION: The Clinical Document contains an <observationMedia> element with an XML ID attribute with the value \"LOGO\".\n\nPass the test where the <observationMedia> contains a reference to the logo.\nElse, Fail the test\n","An Authoring System that includes a logo in the clinical documents has associated observationMedia with an XML ID 'LOGO' value.","TBD",null,{"$f":"IF(H51=\"\",\"0\",IF(H51=\"Pass\",1,IF(H51=\"Fail\",0,IF(H51=\"TBD\",0,IF(H51=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D51)=48,H51=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Logo","TC-Doc-27\n","CDA-RS 26 (d) [NEHTA-1199:2012]\nAuthoring Systems SHALL NOT include an organisational logo larger than 400 pixels in width and 100 pixels in height.\n","C",1,"CONDITION: The Clinical Document contains an <observationMedia> element with an XML ID attribute with the value \"LOGO\".\n\nPass the test where the image referenced from the <observationMedia> element is no larger than 400 pixels in width and 100 pixels in height.\nElse, Fail the test.\n","Any organisation logo used does not exceed 400 pixels in width and 100 pixels in height.","TBD",null,{"$f":"IF(H52=\"\",\"0\",IF(H52=\"Pass\",1,IF(H52=\"Fail\",0,IF(H52=\"TBD\",0,IF(H52=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D52)=48,H52=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Logo","END:  TS-Logo (Logos)"]
["TS-Dext","START:  TS-Dext (Document extensions)"]
["TS-Dext","TC-Doc-28\n","023722 [DH-2481:2017]\nA producer MAY include additional data elements in a clinical document structured data or narrative, but such data elements SHALL NOT qualify or negate any of the data elements defined in the CDA implementation guides.\n\nSection 1.8 Conformance [NEHTACDAIG]\nAny additional content included in the clinical document that is not described by this implementation guide SHALL NOT qualify or negate content described by this guide and it SHALL be clinically safe for receivers of the document to ignore the non-narrative additions when interpreting the existing content.\n\n023724 [DH-2481:2017]\nIf a producer includes additional data in a clinical document, which is not specified in the SCS or CDA implementation guide, the data SHALL conform to the HL7 CDA R2 specification [HL7CDAR2].\n\nNote: A conformance profile for a specific type of clinical document may explicitly disallow extensions. If they are not explicitly disallowed then extensions are allowed. In addition to the need to conform to the HL7 CDA R2 specification, if the additional data contains the codeSystem \"1.2.36.1.2001.1001.101\" (i.e. asserts conformance to a data component defined by NEHTA) then it must conform to the requirements for that data component.\n","C",1,"CONDITION: Extensions are not disallowed by a specific conformance profile.\n\nNote all data elements present in the clinical document that are not described in the CDA implementation guide.\n\nPass the step where each of the data elements defined does not negate or qualify any data elements defined in the CDA Implementation Guide.\nElse, Fail the step\n\nNOTE TO TESTER: \nAn extension qualifies content if it scopes the statement in a significant way, e.g. the patient used to have a condition, but not now. An extension negates an element if it reverses its meaning e.g. the patient did not have a condition, or this content is deleted. The judgement as to whether an extension negates or qualifies is made on clinical grounds (i.e. if an implementer ignores the extension, will it matter?). \n","All elements NOT listed in the CDA Implementation Guide that are contained in the clinical document do not negate or qualify any defined data elements.","TBD",null,{"$f":"IF(H55=\"\",\"0\",IF(H55=\"Pass\",1,IF(H55=\"Fail\",0,IF(H55=\"TBD\",0,IF(H55=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D55)=48,H55=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Dext",null,null,null,2,"Pass the test where each of the data elements found in step 1 passes the test cases in the FS-Types feature set and the TS-GCD, TS-Body, and TS-Dext test sets of the FS-Doc and FS-Narr feature sets.\nElse, Fail the step.\n","Elements identified in Step 1 of this test case also pass the indicated Feature Set test cases specified.","TBD",null,{"$f":"IF(H56=\"\",\"0\",IF(H56=\"Pass\",1,IF(H56=\"Fail\",0,IF(H56=\"TBD\",0,IF(H56=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D56)=48,H56=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Dext",null,null,null,3,"List all components of the clinical document with the codeSystem \"1.2.36.1.2001.1001.101\" that are not specified by the CDA implementation guide for the document type.\n\nNOTE TO TESTER: \nFind the value of the 'code' attribute associated with the codeSystem \"1.2.36.1.2001.1001.101\" in the clinical document. If there is a data component in the CDA implementation guide with that code and codeSystem then the CDA implementation guide contains the specification for that data component. \n\nPass the step if another CDA implementation guide published by NEHTA specifies that data component and the data component conforms to this specification.\nElse, fail the step.\n\nNOTE TO TESTER: \nThe codeSystem \"1.2.36.1.2001.1001.101\" indicates a NEHTA-defined component and maybe a section or data group.\n","Components not specified by the CDA implementation guide conform to the NEHTA published specification.","TBD",null,{"$f":"IF(H57=\"\",\"0\",IF(H57=\"Pass\",1,IF(H57=\"Fail\",0,IF(H57=\"TBD\",0,IF(H57=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D57)=48,H57=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Dext",null,null,null,4,"CONDITION: Extensions are disallowed by a specific conformance profile.\n\nPass the step where the clinical document only contains data elements defined in the CDA Implementation Guide.\n Else, Fail the step\n","Data elements listed in the CDA Implementation Guide are contained in the clinical document.","TBD",null,{"$f":"IF(H58=\"\",\"0\",IF(H58=\"Pass\",1,IF(H58=\"Fail\",0,IF(H58=\"TBD\",0,IF(H58=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D58)=48,H58=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Dext","TC-Doc-29\n","023725 [DH-2481:2017]\nNo obligation for any consuming system to handle additional elements\n\nIf the producing system includes additional elements, they SHALL be included so that the consuming system is able to safely ignore any additional elements that are not specified in the CDA-IGs and their associated schema.\n",null,null,"No additional test case is defined for this requirement.\n"]
["TS-Dext","TC-Doc-36\n","Appendix C. Information Model Specification Parts Legends [NEHTASCS]\nIn an SCS, a component may be prohibited, that is, it occurs in the referenced DCM but it SHALL NOT be included in documents created according to the SCS. This is represented by a multiplicity range of 0..0. The text of the entry is also in a strikethrough font and it has a grey background.\n\n","M",1,"Fail the test if a clinical document includes a prohibited data element according to the relevant Structured Content Specification (SCS). \nElse, Pass the test.\n\nNOTE TO TESTER: \nProhibited data elements by SCS are represented in a strike through font and it has a grey background with cardinality 0..0. This identification can be found in section 2 of the relevant clinical document  SCS data hierarchy.\n","The clinical document does NOT contain prohibited data element in the clinical document according to the SCS.","TBD",null,{"$f":"IF(H60=\"\",\"0\",IF(H60=\"Pass\",1,IF(H60=\"Fail\",0,IF(H60=\"TBD\",0,IF(H60=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D60)=48,H60=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Dext","END:  TS-Dext (Document extensions)"]
["TS-Vers","START:  TS-Vers (Rendering version management)"]
["TS-Vers","TC-Doc-30\n","CDA-RS 64 [NEHTA-1199:2012]\nAuthoring Systems SHALL populate a <templateId> header element with the oldest version of this specification that is required to render the document correctly.\n\nNote: The specification referred to in the requirement is the CDA Rendering Specification.\n","M",1,"Pass the test where the clinical document contains a <templateId> header element with a @ root (OID) value or \"1.2.36.1.2001.1001.100.149\" and an @ extension (version) value of the form \"m.n\",\nElse, Fail the test.\n\nNOTE TO TESTER: The CDA Rendering Specification has a major and a minor version, and the format of the version number is \"m.n\" where \"m\" is the major version and \"n\" is the minor version\".\n","The Authoring System populates a <templateId> header element with the oldest version of the specification.","TBD",null,{"$f":"IF(H63=\"\",\"0\",IF(H63=\"Pass\",1,IF(H63=\"Fail\",0,IF(H63=\"TBD\",0,IF(H63=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D63)=48,H63=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Vers","TC-Doc-31\n","CDA-RS 65 [NEHTA-1199:2012]\nAuthors SHALL NOT require an older version of the CDA Rendering Specification specified as the minimum in the CDA Implementation Guide they are currently following.\n","M",1,"In the CDA implementation guide for clinical document type, find the requirement that mandates conformance to the CDA Rendering Specification.\n\nPass the test where:\na) a version of the CDA Rendering Specification is specified that is the minimum version of the CDA Rendering specification that is required to render the clinical document correctly; or \nb) if no version is specified, then the minimum version is the version specified in the Clinical Documents - Common Conformance Profile [DH-2481:2017]; and\nc) from the <templateId> element in the clinical document - with @ root value @ root (OID) value \"1.2.36.1.2001.1001.100.149\" - the @ extension value does not refer to a version older then the minimum version identified in step a.\nElse, Fail the test.\n","Where a minimum version of the CDA Rendering specification is specified, the minimum version renders the clinical document correctly. Where no minimum is specified ONLY the latest version is used.","TBD",null,{"$f":"IF(H64=\"\",\"0\",IF(H64=\"Pass\",1,IF(H64=\"Fail\",0,IF(H64=\"TBD\",0,IF(H64=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D64)=48,H64=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Vers","END:  TS-Vers (Rendering version management)"]
["TS-DocIdent","START:  TS-DocIdent (Document identification, revisions & addenda)"]
["TS-DocIdent","TC-Doc-32\n","4.2.3.1 ParentDocument [HL7CDAR2]\nDocument Identification, Revisions, and Addenda\n\nThe initial version of a document gets - in addition to a new unique value for ClinicalDocument.id, - a new value for ClinicalDocument.setId, and has the value of ClinicalDocument.versionNumber set to equal \"1\". \n","C",1,"CONDITION: The Clinical Document setID element is present in the clinical document.\n\nObtain a set of clinical documents where each document in the set is a new document (i.e. does not include a document that is a replacement or addenda of another document in the set).\nRemove from the set any clinical document that does not have the ClinicalDocument/setId element. \n\nPass the test where every instance of ClinicalDocument/setId has a unique value.\nElse, Fail the test.\n\nNOTE TO TESTER: \nA set of clinical documents may be for the same person, or for different people, or of the same type (e.g. all SHS) or different types of clinical documents.\n","All new clinical documents have a unique value given.","TBD",null,{"$f":"IF(H67=\"\",\"0\",IF(H67=\"Pass\",1,IF(H67=\"Fail\",0,IF(H67=\"TBD\",0,IF(H67=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D67)=48,H67=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-DocIdent",null,null,"C",2,"CONDITION: The Clinical Document versionNumber is present in the clinical document. \n\nObtain a set of clinical documents where each document in the set is a new document (i.e. does not include a document that is a replacement or addenda of another document in the set).\n\nPass the test where every instance of Clinical Document versionNumber value greater than or equal to 1.\nElse, Fail the test.\n\nNOTE TO TESTER: \nIt is possible that the first version of a document may not be issued by the clinical information system, so even though the requirement is for versionNumber to equal 1 for the first version, it may not be possible to determine if a clinical document being assessed is the first version.\n","Clinical Document versionNumber value greater than or equal to 1.","TBD",null,{"$f":"IF(H68=\"\",\"0\",IF(H68=\"Pass\",1,IF(H68=\"Fail\",0,IF(H68=\"TBD\",0,IF(H68=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D68)=48,H68=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-DocIdent","TC-Doc-33\n","4.2.3.1 ParentDocument [HL7CDAR2]\nDocument Identification, Revisions, and Addenda\n\nA replacement document is a new version of the parent document. The parent document is considered superseded, but a system may retain it for historical or auditing purposes. The parent document being replaced is referenced via act relationship relatedDocument, where relatedDocument.typeCode is set to equal \"RPLC\" (for \"replaces\"). \n\nA replacement document gets a new globally unique ClinicalDocument.id value, and uses the same value for ClinicalDocument.setId as the parent report being replaced, and increments the value of ClinicalDocument.versionNumber by 1. \n\nClinicalDocument/effectiveTime [HL7CDAR2]\nDefinition: Signifies the document creation time, when the document first came into being. \n\nNote: The version number must be incremented by one when a report is replaced, but may also be incremented more often to meet local requirements.\" \n","C",1,"CONDITION: The Clinical Documents being assessed are of a type that allows a document to be superseded.\n\nObtain a clinical document (the 'replacement document') and the document that it superseded.\n\nPass the step where:\na) if the ClinicalDocument/relatedDocument/parentDocument element is present in the replacement document and if it has typeCode \"RPLC\" then verify that in the replacement document the value of the ClinicalDocument/relatedDocument/parentDocument/id root and extension attributes are the same as in the superseded clinical document's identifier (ClinicalDocument/id), and\nb) the value of ClinicalDocument/effectiveTime in the replacement document identifies a time that is after the ClinicalDocument/effectiveTime listed in the superseded document, and\nc) the value of ClinicalDocument/id is different for each clinical document, and\nd) if the version number (ClinicalDocument/versionNumber/@value) is present in the replacement document then verify that ClinicalDocument/versionNumber/@value is present in the superseded document and has been increased by at least 1, and\ne) if the ClinicalDocument/setId is present in the replacement document then verify that ClinicalDocument/setId is present in all superseded documents and has the same value, and\nf) the value of ClinicalDocument/templateId in the replacement document is identical to the value in the superseded document, to indicate that the documents are of the same type.\nElse, Fail the step.\n\nNOTE TO TESTER: \nIf a clinical document was downloaded from the My Health Record system then the XDS.b Association Type can be used to determine if the clinical document is a replacement document [NEHTA-1971:2014]. Otherwise, the presence of a ClinicalDocument/relatedDocument/parentDocument element where the value of the typeCode attribute is \"RPLC\" may be used to determine if the document is a replacement document, but note that inclusion of the parentDocument element is optional; so for documents downloaded from the My Health Record system the XDS metadata should be used.\n \n","All replacement documents have root attributes, id, and version numbers superseded and the appropriate effective time of the replacement indicated. The set/id is present in all replacements and of the same value.  ","TBD",null,0,{"$f":"IF(AND(BGCol(D69)=48,H69=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-DocIdent","TC-Doc-34\n","Section 8.2 id [NEHTACDAIG]\nThese identifiers are allowed to facilitate record matching across multiple versions of related documents so that the same record can consistently be identified, in spite of variations in the information as the record passes through time or between systems. These identifiers have no meaning in the business specification. If senders provide one of these identifiers, it SHALL always be the same identifier in all versions of the record, and it SHALL be globally unique per the rules of the II data type. Throughout the specification, these identifiers are labelled with the following text: \"This is a technical identifier that is used for system purposes such as matching.\"\n","C",1,"CONDITION:  A replacement document and the document it superseded were obtained for test case TC-Doc-32 (Note: the setId element need not be present).\n\nPass the test where:\na) each occurrence of the instance identifier identifies the same object in the replacement document as the clinical documents that it superseded; and\nb) both occurrences of the object are associated with the same instance identifier in the replacement document as the clinical document that it superseded.\nElse, Fail the test.\n\nNOTE TO TESTER: The Instance Identifier data type is also referred to as UniqueIdentifier in the structured content specifications.\n","Objects that have been Instance Identified match between previous and superseded versions and are unique identifiers in themselves.","TBD",null,0,{"$f":"IF(AND(BGCol(D70)=48,H70=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-DocIdent","TC-Doc-35\n","4.2.3.1 ParentDocument [HL7CDAR2]\nDocument Identification, Revisions, and Addenda\n\nAn addendum is a separate document that references the parent document, and may extend or alter the observations in the prior document. The parent document remains a current component of the patient record, and the addendum and its parent are both read by report recipients. The parent report (represented by the ParentDocument class) being appended is referenced via act relationship relatedDocument, where relatedDocument.typeCode is set to equal \"APND\" (for \"appends\").\n\nClinicalDocument/effectiveTime [HL7CDAR2]\nDefinition: Signifies the document creation time, when the document first came into being. \n","C",1,"CONDITION: The Clinical Document/relatedDocument/parentDocument element is present in the clinical document that is an addendum of a previously created clinical document.\n\nObtain a clinical document (the 'addendum document') and the documents that are appended.\n\nPass the test where:\na) the value of the ClinicalDocument/relatedDocument/parentDocument/id root attribute is the appended document's identifier (ClinicalDocument/id); and\nb) the value of ClinicalDocument/effectiveTime in the addendum document identifies a time that is after the ClinicalDocument/effectiveTime listed in the previously created clinical document.\nElse, Fail the test.\n\nNOTE TO TESTER:\n If a clinical document contains a ClinicalDocument/relatedDocument/parentDocument element where the value of the typeCode attribute is \"APND\" then the document is an addendum. In the My Health Record system, there is a requirement that appended documents must not be uploaded to the My Health Record system [NEHTA-1971:2014].\n\n","Addendum document identifier is updated to the clinical document parent root id and the effective time is later than the previous version.","TBD",null,0,{"$f":"IF(AND(BGCol(D71)=48,H71=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-DocIdent","TC-Doc-38\n","4.2.1.1 ClinicalDocument.id [HL7CDAR2]\nDefinition: Represents the unique instance identifier of a clinical document.\n","M",1,"Obtain the clinical document instance identifiers (ClinicalDocument/id) for the set of clinical documents produced by the authoring system.\n\nPass the test where every clinical document instance identifier (ClinicalDocument/id) has a root attribute and every clinical document instance identifier is unique within the set of clinical documents produced by the Authoring System.\nElse, Fail the test.\n\nNOTE TO TESTER: \nThe test applies only to the identifier of the clinical document, rather than every identifier within the clinical document. The comparison of instance identifiers is done by comparing the values of the root and extension attributes of one identifier with the root and extension attributes of another identifier. If the extension attribute is not present in an instance identifier then the comparison is done using the value of the root attribute.","Every clinical document created by an Authoring System has a unique identifier.","TBD",null,0,{"$f":"IF(AND(BGCol(D72)=48,H72=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-DocIdent","END:  TS-DocIdent (Document identification, revisions & addenda)"]
["TS-AdminObs","START:  TS-AdminObs (Administrative Observations)"]
["TS-AdminObs","TC-Doc-40\n\n","Section 2.49 Date of Birth is Calculated From Age [NEHTA-0794:2011]\nDefinition: Indicates whether or not a person's date of birth has been derived from the value in the Age data element. \n\nWhere the date of birth is derived from the age:\n1. only the year SHOULD be supplied;\n2. the date accuracy indicator for the year SHOULD be the same as the Age Accuracy Indicator; and\n3. the date accuracy indicators for the month and day SHOULD be “false”.\n\nSection 2.50 Date of Birth Accuracy Indicator [NEHTA-0794:2011]\nDefinition: The level of certainty or estimation of a person's date of birth.\n\nNote: this data element is optional and if present its values are those stated in the AS 5017-2006 Health Care Client Identifier Date Accuracy, described below Section 10 [NEHTACDAIG]\n\nThe data elements that use this value set consist of a combination of three codes, each of which denotes the accuracy of one date component:\nA – The referred date component is accurately known.\nE – The referred date component is an estimate.\nU – The referred date component is unknown.\nThe data elements that use this value set contain positional fields (DMY).\n\nSection 2.56 Age Accuracy Indicator [NEHTA-0794:2011]\nDefinition: The accuracy of a person's age.\n\nA true or positive value indicates that the information supplied is accurate. A false or negative value indicates that the information supplied is not accurate or has been estimated. If no value is supplied, a null flavour SHALL be available, and the accuracy is unknown.\n\n","C",1,"CONDITION: The clinical document contains the Date of Birth is Calculated From Age data element is present with the value \"true\" and the Date of Birth Accuracy Indicator is present.\n\nPass the step if the Age Accuracy Indicator is \"true\" and the Date of Birth Accuracy Indicator has a value ends in \"A\" to indicate that the Date of Birth year is accurately known.\nElse Pass the step if the Age Accuracy Indicator is \"false\" and the Date of Birth Accuracy Indicator ends in \"A\" or \"E\" to indicate that the Date of Birth year is either accurate or estimated.\nElse, Fail the step.\n\nNOTE TO TESTER: \nIt is possible for the Age Accuracy Indicator to be \"false\" but the Date of Birth year to be accurately known if the uncertainty in the age is in the months rather than years of age.\n","The clinical document has an appropriately paired Age Accuracy and Date of Birth Accuracy:\nAge Accuracy of 'true' has Date of Birth Accuracy Indicator ending in 'A'. \nAge Accuracy of 'false' has Date of Birth Accuracy Indicator ends in either 'A' or 'E''. \n\n","TBD",null,{"$f":"IF(H75=\"\",\"0\",IF(H75=\"Pass\",1,IF(H75=\"Fail\",0,IF(H75=\"TBD\",0,IF(H75=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D75)=48,H75=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-AdminObs","END:  TS-AdminObs (Administrative Observations)"]
[]
[null,null,null,null,null,null,null,"TBD","Total Tests",{"$f":"SUM(J79:J80)","v":43}]
[null,null,null,null,null,null,null,"Fail","Tests Failed or TBD",{"$f":"COUNTIF(J1:J76,\"0\")","v":43}]
[null,null,null,null,null,null,null,"N/A","Tests Passed or N/A",{"$f":"COUNTIF(J2:J76,\"1\")","v":0}]
[null,null,null,null,null,null,null,"Pass","%Passed or N/A",{"$f":"SUM(J80/J78)","v":0}]

{"sheet":"FS-Narr","index":6,"n_rows":131,"n_cols":11,"rows_kept":131,"cut":false,"hidden":false,"merged":[[124,3,125,3],[120,2,121,2],[120,3,121,3],[62,1,64,1],[62,2,64,2],[100,1,103,1],[0,0,0,1],[1,0,1,1],[2,0,2,1],[2,2,2,4],[3,0,3,1],[3,2,3,4],[0,2,0,5],[1,2,1,5],[2,5,3,5]]}
["Feature set identifier:",null,"FS-Narr (Narratives)"]
["Objective:",null,"To assess the conformance of a clinical document to the requirements for narrative blocks.\n"]
["Strategy:",null,"A clinical document to be tested may be obtained from any source, such as an authoring system operated by the tester, a database or from another software system. The tests are designed so a tester may assess the clinical document for conformance to the requirements for narrative blocks without needing any knowledge of the software that authored it. The test cases are written in a style that enables them to be automated wherever practical.\n\nSome conformance requirements for narrative blocks state that a feature MAY be used, and HL7 Clinical Document Architecture, Release 2 [HL7CDAR2] is referenced. A principle used here is that if an optional feature is included then it must be included correctly. Where the HL7 Clinical Document Architecture, Release 2 specification includes requirements for the correct use of the feature these are copied as notes underneath the conformance requirement and the test case priority is 'Conditional'  to indicate that if the feature is present then the test case must be applied.\n\nSome conformance requirements are recommendations, indicated by the keywords SHOULD or SHOULD NOT. In general, the priority of the corresponding test case is 'optional' to indicate that it need only be applied if the developer of the authoring system claims to have implemented the recommended requirement.\n",null,null,"The following Test Sets have been defined:\n\nTS-Narr (General narrative): derived from general requirements for clinical document narrative blocks.\nTS-Info (Information content): derived from requirements for information to be recorded in narrative blocks.\nTS-Auto (Auto generated): derived from requirements for the format of information in automatically generated narrative blocks.\nTS-Mark (Markup content): derived from requirements for the markup content and XML tags in narrative blocks.\nTS-Tab (Tables & Lists): derived from requirements for the inclusion of tables and lists in narrative blocks.\nTS-Style (Style codes): derived from requirements for the use of style codes in narrative blocks.\nTS-Ext (Extensions): derived from requirements for the inclusion of information in narrative blocks that extend the information model.\nTS-Ref (References): derived from requirements for the inclusion of references to multimedia and links in narrative blocks.\n\n"]
["Traceability:",null,"1. CDA Rendering Specification [NEHTA-1199:2012]\n2. HL7 Clinical Document Architecture, Release 2 [HL7CDAR2]\n3. Clinical Documents - Common Conformance Profile [DH-2481:2017]\n4. CDA implementation guides [NEHTACDAIG]\n5. HL7 Version 3 Standard: Data Types - Abstract Specification [HL72004]\n6. Participation Data Specification - Data Specification v3.2 [NEHTA-0794:2011 ]\n7. Extensible Markup Language (XML) 1.0 (Fifth Edition) [W3C2008]\n8. CSS Color Module Level 3 [W3C2018]\n"]
[]
["THIS HEADER CAN BE COLLAPSED BY CLICKING THE '-' SYMBOL ON THE LEFT."]
["TEST SET ID","TEST CASE ID","CONFORMANCE REQUIREMENT","PRIORITY","STEP NO.","TEST STEP","EXPECTED RESULT","TEST RESULT","TESTER COMMENTS","CALC.","MANDATORY AND N/A"]
["TS-Narr","START:   TS-Narr (General narrative)"]
["TS-Narr","TC-Narr-01\n","Section 1.8 Conformance [NEHTACDAIG]\nAny document that claims conformance to any derived conformance profile must meet these base requirements:\n\nThe narrative SHALL conform to the requirements described in this implementation guide.\n",null,null,"No additional test case is needed as conformance is achieved by passing all other test cases within this Feature Set.\n"]
["TS-Narr","TC-Narr-02","025052 [DH-2481:2017]\nA section SHALL contain narrative unless:\n• it does not contain an <author>, <informant>, <ext:coverage2>, <subject> or <entry> element; OR\n• the information that would otherwise be contained in that narrative is contained in the narrative of an ancestor section.\n\n025053 [DH-2481:2017]\nThe narrative for the following sections MAY be omitted:\n• Administrative Observations; and \n• a section containing a logo only.\n\nNote: \na) In this context a section is an organising container qualified by the <section> element tags.\nb) Requirement 025053 overrides the requirements in the CDA implementation guides mandating that all sections in a clinical document must have a title and a text element (i.e. a narrative block). \nc) A section consists entirely of subsections if it contains one or more <section> elements and does not contain any <entry> or participation elements.  Participation elements that occur within the document body contain the document's Actors and their Roles. Participation elements have equity with <entry> elements . A participant can be a human, an organisation or an IT system (e.g. an <author> element within a Pathology Report document). Participations are elaborated in the Participation Specification [NEHTA-0794:2011].\nd) An ancestor section is one which contains the target section.\n","M",1,"For each section <section> of the clinical document that is not the Administrative Observations section, or a section containing only a logo.\n\nPass the test where:\na) every section identified that does not have an ancestor section, and section does not consist entirely of sub-sections contains information in a narrative block <text>; and\nb) every section identified that does not contain a narrative block, and which has an ancestor section,  contains information in the narrative block of the ancestor section (this would otherwise be contained in the section's narrative block).\nElse, Fail the test.\n\nNOTE TO TESTER: The test case applies to custom-defined sections as well as sections specified in the relevant CDA implementation guide. \n","A section, that is not an Administrative Observation section or a section containing only a logo, contains a narrative block, unless it contains sub-sections and only sub-subsections, or the information that would otherwise be contained in that section is contained in the narrative of an ancestor section.","TBD",null,{"$f":"IF(H10=\"\",\"0\",IF(H10=\"Pass\",1,IF(H10=\"Fail\",0,IF(H10=\"TBD\",0,IF(H10=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D10)=48,H10=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Narr","TC-Narr-03","Appendix A. CDA Narratives [NEHTACDAIG]\nThe narrative block SHALL be encapsulated within the text component of the CDA section.\n",null,null,"No additional test case is needed as it is sufficient to test conformance to the Australian CDA Schema Extension [NEHTA-1599:2014], which is performed within test case TC-Doc-02 in the FS-Doc feature set.\n"," "]
["TS-Narr","TC-Narr-04","Appendix A. CDA Narratives [NEHTACDAIG]\nThe narrative contents SHALL conform to the requirements specified in the CDA Rendering Specification.\n",null,null,"No additional test case is needed as specific test cases are in a later part of this worksheet.\n"]
["TS-Narr","TC-Narr-05","Appendix A. CDA Narratives [NEHTACDAIG]\nThe narrative SHALL conform to the content requirements of the CDA specification [HL7CDAR2] and the XML Schema.\n",null,null,"No additional test case is needed as:\na) the test cases for the FS-Doc feature set to verify that the clinical document conforms to the Australian CDA Schema Extension [NEHTA-1599:2014]; and \nb) other test cases in the FS-Narr feature set verify that the narrative conforms to the requirements of the HL7 CDA R2 specification.\n"]
["TS-Narr","TC-Narr-06","024482 [DH-2481:2017]\nConformance level 1A\n\nThe body SHALL contain only one section <section>. The section SHALL include a section label <title> and one narrative block <text>. \nThe narrative block SHALL contain only <renderMultimedia> elements which reference attachments contained in <observationMedia> entry elements that are contained in the same section. \n\nNote: The conformance levels that apply to each clinical document type are specified in each clinical document's conformance profile.  For example, the conformance levels applicable to a Shared Health Summary clinical document are specified in the relevant conformance profile for Shared Health Summary. \n","C",1,"CONDITION: Conformance level 1A is claimed for the clinical document.\n\nPass the test where:\na) the clinical document contains one and only one section <section>;\nb) the <section> contains one and only one narrative block <text>;\nc) the narrative block contains at least one <renderMultiMedia> element; and\nd) each <renderMultiMedia> element references an <observationMedia> in an <entry> that references an attachment.\nElse, Fail the test.\n\nNOTE TO TESTER: Conformance to other aspects of the requirement, such as the presence of a <title>, is verified in the FS-Doc feature set.\n","The clinical document section and text and contained elements meet conformance level 1A when claimed. ","TBD",null,{"$f":"IF(H14=\"\",\"0\",IF(H14=\"Pass\",1,IF(H14=\"Fail\",0,IF(H14=\"TBD\",0,IF(H14=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D14)=48,H14=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Narr","TC-Narr-07","024482 [DH-2481:2017]\nConformance level 2, 3A and 3B\n\nThe body SHALL contain all sections that contain mandatory data elements (represented as narrative) as specified in the SCS and CDA IG. \n\nNote: The appropriate conformance levels that apply to each clinical document type are specified in the separate clinical document conformance profiles. \n","C",1,"CONDITION: Conformance level 2, 3A or 3B is claimed for the clinical document.\n\nPass the test where:\na) the document includes every section specified in the relevant CDA implementation guide as mandatory and having no parent section and all mandatory child sections where the parent section is mandatory; and\nb) each of these mandatory sections has a narrative block (noting qualifications stated in TC-Narr-02).\nElse, Fail the test.\n\nNOTE TO TESTER: \na) The sections specified in a CDA implementation guide are identified by the combination of the codeSystem and the code. Mandatory information includes the information specified in the CDA implementation guide mapping tables has having a minimum cardinality of \"1\" unless the conformance profile for the document type changes minimum cardinality to \"0\". See test case TC-Narr-02 for guidance about sections containing other sections.\nb) The mandatory sections are those specified in the CDA implementation guide as \"Essential\".\n","The clinical document includes every section specified in the relevant CDA implementation guide as containing mandatory information.\n\n","TBD",null,{"$f":"IF(H15=\"\",\"0\",IF(H15=\"Pass\",1,IF(H15=\"Fail\",0,IF(H15=\"TBD\",0,IF(H15=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D15)=48,H15=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Narr","END:   TS-Narr (General narrative)"]
["TS-Info","START:   TS-Info (Information content)"]
["TS-Info","TC-Narr-08","023706 [DH-2481:2017]\nA clinical document producing system SHALL conform to the requirements in the relevant structured content specification, the CDA IG, the Common Conformance Profile for Clinical Documents, and any specific conformance profile for the type of clinical document. Requirements in the specific conformance profile take precedence over requirements in the Common Conformance Profile. Similarly, requirements in the Common Conformance Profile take precedence over requirements in the structured content specification, and the CDA IG.\n\nNote: The requirement applies to all clinical document conformance levels and the implications for the narrative block is that if the clinical document has a section specified in the relevant structured content specification and CDA implementation guide, then the narrative block for that section must contain all the mandatory clinical information for that section. The sections specified in a CDA implementation guide are identified by the combination of the codeSystem \"1.2.36.1.2001.1001.101\" and the code. If the software cannot include all the mandatory information in the section's narrative blocks then the software should generate a custom-defined section.\n","C",1,"CONDITION:  The clinical document contains a section in the clinical document with the codeSystem \"1.2.36.1.2001.1001.101\" (these are sections specified in a structured content specification).\n\nPass the test where every section identified above, including multimedia referenced by <renderMultimedia> tags in the narrative block, contain the mandatory information for the corresponding sections.\nElse, Fail the test.\n\nNOTE TO TESTER: Mandatory information includes the information specified in the structured content specification data hierarchy as having a minimum cardinality of \"1\" unless the conformance profile for the document type changes minimum cardinality to \"0\". Similarly, the mandatory information includes the information specified in the structured content specification as having a minimum cardinality of \"0\" where the conformance profile for the document type changes minimum cardinality to \"1\". Conformance to other aspects of the requirement is verified in the other test cases in this conformance test specification. See test case TC-Narr-02 for guidance about sections containing other sections.\n\nA section's narrative blocks, including multimedia referenced by <renderMultimedia> tags in the narrative blocks, comprise the complete authenticated content of a section. Mandatory information cannot be included in a narrative block through the use of a <linkHtml> tag [HL7CDAR2].","The narrative blocks, including multimedia referenced by <renderMultimedia> tags in the narrative blocks, contain information that is mandatory for the conformance level and the requirements specified in the applicable CDA implementation guide.","TBD",null,{"$f":"IF(H18=\"\",\"0\",IF(H18=\"Pass\",1,IF(H18=\"Fail\",0,IF(H18=\"TBD\",0,IF(H18=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D18)=48,H18=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Info","TC-Narr-09","Appendix A. CDA Narratives [NEHTACDAIG]\nThe narrative is the human-readable and attestable part of a CDA document, and SHALL stand alone as an accurate representation of the content of the document without any need to consult entries in the body.\n\nThe narrative contents SHALL completely and accurately represent the clinical information encoded in the section. Content SHALL NOT be omitted from the narrative.\n\n025053 [DH-2481:2017]\nThe narrative for the following sections MAY be omitted:\n• Administrative Observations; and \n• a section containing a logo only.\n\nNote: Requirement 025053 overrides the requirements in CDA implementation guides mandating that all sections in a clinical document must have a title and a text element (i.e. a narrative block). \n\n","M",1,"For each section in the body of the clinical document that is not an Administrative Observations section, or a section that contains only a logo: \n\nPass the step where for each section, all clinical information that is part of the attested content and contained within the <entry> elements in the section is contained within the corresponding narrative block or within multimedia referenced by <renderMultimedia> tags in the narrative block. \nElse, Fail the step.\n\nNOTE TO TESTER (a-k): \na) A section is contained within <section> elements. \nb) The requirement does not preclude a narrative block from containing information in addition to that in <entry> elements. \nc) The corresponding narrative block is usually in the same section as the <entry> elements but maybe in an ancestor section (see TC-Narr-02).  \nd) Clinical information relevant to the narratives includes information in extensions and information which has been defined in the SCS and mapped by the CDA Implementation Guide to the document body unless specifically excluded (see following).\ne) Clinical information that is part of the attested content also includes information contained within multimedia referenced from an <observationMedia> or <regionOfInterest> element.\nf) Where an identifier has been specified as a “technical identifier” in the related Structured Content Specification (generally identified in a lighter colour within the Data Hierarchy diagram, and is accompanied by the description ‘This data element is intended for machine or system use only’ in its definition), it is not considered as clinical information, and need not be included in the narrative block.\ng) Where a CDA Implementation Guide specifies a fixed value for a data element, the value of the data elements need not be included in the narrative block.\nh) Information in the <entry> elements that is not clinically significant may be omitted from the narrative block. For example, where a dateTime element is clinical information, if the value of the element contains a date, time and time zone, then the time and time zone need not be included in the narrative block if only the date is clinically significant (dateTime data type elements are defined in the related Structured Content Specification). \ni) An exclusion statement is classified as containing clinical information and therefore the information contained within its <entry> elements shall also be represented in the corresponding narrative block, and convey a similar meaning.\nj) The representation of data types does not matter as long as it conforms to the semantic definition of the data type. For example, the representation of Boolean values can be the words \"true\" and \"false,\" \"yes\" and \"no,\" the numbers 0 and 1, any two signs that are distinct from each other.  (See HL7 Version 3 Standard: Data Types - Abstract Specification [HL72004].)\nk) The section's title, if present, is considered to be a part of the narrative content (section 4.3.2.3 [HL7CDAR2]). For example, in a discharge summary section with the section/title \"Ceased Medications\" there is no need to state in the section/text element that the status of a medication is ceased.","For each section in the clinical document, all clinical information contained within the <entry> elements in the section are contained within the corresponding narrative block or within multimedia referenced by <renderMultimedia> tags in the narrative block.","TBD",null,0,{"$f":"IF(AND(BGCol(D19)=48,H19=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Info",null,null,null,2,"Fail the step if the clinical information in any narrative section contradicts clinical information in another section of the clinical document.\nElse, Pass the step.\n\nNOTE TO TESTER: Some types of documents contain a section containing a clinical synopsis, which is information or comments about the clinical management of the patient, and the prognosis of diagnoses or problems identified during the healthcare. The clinical synopsis should not be used to record information that may be included in a specialised section, such as sections for medications, adverse reactions, immunisations, or medical history, but if it does then the information must not be in conflict. For example, a clinical synopsis narrative stating that a medication has been ceased and a medications narrative stating that the same medication has been newly prescribed are in conflict.","No clinical information in any narrative section contradicts any information in any another section.","TBD",null,0,{"$f":"IF(AND(BGCol(D20)=48,H20=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Info",null,null,null,3,"Check that information (including multimedia referenced by <renderMultimedia> tags) is presented so the reader can understand the meaning and context.\n\nFail the step where the reader cannot understand the meaning or context of the information contained in the narrative block, including multimedia referenced by <renderMultimedia> tags in the narrative block.\nElse, Pass the step\n\nNOTE TO TESTER: As an example of what might be meaningful or otherwise. For example, \"3\" is not meaningful, whereas \"dose: 3\" or \"3 capsules\" may be meaningful. This could be for multiple types of information.\n","The information in narrative blocks, including multimedia referenced by <renderMultimedia> tags in the narrative blocks, is legibly presented in meaning and context.","TBD",null,0,{"$f":"IF(AND(BGCol(D21)=48,H21=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Info",null,null,null,4,"Check time intervals; any low, width or high date and/or times values that are present in <entry> elements are also present in the corresponding narrative block, including multimedia referenced by <renderMultimedia> tags in the narrative block.\n\nFail the step where any time intervals or date/time elements in the structured data are not present in corresponding narrative blocks, including multimedia referenced by <renderMultimedia> tags in those narrative blocks.\nElse, Pass the step.\n","Time intervals or date/time elements in the structured data are present in corresponding narrative blocks, including any multimedia referenced by <renderMultimedia> tags","TBD",null,0,{"$f":"IF(AND(BGCol(D22)=48,H22=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Info",null,null,null,5,"Fail the step where:\na) the text colour is identical to the background colour; or\nb) the text and background are different colours but the text cannot be differentiated.\nElse, Pass the step.\n\nNOTE TO TESTER:\na) Text will be presented in a readable format, such that it is not concealed by the choice of foreground and background colours. This can be determined by inspecting the stylecode elements without having to actually render the document. \nb) Where an element containing a styleCode attribute is nested within another element containing a styleCode attribute, the style effects are additive as in the following example (see section 4.3.5.11 of [HL7CDAR2]):\n\nEg: \n<section>\n    <text>\n   <content styleCode=\"Bold\">This is rendered bold, \n        <content styleCode=\"Italics\">this is rendered bold and italicized,</content> this is rendered bold. \n   </content>\n       <content styleCode=\"Bold Italics\">This is also rendered bold and italicized.</content>\n     </text>\n </section>\n","The narrative text is a different colour to the  background.","TBD",null,{"$f":"IF(H23=\"\",\"0\",IF(H23=\"Pass\",1,IF(H23=\"Fail\",0,IF(H23=\"TBD\",0,IF(H23=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D23)=48,H23=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Info",null,null,"C",6,"CONDITION:  physical quantity elements are present in <entry> elements.\n\nCheck physical quantities (i.e. data elements of the HL7 \"PQ\" data type); the value and unit or measure are included in the corresponding narrative block, including any attachments referenced from the narrative block.\n\nFail the step where for any physical quantity elements that are present in any <entry> elements, the value and unit of measure is not present in corresponding narrative blocks, including multimedia referenced by <renderMultimedia> tags in the narrative blocks.\nElse, Pass the step.\n\nNOTE TO TESTER:If a physical quantity in an <entry> contains a 'low' element with inclusive=\"false\" then the narrative must indicate that the low boundary is not included and if inclusive=\"true\" or if there is no 'inclusive' attribute, then the narrative must not state that the low boundary is not included. The same requirement applies for the 'high' element.","Physical quantity elements have their value and unit of measure presented in both the <entry> elements and corresponding narrative blocks, including multimedia referenced by <renderMultimedia> tags in those narrative blocks.","TBD",null,0,{"$f":"IF(AND(BGCol(D24)=48,H24=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Info",null,null,null,7,"CONDITION:  character string data elements are present in <entry> elements.\n\nCheck character strings (i.e. data elements of the HL7 \"ST\" or \"ED\" data types); the character string is included in the corresponding narrative block, including multimedia referenced by <renderMultimedia> tags in the narrative block.\n\nFail the step where for any character string elements that are present in any <entry> elements, the character string is not present in corresponding narrative blocks, including multimedia referenced by <renderMultimedia> tags in the narrative blocks.\nElse, Pass the step.\n","Character strings elements have their character strings presented in both the <entry> elements and corresponding  narrative blocks, including multimedia referenced by <renderMultimedia> tags in the narrative blocks.","TBD",null,0,{"$f":"IF(AND(BGCol(D25)=48,H25=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Info",null,null,null,8,"CONDITION: Tables or lists are present in narrative blocks.\n\nWhere any information in an <entry> element is included in tables or lists in a narrative block, including multimedia referenced by <renderMultimedia> tags in the narrative block, verify that there is a table row or a list item for each <entry> element in that section.\n\nFail the step where for any table or list provided in a narrative block, including multimedia referenced by <renderMultimedia> tags in the narrative block, all <entry> elements from the related section are not included in the table or list,\nElse, Pass the step.\n","Where a table or list is provided in a narrative block, including multimedia referenced by <renderMultimedia> tags in the narrative block, the information from all <entry> elements in the related section are included in the table or list.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D26)=48,H26=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Info",null,null,null,9,"CONDITION: <entry> elements have a nullFlavor.\n\nCheck that when a nullFlavor is included in an <entry> element that equivalent information is included in the corresponding narrative block, including multimedia referenced by <renderMultimedia> tags in the narrative block.\n\nFail the step where:\na) for any <entry> element that has a nullFlavor, the text provided in the corresponding narrative block, including multimedia referenced by <renderMultimedia> tags in the narrative block, does not have the same meaning as the nullFlavor code; or\nb) for any <entry> element which has a nullFlavor, the nullFlavor used is not suitable for the context of the <entry> element for which it has been provided.\nElse, Pass the step.\n\nNOTE TO TESTER: The nullFlavor codes and names are from ISO standard ISO21090. These names or text with the same meaning may be used in the narrative blocks. (scroll down for the full list - ends NA).\n\nnullFlavor=\"PINF\", display name = \"positive infinity\"\nnullFlavor=\"NINF\", display name = \"negative infinity\"\nnullFlavor=\"ASKU\", display name = \"asked but unknown\"\nnullFlavor=\"NAV\", display name = \"temporarily unavailable\"\nnullFlavor=\"NASK\", display name = \"not asked\"\nnullFlavor=\"QS\", display name = \"sufficient quantity\"\nnullFlavor=\"TRC\", display name = \"trace\"\nnullFlavor=\"MSK\", display name = \"masked\"\nnullFlavor=\"NA\", display name = \"not applicable\"","The nullFlavor display name or text with equivalent meaning is included in the corresponding narrative blocks, including multimedia referenced by <renderMultimedia> tags in the narrative blocks. NullFlavor is also appropriate to the context of the <entry> element it represents.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D27)=48,H27=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Info",null,null,null,10,"CONDITION: Terminology codes are present in <entry> elements. \n\nPass this test where text in the narrative block, including multimedia referenced by <renderMultimedia> tags in the narrative block, is synonymous with the value of the displayName, \nElse, Fail the step.\n","Where Terminology codes are present in <entry> elements, the text in the narrative block, including multimedia referenced by <renderMultimedia> tags in the narrative block, is synonymous with the value of the displayName. ","TBD",null,{"$f":"IF(H28=\"\",\"0\",IF(H28=\"Pass\",1,IF(H28=\"Fail\",0,IF(H28=\"TBD\",0,IF(H28=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D28)=48,H28=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Info",null,null,null,11,"CONDITION: A data element in an <entry> element contains a code and no displayName.\n\nPass this test if the concept described by the code is contained within the associated narrative block.\nElse, Fail the step.\n\nNOTE TO TESTER: If the data element contains a code and originalText then TC-Types-66 ensures that the code and the originalText describe the same concepts, so the test step is most applicable for data elements containing a code and no originalText or displayName. The test only applies to data elements containing clinical information. The clinical information may be in the narrative block text or multimedia referenced by <renderMultiMedia> tags in the narrative block.\n","When a displayName is not present, the value of the preferred term corresponding to the code in the code system is the text in the narrative block, including multimedia referenced by <renderMultimedia> tags in the narrative block and is synonymous with the value of the preferred term.","TBD",null,{"$f":"IF(H29=\"\",\"0\",IF(H29=\"Pass\",1,IF(H29=\"Fail\",0,IF(H29=\"TBD\",0,IF(H29=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D29)=48,H29=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Info",null,null,null,12,"CONDITION: Clinical document contains an Exclusion statement.\n\nPass the test  \nWhen code=\"01\", displayName=\"None known\" and the meaning is \"No information about the item is known\".\nor\nWhen code=\"02\", displayName=\"Not asked\" and the meaning is \"No information about the item is available because the patient was not asked or not able to be asked\".\nor\nWhen code=\"03\", displayName=\"None supplied\" and the meaning is \"No information about the item is supplied\".\nElse, Fail the step.\n\nNOTE TO TESTER: Where the item is either adverse reactions; medications; problems and diagnoses; procedures; or immunisations, the text in the narrative must be consistent with the meaning and need not be the same words.\n","The information from all exclusion statements in the related section is included in the corresponding narrative blocks with the same meaning.","TBD",null,0,{"$f":"IF(AND(BGCol(D30)=48,H30=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Info",null,null,null,13,"CONDITION: External objects referenced from within an <entry> element.\n\nFail the step where clinical information referenced from any <externalAct>, <externalDocument>, <externalObservation> or <externalProcedure> in the <entry> elements is not referenced by <linkHtml> in the corresponding narrative.\nElse, Pass the step.\n\nNOTE TO TESTER: In the <entry> clinical information that is not part of the attested content is represented by an <externalAct>, <externalDocument>, <externalObservation> or <externalProcedure>. In the narrative a <linkHtml> element directly references an object using an absolute URI or a relative reference and cannot reference an <externalAct>, <externalDocument>, <externalObservation> or <externalProcedure> as they do not have an ID element to reference. Therefore the <linkHtml>, <externalAct>, <externalDocument>, <externalObservation> or <externalProcedure> elements must all directly reference the same object.\n","All external objects referenced from within an <entry> element are referenced from the corresponding narrative block using a <linkHtml> element.","TBD",null,0,{"$f":"IF(AND(BGCol(D31)=48,H31=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Info",null,null,null,14,"CONDITION: An <entry> element contains a reference to multimedia from an <observation>, <act> or <observationMedia> element.\n\nPass the step where the multimedia is not part of the attested content.\n Else if the reference to the multimedia is from an <observationMedia> element then Pass the step where the corresponding narrative block contains a <renderMultiMedia> element that references the <observationMedia> element.\n Else if the reference to the multimedia is from an <observation> or an <act> element then Pass the step where the section contain an <observationMedia> element that also references the multimedia and the corresponding narrative block contains a <renderMultiMedia> element that references the <observationMedia> element.\n Else, Fail the step.\n\nNOTE TO TESTER: \na) An example of multimedia is not part of the attested content is an <observationMedia> element that references a logo. \n\nb) Section 4.3.5.2 [HL7CDAR2]\nMultimedia that is integral to a document and part of the attestable content of the document requires the use of the ObservationMedia CDA entry, which is referenced by the <renderMultiMedia> element ().\n\nNote: A <renderMultiMedia> element cannot directly reference the multimedia so it must reference the observationMedia element (section 4.3.5.6 [HL7CDAR2]). An <observation> and an <act> element may also reference multimedia that is part of the attestable content (sections 3.1.1 and 3.1.13 [HL72013]) but as a <renderMultiMedia> element cannot reference <observation> and <act> elements in order to meet the requirement that in a sections' content must also be the narrative block, the section must also contain an <observationMedia> element that references the same multimedia that is refenced from the <observation> or <act> element.\n","All the objects (<observation>, <act> or <observationMedia>) referenced from within an <entry> element are referenced from the corresponding narrative block using a <renderMultiMedia> element.","TBD",null,{"$f":"IF(H32=\"\",\"0\",IF(H32=\"Pass\",1,IF(H32=\"Fail\",0,IF(H32=\"TBD\",0,IF(H32=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D32)=48,H32=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Info","TC-Narr-10","Appendix A. CDA Narratives [NEHTACDAIG]\nWhere available, the originalText SHOULD be found in the narrative, otherwise, the displayName SHOULD be found in the narrative.\n\nNote: The context of the requirement is originalText and displayName in codedText or codeableText data elements defined in a structured content specification. The specifications allow for the presence of a nullFlavor and no originalText and displayName.\n","O",1,"Find all data elements listed in the Structured Content Specification and Participation Data Specification [NEHTA-0794:2011] of the CodedText or CodeableText data types.\n\nFind every occurrence of these data elements in the clinical document <entry> elements, pass the test where: \na) each data element containing originalText, the originalText is a reference to a clinical document narrative, or the value of the originalText is included in the corresponding narrative block, including multimedia referenced by <renderMultimedia> tags in the narrative block; or\nb) each data element containing a displayName and no originalText includes the value of the displayName in the corresponding narrative block, including multimedia referenced by <renderMultimedia> tags in the narrative block; or\nElse, Fail the test.\n\nNOTE TO TESTER: Example 5 in the HL7 Clinical Document Architecture, Release 2 [HL7CDAR2] shows how an originalText can reference into a narrative block. See test case TC-Narr-02 for guidance about sections containing other sections.","For all data elements listed in the Structured Content Specification and Participation Data Specification [NEHTA-0794:2011] as being of the CodedText or CodeableText data type within the clinical document <entry> elements: \n\n- For each data element containing originalText, the originalText is a reference to a clinical document narrative, or the value of the originalText is included in the corresponding narrative block, including multimedia referenced by <renderMultimedia> tags in the narrative block.\n- Each data element containing no originalText includes the value of the displayName in the corresponding narrative block, including multimedia referenced by <renderMultimedia> tags in the narrative block.  \n- Each data element with a nulflavor and neither a displayName or Originaltext includes the display name of the nullFlavor in the narrative block, including multimedia referenced by <renderMultimedia> tags in the narrative block.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D33)=48,H33=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Info","END:   TS-Info (Information content)"]
["TS-Auto","START:  TS-Auto (Auto generated)"]
["TS-Auto","CONDITION: Test set TS-Auto applies ONLY when the narrative information is automatically generated. Therefore all test cases in this set are either conditional or optional."]
["TS-Auto",null,null,null,null,"NOTE TO TESTER: The following describes how to determine if narrative blocks have been automatically generated.\n\na) Where at least one <entry> element associated with a narrative block contains the typeCode=\"DRIV\" then the narrative block has been automatically generated from the information in the <entry> elements. Section 4.3.4.2 of  [HL7CDAR2]  states \"The entries sourced from a Section may have a mix of ActRelationship typeCodes. In such a case, the union of the targets with a \"DRIV\" relationship are those used to generate the narrative block, and are those that, taken in total, are equivalent to the narrative block\".\n\nb) Where there is no <entry> with typeCode=\"DRIV\" then the clinical document does not state anything about the relationship between the narrative and the  <entry>, in this case, the software designer needs to be consulted to determine if the narrative blocks are automatically generated.\n\nc) Requirement 025053 in the common conformance profile states that narratives may be omitted from the Administrative Observations section, and a section containing a logo only. That means that even if there is information in the <entry> elements for these sections then the narrative block may be absent. This applies even if the <entry> element has typeCode=\"DRIV\".\n"]
["TS-Auto","TC-Narr-11","CDA-RS 13 [NEHTA-1199:2012]\nHI Service identifiers (e.g. IHI, HPI-O and HPI-I) values SHALL be formatted as four groups of four digits with a space separating each four-digit group (e.g. 8300 0000 0000 0000 for an IHI).\n","C",1,"CONDITION: Narrative blocks are automatically generated and contain HI Service identifiers.\n\nPass the test where all HI Service identifiers in narrative blocks are in four groups of four digits with a space separating each four-digit group.\nElse, Fail the test.\n\nNOTE TO TESTER: The HI Service identifiers that may be present in the narrative blocks can be obtained from the clinical document header and structured data in the clinical document body.","All HI Service Identifiers in narrative blocks are in four groups of four digits with a space separating each four-digit group.","TBD",null,{"$f":"IF(H38=\"\",\"0\",IF(H38=\"Pass\",1,IF(H38=\"Fail\",0,IF(H38=\"TBD\",0,IF(H38=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D38)=48,H38=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Auto","TC-Narr-12","CDA-RS 14 [NEHTA-1199:2012]\nTime values SHALL be formatted with a one-digit or two-digit hour and two-digit minute separated by a colon, using a 24 hour clock (e.g. 13:00 for 1:00pm or 1:00 for 1:00am).\n","C",1,"CONDITION: Narrative blocks are automatically generated with time values\n\nPass the test where all time values in narrative blocks are formatted with a one-digit or two-digit hour and two-digit minute separated by a colon, using a 24-hour clock.\nElse, Fail the test.\n\nNOTE TO TESTER: The time values that may be present in the narrative blocks can be obtained from the DateTime values in the clinical document header and structured data in the clinical document body. The CDA Rendering Specification [NEHTA-1199:2012] does not state that the time component of a DateTime data element must be included in a narrative block.\n","All time values in narrative blocks have a one-digit or two-digit hour and two-digit minute separated by a colon, using a 24 hour clock.\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D39)=48,H39=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Auto","TC-Narr-13","CDA-RS 15 (a) [NEHTA-1199:2012]\nTime zone values SHALL be formatted as follows:\n\nIf a time zone is required, it SHALL be formatted using a plus (+) or minute (-) sign immediately after the time, followed by the number of hours and minutes ahead or behind UTC time respectively.\n\nNote: \"if a time zone is required\" refers to a business rather than a software requirement for time zones in narratives.\n","C",1,"CONDITION: Narrative blocks are automatically generated with timezone values.\n\nPass the test where all time zone values are formatted using a plus (+)  or a minus (-) sign immediately after the time, followed by a number of hours and minutes ahead or behind UTC time,\nElse, Fail the test.\n\nNOTE TO TESTER: The time zone values that may be present in the narrative blocks can be obtained from the DateTime values in the clinical document header and structured data in the clinical document body. If the date and/or time values are in a different time zone then the time zone is expected to be included in a narrative block (see requirement CDA-RS 49 (b)), otherwise there is no need for date and time values in a narrative block to contain a time zone.\n","All time zone values in narrative blocks use a plus (+) or minus (-) sign immediately after the time, followed by the number of hours and minutes ahead or behind UTC time respectively.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D40)=48,H40=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Auto","TC-Narr-14","CDA-RS 15 (b) [NEHTA-1199:2012]\nTime zone values SHALL be formatted as follows:\n\nThe hours and the minutes for the time zone SHALL both be two-digit values with no other characters separating the number of hours and minutes (e.g. 13:00+1000 or 1:00-0600).\n","C",1,"CONDITION: Narrative blocks are automatically generated with timezone values.\n\nPass the test where all time zones have the hours and the minutes as two-digit values with no other characters separating the number of hours and minutes.\nElse, Fail the test.\n\nNOTE TO TESTER: The time values that may be present in the narrative blocks can be obtained from the DateTime values in the clinical document header and structured data in the clinical document body. The CDA Rendering Specification [NEHTA-1199:2012] does not state that the time component of a DateTime data element must be included in a narrative block.\n","All time zone values in narrative blocks have the hours and the minutes both being two-digit values with no other characters separating the number of hours and minutes.","TBD",null,0,{"$f":"IF(AND(BGCol(D41)=48,H41=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Auto","TC-Narr-15","CDA-RS 16 (a) [NEHTA-1199:2012]\nDate values containing day, month, and year SHALL be formatted as follows:\n\nDate values containing day, month, and year SHALL be formatted with a one-digit or two-digit day, three-character month, and four-digit year. i.e. 'd-Mmm-yyyy' or 'dd-Mmm-yyyy'\n","C",1,"CONDITION: Narrative blocks are automatically generated with date values.\n\nPass the test where all date values have the day as either one-digit or two-digits, the month value as three-characters, and the year value as four-digits.\nElse, Fail the test.\n\nNOTE TO TESTER: The Day values that may be present in the narrative blocks can be obtained from the DateTime values in the clinical document header and structured data in the clinical document body.","All date values in narrative blocks have a one-digit or two-digit day, a three-character month, and a four-digit year.","TBD",null,0,{"$f":"IF(AND(BGCol(D42)=48,H42=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Auto","TC-Narr-16","CDA-RS 16 (b) [NEHTA-1199:2012]\nDate values containing day, month, and year SHALL be formatted as follows:\n\nThe three-character month SHALL be the first three characters of the month with the first letter capitalised. i.e. month is 'Mmm'\n","C",1,"CONDITION: Narrative blocks are automatically generated with date values.\n\nPass the test where all date values have the three-character month containing the first three letters of the month with the first letter capitalised.\nElse, Fail the test.\n\nNOTE TO TESTER: The Date values expected to be in the narrative blocks can be obtained from the clinical document header and structured data in the clinical document body.\n","All date values in narrative blocks have a three-character month which contains the first three characters of the month with the first letter capitalised.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D43)=48,H43=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Auto","TC-Narr-17","CDA-RS 16 (c) [NEHTA-1199:2012]\nDate values containing day, month and year SHALL be formatted as follows:\n\nThe day, month and year SHALL be separated with a separator which SHALL be either a single space or a single dash (e.g. “10 Jul 2010” or “1-Jan-2011”).\n","C",1,"CONDITION: Narrative blocks are automatically generated with date values.\n\nPass the test where all date values have the day, month, and year separated only with one of the following separators, either a single space or a single dash.\nElse, Fail the test.\n\nNOTE TO TESTER: The Date values expected to be in the narrative blocks can be obtained from the clinical document header and structured data in the clinical document body.","All date values in narrative blocks have the day, month and year separated with a either a single space or a single dash (e.g. “10 Jul 2010” or “1-Jan-2011”).\n","TBD",null,0,{"$f":"IF(AND(BGCol(D44)=48,H44=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Auto","TC-Narr-18","CDA-RS 16 (d) [NEHTA-1199:2012]\nDate values containing day, month and year SHALL be formatted as follows:\n\nSeparators SHALL NOT be used interchangeably within a single date i.e. 1-Jan 2012 is NOT ALLOWED due to a space and a dash being used as a separator character.\n","C",1,"CONDITION: Narrative blocks are automatically generated with date values.\n\nPass the test where all date values do not use the separators (space or dash) interchangeably within a single date (i.e. within a single date either a space or a dash is used as the separator at both separation points).\nElse, Fail the test.\n\nNOTE TO TESTER: The Date values expected to be in the narrative blocks can be obtained from the clinical document header and structured data in the clinical document body.\n","All date values in narrative blocks use the same separator character within a single date and separators are not used interchangeably within a single date (i.e. 1-Jan 2012 is NOT valid due to a space and a dash being used as a separator character).\n","TBD",null,0,{"$f":"IF(AND(BGCol(D45)=48,H45=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Auto","TC-Narr-19","CDA-RS 17 (a) [NEHTA-1199:2012]\nDate and time values made up of a date value and time value SHALL be formatted as follows:\n\nDate and time values made up of a date value and time value SHALL be formatted with the date first followed by the time with a space between the two.\n","C",1,"CONDITION: Narrative blocks are automatically generated with date and time values.\n\nPass the test where all DateTime values are formatted with the date first followed by the time with a space between the two.\nElse, Fail the test.\n\nNOTE TO TESTER: The DateTime values expected to be in the narrative blocks can be obtained from the clinical document header and structured data in the clinical document body. The CDA Rendering Specification [NEHTA-1199:2012] does not state that the time component of a DateTime data element must be included in a narrative block.\n","All DateTime values in narrative blocks have the date first followed by the time with a space between the two.\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D46)=48,H46=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Auto","TC-Narr-20","CDA-RS 17-b [NEHTA-1199:2012]\nDate and time values made up of a date value and time value SHALL be formatted as follows:\n\nThe individual date and individual time values SHALL be formatted as described in this document (e.g. \"10 Jul 2010 1:00\" or \"1 Jul 2010 1:00+1000\").\n",null,null,"No additional test case is needed as all DateTime values tested individually in test cases TC-Narr-12, TC-Narr-13, TC-Narr-14, TC-Narr-15, TC-Narr-16, TC-Narr-17, TC-Narr-18, and TC-Narr-19.\n"]
["TS-Auto","TC-Narr-26","CDA-RS 49 (a) [NEHTA-1199:2012]\nTime zones in narrative blocks:\n\nAuthoring Systems SHOULD ensure that all date and/or time values in the narrative blocks of the CDA document body are in the same time zone as the document itself.\n","O",1,"Mark the test N/A where there are no date and/or time values contained in any narrative blocks.\nPass the test where:\na) every date and/or time value in the narrative blocks is accompanied with a time zone, and every time zone value in the narrative blocks is the same as the document authored date and/or time; or\nb) every date and/or time value in the narrative blocks do not have a time zone.\nElse, Fail the test.\n\nNOTE TO TESTER: \na) The date and/or time values expected to be in the narrative blocks can be obtained from the clinical document header and structured data in the clinical document body.\nb) The date and/or time values are contained within a dateTime data type as defined in the relevant Structured Content Specification.","The date and/or time values in the narrative blocks of the clinical document body are the same time zone as the document itself, or the narrative blocks do not contain time zones.\n\n","TBD",null,{"$f":"IF(H48=\"\",\"0\",IF(H48=\"Pass\",1,IF(H48=\"Fail\",0,IF(H48=\"TBD\",0,IF(H48=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D48)=48,H48=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Auto","TC-Narr-27","CDA-RS 49 (b) [NEHTA-1199:2012]\nTime zones in narrative blocks:\n\nIf the date and/or time values are in a different time zone, the time zone SHALL be specified clearly so that the reader understands which time zone a specific date and/or time is in.\n","C\n",1,"CONDITION:  Time zones are provided, or all dates and times are not in the same time zone.\n\nPass the test where:\na) all date and time values that belong to different time zones are accompanied with the related time zone value; or\nb) all date and time values that belong to a different time zone to the document authored dateTime, are accompanied with the related time zone value.\nElse, Fail the test.\n\nNOTE TO TESTER: If time zones are included for the local date and time they are obtained from the document authored dateTime.","Date and/or time values that belong to different time zones are accompanied by the correct time zone value.\n","TBD",null,{"$f":"IF(H49=\"\",\"0\",IF(H49=\"Pass\",1,IF(H49=\"Fail\",0,IF(H49=\"TBD\",0,IF(H49=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D49)=48,H49=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Auto","TC-Narr-21","CDA-RS 18 [NEHTA-1199:2012]\nPerson name values SHALL be formatted in the following order: Name Title(s), Given Name(s), Family Name(s), Name Suffix(es) (e.g. “Prof Sir John Gregory Citizen III MP”).\n","C",1,"CONDITION: Narrative blocks are automatically generated with person name values.\n\nPass the test where all person names are formatted to display in the following order: Name Title(s), Given Name(s), Family Name(s), Name Suffix(es).\nElse, Fail the test.\n\nNOTE TO TESTER: The person name attribute values may be obtained from the clinical document header and matched against the narrative blocks.\n","All person name values in narrative blocks are in the following order: Name Title(s), Given Name(s), Family Name(s), Name Suffix(es).\n\n","TBD",null,{"$f":"IF(H50=\"\",\"0\",IF(H50=\"Pass\",1,IF(H50=\"Fail\",0,IF(H50=\"TBD\",0,IF(H50=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D50)=48,H50=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Auto","TC-Narr-22","CDA-RS 19 [NEHTA-1199:2012]\nPatient family name values SHALL be formatted in uppercase letters as part of their name (e.g. “Mr Fred CITIZEN”).\n","C",1,"CONDITION: Narrative blocks are automatically generated with person name values.\n\nPass the test where all patient family names are formatted and displayed in uppercase letters.\nElse, Fail the test.\n\nNOTE TO TESTER: The patient's family name obtained from the clinical document header can be matched against the narrative blocks to find the instances of the family name.\n","All patient family name values in narrative blocks are in upper case letters (e.g. \"Mr Fred CITIZEN\").\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D51)=48,H51=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Auto","TC-Narr-23","CDA-RS 20 [NEHTA-1199:2012]\nSex values SHALL be formatted in full with no abbreviations (e.g. “Male”, “Female”, “Intersex or Indeterminate”, “Not stated / Inadequately described”).","C",1,"CONDITION: Narrative blocks are automatically generated with sex values.\n\nPass the test where all Sex values are formatted in full with no abbreviations.\nElse, Fail the test.\n\nNOTE TO TESTER: The fully qualified values for the presentation of the Sex field may be obtained from the values contained within the structured data.\nThe full descriptions for Sex values are; “Male”, “Female”, “Intersex or Indeterminate”, “Not stated / Inadequately described”.\n","All sex values in narrative blocks are provided in full with no abbreviations.\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D52)=48,H52=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Auto","TC-Narr-24","CDA-RS 21 [NEHTA-1199:2012]\nNational and International phone number values SHOULD be formatted according to the ITU-T E.123 standard [ITU-T2001] e.g. (07) 123 4567 and +44 208 123 4567.\n\nNote: The ITU-T E.123 standard states:\ni. The international prefix symbol should be + (plus) and should precede the country code in the international number.\nii. The symbol ( ) (parentheses) should be used to indicate that the digits within the ( ) are not always dialled.\niii. Spacing symbols are symbols which are used solely to separate parts of a telephone number from each other. In the international number, spacing shall occur between the country code and the trunk code and between the trunk code and the subscriber number. The major separation among digits in a telephone number (national or international) should occur between trunk code and subscriber number.\n","O",1,"Where the narrative block is automatically generated and the <entry> element has the typeCode=\"DRIV\" then:\nMark the test N/A if:\na) there are no phone numbers in any of the narrative blocks; or\nb) any phone number in any of the narrative blocks' corresponding <entry> elements are not in ITU-T E.123 format.\n\nPass the test where all phone numbers in narrative blocks are in ITU-T E.123 format (i.e. the <entry> elements associated with the narrative block have phone numbers in ITU-T E.123 format so that format is expected to be used in the corresponding narrative block).\nElse, Fail the test (phone numbers in the <entry> elements are in ITU-T E.123 format, but they are not in that format in the corresponding narrative block).\n\nWhere the narrative block is  automatically generated and the <entry> element has the typeCode=\"COMP\" then:\nPass the test where all phone numbers in narrative blocks are in ITU-T E.123 format (i.e. the <entry> elements associated with the narrative block have phone numbers in ITU-T E.123 format so that format is expected to be used in the corresponding narrative block).\nElse, Mark the test N/A.\n\nNOTE TO TESTER: \na) If the phone numbers in the <entry> elements are not in the ITU-T E.123 format then it is assumed that the source of the phone numbers is not provided in ITU-T E.123 format.\nb) An <entry> element will only have a typeCode of \"DRIV\" or \"COMP\".","All National and International phone number values in narrative blocks are provided according to the ITU-T E.123 standard [ITU-T2001] e.g. (07) 123 4567 and +44 208 123 4567.\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D53)=48,H53=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Auto","TC-Narr-25","CDA-RS 22 [NEHTA-1199:2012]\nEmail address values SHALL be formatted according to the ITU-T E.123 standard [ITU-T2001] e.g. fred@example.com.\n\nNote: The ITU-T E.123 standard states an electronic mail address, if present, should be in the SMTP (Simple Mail Transfer Protocol) style.\n","C",1,"CONDITION: Narrative blocks are automatically generated with email values.\n\nPass the test where all email address values conform to the SMTP style as specified in ITU-T E.123.\nElse, Fail the test.\n\nNOTE TO TESTER: The email addresses may be obtained from the clinical document header and matched against the narrative blocks.\n","The clinical document narrative blocks contains email address values according to the SMTP style as specified in ITU-T E.123 [ITU-T2001] e.g. fred@example.com.\n","TBD",null,{"$f":"IF(H54=\"\",\"0\",IF(H54=\"Pass\",1,IF(H54=\"Fail\",0,IF(H54=\"TBD\",0,IF(H54=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D54)=48,H54=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Auto","TC-Narr-93","Section 4.3.4.2 [HL7CDAR2] \nDefinition of typeCode=\"DRIV\": The narrative was rendered from the CDA Entries, and contains no clinical content not derived from the entries.\n\nThe entry relationship \"DRIV\" (is derived from) can be used in the special case where the narrative is fully derived from CDA Entries. \n\nWhen a report consisting entirely of structured entries is transformed into CDA, the encoding application must ensure that the authenticated content (narrative plus multimedia) is a faithful and complete rendering of the clinical content of the structured source data. \n\nIn this case, narrative plus multimedia does not contain any clinical content that is not present in the Entries. \n","C",1,"CONDITION: A narrative block has at least one corresponding <entry typeCode=\"DRIV\">\n\nPass the test where all clinical information in the narrative and multimedia is also present in the <entry> elements with typeCode=\"DRIV\".\nElse, Fail the test.\n\nNOTE TO TESTER: The requirement does not state that all information in the CDA Entries with typeCode=\"DRIV\" must appear in the narrative. Although clinical information in the <entry> elements must be included in the narrative (see test case TC-Narr-09) the encoding application may omit non-clinical information from the narrative.\n","The narrative plus multimedia does not contain any clinical content that is not present in the associated <entry typeCode=\"DRIV\"> elements. ","TBD",null,0,{"$f":"IF(AND(BGCol(D55)=48,H55=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Auto","END:   TS-Auto (Auto generated)"]
["TS-Mark","START:   TS-Mark (Markup content)"]
["TS-Mark","TC-Narr-28","024482 [DH-2481:2017]\nConformance level 1B, 2, 3A and 3B\n\nThe narrative block SHALL contain human-readable markup content.\n\nNote: The appropriate conformance levels that apply to each clinical document type are specified in the separate clinical document conformance profiles. Additionally, 4.2 Conformance Requirements in [NEHTA-1199:2012] details the Authoring Systems specifications for narrative blocks.","C",1,"CONDITION: The conformance level 1B, 2, 3A or 3B is claimed for the clinical document.\n\nFor every narrative block in the clinical document, verify that there is no markup content that is not listed in the CDA Rendering specification [NEHTA-1199:2012].\n\nPass the test where for each narrative block in the clinical document there is no markup content that is not listed in the CDA Rendering Specification [NEHTA-1199:2012].\nElse, Fail the test.\n\nNOTE TO TESTER: Markup instructs a rendering system to carry out appropriate formatting actions. The rationale for the test step is that a narrative is human readable only if the markup content can be fully processed by a rendering system conformant to the CDA Rendering Specification [NEHTA-1199:2012]. By contrast, other types of markup tags (e.g. RTF markup tags) in a narrative are likely to be displayed to a user rather than be processed by a rendering system, potentially making the narrative unreadable.\n\nMarkup should not be confused with XML character escapes such as “&gt;”, “&#62;” or “&#x3e;” used to include special Unicode characters in XML, [W3C2008], [W3C2013].","Each narrative block in the clinical document contains only markup content that is listed in the CDA Rendering Specification [NEHTA-1199:2012].\n","TBD",null,{"$f":"IF(H58=\"\",\"0\",IF(H58=\"Pass\",1,IF(H58=\"Fail\",0,IF(H58=\"TBD\",0,IF(H58=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D58)=48,H58=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Mark","TC-Narr-29","CDA-RS 43 [NEHTA-1199:2012]\nAuthoring Systems SHALL NOT populate the narrative block with free text that is not contained in an allowed narrative block element e.g. <paragraph> or <content>.\n","M",1,"Pass the test where each narrative block contains free text that is contained within an allowed narrative block element (i.e. <paragraph>, <content>, <item>, <td>, <th>, <caption>, <footnote>, <sub> or <sup>).\nElse, Fail the test.\n\nNOTE TO TESTER: \na) Free text is text contained within a text data type element, or provided from a non-coded source (e.g. comments entered from the Authoring system).\nb)Text is not allowed within the <text> element itself, unless contained within an element allowed within the <text> element. As indicated in the test, allowed narrative block elements within the <text> narrative block element are; <paragraph>, <content>, <item>, <td>, <th>, <caption>, <footnote>, <sub> and <sup>.\nThere are other narrative block elements allowed within the <text> element, however, they are not allowed to contain text. \n","Clinical document narrative blocks contain all free text in allowed narrative block elements within the <text> narrative block element.\n\n","TBD",null,{"$f":"IF(H59=\"\",\"0\",IF(H59=\"Pass\",1,IF(H59=\"Fail\",0,IF(H59=\"TBD\",0,IF(H59=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D59)=48,H59=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Mark","TC-Narr-30","CDA-RS 44 [NEHTA-1199:2012]\nAuthoring Systems SHOULD use separate <paragraph> narrative block elements to separate paragraphs of text.\n","O",1,"Mark the test N/A where there is no separate paragraphed text within narrative blocks.\nPass the test where all separate paragraphed text within <text> narrative block elements use separate <paragraph> elements.\nElse, Fail the test.\n","The clinical document narrative blocks contain separate <paragraph> narrative block elements to separate paragraphs of text.\n\n\n","TBD",null,{"$f":"IF(H60=\"\",\"0\",IF(H60=\"Pass\",1,IF(H60=\"Fail\",0,IF(H60=\"TBD\",0,IF(H60=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D60)=48,H60=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Mark","TC-Narr-31","CDA-RS 45 [NEHTA-1199:2012]\nAuthoring Systems SHOULD represent free text in <paragraph> narrative block elements.\n\nNote: Requirement CDA-RS 43 mandates that free text must be contained in an allowed narrative block element. This requirement provides the option that where the text is not provided in tabular or list form, that the <paragraph> element be used instead of the <content> element to present the free text. When there is a need for <entry> elements to reference narrative text then the narrative must contain a <content> element with an ID attribute inside the  <paragraph> narrative block element. \n","O",1,"Mark the test N/A where there is no free text represented within <text> narrative block elements.\nPass the test where all free text within <text> narrative block elements are represented by <paragraph> elements.\nElse, mark the test N/A.\n\n","The clinical document narrative blocks contain free text in <paragraph> narrative block elements.\n\n","TBD",null,{"$f":"IF(H61=\"\",\"0\",IF(H61=\"Pass\",1,IF(H61=\"Fail\",0,IF(H61=\"TBD\",0,IF(H61=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D61)=48,H61=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Mark","TC-Narr-32","CDA-RS 50 [NEHTA-1199:2012]\nAuthoring Systems MAY use the following narrative block elements as specified in the CDA R2 specification [HL7CDAR2]:\n\n• <content>\n\nNote: The <content> element contains an optional \"revised\" attribute that can be valued with \"insert\" or \"delete\", which can be used to indicate narrative changes from the last version of a CDA document.  If applied, it needs to be used in conjunction with standard CDA revision tracking (HL7 Clinical Document Architecture, Release 2 [HL7CDAR2]).\n",null,null,"No additional test case is needed as it is sufficient to test conformance to the Australian CDA Schema Extension [NEHTA-1599:2014], which is performed in the FS-Doc feature set.\n"]
["TS-Mark","TC-Narr-33","CDA-RS 50 [NEHTA-1199:2012]\nAuthoring Systems MAY use the following narrative block elements as specified in the CDA R2 specification [HL7CDAR2]:\n\n• <linkHtml>\n\nCDA-RS 47 (a) [NEHTA-1199:2012]\nAuthoring Systems MAY use the <linkHtml> narrative block element to provide links to other narrative elements or to specific sections.\n\nCDA-RS 47 (b) [NEHTA-1199:2012]\nWhen using <linkHtml>, Authoring Systems SHALL ensure that the elements being linked to contain the correct XML ID attribute value.\n\n\nNote: The source of a link uses the linkHtml.href attribute. According to the HL7 Clinical Document Architecture, Release 2 [HL7CDAR2] \"The source of a link uses the linkHtml.href attribute. The target is an identifier of type XML ID either internal or external to the document. Internal identifiers can include other elements in the same or a different narrative block, or XML ID attributes that have been added to the <section>, <ObservationMedia>, or <renderMultiMedia> elements of the CDA Schema.\" The value of the linkHtml.href attribute may be a Uniform Resource Identifier (URI) with the syntax of an absolute URI, a relative reference or a same-document reference (see Uniform Resource Identifier (URI): Generic Syntax [RFC3986]).\n","C",1,"CONDITION: Clinical document contains a <linkHtml> element.\n\nPass the step where the <linkHtml> element contains the 'href' attribute.\nElse, Fail the step.\n","The <linkHtml> element in the narrative block of the clinical document contains the \"href\"' attribute.\n","TBD",null,{"$f":"IF(H63=\"\",\"0\",IF(H63=\"Pass\",1,IF(H63=\"Fail\",0,IF(H63=\"TBD\",0,IF(H63=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D63)=48,H63=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Mark",null,null,null,2,"CONDITION: Clinical document contains a <linkHtml> element containing a same-document reference (i.e. where the value of the href attribute starts with the character \"#\").\n\nPass the step where the value of the href attribute with the \"#\" removed is an XML ID attribute that identifies another element in the same or a different narrative block, a <section>, <observationMedia> or <renderMultiMedia> element within the clinical document.\nElse, Fail the step.\n","A same-document reference in a <linkHtml> element in a narrative block has the value of the href attribute commencing with the character \"#\" (indicating the value is a same-document reference) and the remainder of the value of the href attribute is an XML ID that identifies another element in the same or a different narrative block, <section>, <observationMedia> or <renderMultiMedia> element within the clinical document. \n\n\n","TBD",null,{"$f":"IF(H64=\"\",\"0\",IF(H64=\"Pass\",1,IF(H64=\"Fail\",0,IF(H64=\"TBD\",0,IF(H64=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D64)=48,H64=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Mark",null,null,null,3,"CONDITION: Clinical document contains a <linkHtml> element containing an absolute URI (i.e. where the value of the href attribute contains the character \":\").\n\nPass the step where the <linkHtml> element contains the href attribute commencing with the name of a URI scheme (e.g. \"http\" or \"mailto\", indicating the value is an absolute URI) followed by a \":\" and the value that conforms to the syntax applicable for that URI scheme,\nElse, Fail the step.\n\nNOTE TO TESTER: A third option is for the clinical document to contain a <linkHtml> element containing a relative reference. (i.e. The value of the href attribute is a relative reference to another document in the CDA package. A relative reference does not commence with a \"#\" and does not contain a \":\"). No test case is defined here for that option as it is assessed in the Conformance Test Specification for CDA Packaging [NEHTA-2065:2015].\n","An absolute URI reference in a <linkHtml> element in the narrative block has the href attribute commencing with the name of a URI scheme (e.g. \"http\" or \"mailto\", indicating the value is an absolute URI) followed by a \":\" and a value that conforms to the syntax applicable for that URI scheme.\n\n\n","TBD",null,{"$f":"IF(H65=\"\",\"0\",IF(H65=\"Pass\",1,IF(H65=\"Fail\",0,IF(H65=\"TBD\",0,IF(H65=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D65)=48,H65=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Mark","TC-Narr-34","CDA-RS 50 [NEHTA-1199:2012]\nAuthoring Systems MAY use the following narrative block elements as specified in the CDA R2 specification [HL7CDAR2]:\n\n• <sub>\n",null,null,"No additional test case is needed as there is no specific requirement that must be met if the element is included in the narrative block.\n"]
["TS-Mark","TC-Narr-35","CDA-RS 50 [NEHTA-1199:2012]\nAuthoring Systems MAY use the following narrative block elements as specified in the CDA R2 specification [HL7CDAR2]:\n\n• <sup>\n",null,null,"No additional test case is needed as there is no specific requirement that must be met if the element is included in the narrative block.\n"]
["TS-Mark","TC-Narr-36","CDA-RS 50 [NEHTA-1199:2012]\nAuthoring Systems MAY use the following narrative block elements as specified in the CDA R2 specification [HL7CDAR2]:\n\n• <br>\n\nNote: the <br/> element has no content (HL7 Clinical Document Architecture, Release 2 [HL7CDAR2]).\n",null,null,"No additional test case is needed as there is no specific requirement that must be met if the element is included in the narrative block.\n"]
["TS-Mark","TC-Narr-37","CDA-RS 50 [NEHTA-1199:2012]\nAuthoring Systems MAY use the following narrative block elements as specified in the CDA R2 specification [HL7CDAR2]:\n\n• <footnote>\n",null,null,"No additional test case is needed as it is sufficient to test conformance to the Australian CDA Schema Extension [NEHTA-1599:2014 ], which is performed in the FS-Doc feature set.\n"]
["TS-Mark","TC-Narr-38","CDA-RS 50 [NEHTA-1199:2012]\nAuthoring Systems MAY use the following narrative block elements as specified in the CDA R2 specification [HL7CDAR2]:\n\n• <footnoteRef>\n\nNote: The value of the footnoteRef.IDREF must be a footnote.ID value in the same document  (HL7 Clinical Document Architecture, Release 2 [HL7CDAR2]).\n","C",1,"CONDITION: The clinical document contains <footnoteRef> elements.\n\nPass the test where the <footnoteRef> element contains a mandatory \"IDREF\" attribute and that the IDREF attribute references an existing footnote in the same or different narrative block of the clinical document,\nElse, Fail the test.\n","The <footnoteRef> element in the narrative block contains the mandatory \"IDREF\" attribute referencing an existing footnote in the same or different clinical document narrative block of the same document.\n\n\n","TBD",null,{"$f":"IF(H70=\"\",\"0\",IF(H70=\"Pass\",1,IF(H70=\"Fail\",0,IF(H70=\"TBD\",0,IF(H70=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D70)=48,H70=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Mark","TC-Narr-39","CDA-RS 50 [NEHTA-1199:2012]\nAuthoring Systems MAY use the following narrative block elements as specified in the CDA R2 specification [HL7CDAR2]:\n\n• <paragraph>\n\nNote: A CDA <paragraph> element contains an optional caption, which if present must come first before any other character data (HL7 Clinical Document Architecture, Release 2 [HL7CDAR2]).\n","C",1,"CONDITION: The clinical document contains a <paragraph> element with a <caption>.\n\nPass the test where each <paragraph> element that contains a <caption> element, the <caption> element is present before any character data.\nElse, Fail the test.\n\nNOTE TO TESTER: Whitespace does not count as character data.\n","The clinical document includes a <caption> element within <paragraph> elements of the narrative block of the clinical document, and each <caption> element is present before any character data.\n\n","TBD",null,{"$f":"IF(H71=\"\",\"0\",IF(H71=\"Pass\",1,IF(H71=\"Fail\",0,IF(H71=\"TBD\",0,IF(H71=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D71)=48,H71=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Mark","TC-Narr-40","CDA-RS 50 [NEHTA-1199:2012]\nAuthoring Systems MAY use the following narrative block elements as specified in the CDA R2 specification [HL7CDAR2]:\n\n• <list>\n",null,null,"No additional test case is needed as it is sufficient to test conformance to the Australian CDA Schema Extension [NEHTA-1599:2014 ], which is performed in the FS-Doc feature set.\n"]
["TS-Mark","TC-Narr-41","CDA-RS 50 [NEHTA-1199:2012]\nAuthoring Systems MAY use the following narrative block elements as specified in the CDA R2 specification [HL7CDAR2]:\n\n• <item>\n\nNote: A CDA <item> element contains an optional caption, which if present must come first before any other character data (HL7 Clinical Document Architecture, Release 2 [HL7CDAR2]).\n","C",1,"CONDITION: The clinical document contains an <item> element with a <caption>:\n\nPass the test where each <item> element that contains a <caption> element, the <caption> element is present before any character data.\nElse, Fail the test.\n\nNOTE TO TESTER: Whitespace does not count as character data.\n","The clinical document includes a <caption> element within <item> elements of the narrative block of the clinical document, and each <caption> element is present before any character data\n\n","TBD",null,{"$f":"IF(H73=\"\",\"0\",IF(H73=\"Pass\",1,IF(H73=\"Fail\",0,IF(H73=\"TBD\",0,IF(H73=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D73)=48,H73=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Mark","TC-Narr-42","CDA-RS 50 [NEHTA-1199:2012]\nAuthoring Systems MAY use the following narrative block elements as specified in the CDA R2 specification [HL7CDAR2]:\n\n• <table>\n",null,null,"No additional test case is needed as it is sufficient to test conformance to the Australian CDA Schema Extension [NEHTA-1599:2014 ], which is performed in the FS-Doc feature set.\n"]
["TS-Mark","TC-Narr-43","CDA-RS 50 [NEHTA-1199:2012]\nAuthoring Systems MAY use the following narrative block elements as specified in the CDA R2 specification [HL7CDAR2]:\n\n• <thead>\n",null,null,"No additional test case is needed as it is sufficient to test conformance to the Australian CDA Schema Extension [NEHTA-1599:2014 ], which is performed in the FS-Doc feature set.\n"]
["TS-Mark","TC-Narr-44","CDA-RS 50 [NEHTA-1199:2012]\nAuthoring Systems MAY use the following narrative block elements as specified in the CDA R2 specification [HL7CDAR2]:\n\n• <tbody>\n",null,null,"No additional test case is needed as it is sufficient to test conformance to the Australian CDA Schema Extension [NEHTA-1599:2014 ], which is performed in the FS-Doc feature set.\n"]
["TS-Mark","TC-Narr-45","CDA-RS 50 [NEHTA-1199:2012]\nAuthoring Systems MAY use the following narrative block elements as specified in the CDA R2 specification [HL7CDAR2]:\n\n• <tr>\n",null,null,"No additional test case is needed as it is sufficient to test conformance to the Australian CDA Schema Extension [NEHTA-1599:2014 ], which is performed in the FS-Doc feature set.\n"]
["TS-Mark","TC-Narr-46","CDA-RS 50 [NEHTA-1199:2012]\nAuthoring Systems MAY use the following narrative block elements as specified in the CDA R2 specification [HL7CDAR2]:\n\n• <td> \n",null,null,"No additional test case is needed as it is sufficient to test conformance to the Australian CDA Schema Extension [NEHTA-1599:2014 ], which is performed in the FS-Doc feature set.\n"]
["TS-Mark","TC-Narr-47","CDA-RS 50 [NEHTA-1199:2012]\nAuthoring Systems MAY use the following narrative block elements as specified in the CDA R2 specification [HL7CDAR2]:\n\n•  <th>\n",null,null,"No additional test case is needed as it is sufficient to test conformance to the Australian CDA Schema Extension [NEHTA-1599:2014 ], which is performed in the FS-Doc feature set.\n"]
["TS-Mark","END:   TS-Mark (Markup content)"]
["TS-Tab","START: TS-Tab (Tables & Lists)"]
["TS-Tab","TC-Narr-48","CDA-RS 52 (a) [NEHTA-1199:2012]\nAuthoring Systems MAY use <caption> narrative block elements in <table> narrative block elements.\n",null,null,"No additional test case is needed as there is no specific requirement that must be met if the element is included in the narrative block.\n"]
["TS-Tab","TC-Narr-49","CDA-RS 52 (b) [NEHTA-1199:2012]\nAuthoring Systems SHOULD provide a single <tr> narrative block element as a column heading row when using the <table> narrative block elements.\n","O",1,"Mark the test N/A where the clinical document does not contain tables in narrative blocks:\na) Fail the test when a table does not contain a <thead> element; or \nb) Fail the test if a <thead> element does not contain one <tr> element.\nElse, Pass the test.\n\nNOTE TO TESTER: Tables are not required to have a heading row. Where a heading row exists, the <tr> narrative block element representing the column heading row should be coded within a <thead> element, as per requirements CDA-RS 52 (c) and CDA-RS 52 (d).\n","The clinical document contains a single <tr> narrative block element as a column heading row when using the <table> narrative block elements.\n\n","TBD",null,{"$f":"IF(H83=\"\",\"0\",IF(H83=\"Pass\",1,IF(H83=\"Fail\",0,IF(H83=\"TBD\",0,IF(H83=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D83)=48,H83=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Tab","TC-Narr-50","CDA-RS 52 (c) [NEHTA-1199:2012]\nAuthoring Systems SHALL ensure that the column heading row is contained in the <thead> narrative block element of <table> narrative block elements.\n\nCDA-RS 52 (d) [NEHTA-1199:2012]\nAuthoring Systems SHALL provide individual column headings in <th> narrative block elements.\n","C",1,"CONDITION: Clinical document contains table column heading rows.\n\nPass the step where all tables that include a column heading row have the column heading row contained in a <thead> narrative block element.\nElse, Fail the step.\n\nNOTE TO TESTER: A column heading row is represented within a <table> narrative block element by a table row <tr> element which will contain <th> elements representing the column headings, as per requirements CDA-RS 52 (b) and CDA-RS 52 (d). \n","The clinical document contains column heading rows in the <thead> narrative block element of <table> narrative block elements.\n\n\n","TBD",null,{"$f":"IF(H84=\"\",\"0\",IF(H84=\"Pass\",1,IF(H84=\"Fail\",0,IF(H84=\"TBD\",0,IF(H84=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D84)=48,H84=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Tab",null,null,null,2,"CONDITION:  Clinical document contains tables in narrative blocks with column headings provided.\n\nPass the step where tables contain individual column headings in <th> narrative block elements within a <thead> narrative block element.\nElse, Fail the step.\n\nNOTE TO TESTER: Not all columns will require a column heading, but where a column heading is provided it must be within a <th> element.\n","The clinical document contains individual column headings in <th> narrative block elements for each <table> element.\n","TBD",null,{"$f":"IF(H85=\"\",\"0\",IF(H85=\"Pass\",1,IF(H85=\"Fail\",0,IF(H85=\"TBD\",0,IF(H85=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D85)=48,H85=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Tab","TC-Narr-51","CDA-RS 52 (e) [NEHTA-1199:2012]\nAuthoring Systems SHALL ensure that non-heading table data rows are contained in the <tbody> narrative block element of <table> narrative block elements.\n","C",1,"CONDITION: The clinical document contains <table> narrative block elements.\n\nFail the test where:                                                                                             \na) a row (i.e. a <tr> element) exists within a <table> element which is not contained within a <tbody> or <thead> element, or \nb) a row within a <tbody> element is a heading data row (i.e. contains a <th> element).\nElse, Pass the test.\n\nNOTE TO TESTER: The <tbody> narrative block elements may contain rows consisting of any combination of valid narrative block elements, with the exception of a heading data row. A heading data row is one which contains only heading data elements (i.e. the <th> element is a heading data element) and is treated as a column heading row. As per requirement CDA-RS 52 (c) a column heading row must reside in the <thead> narrative block element.\n","All non-heading table rows in the clinical document are contained in the <tbody> narrative block element of <table> narrative block elements.\n\n","TBD",null,{"$f":"IF(H86=\"\",\"0\",IF(H86=\"Pass\",1,IF(H86=\"Fail\",0,IF(H86=\"TBD\",0,IF(H86=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D86)=48,H86=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Tab","TC-Narr-52","CDA-RS 52 (f) [NEHTA-1199:2012]\nAuthoring Systems MAY provide colspan and rowspan attributes in <th> and <td> narrative block elements.\n",null,null,"No additional test case is needed as there is no specific requirement that must be met if the element is included in the narrative block.\n"]
["TS-Tab","TC-Narr-53","CDA-RS 52 (g) [NEHTA-1199:2012]\nAuthoring Systems SHALL ensure the number of columns in each table row is kept constant.\n","C",1,"CONDITION: The clinical document contains <table> narrative block elements.\n\nPass the test where each row (specified by the <tr> element) within each table <tbody> element consists of the same number of columns.\nElse, Fail the test.\n\nNOTE TO TESTER: The number of columns within a row is calculated using the number of data and/or header elements in conjunction with any \"colspan\" attribute values applied within that row, as well as any \"rowspan\" attribute values applied in preceding rows within the same <tbody> narrative block element.\n","In the clinical document the number of columns in each table row is kept constant.\n\n\n\n","TBD",null,{"$f":"IF(H88=\"\",\"0\",IF(H88=\"Pass\",1,IF(H88=\"Fail\",0,IF(H88=\"TBD\",0,IF(H88=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D88)=48,H88=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Tab","TC-Narr-54","CDA-RS 52 (h) [NEHTA-1199:2012]\nAuthoring Systems MAY nest <list> narrative block elements inside <td> narrative block elements.\n",null,null,"No additional test case is needed as there is no specific requirement that must be met if the element is included in the narrative block.\n"]
["TS-Tab","TC-Narr-55","CDA-RS 52 (i) [NEHTA-1199:2012]\nAuthoring Systems MAY nest <paragraph> narrative block elements inside <td> narrative block elements.\n",null,null,"No additional test case is needed as there is no specific requirement that must be met if the element is included in the narrative block.\n"]
["TS-Tab","TC-Narr-56","CDA-RS 52 (j) [NEHTA-1199:2012]\nAuthoring Systems MAY nest <content> narrative block elements inside <td> narrative block elements.\n",null,null,"No additional test case is needed as there is no specific requirement that must be met if the element is included in the narrative block.\n"]
["TS-Tab","TC-Narr-57","CDA-RS 52 (k) [NEHTA-1199:2012]\nAuthoring Systems SHOULD ensure a <caption> narrative block element is provided in all <table> narrative block elements.\n","O",1,"Mark the test N/A where the clinical document does NOT contain <table> narrative block elements.\nPass the test where the clinical document contains a <caption> narrative block element within each <table> narrative block element.\nElse, Fail the test.\n","The clinical document contains a <caption> narrative block element within each <table> narrative block element.\n\n","TBD",null,{"$f":"IF(H92=\"\",\"0\",IF(H92=\"Pass\",1,IF(H92=\"Fail\",0,IF(H92=\"TBD\",0,IF(H92=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D92)=48,H92=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Tab","TC-Narr-58","CDA-RS 52 (l) [NEHTA-1199:2012]\nAuthoring Systems MAY use the listType attribute of the <list> narrative block element to specify an ordered list.\n",null,null,"No additional test case is needed as there is no specific requirement that must be met if the element is included in the narrative block.\n"]
["TS-Tab","TC-Narr-59","CDA-RS 52 (m) [NEHTA-1199:2012]\nAuthoring Systems SHALL provide at least one <item> narrative block element inside the <list> narrative block element.\n",null,null,"No additional test case is needed as it is sufficient to test conformance to the Australian CDA Schema Extension [NEHTA-1599:2014 ], which is performed in the FS-Doc feature set.\n\n"]
["TS-Tab","TC-Narr-60","CDA-RS 52 (n) [NEHTA-1199:2012]\nAuthoring Systems SHALL NOT nest <paragraph> or <table> narrative block elements inside <item> narrative block elements.\n","C",1,"CONDITION: The clinical document contains <list> narrative block elements.\n\nPass the test where each <item> narrative block element does not contain a nested <paragraph> or <table> element.\nElse, Fail the test.\n","The clinical document does not nest <paragraph> or <table> narrative block elements inside <item> narrative block elements.\n\n","TBD",null,{"$f":"IF(H95=\"\",\"0\",IF(H95=\"Pass\",1,IF(H95=\"Fail\",0,IF(H95=\"TBD\",0,IF(H95=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D95)=48,H95=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Tab","TC-Narr-61","CDA-RS 52 (o) [NEHTA-1199:2012]\nAuthoring Systems MAY nest <list> narrative block elements in <item> narrative block elements.\n",null,null,"No additional test case is needed as there is no specific requirement that must be met if the element is included in the narrative block.\n"]
["TS-Tab","TC-Narr-62","CDA-RS 52 (p) [NEHTA-1199:2012]\nAuthoring Systems SHALL NOT exceed three levels of nested <list> narrative block elements.\n","C",1,"CONDITION:  The clinical document contains <list> narrative block elements.\n\nPass the test where for each <list> narrative block element, there are no more than three levels of nested <list> elements.\nElse, Fail the test.\n"," The clinical document does not exceed three levels of nested <list> narrative block elements.\n\n","TBD",null,{"$f":"IF(H97=\"\",\"0\",IF(H97=\"Pass\",1,IF(H97=\"Fail\",0,IF(H97=\"TBD\",0,IF(H97=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D97)=48,H97=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Tab","END:   TS-Tab (Tables & Lists)"]
["TS-Style","START:   TS-Style (Style codes)"]
["TS-Style","TC-Narr-63","CDA-RS 54 (a) [NEHTA-1199:2012]\nAuthoring Systems MAY use the styleCode attribute in the <content>, <table>, <list>, <paragraph>, <item>, <th> and <td> narrative block elements.\n",null,null,"No additional test case is needed as the specific test cases to meet this requirement are provided below.\n"]
["TS-Style","TC-Narr-64","CDA-RS 54 (b) [NEHTA-1199:2012]\nAuthoring Systems SHALL NOT use the styleCode attribute in narrative block elements not explicitly allowed in this specification.\n\nNote: The specification referred to in the requirement is the CDA Rendering Specification [NEHTA-1199:2012]. The narrative block elements implicitly allowed to contain the styleCode attribute are those provided in requirement CDA-RS 54 (a).\n\nCDA-RS 55 [NEHTA-1199:2012]\n<content>, <item>, <th>, <td>, and <paragraph> style codes\n\na) Authoring Systems MAY use the “Bold” styleCode attribute value if the bold text is required.\nb) Authoring Systems MAY use the “Underline” styleCode attribute value if the underlined text is required.\nc) Authoring Systems MAY use the “Italics” styleCode attribute value if the text in italics is required.\nd) Authoring Systems MAY use the “Emphasis” styleCode attribute value if text with emphasis is required.\ne) Authoring Systems MAY use the custom “xFixed” styleCode attribute value if a fixed-width/monospace font is required.\nf) Authoring Systems MAY use the custom “xPre” styleCode attribute value if text containing whitespace and carriage returns (which may not be ignored) is required.\n\n","C",1,"CONDITION: Clinical Document contains styleCodes.\n\nPass the step where styleCode attributes are used only in <content>, <list>, <paragraph>, <item>, <th> and <td> narrative block elements.\nElse, Fail the step.\n\nNOTE TO TESTER: Although requirement CDA-RS 54 (a) states a <table> narrative block element may contain a styleCode attribute, the CDA Rendering specification does not list any styleCode values that may be used in the <table> element. Requirement CDA-RS 54 (b) states \"Authoring Systems SHALL NOT use the styleCode attribute in narrative block elements not explicitly allowed in this specification\", and, as there is no requirement within the specification which explicitly allows for styleCodes in the <table> narrative block element, the effect is that the <table> narrative block element must not contain a styleCode attribute.","Only the allowed styleCode attributes are contained in <content>, <table>, <list>, <paragraph>, <item>, <th> and <td> narrative block elements.\n\n\n\n","TBD",null,{"$f":"IF(H101=\"\",\"0\",IF(H101=\"Pass\",1,IF(H101=\"Fail\",0,IF(H101=\"TBD\",0,IF(H101=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D101)=48,H101=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Style",null,"CDA-RS 56 [NEHTA-1199:2012]\n<th> and <td> style codes\n\na) Authoring Systems MAY use the “Lrule” styleCode attribute value if rendering a cell with a left-sided rule is required.\nb) Authoring Systems MAY use the “Rrule” styleCode attribute value if rendering a cell with a right-sided rule is required.\nc) Authoring Systems MAY use the “Toprule” styleCode attribute value if rendering a cell with a top rule is required.\nd) Authoring Systems MAY use the “Botrule” styleCode attribute value if rendering a cell with a bottom rule is required.",null,2,"CONDITION: Clinical Document contains <content>, <item> or <paragraph> elements.\n\nPass the step where styleCode attributes used in <content>, <item> and <paragraph> narrative block elements do not contain values other than \"Bold\", \"Underline\", \"Italics\", \"Emphasis\", \"xFixed\", \"xPre\", or do not commence with \"xBgColour\", \"xFgColour\", \"xFontSizeEm\", \"xFontSizePx\", or \"xColWidthPx\".\n Else, Fail the step\n\nNOTE TO TESTER: custom style codes listed in the CDA Rendering Specification [NEHTA-1199:2012] must commence with the character \"x\". For example \" xFixed\" is invalid as the first character is a space \" \". See the HL7 Clinical Document Architecture, Release 2 specification [HL7CDAR2] for more information.\n","styleCode attributes in <content>, <item> and <paragraph> narrative block elements do not contain values other than \"Bold\", \"Underline\", \"Italics\", \"Emphasis\", \"xFixed\", \"xPre\", \"xBgColourHHHHHH\", \"xFgColourHHHHHH\", \"xFontSizeEmZ\", \"xFontSizePxZ\", and \"xColWidthPxZ\". \n\n\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D102)=48,H102=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Style",null,"CDA-RS 57 [NEHTA-1199:2012]\n<list> style codes\n\na) Authoring Systems MAY use the “Disc” styleCode attribute value in unordered list narrative block elements if solid circle bullets are required.\nb) Authoring Systems MAY use the “Circle” styleCode attribute value in unordered list elements if empty circle bullets are required.\nc) Authoring Systems MAY use the “Square” styleCode attribute value in unordered list elements if square shaped bullets are required.\nd) Authoring Systems MAY use the “LittleRoman” styleCode attribute value in ordered <list> narrative block elements if little Roman numerals are required (i.e. i, ii, iii).\ne) Authoring Systems MAY use the “BigRoman” styleCode attribute value in ordered <list>narrative block elements if big Roman numerals are required (i.e. I, II, III).\nf) Authoring Systems MAY use the “LittleAlpha” styleCode attribute value in ordered <list>narrative block elements if little alphabetic letters are required (i.e. a, b, c).\ng) Authoring Systems MAY use the “BigAlpha” styleCode attribute value in ordered <list> narrative block elements if big alphabetic letters are required (i.e. A, B, C).\n",null,3,"CONDITION: Clinical Document contains <th> or <td> elements.\n\nPass the step where styleCode attributes used in <th> and/or <td> narrative block elements do not contain values other than \"Bold\", \"Underline\", \"Italics\", \"Emphasis\", \"xFixed\", \"xPre\", \"Lrule\", \"Rrule\", \"Toprule\", or \"Botrule\" or do not commence with \"xBgColour\", \"xFgColour\", \"xFontSizeEm\", \"xFontSizePx\", or \"xColWidthPx\".\n Else, Fail the step.\n","styleCode attributes in <th> and/or <td> narrative block elements do not contain values other than \"Bold\", \"Underline\", \"Italics\", \"Emphasis\", \"xFixed\", \"xPre\", \"Lrule\", \"Rrule\", \"Toprule\", and \"Botrule\",\"xBgColourHHHHHH\", \"xFgColourHHHHHH\", \"xFontSizeEmZ\", \"xFontSizePxZ\", and \"xColWidthPxZ\". \n\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D103)=48,H103=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Style",null,null,null,4,"CONDITION: Clinical Document contains <list> elements.\n\nPass the step where styleCode attributes used in ordered <list> narrative block elements only contain values \"LittleRoman\", \"BigRoman\", \"LittleAlpha\" or \"BigAlpha\". \nElse, Passthe step where styleCode attributes used in unordered <list> narrative block elements only contain values \"Disc\", \"Circle\" or \"Square\". \nElse, Fail the step.\n\nNOTE TO TESTER: List type attribute specifies whether the <list> is ordered or unordered (with unordered being the default). Unordered lists are typically rendered with bullets, whereas ordered lists are typically rendered with numbers, although this is not a requirement.\n","styleCode attributes in <list> narrative block elements do not contain values other than \"Disc\", \"Circle\", \"Square\", \"LittleRoman\", \"BigRoman\", \"LittleAlpha\", and \"BigAlpha\".\n\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D104)=48,H104=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Style",null,null,null,5,"CONDITION: Clinical Document contains <table> element.\n\nPass the step where NO styleCode attributes used in <table> narrative block element.\nElse, Fail the step.\n","NO styleCode attributes are contained in <table> narrative block element.","TBD",null,{"$f":"IF(H105=\"\",\"0\",IF(H105=\"Pass\",1,IF(H105=\"Fail\",0,IF(H105=\"TBD\",0,IF(H105=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D105)=48,H105=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Style","TC-Narr-65","CDA-RS 54 (c) [NEHTA-1199:2012]\nAuthoring Systems SHALL support multiple applicable values (separated by a single space) in a single styleCode attribute e.g. ”Bold Italics Underline”.\n","C",1,"CONDITION: Clinical document contains styleCodes with multiple styles.\n\nPass the test where all elements containing multiple styleCode attribute values are separated by a single space,\nElse, Fail the test.\n","All elements containing multiple styleCode attribute values are separated by a single space.\n\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D106)=48,H106=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Style","TC-Narr-71","CDA-RS 55 (f) [NEHTA-1199:2012]\n<content>, <item>, <th>, <td>, and <paragraph> style codes\n\nAuthoring Systems MAY use the custom “xPre” styleCode attribute value if text containing whitespace and carriage returns (which may not be ignored) is required.\n","O",1,"Mark the step N/A where the clinical document does not contain the custom \"xPre\" style code attribute.\nPass the step where the contents of the element with the \"xPre\" style code consist of plain text where the width of any single line does not exceed 100 characters.\nElse, Fail the step.\n\nNOTE TO TESTER: Although not specified, a single line not in excess of 100 characters is recommended for readability.\n","The clinical document uses the custom style code \"xPre\" attribute and the contents of the element with that style code consist of plain text where the width of any single line does not exceed 100 characters.\n","TBD",null,{"$f":"IF(H107=\"\",\"0\",IF(H107=\"Pass\",1,IF(H107=\"Fail\",0,IF(H107=\"TBD\",0,IF(H107=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D107)=48,H107=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Style","TC-Narr-72","CDA-RS 55 (g) [NEHTA-1199:2012]\n<content>, <item>, <th>, <td>, and <paragraph> style codes\n\nAuthoring Systems MAY use the custom “xBgColourHHHHHH” styleCode attribute value if a specific background colour specified by the HHHHHH hex code is required \ne.g. “xBgColourFF0000” for a red background.\n\nNote: The CDA Rendering specification requires the use of six hexadecimal characters as the three character shorthand allowed by Web specifications (https://www.w3.org/TR/css3-color[W3C2018]) is not always correctly implemented. For example 'FFF' is sometimes implemented to be 'F0F0F0' (grey) whereas it is actually 'FFFFFF' (white).\n","C",1,"CONDITION: Clinical document contains styleCodes with \"xBgColourHHHHHH\" style attributes.\n\nPass the test where the \"HHHHHH\" component of the attribute consists only of 6 valid hexadecimal values (0-9, A-F).\nElse, Fail the test.\n\nNOTE TO TESTER: Hexadecimal values are case insensitive.\n","The clinical document uses the custom \"xBgColourHHHHHH\" style code attribute where the \"HHHHHH\" component of the attribute consists of 6 valid hexadecimal values (0-9, A-F). \n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D108)=48,H108=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Style","TC-Narr-73","CDA-RS 55 (h) [NEHTA-1199:2012]\n<content>, <item>, <th>, <td>, and <paragraph> style codes\n\nAuthoring Systems MAY use the custom “xFgColourHHHHHH” styleCode attribute value if a specific foreground colour specified by the HHHHHH hex code is required \ne.g. “xFgColour00FF00” for a green foreground.\n\nNote:  The CDA Rendering specification requires the use of six hexadecimal characters as the three character shorthand allowed by Web specifications (https://www.w3.org/TR/css3-color[W3C2018]) is not always correctly implemented. For example 'FFF' is sometimes implemented to be 'F0F0F0' (grey) whereas it is actually 'FFFFFF' (white).\n","C",1,"CONDITION: Clinical document contains styleCodes with \"xFgColourHHHHHH\" style attributes.\n\nPass the test where the \"HHHHHH\" component of the attribute consists only of 6 valid hexadecimal values (0-9, A-F).\nElse, Fail the test.\n\nNOTE TO TESTER: Hexadecimal values are case insensitive.\n","The clinical document uses the custom \"xFgColourHHHHHH\" style code attribute where the \"HHHHHH\" component of the attribute consists of 6 valid hexadecimal values (0-9, A-F). \n","TBD",null,0,{"$f":"IF(AND(BGCol(D109)=48,H109=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Style","TC-Narr-74","CDA-RS 55 (i) [NEHTA-1199:2012]\n<content>, <item>, <th>, <td>, and <paragraph> style codes\n\nAuthoring Systems MAY use the custom “xFontSizeEmZ” styleCode attribute value if a specific font size in ems specified by Z is required \ne.g. “xFontSizeEm1” for a font size of one em.\n","C",1,"CONDITION: Clinical document contains styleCodes with \"FontSizeEmZ\" style attributes.\n\nPass the test where the \"Z\" component of the attribute consists of a non-zero whole number value (e.g. 1, 2, 3 etc.).\nElse, Fail the test.\n","The clinical document uses the custom \"xFontSizeEmZ\" style code attribute where the \"Z\" component of the attribute consists of a non-zero whole number value.","TBD",null,0,{"$f":"IF(AND(BGCol(D110)=48,H110=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Style","TC-Narr-75","CDA-RS 55 (j) [NEHTA-1199:2012]\n<content>, <item>, <th>, <td>, and <paragraph> style codes\n\nAuthoring Systems MAY use the custom “xFontSizePxZ” styleCode attribute value if a specific font size in pixels specified by Z is required \ne.g. “xFontSizePx10” for a font size of ten pixels.\n","C",1,"CONDITION: Clinical document contains styleCodes with \"FontSizePxZ\" style attributes.\n\nPass the test where the \"Z\" component of the attribute consists of a non-zero whole number value (e.g. 1, 2, 3 etc.).\nElse, Fail the test.\n","The clinical document uses the custom \"xFontSizePxZ\" style code attribute where the \"Z\" component of the attribute consists of a non-zero whole number value.\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D111)=48,H111=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Style","TC-Narr-76","CDA-RS 55 (k) [NEHTA-1199:2012]\n<content>, <item>, <th>, <td>, and <paragraph> style codes\n\nAuthoring Systems MAY use the custom \"xColWidthPxZ\" styleCode attribute value if a specific column width specified by Z is required in <td> or <th> elements \ne.g. \"xColWidthPx10\" for a column width of ten pixels.\n","C",1,"CONDITION: Clinical document contains styleCodes with \"ColWidthPxZ\" style attributes.\n\nPass the test where\na) style code \"xColWidthPxZ\" is only provided in a <th> or <td> element; and\nb) the \"Z\" component of the attribute consists of a non-zero whole number value (i.e. 1-nnnn). \nElse, Fail the test.\n","The clinical document uses the custom \"xColWidthPxZ\" style code attribute only in <th> and <td> elements and the \"Z\" component of the attribute consists of a non-zero whole number value (1-nnnn). \n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D112)=48,H112=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Style","END:   TS-Style (Style codes)"]
["TS-Ext","START:   TS-Ext (Extensions)"]
["TS-Ext","TC-Narr-88","023722 [DH-2481:2017]\nA producer MAY include additional data elements in a clinical document structured data or narrative, but these data elements SHALL NOT qualify or negate any of the data elements defined in the CDA implementation guides.\n\nSection 1.8 Conformance [NEHTACDAIG]\nAny additional content included in the CDA document that is not described by this implementation guide SHALL not qualify or negate content described by this guide and it SHALL be clinically safe for receivers of the document to ignore the non-narrative additions when interpreting the existing content.\n\nNote: A conformance profile for a specific type of clinical document may explicitly disallow extensions. If they are not explicitly disallowed then the test cases for extensions are applicable. \n","C",1,"CONDITION: Extensions are allowed for the specific type of clinical document.\n\na) In every section specified in the relevant CDA implementation guide, list any information in the narrative block, including multimedia referenced by <renderMultimedia> tags in the narrative block, that does not correspond to an item on the NEHTA SCS Data Component column of the relevant mapping table.\nb) For the list of information found in (a) determine if it is present in a Detailed Clinical Model that is applicable for the section.\nc) For information that is not present in a Detailed Clinical Model:\n    i)  Ensure that the information does not qualify any of the elements listed in the CDA implementation guide.\n    ii) Ensure that the information does not negate any of the elements listed in the CDA implementation guide.\n\nMark the test N/A where there is no additional information in the narrative block.\nPass the test where all additional information contained in narrative blocks, including multimedia referenced by <renderMultimedia> tags in the narrative blocks, which does not correspond to an item on the NEHTA SCS Data Component column of the relevant mapping table, and is not present in the Detailed Clinical Model that is applicable for the section, does not qualify or negate any elements listed in the CDA implementation guide.\nElse, Fail the test.\n\nNOTE TO TESTER: \na) An extension negates an element if it reverses its meaning e.g. the patient did not have a condition, or this record is deleted. \nb) An extension qualifies an element if it scopes the statement in a significant way e.g. the patient used to have a condition, but not now. \nc) The judgement as to whether an extension negates or qualifies is made on clinical grounds (i.e. if an implementer ignores the extension, will it matter?). The library of Detailed Clinical Models is published on the NEHTA website. It is acceptable for information to be present if it is in a Detailed Clinical Model as a clinical document implementation guide is a subset of the information specified in the Detailed Clinical Models. The FS-Doc feature set contains a related test case for the structured data in a clinical document.\n","Any additional data elements that are included in the clinical document narrative blocks, including multimedia referenced by <renderMultimedia> tags in the narrative blocks, do not qualify or negate (structured data or narrative data) any of the data elements defined in the CDA implementation guide.","TBD",null,{"$f":"IF(H115=\"\",\"0\",IF(H115=\"Pass\",1,IF(H115=\"Fail\",0,IF(H115=\"TBD\",0,IF(H115=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D115)=48,H115=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Ext","END:   TS-Ext (Extensions)",null,null,null,null,null,null," "]
["TS-Ref","START:   TS-Ref (References)"]
["TS-Ref","TC-Narr-89","CDA-RS 50 [NEHTA-1199:2012]\nAuthoring Systems MAY use the following narrative block elements as specified in the CDA R2 specification [HL7CDAR2]:\n\n• <renderMultiMedia>\n\nNote: The <renderMultiMedia> element has an optional <caption>, and contains a required referencedObject attribute (of type XML IDREFS), the values of which must equal the XML ID value(s) of ObservationMedia or RegionOfInterest CDA entries within the same document. A <caption> contains plain text and may contain links and footnotes   (HL7 Clinical Document Architecture, Release 2 [HL7CDAR2]).\n","C",1,"CONDITION: Clinical document contains the <renderMultimedia> element.\n\nPass the step where all <renderMultiMedia> element's referencedObject attributes have the value which equals the XML ID value(s) of ObservationMedia or RegionOfInterest CDA entries within the same clinical document.\nElse, Fail the step.\n","For each <renderMultimedia> element in the narrative block of the clinical document, the value of the referencedObject attribute equals the XML ID value(s) of ObservationMedia or RegionOfInterest CDA entries within the same clinical document. \n\n","TBD",null,{"$f":"IF(H118=\"\",\"0\",IF(H118=\"Pass\",1,IF(H118=\"Fail\",0,IF(H118=\"TBD\",0,IF(H118=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D118)=48,H118=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Ref","TC-Narr-90","CDA-RS 53 (a) [NEHTA-1199:2012]\nAuthoring Systems MAY use the <renderMultimedia> narrative block element to reference an observationMedia entry in the CDA document to include GIF, JPEG and PNG images in narrative blocks.\n\nCDA-RS 53 (b) [NEHTA-1199:2012]\nAuthoring Systems MAY use the <renderMultimedia> narrative block element to reference an observationMedia entry in the CDA document to include Hypertext Markup Language (HTML) document attachments in narrative blocks.\n\nCDA-RS 53 (c) [NEHTA-1199:2012]\nAuthoring Systems MAY use the <renderMultimedia> narrative block element to reference an observationMedia entry in the CDA document to include Adobe Portable Document Format (PDF) document attachments in narrative blocks.\n\nCDA-RS 53 (d) [NEHTA-1199:2012]\nAuthoring Systems MAY use the <renderMultimedia> narrative block element to reference an observationMedia entry in the CDA document to include Rich Text Format (RTF) document attachments in narrative blocks.\n\nCDA-RS 53 (e) [NEHTA-1199:2012]\nAuthoring Systems MAY use the <renderMultimedia> narrative block element to reference an observationMedia entry in the CDA document to include Plain Text (TXT) document attachments in narrative blocks.\n\nNote: HTML, RTF and plain text  attachments are disallowed in the My Health Record system context by requirement 023741 in the Clinical Documents Common Conformance Profile [DH-2481:2017]. HTML attachments are allowed in the P2P context.\n",null,null,"No additional test case is needed as the inclusion of attachments is performed in the Conformance Test Specification for CDA Packaging [NEHTA-2065:2015] and the test for the correct use of the <renderMultiMedia> element is performed in TC-Narr-89. \n"]
["TS-Ref","TC-Narr-91","CDA-RS 53 (h) [NEHTA-1199:2012]\nAuthoring Systems SHALL include a <caption> narrative block element in all <renderMultimedia> narrative block elements when referencing HTML, PDF, RTF or Plain Text documents.\n\nNote: HTML, RTF and Plain Text  attachments are disallowed in the My Health Record system context by requirement 023741 of the Clinical Documents Common Conformance Profile [DH-2481:2017]. HTML, RTF and Plain Text  attachments are allowed in the P2P context.\n","C",1,"CONDITION: Clinical document contains <renderMultimedia> narrative block elements to reference a HTML, PDF, RTF or Plain Text document.\n\nPass the test where each <renderMultimedia> narrative block element contains a <caption> narrative block element.\nElse, Fail the test.\n","The clinical document includes a <caption> narrative block element in all <renderMultimedia> narrative block elements when referencing HTML, PDF, RTF or Plain Text documents.\n\n","TBD",null,{"$f":"IF(H120=\"\",\"0\",IF(H120=\"Pass\",1,IF(H120=\"Fail\",0,IF(H120=\"TBD\",0,IF(H120=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D120)=48,H120=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Ref","TC-Narr-92","4.3.5.6 <renderMultiMedia> [HL7CDAR2]\nThe CDA <renderMultiMedia> element references external multimedia that is integral to a document, and part of the attestable content of the document, and serves to show where the referenced multimedia is to be rendered. \nMultimedia that is simply referenced by the document and not an integral part of the document must use <linkHtml>.\n\nNote: external objects, represented by ExternalAct, ExternalDocument, ExternalObservation and ExternalProcedure, are not part of the attestable content so need to be included in a narrative block using <linkHtml> elements and not <renderMultiMedia> elements.\n","M",1,"Fail the test if the clinical document contains a <linkHtml> element that references multimedia that is also referenced by an <observationMedia> or <regionOfInterest> element in the same clinical document.\nElse Pass the test.\n\n","All external objects referenced from within an <entry> element are referenced from the corresponding narrative block using a <linkHtml> element.\n\n\n","TBD",null,{"$f":"IF(H121=\"\",\"0\",IF(H121=\"Pass\",1,IF(H121=\"Fail\",0,IF(H121=\"TBD\",0,IF(H121=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D121)=48,H121=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Ref",null,null,null,2,"Fail the test if the clinical document contains a <renderMultiMedia> element that references multimedia that is also referenced by an <externalAct>, <externalDocument>, <externalObject> or <externalProcedure> element in the same clinical document.\nElse Pass the test.\n\nNOTE TO TESTER: \n external objects represented by ExternalAct, ExternalDocument, ExternalObservation and ExternalProcedure are not part of the attestable content so need to be included in a narrative block using <linkHtml> elements and not <renderMultiMedia> elements.\n","Each <renderMultiMedia> element within a narrative block does not directly or indirectly reference an external object.\n\n\n","TBD",null,{"$f":"IF(H122=\"\",\"0\",IF(H122=\"Pass\",1,IF(H122=\"Fail\",0,IF(H122=\"TBD\",0,IF(H122=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D122)=48,H122=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Ext","END:   TS-Ref (References)",null,null,null,null,null,null," "]
["TS-Body","START:  TS-Body (CDA body)"]
["TS-Body","TC-Narr-94","025054 [DH-2481:2017]\nRequirements for title element\n\nIf a section contains a <text> element then the <title> element SHALL be included.\n\n'027731 [DH-2481:2017]\nOmission of the section title\n\nIf a narrative is not included in a section, then the corresponding section title SHOULD NOT be included.\n\nNote: this overrides requirement CDA-RS 42 in the CDA Rendering Specification [NEHTA-1199:2012].\n\nAdditional Notes: The purpose of this requirement is to state that when there is no narrative block then the title for the narrative block should not be present.","M",1,"Fail the test where, if <text> is present in the section, then no <title> is present in the section.\nElse, Pass the test.\n\nNOTE TO TESTER: The test step applies if the <text>  element is a child element of the parent <section> element. Not valid for 1A template packages.","A section has  <title> element and  <title> element.","TBD",null,{"$f":"IF(H125=\"\",\"0\",IF(H125=\"Pass\",1,IF(H125=\"Fail\",0,IF(H125=\"TBD\",0,IF(H125=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D125)=48,H125=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Body","END:   TS-Body (CDA body)"]
[]
[null,null,null,null,null,null,null,"TBD","Total Tests",{"$f":"SUM(J129:J130)","v":72}]
[null,null,null,null,null,null,null,"Fail","Tests Failed or TBD",{"$f":"COUNTIF(J1:J126,\"0\")","v":72}]
[null,null,null,null,null,null,null,"N/A","Tests Passed or N/A",{"$f":"COUNTIF(J1:J126,\"1\")","v":0}]
[null,null,null,null,null,null,null,"Pass","%Passed or N/A",{"$f":"SUM(J130/J128)","v":0}]

{"sheet":"FS-Types","index":7,"n_rows":225,"n_cols":11,"rows_kept":225,"cut":false,"hidden":false,"merged":[[172,1,173,1],[197,2,198,2],[71,2,72,2],[115,1,115,5],[28,3,29,3],[135,2,136,2],[138,3,139,3],[172,3,173,3],[172,2,173,2],[0,0,0,1],[0,2,0,5],[1,0,1,1],[1,2,1,5],[3,0,3,1],[3,2,3,4],[2,0,2,1],[11,5,11,6],[2,2,2,4],[26,2,27,2],[26,1,27,1],[23,1,24,1],[23,2,24,2],[23,3,24,3]]}
["Feature set identifier:",null,"FS-Types (Data types and data groups)"]
["Objective:",null,"To assess the conformance of a clinical document to the requirements for complex data types, and data groups defined in Australian CDA extensions."]
["Strategy:",null,"A clinical document to be tested may be obtained from any source, such as an authoring system operated by the tester, a database or from another software system. The test sets are designed so a tester may assess the clinical document for conformance to the applicable requirements without needing any knowledge of the software that authored it. The test cases are written in a style that enables them to be automated wherever practical. \n\nTest cases in the FS-Types feature set are organised as follows:\n    1) NEHTA-defined data types\n    2) NEHTA-defined data groups \n    3) ISO data types that are the foundation of the NEHTA-defined data types\n    4) Classes defined in the HL7 reference information model\n\nDetailed Explanation (scroll down for all details):\nThe data type of each clinical document data element is stated in the Participation Data Specification and the relevant structured content specification. These data types are defined in Data Types in NEHTA Specifications [NEHTA-1136:2010] which profile the ISO data types [ISO21090], which in turn are based on the HL7 data types [HL72004]. Other data types, such as Entity Identifier are defined in the Participation Data Specification [NEHTA-0794:2011]. The HL7 data types specification [HL72004] is an abstract specification that is accompanied by another specification describing the instantiation in XML [HL72004b]. \n\nThe set of attributes supported by the clinical document data types are a subset of the attributes supported by the ISO and HL7 data types and were selected to make it easier for software systems to process information in clinical documents. However extensions to clinical document specifications may use any HL7 data type, therefore the Australian CDA schema allows the use of all attributes defined in the HL7 data type specification so test cases are needed to ensure data elements defined in the clinical document specifications conform to the requirements for NEHTA-defined data types.\n\nThe Participation Data Specification also states requirements for data groups including Entitlement and Address. Test cases are defined to ensure that clinical documents conform to these requirements. \n\nThe clinical document specifications state that code sets must either be national code sets or be registered through the HL7 code set registration procedure. Therefore test cases for NEHTA-defined data types include test cases derived from the requirements of national code sets defined by NEHTA, the Australian Institute of Health and Welfare and the Australian Bureau of Statistics; and code sets registered with the HL7 OID registry. Similarly, the test cases for Entity Identifiers and Entitlements include test cases derived from the requirements published by Standards Australia for healthcare client and provider identification.\n\nDue to the need to also conform to the requirements for HL7 data types, some attributes in some NEHTA and ISO data types are not currently supported. These attributes are indicated by the use of red font. Note also that although the nullFlavor attribute is allowed by default, specifications for some clinical documents may disallow the use of nullFlavor for specific data elements. An attribute in the ISO datatype is defined as a characteristic of an object that is assigned a name and a type (Refer 3.1 of the ISO 21090 Healthcare Datatypes specification). It shall be noted that an attribute for an ISO data type is different from an XML attribute.\n\nAlso included are a small number of test cases derived from requirements in the HL7 reference information model (RIM). A new feature set should be defined for these test cases, rather than using FS-Types, but are included here while the number of test cases is small. A comprehensive set of test cases is currently not needed as conformance to most RIM requirements is achieved through conformance to the implementation guides and structured content specifications.\n",null,null,"The following test sets have been defined.\n\nTS-UID contains test cases for unique identifiers and are referenced by test cases for the NEHTA-defined ISO data types.\nTS-BTB, TS-Coded, TS-IL, TS-Quant, TS-Cont and TS-EntId contain test cases for NEHTA-defined data types.\nTS-Entit and TS-AddrDG contain test cases for NEHTA-defined data groups. Note that test sets for other data groups are listed in the FS-Auth feature set.\nTS-NF, TS-BL, TS-ED, TS-ST, TS-CD, TS-TEL, TS-II, TS-PQ, TS-INT, TS-REAL, TS-RTO, TS-PQ.TIME, TS-TS and TS-IVL contain test cases for ISO data types that form the foundation of NEHTA-defined data types .\nTS-Class contains test cases for classes defined in the HL7 reference information model.\n"]
["Traceability:",null,"Traceability References 1-25 (scroll down for full list)\n1. Clinical Documents - Common Conformance Profile [DH-2481:2017]\n2. Data Types in NEHTA Specifications - A Profile of ISO 21090 Specification v1.0 [NEHTA-1136:2010]\n3. Participation Data Specification [NEHTA-0794:2011]\n4. CDA implementation guides [NEHTACDAIG]\n5. Structured content specifications [NEHTASCS]\n6. HL7 Reference Information Model, Release 6 [HL72013]\n7. HL7 Version 3 Standard: Data Types -  HL7 OID Registry [HL72015]\n8. SNOMED CT Technical Implementation Guide [IHTSDO2014] \n9. Clinical Documents - CDA Package v1.0 [NEHTA-1229:2011] \n10. CDA Package Specification [CDAP2011] - Old reference to same document above\n11. Open Group, CDE 1.1 Remote Procedure Call specification, Universal Unique Identifier (UUID) [OG1997]\n12. Metadata Online Registry [AIHW2015]\n13. OID Repository www.oid-info.com [OIDR2015]\n14. Clinical specialties (Various), AIHW [AIHWCS] http://meteor.aihw.gov.au/content/index.phtml/itemId/\n15. Australian Securities and Investment Commission www.asic.gov.au [ASIC2015]\n16. Health informatics -- Harmonized data types for information interchange [ISO 21090]\n17. AS 5017-2006: Health Care Client Identifier Geographic Area [SA2006a]\n18. Standards Australia handbook 234 – 2012, section 7\n19. Conformance Test Specification for CDA Packaging [NEHTA-2065:2015]\n20. CDA Rendering Specification [NEHTA-1199:2012]\n21. Australian CDA Schema Extension [NEHTA-1599:2014]\n22. eDischarge Summary - PCEHR Conformance Profile v1.5 [NEHTA 1448:2013]\n23. ITU-T X.667 Series X: Data Networks and Open System Communications [ITU2004]\n24. Use of HIs in Health Software Systems - Conformance Requirements v3.1 [ NEHTA-1732:2014 ]\n25. AS 5017-2006: Health Care Client Identifier Geographic Area [SA2006a]"]
[]
["THIS HEADER CAN BE COLLAPSED BY CLICKING THE '-' SYMBOL ON THE LEFT."]
["TEST SET ID","TEST CASE ID","CONFORMANCE REQUIREMENT","PRIORITY","STEP NO.","TEST STEP","EXPECTED RESULT","TEST RESULT","TESTER COMMENTS","CALC.","MANDATORY AND N/A"]
["TS-UID","START:  TS-UID (Unique identifier)"]
["TS-UID","TC-Types-105","Universal Unique Identifier (UUID) [OG1997] \n\nNote: A UUID is a globally unique identifier that has the advantage of not needing a registration system (in contrast to OIDs which need to be registered). An alternative name for UUID is Globally Unique Identifier (GUID). Rather than copying the UUID requirements, the format of the UUID string representation used in clinical documents is summarised here.\n\nA conformant UUID in the string representation must have the following appearance (where “h” is a hexdigit): hhhhhhhh-hhhh-hhhh-hhhh-hhhhhhhhhhhh. That is, there must be eight hexdigits, followed by a “-“, followed by four hexdigits, followed by a “-“, followed by four hexdigits, followed by a “-“, followed by four hexdigits, followed by a “-“, followed by twelve hexdigits. A hexdigit must be one of the characters “0”, “1”, “2”, “3”, “4”, “5”, “6”, “7”, “8”, “9”, “a”, “b”, “c”, “d”, “e”, “f”.  For example 2fac1234-31f8-11b4-a222-08002b34c003.\n\nThere are two conflicting requirements for the case of a hexdigit in a UUID: The hexadecimal values a to f inclusive are output as lower case characters [OG1997] and UUIDs shall be represented in upper case [ISO21090]. Both forms are in widespread use so conformance testing need only check that the hexdigit letters are either all lowercase or all uppercase.\n\nAs a UUID is created from a timestamp then it is not valid for all characters to be zero.\n","M",1,"For any UUID:\n\nFail the test if the UUID does not have the format hhhhhhhh-hhhh-hhhh-hhhh-hhhhhhhhhhhh where “h” is a hexdigit that is one of the characters “0”, “1”, “2”, “3”, “4”, “5”, “6”, “7”, “8”, “9”, “a”, “b”, “c”, “d”, “e”, “f”, “A”, “B”, “C”, “D”, “E”, “F”.\nElse, Fail the test if all letters in the UUID are not entirely in uppercase or lowercase (i.e. Fail the test if there is mixed case).\nElse, Fail the test if all hexdigits are \"0\" (as in 00000000-0000-0000-0000-000000000000).\nElse, Pass the test.\n","Universal Unique Identifier (UUID) has the correct format, character set and is either fully lowercase or fully uppercase.","TBD",null,{"$f":"IF(H9=\"\",\"0\",IF(H9=\"Pass\",1,IF(H9=\"Fail\",0,IF(H9=\"TBD\",0,IF(H9=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D9)=48,H9=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-UID","TC-Types-106","Object Identifier (OID) [ITU2004]\n\nNote: Rather than copying the OID requirements, the format of the OID dot notation used in clinical documents is summarised here.\nIn clinical documents an OID is a series of numeric strings, with a dot “.” separating each pair of numeric strings; for example \"2.5.4.10\". \n\nEach numeric string in an OID is called an “arc” and contains digits in the range from 0 to 9.  The root arc can be \"0\", \"1\" or \"2\". However, an arc can only commence with a zero if it is a single digit.\n","M",1,"OID format test\n\nFor any OID:\n\nFail the test if the OID does not consist of one or more numeric strings (arcs) with a dot “.” separating each pair of numeric strings (for example \"2.5.4.10\").\nElse, Fail the test if the first arc is not \"0\", \"1\" or \"2\".\nElse, Fail the test if any arcs commence with '0' and have more than one numeric character.\nElse, Pass the test.","All Object Identifiers (OID) included by the Authoring System have the correct format.","TBD",null,{"$f":"IF(H10=\"\",\"0\",IF(H10=\"Pass\",1,IF(H10=\"Fail\",0,IF(H10=\"TBD\",0,IF(H10=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D10)=48,H10=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-UID","TC-Types-107","Object Identifier (OID) [ITU2004]\n\nNote: An OID is a globally unique identifier that uses a public registration system (in contrast to UUIDs which do not need to be registered). The management of the entire OID is accomplished by a process of delegation of authority where a registration authority delegates the registration responsibility for each subsequent OID to a subordinate registration authority and the delegation may be applied repeatedly.\n\nAdditional information about OID registration and the HL7 registration procedure is on the HL7 OID Registry website www.hl7.org/oid/index.cfm. \n","M",1,"Registered OID test\n\nFor any OID:\n\nFail the test if the OID is not found to be valid by applying the instructions below which detail how to verify the registration of an OID.\nElse, Pass the test.\n\nNOTE TO TESTER: \nSee steps detailed below for general OID Registration instruction, including examples and reference to other tests.\n","Object Identifier (OID) has current registration.","TBD",null,{"$f":"IF(H11=\"\",\"0\",IF(H11=\"Pass\",1,IF(H11=\"Fail\",0,IF(H11=\"TBD\",0,IF(H11=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D11)=48,H11=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-UID",null,null,null,null,"Step 1: Search for the OID in the HL7 OID Registry, www.hl7.org/oid/index.cfm. If it is present then the OID is valid, otherwise proceed to step 2. Note also that the OID repository (http://www.oid-info.com) can also be checked as not all OIDs in use are in the HL7 OID register.\nStep 2: Remove the last arc of the OID and search the HL7 OID Registry again. If it is present, then determine whether the remaining arcs in the entire OID are within the namespace of the registered OID.  This can be done in the following was:\na. If the namespace is a public system that can be searched and if the last arc in the entire OID is listed in the public system then the entire OID is valid (see Example 1).\nb. If the namespace is a public system but it cannot be searched then apply another test of assurance if one is available (see Example 2), otherwise assume that the last arc is valid.\nc. If the namespace is not a public system but the organisation managing the namespace is the appropriate organisation for managing the entire OID then assume the entire OID is valid. \nStep 3: Repeat Step 2 by removing another arc (and keep repeating step 2 until the OID is determined to be valid).\nStep 4: If the definition of the data element containing the OID requires the OID to be listed in the HL7 OID Registry. In this case if the outcome of repeating Step 2 is that the OID is not in the HL7 OID Registry then the OID is invalid. If the OID is not required to be listed in the HL7 OID Registry then proceed to Step 5.\nStep 5: If the OID commences with “2.25” then the OID is valid if it passes the UUID OID test, TC-Types-108.\nStep 6: If the OID commences with “1.2.36” and the next arc is either registered on the OID Repository or is a numeric string of 2 to 11 digits then the OID is valid if it passes the Australian Registered Company OID test, TC-Types-109.\n\nExample 1: METeOR is a Metadata Online Registry maintained by the Australian Institute of Health and Welfare [AIHW2013]. The OID “2.16.840.1.113883.3.879.329673” identifies the METeOR codeSystem for specialties. However “2.16.840.1.113883.3.879.329673” is not listed in the HL7 OID Registry or the OID Repository. Instead, “2.16.840.1.113883.3.879” is listed in the HL7 OID Registry with the description that it is the “Root OID to be used for Metadata Online Registry” (i.e. METeOR). That is, “2.16.840.1.113883.3.879” identifies the METeOR namespace. A search of METeOR (http://meteor.aihw.gov.au/content/index.phtml/itemId/181162) for the arc “329673” returns the list of specialties for health professionals. \n\nExample 2: An example of a type of OID used in every clinical document is “1.2.36.1.2001.1003.0.8003621234567890\". This OID is not included in the HL7 OID Registry. Removing the last arc creates the new OID “1.2.36.1.2001.1003.0”, which is listed in the HL7 OID Registry with the description “An identifier issued by the HI Service”. That indicates the last arc, “8003621234567890”, is a national healthcare identifier registered in the HI Service. In other words, “1.2.36.1.2001.1003.0” identifies the healthcare identifier namespace. Searching the HI Service to check the validity of “8003621234567890” is generally not possible for privacy reasons however it is possible to determine if “8003621234567890” is likely to be a valid healthcare identifier as every such identifier must conform to specific mathematical rules.\n"]
["TS-UID","TC-Types-108","UUID OID (OID \"2.25\") [ITU2004]\n\nNote: A specific example of an OID is the use of a UUID to form an OID as an alternative to the hexadecimal representation of a UUID. \nAn OID formed using a UUID commences with “2.25”, following by an arc that is the integer representation of a UUID. The integer representation of an UUID produces a numeric string of up to a maximum of 39 digits. Additional information is available in the technical specification [ITU2004] and in the OID Repository [OIDR2015] by searching for the OID “2.25”.\n\nFor example the UUID f81d4fae-7dec-11d0-a765-00a0c91e6bf6 can be transformed into “329800735698586629295641978511506172918” so the OID containing this UUID is “2.25.329800735698586629295641978511506172918”.\n","M",1,"UUID OID length test\n\nFor any OID commencing with “2.25”:\n\nFail the test if the arc following “2.25” contains more than 39 digits.\nElse, Pass the test.\n\nNOTE TO TESTER: \nIt is permitted to have other arcs after the integer representation of a UUID.\n","UUID OID value that starts with '2.25' contains no more than 39 digits in total.","TBD",null,{"$f":"IF(H13=\"\",\"0\",IF(H13=\"Pass\",1,IF(H13=\"Fail\",0,IF(H13=\"TBD\",0,IF(H13=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D13)=48,H13=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-UID","TC-Types-109","Australian Company Number (ACN) or Australian Business Number (ABN) (OID \"1.2.36\") [OIDR2015]\n\nNote: A specific example of an OID is an Australian Registered Company OID. Every company registered in Australia has their own OID. The OID “1.2.36” is managed by Standards Australia and is listed in the OID Repository [OIDR2015]. The OID for a company registered in Australia is formed by adding the Australian Company Number (ACN) or Australian Business Number (ABN), excluding leading zeros, to “1.2.36”. Leading zeroes must be stripped due to the OID format requirements. An ACN has nine digits and an ABN has 11 digits  [ASIC2015]. Additional information is available in the technical specification [ITU2004] and in the OID Repository [OIDR2015] by searching for the OID “1.2.36”.\n\nFor example, a company with ACN 073 777 777 has OID “1.2.36.73777777”.  \n","M",1,"Australian Registered Company OID test\n\nFor any OID commencing with “1.2.36” and the next arc is a numeric of 2 to 11 digits:\nPass the test if the OID commences with \"1.2.36.174030967\" (this is the OID for Medicare Australia).\nElse if the arc is a numeric of 2 (or 10) digits then add leading zeros '0' to form a string with the correct number of digits for an ACN (i.e. 9 digits) then verify that the check digit is valid and lookup the ABN or ACN (www.abr.business.gov.au) and determine if the arc is a registered ACN and the name of the company.\nElse if the arc has an invalid check digit or is not a registered ACN then add leading zeros '0' to form a string with the correct number of digits for an ABN (i.e. 11 digits) then verify that the check digit is valid and determine if the arc is a registered ABN and the name of the company.\nFail the test if the check digit calculation or lookup fails.\nElse, Pass the test.\n\nNOTE TO TESTER: \nIf an ACN or ABN includes leading zeroes then leading zeroes are excluded from the arc in order for the OID to have a valid format.\nThe ACN check digit calculation is described here: \nhttps://asic.gov.au/for-business/registering-a-company/steps-to-register-a-company/australian-company-numbers/australian-company-number-digit-check\nThe ABN check digit calculation is described here: https://abr.business.gov.au/Help/AbnFormat\n","Australian Company Number (ACN) or Australian Business Number (ABN) OID starts with '1.2.36' and has a valid arc of 8 to 11 numeric digits that is a registered ABN or ACN.","TBD",null,{"$f":"IF(H14=\"\",\"0\",IF(H14=\"Pass\",1,IF(H14=\"Fail\",0,IF(H14=\"TBD\",0,IF(H14=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D14)=48,H14=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-UID","END:  TS-UID (Unique identifier)"]
["TS-BTB","START:  TS-BTB (Basic, text and binary data types)"]
["TS-BTB","Note: Basic, text and binary data types are defined in Data Types in NEHTA Specifications [NEHTA-1136:2010]."]
["TS-BTB","TC-Types-01","NEHTA data type: 4.2 Boolean [NEHTA-1136:2010]\nDerived from the ISO data type: BL\nAttributes: value, nullFlavor\n","M",1,"For any data element of type Boolean based on the HL7 \"BL\" data type:\n\nFail the test if the data element fails any test case in TS-BL.\nElse,Fail the test if the data element has attributes other than value or nullFlavor and fails the tests for extensions in TS-Dext.\nElse, Pass the test.\n\nNOTE TO TESTER: \n- Above reference to TS-BL indicates individual test cases for Boolean data types in this worksheet below (*See TC-Types-50).\n- For Boolean data types, there are no individual test cases other than the execution of the Australian CDA Schema Extension in FS-Doc-02\n- The CDA schema may need to be examined to determine the HL7 data type that applies to a specific data element.\n","Boolean data elements are true or false values, or are a nullFlavor and comply to the cardinality specifications outlined in Data Types in NEHTA Specifications [NEHTA-1136:2010].","TBD",null,{"$f":"IF(H18=\"\",\"0\",IF(H18=\"Pass\",1,IF(H18=\"Fail\",0,IF(H18=\"TBD\",0,IF(H18=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D18)=48,H18=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-BTB","TC-Types-02","5.1 EncapsulatedData [NEHTA-1136:2010]\nISO data type: ED (encapsulated data)\nAttributes: value, data, xml, reference (Link), mediaType (CodedText), charset (CodedText), language, compression, integrityCheck, integrityCheckAlgorithm, description (Text), thumbnail (EncapsulatedData), translation (EncapsulatedData) or nullFlavor\n\nNote: Attributes indicated in red are currently unsupported.\n\n\n","M",1,"For any data element of type EncapsulatedData based on the HL7 \"ED\" data type:\n\nFail the test if the data element fails any test case in TS-ED.\nElse, Fail the test if the data element has attributes other than value, data, xml, reference, mediaType, charset, language, compression, integrityCheck, integrityCheckAlgorithm, description, thumbnail, translation or nullFlavor and fails the tests for extensions in TS-Dext.\nElse, Fail the test if the reference attribute (if present) fails any test case in TS-IL for the Link data type.\nElse, Fail the test if the mediaType attribute (if present) fails any test case in TS-Coded for the CodedText data type.\nElse, Fail the test if the charset attribute (if present) fails any test case in TS-Coded for the CodedText data type.\nElse, Pass the test. \n\nNOTE TO TESTER: \n- Above reference to TS-ED indicates individual test cases for Encapsulated data types in this worksheet below (See TC-Types-51 to 54).\n- Above reference to TS-IL indicates individual test cases for Identification and Location data type Link in this worksheet below (See TC-Types-10).\n- Above reference to TS-Coded indicates individual test cases for coded data types in this worksheet below (See TC-Types-04 to 09).\nThese aspects of testing are to be considered as part of overall Encapsulated data type specification conformance.  \n- The CDA schema may need to be examined to determine the HL7 data type that applies to a specific data element.","Encapsulated data elements are value, data, xml, reference, mediaType, charset, language, compression, integrityCheck, integrityCheckAlgorithm, description, thumbnail, translation or nullFlavor and comply with the specifications outlined in Data Types in NEHTA Specifications [NEHTA-1136:2010].","TBD",null,{"$f":"IF(H19=\"\",\"0\",IF(H19=\"Pass\",1,IF(H19=\"Fail\",0,IF(H19=\"TBD\",0,IF(H19=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D19)=48,H19=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-BTB","TC-Types-03","5.2 Text [NEHTA-1136:2010]\nISO data type: ST (character string)\nAttributes: value, language (CodedText), translation or nullFlavor\n\nNote: The full scope of the NEHTA profile of the data types is indicated on the UML model diagram in section 3 of [NEHTA-1136:2010]. For cardinality,  <data Type> Integer is indicated in the UML model as  which is also stated in the Text attribute Value: string[0..1]. See the UML model in the document for full details. \n\nNote: Attributes indicated in red are currently unsupported.\n","M",1,"For any data element of type Text based on the HL7 \"ST\" data type:\n\nFail the test if the data element fails any test case in TS-ST.\nElse, Fail the test if the data element has attributes other than value, language, translation or nullFlavor and fails the tests for extensions in TS-Dext.\nElse, Fail the test if the language attribute (if present) fails any test case in TS-Coded for the CodedText data type.\nElse, Pass the test. \n\nNOTE TO TESTER: \n- Above reference to TS-ST indicates individual test cases for character string types in this worksheet below (See TC-Types-55 & 56).\n- Above reference to TS-Coded indicates individual test cases for coded data types in this worksheet below (See TC-Types-04 to 09).\n- These aspects of testing are to be considered as part of overall text data type specification conformance.  \n- The CDA schema may need to be examined to determine the HL7 data type that applies to a specific data element.\n\n","Text data elements are value, language, translation or nullFlavor and comply with the specifications outlined in Data Types in NEHTA Specifications [NEHTA-1136:2010].","TBD",null,{"$f":"IF(H20=\"\",\"0\",IF(H20=\"Pass\",1,IF(H20=\"Fail\",0,IF(H20=\"TBD\",0,IF(H20=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D20)=48,H20=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-BTB","END:  TS-BTB (Basic, text and binary data types)"]
["TS-Coded","START:  TS-Coded (Coded data types)"]
["TS-Coded","Note: Coded data types are defined in Data Types in NEHTA Specifications [NEHTA-1136:2010]."]
["TS-Coded","TC-Types-04","6.1 CodeableText [NEHTA-1136:2010]\nISO data type: CD (concept descriptor)\nAttributes: originalText, code, codeSystem, codeSystemName, codeSystemVersion, displayName, valueSet, valueSetVersion, codingRationale, source (CodedText), translation (CodeableText), nullFlavor\n\nMUST have one of displayName or original text where there is no null flavour.\n\nNote: The originalText of the code also applies to the translation element. If there was no originalText present, then the code should have a displayName. The code is the \"data element\" and the translation element would be considered a property of that element, not a data element in and of itself.\n\nNote: Attributes indicated in red are currently unsupported.\n\n\n","M",1,"For any data element of type CodeableText based on the HL7 CD data type or sub types of CD:\n\nFail the test if the data element fails any test case in TS-CD.\nElse, Fail the test if the data element has attributes other than originalText, code, codeSystem, codeSystemName, codeSystemVersion, displayName, valueSet, valueSetVersion, codingRationale, source, translation, nullFlavor and fails the tests for extensions in TS-Dext, or qualifier (for those data elements where the applicable CDA implementation guide specifically allows the qualifier attribute).\nElse, Fail the test if the translation attribute (if present) fails any test case in TS-Coded for the CodeableText data type.\nElse, Pass the test. \n\nNOTE TO TESTER: \nAbove reference to TS-CD indicates individual test cases for concept descriptor types in this worksheet below (See TC-Types-57 to 68).\nThe CDA schema may need to be examined to determine the HL7 data type that applies to a specific data element.\n","Codeable Text data elements are originalText, code, codeSystem, codeSystemName, codeSystemVersion, displayName, valueSet, valueSetVersion, codingRationale, source (CodedText), translation (CodeableText) or nullFlavor and comply to the specifications outlined in Data Types in NEHTA Specifications [NEHTA-1136:2010]. Any qualifier data elements are specified as allowed in the applicable CDA implementation guide.","TBD",null,{"$f":"IF(H24=\"\",\"0\",IF(H24=\"Pass\",1,IF(H24=\"Fail\",0,IF(H24=\"TBD\",0,IF(H24=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D24)=48,H24=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Coded",null,null,null,2,"For any data element of type CodeableText based on the HL7 CD data type or sub types of CD:\n\nPass the test if the data element contains a nullFlavor;\nElse Pass the test if the data element does not contain a nullFlavor and contains a displayName or originalText or both;\nElse Fail the test.","Codeable Text data elements contain a nullFlavor, or where they do not contain a nullFlavor, they contain a displayName or originalText or both.","TBD",null,{"$f":"IF(H25=\"\",\"0\",IF(H25=\"Pass\",1,IF(H25=\"Fail\",0,IF(H25=\"TBD\",0,IF(H25=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D25)=48,H25=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Coded","TC-Types-05\n","CDA Level 3B [DH-2481:2017]\nIn addition, each section’s encoded content SHALL use the clinical terminology (e.g. AMT and SNOMED CT-AU) and codes from the Pharmaceutical Benefits Schedule and the Medicare Benefits Schedule, as specified in the “Vocab” column of the CDA IGs.\n\n7.5.2.1 Description [ISO21090]\nA CD that has a code, codeSystem or originalText attribute but does not meet external constraints of the applicable value set shall have a nullFlavor attribute with a value of \"OTH\".\n\nNote: It is acceptable to have both a code and a nullFlavor attribute. For example, if a code is available but it is not from the specified reference set then the code is included as well as the nullFlavor \"OTH\" to indicate that the code is not from the specified reference set.\n","C",1,"CONDITION: Conformance level 3B is claimed:\n\nFor every data element where the “Vocab” column of the CDA implementation guide specifies the use of AMT, SNOMED CT-AU, Pharmaceutical Benefits Schedule or Medicare Benefits Schedule:\nFail the test if the applicable codeSystem identifier is not present in either the primary or translation code.\nElse, Fail the test if neither a code nor the nullFlavor \"OTH\" are present with the codeSystem.\nElse, if a reference set is specified then Fail the test where a code is present but is not a value from the specified reference set and nullFlavor \"OTH\" is not present.\nElse, Pass the test.\n\nNOTE TO TESTER: \nA reference set is a subset of the code system and will be stated in the Vocab column if the code must be from a reference set.","Data elements where the “Vocab” column of the CDA implementation guide specifies the use of AMT, SNOMED CT-AU, Pharmaceutical Benefits Schedule or Medicare Benefits Schedule include a codeSystem identifier in either the primary or translation code. This is either a valid code or the nullFlavor \"OTH\" or a combination of both.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D26)=48,H26=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Coded","TC-Types-06","Section 1.8 Conformance [NEHTACDAIG]\nThe following requirement applies to data elements when the value domain is not specified:\n\nIf the vocabulary has been explicitly stated as 'NS', the code sets used SHALL be registered code sets, i.e. registered through the HL7® code set registration procedure with an appropriate object identifier (OID), and SHALL be publicly available.\n\nWhen national standard code sets become available, they SHALL be used and the non-standard code sets SHALL be deprecated.\n\nNote: Contact NEHTA help-desk for code-set clarification.\n          ","M",1,"For any data element of type CodeableText or CodedText where the structured content specification or participation data specification states the value domain is 'NS' (Not Specified):\n\nFail the test if a codeSystem attribute is present and does not pass the TS-UID test case for an OID registered via the HL7® code set registration procedure.\nElse, Pass the test.\n\nNOTE TO TESTER: \nCodeSystem Attribute represents the code set.\nAbove reference to TS-UID indicates individual test case for OID registration in this worksheet below (See TC-Types-107)\n","Codeable Text data elements, where the value domain is 'NS' (Not Specified), has a codeSystem attribute which is publicly available and is OID registered via HL7® code set registration procedure.","TBD",null,0,{"$f":"IF(AND(BGCol(D27)=48,H27=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Coded",null,null,"C",2,"CONDITION: For any data element of type CodedText where a national standard code set is available:\n\nFail the step if the data element does not contain a code from the national standard code set.\nElse, Pass the test.\n\nNOTE TO TESTER:\nA national standard code set will either be listed in the CDA implementation guide, structured content specification, detailed clinical model or published separately as a SNOMED CT-AU reference set. If the CDA implementation guide does not list a national standard code set for the CodedText data element then contact the help desk to determine if a national standard code set is available.\n","CodedText data element has a code from the national standard code set.","TBD",null,{"$f":"IF(H28=\"\",\"0\",IF(H28=\"Pass\",1,IF(H28=\"Fail\",0,IF(H28=\"TBD\",0,IF(H28=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D28)=48,H28=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Coded","TC-Types-07","6.2 CodedText [NEHTA-1136:2010]\nISO data type: CD (concept descriptor)\nAttributes: originalText, code, codeSystem, codeSystemName, codeSystemVersion, displayName or nullFlavor\n\nNote: \nThe full scope of the NEHTA profile of the data types is indicated on the UML model diagram in section 3 of [NEHTA-1136:2010]. For cardinality,  <data Type> Integer is indicated in the UML model as  which is also stated in the Text attribute Value: string[0..1]. See the UML model in the document for full details.  \n\nSome CodedText data elements are mapped to elements of the HL7 ST or CS data type instead of the CD data type. For example, name prefix CodedText is mapped to a ST data and name usage CodedText is mapped to a CS data element.\n","M",1,"For any data element of type CodedText based on the HL7 CD data type or sub types of CD:\n\nIf the CodedText element is mapped to a text element then:\nFail the step if the data element fails test case TC-Types-03.\nElse Pass the test.\nIf the CodedText element is mapped to a CS element then:\nFail the step if the data element fails any test case in TS-CS.\nElse Pass the test.\nIf the CodedText element is mapped to a CD, CV or CE element then:\nFail the step if the data element fails any test case in TS-CD.\nElse, Fail the step if the data element has attributes other than originalText, code, codeSystem, codeSystemName, codeSystemVersion, displayName or nullFlavor and fail the tests for extensions in TS-Dext.\nElse, Fail the step if the number of instances of each type of attribute is not according to the specified cardinality.\nElse, Pass the step.\n\nNOTE TO TESTER: \n- When a CodedText data element is used to qualify a CodeableText data element then in the clinical document the CodedText test case must be applied to the qualifier/value.\n- Above reference to TS-CD indicates individual test cases for concept descriptor types in this worksheet below (See TC-Types-57 to 68).\n- The CDA schema may need to be examined to determine the HL7 data type that applies to a specific data element.\n","Coded Text data elements are originalText, code, codeSystem, codeSystemName, codeSystemVersion, displayName or nullFlavor and comply to the specifications outlined in Data Types in NEHTA Specifications [NEHTA-1136:2010].","TBD",null,0,{"$f":"IF(AND(BGCol(D29)=48,H29=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Coded",null,"CodedText [NEHTASCS]\nValues in this data type SHALL come from the bound value domain, with no exceptions.\n\nNote: As the nullFlavor \"OTH\" means that the applicable concept is not in the value domain then this requirement disallows the use of nullFlavor \"OTH\". \n",null,2,"For any data element of type CodedText based on the HL7 CD data type or sub types of CD:\n\nFail the step if neither a code nor a nullFlavor are present.\nElse, Fail the step if a code is present and the value of the code is not a member of the specified vocabulary.\nElse, Fail the step if a nullFlavor is present and has the value \"OTH\".\nElse, Fail the step if a translation or a qualifier element is present.\nElse, Pass the test.\n\nNOTE TO TESTER: \n- The CDA schema may need to be examined to determine the HL7 data type that applies to a specific data element.\n","Coded text data elements contain a code attribute which is a member of  the specified vocabulary, or a nullFlavor attribute other than 'OTH'.","TBD",null,0,{"$f":"IF(AND(BGCol(D30)=48,H30=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Coded","TC-Types-08","Appendix A. CDA Narratives [NEHTACDAIG]\nIn accordance with the requirement to completely represent section contents, values of codedText or codeableText data elements defined in the SCS SHALL include an originalText or a displayName component (or both). \n\nNote: The requirement above applies to sections of a clinical document. As sections are present only in the body of a document the requirement does not apply to data elements in a document header. \n","M",1,"For any CodeableText or CodedText data element in a section of the clinical document where the data element contains information (i.e. does not have only a nullFlavor attribute):\n\nFail the test if the element does not include an originalText or a displayName.\nElse, Pass the test.\n","CodedText and CodeableText data elements in a section include an originalText or displayName (or both).","TBD",null,0,{"$f":"IF(AND(BGCol(D31)=48,H31=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Coded","TC-Types-09","Section 1.8 Conformance [NEHTACDAIG]\nAny document that claims conformance to any derived conformance profile must meet these base requirements:\n\nIf the vocabulary has been explicitly stated as 'NS' it must be interpreted as:\n\n• NS = In the absence of national standard code sets, the code sets used SHALL be registered code sets, i.e. registered through the HL7 code set registration procedure with an appropriate object identifier (OID), and SHALL be publicly available.\n\n• When national standard code sets become available, they SHALL be used and the non-standard code sets SHALL be deprecated.\n\nNote: The clinical document conformance level requirements allow non-standard code sets to be used instead of codes from AMT, SNOMED CT-AU the Pharmaceutical Benefits Schedule and the Medicare Benefits Schedule if the conformance level is not 3B.\n",null,null,"No additional test case is needed as the test is already provided by TC-Types-06.\n"]
["TS-Coded","END:  TS-Coded (Coded data types)"]
["TS-IL","START:  TS-IL (Identifier and location data types)"]
["TS-IL","Note: Identifier and location data types are defined in Data Types in NEHTA Specifications [NEHTA-1136:2010]."]
["TS-IL","TC-Types-10","7.1 Link [NEHTA-1136:2010]\nISO data type: TEL (telecommunications address)\nAttributes: value or nullFlavor\n\nValue attribute: A Uniform Resource Identifier (URI) specified according to [RFC2396-1998]. MUST point to a locatable resource that returns binary content.\n\nNote: In a Link the useablePeriod and use attributes are prohibited (section 7.1.5 of [NEHTA-0794:2011]).","M",1,"For any data element of type Link based on the HL7 \"TEL\" data type:\n\nFail the test if the data element fails any test case in TS-TEL.\nElse, Fail the test if the data element has attributes other than value or nullFlavor and fails the tests for extensions in TS-Dext.\nElse, Fail the test if the useablePeriod or use attributes are present.\nElse, Pass the test.\n\nNOTE TO TESTER: \n- Above reference to TS-TEL indicates individual test cases for telecommunications address types in this worksheet below (*See TC-Types-69). \n- The 'value' attribute is optional, not mandatory as stated in the ISO 21090 requirements for TEL.\n- The attributes 'useablePeriod' and 'use' are prohibited (section 7.1.5 of [NEHTA-1136:2011]).\n- The CDA schema may need to be examined to determine the HL7 data type that applies to a specific data element.\n","Link data elements have a valid value or a nullFlavor and comply to the specifications outlined in Data Types in NEHTA Specifications [NEHTA-1136:2010].","TBD",null,{"$f":"IF(H36=\"\",\"0\",IF(H36=\"Pass\",1,IF(H36=\"Fail\",0,IF(H36=\"TBD\",0,IF(H36=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D36)=48,H36=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-IL","TC-Types-11","7.2 UniqueIdentifier [NEHTA-1136:2010]\nISO data type: II (Instance identifier)\nAttributes: root, extension, displayable, identifierName, scope, reliability or nullFlavor\n\nNote: An additional attribute, assigningAuthorityName, is allowed when the UniqueIdentifier is contained in an EntityIdentifier [NEHTACDAIG]. \n\nNote: Attributes indicated in red are currently unsupported.\n","M",1,"For any data element of type UniqueIdentifier based on the HL7 \"II\" data type:\n\nFail the test if the data element fails any test case in TS-II.\nElse, if the data element is in an EntityIdentifier then:\nFail the test if the data element has attributes other than root, extension, displayable, identifierName, scope, reliability, nullFlavor and fails the tests for extensions in TS-Dext or assigningAuthorityName.\nElse, Fail the test if the data element has assigningAuthorityName and UniqueIdentifier is not within an EntityIdentifier.\nElse, Pass the test.\n\nNOTE TO TESTER: \n- Above reference to TS-II indicates individual test cases for Instance Identifier data type in this worksheet below (See TC-Types-70 to 92).\n- The CDA schema may need to be examined to determine the HL7 data type that applies to a specific data element.\n","Uniqueidentifier data elements are root, extension, displayable, identifierName, scope, reliability or nullFlavor and comply to the specifications outlined in Data Types in NEHTA Specifications [NEHTA-1136:2010]. Additionally, assigningAuthorityName is allowed when the data element is in an EntityIdentifier.","TBD",null,{"$f":"IF(H37=\"\",\"0\",IF(H37=\"Pass\",1,IF(H37=\"Fail\",0,IF(H37=\"TBD\",0,IF(H37=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D37)=48,H37=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-IL","TC-Types-12","UniqueIdentifier [NEHTASCS]\nIn using this data type, the attributes of the UniqueIdentifier data type SHOULD be populated from the identifiers as defined in AS 5017 (2006) [SA2006a] and AS 4846 (2006) [SA2006b].\n",null,null,"No additional test case is needed as test are already provided elsewhere, including specific tests for Uniqueidentifier in TS-II & TS-UUID."]
["TS-IL","END:  TS-IL (Identifier and location data types)"]
["TS-Quant","START:  TS-Quant (Quantity data types)"]
["TS-Quant","Note: Quantity data types are defined in Data Types in NEHTA Specifications [NEHTA-1136:2010]."]
["TS-Quant","TC-Types-13","8.1 Quantity [NEHTA-1136:2010]\nISO data type: PQ (physical quantity) \nAttributes: value (decimal), unit (CodedText), uncertainty (QTY), uncertaintyType or nullFlavor\n\nNote: When present in the low or high boundaries of a QuantityRange a Quantity may include the boolean ‘inclusive’ attribute to indicate if the boundary is included.\n\nNote: The full scope of the NEHTA profile of the data types is indicated on the UML model diagram in section 3 of [NEHTA-1136:2010]. For example,  <data Type> Real is indicated in the UML model as decimal. See the UML model in the document for full details.  Attributes indicated in red are currently unsupported.\n\nNote: In a Quantity the translation element is prohibited (section 8.1.5 of [NEHTA-0794:2011]).\n\nNote: Attributes indicated in red are currently unsupported.","M",1,"For any data element of type Quantity based on the HL7 \"PQ\" data type:\n\nFail the test if the data element fails any test case in TS-PQ.\nElse, Fail the test if the data element has attributes other than value (decimal), unit (Codedtext), uncertainty (QTY), uncertaintyType, nullFlavor and fails the tests for extensions in TS-Dext or inclusive (BL) (inclusive may be present only if the Quantity is a low or high boundary of a QuantityRange).\nElse, Fail the test if the value attribute (if present) is not a decimal value.\nElse, Fail the test if a translation element is present.\nElse, Pass the test.\n\nNOTE TO TESTER: \n- Above reference to TS-PQ indicates individual test cases for physical quantity data types in this worksheet below (See TC-Types-92 to 93). These aspects of testing are to be considered as part of overall Quantity data type specification conformance.  \n- The CDA schema may need to be examined to determine the HL7 data type that applies to a specific data element.\n","Quantity data elements are either a valid decimal value, unit (CodedText), uncertainty (Quantity), uncertaintyType, nullFlavor or inclusive (BL) and comply to the specifications outlined in Data Types in NEHTA Specifications [NEHTA-1136:2010].\n\n","TBD",null,{"$f":"IF(H42=\"\",\"0\",IF(H42=\"Pass\",1,IF(H42=\"Fail\",0,IF(H42=\"TBD\",0,IF(H42=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D42)=48,H42=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Quant","TC-Types-14","8.2 Integer [NEHTA-1136:2010]\nISO data type: INT \nAttributes: value (Integer), uncertainty (QTY), uncertaintyType or nullFlavor\n\nNote: The full scope of the NEHTA profile of the data types is indicated on the UML model diagram in section 3 of [NEHTA-1136:2010]. \n\nNote: Attributes indicated in red are currently unsupported.\n","M",1,"For any data element of type Integer based on the HL7 \"INT\" data type:\n\nFail the test if the data element fails any test case in TS-INT.\nElse, Fail the test if the data element has attributes other than value (integer), uncertainty (QTY), uncertaintyType or nullFlavor and fails the tests for extensions in TS-Dext.\nElse, Pass the test.\n\nNOTE TO TESTER: \n- Above reference to TS-INT indicates individual test cases for Integer data types in this worksheet below (*See TC-Types-95).\n*Note that currently, for Real data types, there are no individual test cases other than the execution of the Australian CDA Schema Extension.\n- The CDA schema may need to be examined to determine the HL7 data type that applies to a specific data element.\n","Integer data element attributes are a valid value (Integer), uncertainty (QTY), uncertaintyType, nullFlavor and comply to the specifications outlined in Data Types in NEHTA Specifications [NEHTA-1136:2010].\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D43)=48,H43=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Quant","TC-Types-15","8.3 Real [NEHTA-1136:2010]\nISO data type: REAL\nAttributes: value (decimal), uncertainty (QTY), uncertaintyType or nullFlavor\n\nThe NEHTA Real data type SHOULD NOT be used to specify a ‘quantity’ such as. ‘10 people’ or ‘2.4 children’. these are not true examples of Real: they are composites that comprise a real (10, 2.4) and a unit (person, child).\n\nNote: The full scope of the NEHTA profile of the data types is indicated on the UML model diagram in section 3 of [NEHTA-1136:2010]. For example,  <data Type> Real is indicated in the UML model as decimal. See the UML model in the document for full details.  \n\nNote: Attributes indicated in red are currently unsupported.\n","M",1,"For any data element of type Real based on the HL7 \"REAL\" data type:\n\nFail the test if the data element fails any test case in TS-REAL.\nElse, Fail the test if the data element has attributes other than value (decimal), uncertainty (QTY), uncertaintyType or nullFlavor and fails the tests for extensions in TS-Dext.\nElse, Pass the test.\n\nNOTE TO TESTER: \n- No test step is needed for the requirement for the value attribute as the TS-REAL test set contains a test case for the value attribute.\n- Above reference to TS-REAL indicates individual test cases for Real data types in this worksheet below (*See TC-Types-96).\n- The CDA schema may need to be examined to determine the HL7 data type that applies to a specific data element.\n\n","Real data element attributes are a valid value (decimal), uncertainty (QTY), uncertaintyType, or nullFlavor and comply to the specifications outlined in Data Types in NEHTA Specifications [NEHTA-1136:2010].\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D44)=48,H44=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Quant","TC-Types-16","8.4 QuantityRatio [NEHTA-1136:2010]\nISO data type: RTO (ratio)\nAttributes: denominator (Quantity), numerator (Quantity), uncertainty (QTY), uncertaintyType or nullFlavor\n\nNote: The full scope of the NEHTA profile of the data types is indicated on the UML model diagram in section 3 of [NEHTA-1136:2010]. \n\nNote: Attributes indicated in red are currently unsupported.\n","M",1,"For any data element of type QuantityRatio based on the HL7 \"RTO\" data type:\n\nFail the test if the data element fails any test case in TS-RTO.\nElse, Fail the test if the data element has attributes other than denominator (Quantity), numerator (Quantity), uncertainty (QTY), uncertaintyType or nullFlavor and fails the tests for extensions in TS-Dext.\nElse, Fail the test if the denominator attribute (if present) fails any test case in TS-Quant for the Quantity data type.\nElse, Fail the test if the numerator attribute (if present) fails any test case in TS-Quant for the Quantity data type.\nElse, Pass the test.\n\nNOTE TO TESTER: \n- Above reference to TS-RTO indicates individual test cases for ratio data types in this worksheet below (See TC-Types-97)\n- The CDA schema may need to be examined to determine the HL7 data type that applies to a specific data element.\n","Quantity Ratio data element attributes are a valid denominator (Quantity), numerator (Quantity), uncertainty (QTY), uncertaintyType or nullFlavor and comply to the specifications outlined in Data Types in NEHTA Specifications [NEHTA-1136:2010].\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D45)=48,H45=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Quant","TC-Types-17","8.5 Duration [NEHTA-1136:2010]\nISO data type: PQ.TIME\nAttributes: value (decimal), unit (CodedText), uncertainty (QTY), uncertaintyType or nullFlavor\n\nNote: The full scope of the NEHTA profile of the data types is indicated on the UML model diagram in section 3 of [NEHTA-1136:2010]. \n\nNote: In a Duration the translation element is prohibited (section 8.5.5 of [NEHTA-0794:2011]).\n\nNote: Attributes indicated in red are currently unsupported.\n","M",1,"For any data element of type Duration based on the HL7 \"PQ.TIME\" data type:\n\nFail the test if the data element fails any test case in TS-PQ.TIME.\nElse, Fail the test if the data element has attributes other than value (decimal), unit (CodedText),  uncertainty (QTY), uncertaintyType or nullFlavor and fails the tests for extensions in TS-Dext.\nElse, Fail the test if the value attribute (if present) is not a decimal value.\nElse, Fail the test if a translation element is present.\nElse, Pass the test.\n\nNOTE TO TESTER: \n- Above reference to TS-PQ.TIME indicates individual test cases for PQ.TIME data types in this worksheet below (See TC-Types-98). These aspects of testing are to be considered as part of overall Duration data type specification conformance.  \n- The CDA schema may need to be examined to determine the HL7 data type that applies to a specific data element.\n","Duration data element attributes are a valid value (decimal), unit (CodedText),  uncertainty (QTY), uncertaintyType  or nullFlavor and comply to the specifications outlined in Data Types in NEHTA Specifications [NEHTA-1136:2010].\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D46)=48,H46=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Quant","TC-Types-18","8.6 DateTime [NEHTA-1136:2010]\nISO data type: TS (point in time)\nAttributes: value, uncertainty (QTY), uncertaintyType or nullFlavor\n\nNote: When present in the low or high boundaries of a TimeInterval a DateTime may include the boolean ‘inclusive’ attribute to indicate if the boundary is included.\n\nNote: The full scope of the NEHTA profile of the data types is indicated on the UML model diagram in section 3 of [NEHTA-1136:2010]. \n\nNote: Attributes indicated in red are currently unsupported.\n","M",1,"For any data element of type DateTime based on the HL7 \"TS\" data type:\n\nFail the test if the data element fails any test case in TS-TS.\nElse, Fail the test if the data element has attributes other than value, uncertainty (QTY), uncertaintyType, nullFlavor or inclusive (BL) (inclusive may be present only if the DateTime is a low or high boundary of a TimeInterval).\nElse, Pass the test.\n\nNOTE TO TESTER: \n- Above reference to TS-TS indicates individual test cases for TS data types in this worksheet below (See TC-Types-99 to 101).\n- The CDA schema may need to be examined to determine the HL7 data type that applies to a specific data element.","DateTime data element attributes are a valid value, uncertainty (QTY), uncertaintyType, nullFlavor or inclusive and comply to the specifications outlined in Data Types in NEHTA Specifications [NEHTA-1136:2010].\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D47)=48,H47=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Quant","TC-Types-19","DateTime [NEHTASCS]\nString representations of known dates SHALL conform to the nonextended format within the ISO 21090-2011 standard, i.e. YYYY[MM[DD[HH[MM[SS[.U[U[U[U]]]]]]]]][+|-ZZzz].\n\n",null,null,"No additional test case is needed as the same requirement applies to the ISO TS data type and there is an existing test case.\n"]
["TS-Quant","TC-Types-20","The test case was removed as it did not apply to all types of documents so did not belong in this conformance test specification (reference CCA-1431)."]
["TS-Quant","END:  TS-Quant (Quantity data types)"]
["TS-Cont","START:  TS-Cont (Continuous set data types)"]
["TS-Cont","Note: Continuous set data types are defined in Data Types in NEHTA Specifications [NEHTA-1136:2010]."]
["TS-Cont","TC-Types-21","9.1 QuantityRange [NEHTA-1136:2010]\nISO data type: IVL (interval)\nAttributes: low (Quantity), high (Quantity), lowClosed (Boolean), highClosed (Boolean), nullFlavor\n\nIf the upper bound is not known, a nullFlavor may be specified. The high limit SHALL NOT be negative infinity, and shall be higher than the low limit if one exists.\n\nNote: ‘lowClosed’ and ‘highClosed’ are abstract attributes that are included as the ‘inclusive’ attribute defined in the XML instantiation of the HL7 data types [HL72004b]. That is, an ‘inclusive’ attribute is added to the Quantity data type to state that the low or high boundaries are closed.\n\nNote: In a QuantityRange the width element is prohibited (section 9.1.5 of [NEHTA-0794:2011]).\n\nNote: The QuantityRange datatype must be specified as xsi:type=\"IVL_PQ\", as this is a requirement within the CDA schema.","M",1,"For any data element of type QuantityRange based on the HL7 \"IVL\" data type:\n\nFail the test if the data element fails any test case in TS-IVL.\nElse, Fail the test if the data element has attributes other than low, high and nullFlavor and fails the tests for extensions in TS-Dext.\nElse, Fail the test if the low attribute (if present) fails any test case in TS-Quant for the Quantity data type.\nElse, Fail the test if the high attribute (if present) fails any test case in TS-Quant for the Quantity data type.\nElse, Fail the test if a width element is present.\nElse, Pass the test.\n\nNOTE TO TESTER: \n- Above reference to TS-IVL indicates individual test cases for Interval Inv data types in this worksheet below (See TC-Types-102 to 104).\n- Above reference to TS-Quant indicates individual test cases for quantity data types in this worksheet above (See TC-Types-13 to 20).\n- Above reference to TS-BTB indicates individual test case for the boolean data types in this worksheet above (See TC-Types-01). \n- These aspects of testing are to be considered as part of overall QuantityRange data type specification conformance. \n- The CDA schema may need to be examined to determine the HL7 data type that applies to a specific data element.\n\nThe CDA schema allows the unit of the low and high elements to be stated once as an alternative to recording it twice in each of the low and high elements, as in the following example:\n<value unit=\"mL\" xsi:type=\"IVL_PQ\">\n    <low value=\"50\"/>\n    <high value=\"200\"/>\n<value>\n","QuantityRange data element attributes are valid low (Quantity), high (Quantity) or nullFlavor and comply to the specifications outlined in Data Types in NEHTA Specifications [NEHTA-1136:2010]","TBD",null,{"$f":"IF(H53=\"\",\"0\",IF(H53=\"Pass\",1,IF(H53=\"Fail\",0,IF(H53=\"TBD\",0,IF(H53=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D53)=48,H53=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Cont","TC-Types-22","9.2 TimeInterval [NEHTA-1136:2010]\nISO data type: IVL (interval)\nAttributes: low (DateTime), high (DateTime), lowClosed (Boolean), highClosed (Boolean), nullFlavor\n\nIf the upper bound is not known, a nullFlavor may be specified. The high limit SHALL NOT be negative infinity, and shall be higher than the low limit if one exists.\n\nNote: \n‘lowClosed’ and ‘highClosed’ are abstract attributes that are included as the ‘inclusive’ attribute defined in the XML instantiation of the HL7 data types [HL72004b]. That is, an ‘inclusive’ attribute is added to the DateTime data type to state that the low or high boundaries are closed.\n\nA data element based on the HL7 TS data type is equivalent to a data element based on the HL7 IVL data type (section 3.8.1 of [HL72004]). The interval's low boundary is the value of the element and the precision determines the interval's high boundary. The low boundary is included in the interval and the high boundary is not included.\nFor example, suppose the following is used in a TimeInterval data element:\n<effectiveTime value=\"20001204\"/>\nThis is equivalent to the following for a time interval of one day:\n<effectiveTime>\n   <low value='200012040000' inclusive=\"true\"/>\n   <high value='200012050000' inclusive=\"false\"/>\n</effectiveTime>\n","M",1,"For any data element of type TimeInterval based on the HL7 \"IVL\" or \"TS\"data type:\n\nFail the test if the data element fails any test case in TS-IVL or TS-TS,\nElse, if the data element has a low or high attribute then Fail the test if the data element has attributes other than low, high and nullFlavor and fails the tests for extensions in TS-Dext.\nElse, if the data element has a value attribute then Fail the test if the data element has attributes other than value and nullFlavor.\nElse, Fail the test if the low attribute (if present) fails any test case in TS-Quant for the DateTime data type.\nElse, Fail the test if the high attribute (if present) fails any test case in TS-Quant for the DateTime data type.\nElse, Fail the test if the value attribute (if present) fails any test case in TS-Quant for the DateTime data type.\nElse, Pass the test.\n\nNOTE TO TESTER: \n- Above reference to TS-IVL indicates individual test cases for the Interval data types in this worksheet below (See TC-Types-102 to 104).\n-Above reference to TS-TS indicates individual test cases for the Interval data types in this worksheet below (See TC-Types-99 to 101).\n- Above reference to TS-Quant indicates individual test cases for the Quantity data types in this worksheet above (See TC-Types-18 & 19).\n- Above reference to TS-BTB indicates individual test case for the Boolean data types in this worksheet above (See TC-Types-01). \n- These aspects of testing are to be considered as part of overall TimeInterval data type specification conformance. \n- The CDA schema may need to be examined to determine the HL7 data type that applies to a specific data element.","TimeInterval data element attributes are valid low (DateTime), high (DateTime) or nullFlavor and comply with the specifications outlined in Data Types in NEHTA Specifications [NEHTA-1136:2010].","TBD",null,{"$f":"IF(H54=\"\",\"0\",IF(H54=\"Pass\",1,IF(H54=\"Fail\",0,IF(H54=\"TBD\",0,IF(H54=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D54)=48,H54=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Cont","END:  TS-Cont (Continuous set data types)"]
["TS-EntId","START:  TS-EntId (Entity identifier)"]
["TS-EntId","Note: The EntityIdentifier data type is defined in the Participation Data Specification [NEHTA-0794:2011] and CDA implementation guides [NEHTACDAIG]."]
["TS-EntId","TC-Types-23","Section 2.9 Entity Identifier [NEHTA-0794:2011]\nDefinition: A number or code issued for the purpose of identifying a participant within a healthcare context.\n\nNote: An Entity Identifier contains an id, an optional code and an optional assigningGeographicArea, and if the identifier is unknown then a nullFlavor may be present instead of the id element [NEHTACDAIG]. The id element is a UniqueIdentifier [NEHTA-0794:2011]; the code is of the CD data type and assigningGeographicArea@name is of the ST data type. \n\nNote: A participant in a healthcare event belongs to one of these categories [NEHTA-0794:2011]:\n• a person who is a healthcare provider;\n• a person who is not a healthcare provider;\n• an organisation (healthcare provider or otherwise); or\n• a device that authors, sends or receives healthcare information.\n","M",1,"For any data element of type EntityIdentifier:\n\nFail the step if the id (if present) does not pass the UniqueIdentifier test cases in TS-IL.\nElse, Fail the step if the code (if present) does not pass the TS-CD test cases.\nElse, Fail the step if the assigningGeographicArea@name (if present) does not pass the TS-ST test cases.\nElse, Pass the step.\n\nNOTE TO TESTER: \n- Above reference to TS-IL indicates individual test cases for UniqueIdentifier data types in this worksheet above (See TC-Types-11 & 12).\n- Above reference to TS-CD indicates individual test cases for Concept descriptor data types in this worksheet above (See TC-Types-57 to 68).\n- Above reference to TS-ST indicates individual test cases for string data types in this worksheet below (See TC-Types-55 to 56).\n","Any id, code or assigningGeographicArea/name attributes present in the EntityIdentifier are of valid associated data type definitions.","TBD",null,{"$f":"IF(H58=\"\",\"0\",IF(H58=\"Pass\",1,IF(H58=\"Fail\",0,IF(H58=\"TBD\",0,IF(H58=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D58)=48,H58=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-EntId",null,null,null,2,"For any data element of type EntityIdentifier:\n\nFail the step if the data element does not uniquely identify a participant.\nElse, Fail the step if the data element identifies a healthcare recipient and the participant is not a healthcare recipient.\nElse, Fail the step if the data element identifies a person in a healthcare provider organisation (e.g. a legal authenticator or healthcare provider individual) and the participant is not a person in a healthcare provider organisation.\nElse, Fail the step if the data element identifies an organisation and the participant is not an organisation.\nElse, Fail the step if the data element identifies a device and the participant is not a device.\nElse, Pass the step.\n\nNOTE TO TESTER:\nExamples of where a data element does not uniquely identify a participant are a) when the id element includes a Medicare card number (to uniquely identify a person the IRN is also needed) and b) when there is no extension attribute even though that is required by the rules of the namespace identified by the id@root (in this example, to uniquely identify a person the extension attribute is needed). Another example where the data element fails to uniquely identify a participant is when the id element is absent or contains a nullFlavor.\n\nThe identifier type is described by the code (if present) otherwise the identifier type is implied by the value of id. If the code contains codeSystem=\"2.16.840.1.113883.12.203\" then the identifier is described using the HL7 identifier types. If there is no code element but the id includes a national healthcare identifier then the identifier type is a healthcare recipient (for an IHI), healthcare provider individual (for an HPI-I), organisation (for an HPI-O or PAI-O) or a device (for a PAI-D). If there is no code but the id@root is a registered OID then the identifier type may be deduced from the id@root.\n","EntityIdentifier data elements have unique participants with the appropriate associated healthcare details identified for healthcare recipients, healthcare provider organisations, organisations and devices.","TBD",null,{"$f":"IF(H59=\"\",\"0\",IF(H59=\"Pass\",1,IF(H59=\"Fail\",0,IF(H59=\"TBD\",0,IF(H59=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D59)=48,H59=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-EntId","TC-Types-24","Section 8.4 Entity Identifier [NEHTACDAIG] - id@root \nAttribute @root SHALL be used, SHALL be an OID and SHALL NOT be a UUID. \n\nNote: The requirements in the Participation Data Specification [NEHTA-0794:2011] are not listed here as they are equivalent to the requirements in the CDA implementation guides.\n","M",1,"For any data element of type EntityIdentifier:\n\nFail the test if the root attribute is not present in the id element.\nElse, Fail the test if the value of the root attribute does not pass the OID format test in the TS-UID test set.\nElse, Pass the test.\n\nNOTE TO TESTER: \n- Above reference to TS-UID indicates individual test case for OID data types in this worksheet above (See TC-Types-106).\n","Entity Identifier data elements contain an OID in the root attribute of the id element.","TBD",null,{"$f":"IF(H60=\"\",\"0\",IF(H60=\"Pass\",1,IF(H60=\"Fail\",0,IF(H60=\"TBD\",0,IF(H60=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D60)=48,H60=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-EntId","TC-Types-25","Section 8.4 Entity Identifier [NEHTACDAIG] - id@root \nAttribute @root SHALL be a globally unique object identifier (i.e. OID) that identifies the combination of geographic area, issuer and type. If no such OID exists, it SHALL be defined before any identifiers can be created. \n","M",1,"For any data element of type EntityIdentifier:\n\nFail the test if the root attribute fails TC-Types-73 (i.e. does not identify a namespace).\nElse, Fail the test if the namespace identified by the root attribute is not a namespace for the Entity Identifier, that is the geographic area, issuer and type of identifier for a healthcare participant.\nElse, Pass the test.\n\nNOTE TO TESTER: \n- For example, if the value of the root attribute is the identifier of a code system then the root attribute identifies a namespace but it is not the namespace for an Entity Identifier.\n","Namespace identified by the root attribute is a namespace for the Entity Identifier, that is the geographic area, issuer and type of identifier for a healthcare participant.","TBD",null,{"$f":"IF(H61=\"\",\"0\",IF(H61=\"Pass\",1,IF(H61=\"Fail\",0,IF(H61=\"TBD\",0,IF(H61=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D61)=48,H61=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-EntId","TC-Types-26","Section 8.4 Entity Identifier [NEHTACDAIG] - id@extension \nAttribute @extension MAY be used and, if it is used, SHALL be a unique identifier within the scope of the root that is populated directly from the designation.\n\n",null,null,"No additional test case is needed as the same requirement applies to the ISO II data type and there is an existing test case in the TS-II test set.\n"]
["TS-EntId","TC-Types-27","Section 8.4 Entity Identifier [NEHTACDAIG] - id@assigningAuthorityName\nAttribute @assigningAuthorityName SHOULD be used and, if it is used, SHALL be a human readable name for the namespace represented in the root that is populated with the issuer, or identifier type, or a concatenation of both as appropriate. This SHOULD NOT be used for machine readability purposes.\n",null,null,"No additional test case is needed as the test case is included in the TS-II test set.\n"]
["TS-EntId","TC-Types-28","Section 8.4 Entity Identifier [NEHTACDAIG] - assigningGeographicArea \nElement ext:name MAY be used and, if it is used, SHALL be the range and extent that the identifier applies to the object with which it is associated that is populated directly from the geographic area. This SHOULD NOT be used for machine readability purposes.\n\nFor details see: AS 5017-2006: Health Care Client Identifier Geographic Area [SA2006a].\n","M",1,"For any data element of type EntityIdentifier:\n\nFail the test if the assigningGeographicArea is present and has a value that is not one of the values listed in AS 5017-2006: Health Care Client Identifier Geographic Area [SA2006a].\nElse, Fail the test if the value of assigningGeographicArea does not match the associated identifier's range and extent.\nElse, Pass the test.\n\nNOTE TO TESTER: \nThe values listed in AS 5017-2006: Health Care Client Identifier Geographic Area are \"Local Client (Unit Record) Identifier\", \"Area/Region/District Identifier\", \"State or Territory Identifier\" and \"National Identifier\".\n","Any instance of assigningGeographicArea in EntityIdentifier data elements are of a value listed in AS 5017-2006: Health Care Client Identifier Geographic Area [SA2006a] and describe the range and extent applicable to the object.","TBD",null,{"$f":"IF(H64=\"\",\"0\",IF(H64=\"Pass\",1,IF(H64=\"Fail\",0,IF(H64=\"TBD\",0,IF(H64=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D64)=48,H64=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-EntId","Note: Included below are test cases for specific types of Entity Identifiers common to many types of documents, which have requirements additional to the general Entity Identifier requirements."]
["TS-EntId","TC-Types-29","027738 Organisation OID [DH-2481:2017] \nThe root attribute of the id element SHALL identify the organisation that maintains the identifier using an OID registered with the HL7 OID registry.\n\nNote: \nThe OID in the root attribute of the id element will either be the registered OID or derived from an OID registered for an organisation that owns or has the authority over the registration that maintains the identifier. \n\n027736 Value of the id extension attribute [DH-2481:2017] \nThe identifier SHALL be recorded as the value of the id element extension attribute.\n\n027737 Recording an organisation name [DH-2481:2017] \nThe name of the organisation that maintains the identifier SHALL be recorded as the assigningAuthorityName in id element assigningAuthorityName attribute.\n\n\n","C",1,"CONDITION: A healthcare provider organisation has included an entity identifer for a person.\n\nFail the test if id@root does not identify the organisation that maintains the identifier using an OID registered with the HL7 OID registry.\nElse, Fail the step if the extension attribute is a null string.\nElse, Fail the step if the extension attribute is absent and there is no nullFlavor. \nElse, Fail the test if id@assigningAuthorityName is not present, or has a value that does not represent the organisation that registered the OID.\nElse, Pass the test.\n\nNOTE TO TESTER: \n The requirement applies to any type of person, such as an individual healthcare provider, a healthcare individual, or a legal authenticator.\n An example of the use of the assigningAuthorityName attribute is provided in the Common Patterns section within each CDA IG. Refer to section 8 (Entity Identifiers)","The healthcare provider organisation has an OID registered with the HL7 OID registry, has its name in the assigningAuthorityName attribute, and has provided the person's identifier in the extention attribute.","TBD",null,{"$f":"IF(H66=\"\",\"0\",IF(H66=\"Pass\",1,IF(H66=\"Fail\",0,IF(H66=\"TBD\",0,IF(H66=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D66)=48,H66=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-EntId","TC-Types-30","027789 Root attribute for healthcare individual [DH-2481:2017] \nIf the person being identified is a healthcare individual, the root attribute of the id element SHALL either be the OID 1.2.36.1.2001.1005.29 followed by the healthcare identifier of the organisation that maintains the identifier, or an OID that identifies the organisation.\n\nNote: \nThe healthcare identifier of the organisation is commonly referred to as a healthcare provider identifier - organisation (HPI-O). \n\n027790 Entity Identifier for healthcare individual [DH-2481:2017] \nIf the person being identified is a healthcare individual, the entity identifier SHALL include a code element with attributes codeSystem=“2.16.840.1.113883.12.203” and codeSystemName=“Identifier Type (HL7)”, and the code SHALL be a valid HL7 Identifier Type code that does not indicate an employee (i.e. to differentiate between identifiers).\n\nNote: \nThe following codes can be used: \nLR - Local Registry ID; \nMR - Medical record number; \nMRT - Temporary medical record number; \nPE - Living subject enterprise number; \nPI - Patient internal identifier; \nPN - Person number; \nPNT - Temporary living subject number; \nor PT - Patient external identifier.\n","C",1,"CONDITION: A healthcare provider organisation has included an entity identifer for a healthcare individual.\n\nFail the test if id@root neither commences with the OID \"1.2.36.1.2001.1005.29\"  followed by the national healthcare identifier of the organisation nor an OID that identifies the organisation.\nElse, Fail the test if code @codeSystem is not present with the value \"2.16.840.1.113883.12.203\".\nElse, Fail the test if code @codeSystemName is not present with the value \"Identifier Type (HL7)\".\nElse, Fail the test if the code is not applicable for the healthcare Individual.\nElse, Pass the test.\n\nNOTE TO TESTER: \nExample of an invalid code is \"EI\" which means 'Employee Identifier'. Refer to the list in the requirements cell which provides a list of valid codes.\nHealthcare individual refers to healthcare consumer.\n","The healthcare provider organisation is identified by the value of the OID in the root attribute and has provided a valid identifer type code for the healthcare individual.","TBD",null,0,{"$f":"IF(AND(BGCol(D67)=48,H67=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-EntId","TC-Types-82","027791 Root attribute for individual healthcare provider or legal authenticator [DH-2481:2017] \nIf the person being identified is an individual healthcare provider or a legal authenticator, the root attribute of the id element SHALL either be the OID 1.2.36.1.2001.1005.41 followed by the healthcare identifier of the organisation that maintains the identifier, or an OID that identifies the organisation.\n\nNote: The healthcare identifier of the organisation is commonly referred to as a healthcare provider identifier - organisation (HPI-O).\n\n027792 Entity identifier for individual healthcare providers or legal authenticators [DH-2481:2017] \nIf the person being identified is an individual healthcare provider or a legal authenticator, the entity identifier SHALL include a code element with attributes code=“EI”, codeSystem=“2.16.840.1.113883.12.203” and codeSystemName=“Identifier Type (HL7)”, to indicate the identifier is a local employee identifier.\n","C",1,"CONDITION: A healthcare provider organisation has included an entity identifer for a healthcare provider individual or legal authenticator\n\nFail the test if id@root neither commences with the OID \"1.2.36.1.2001.1005.41\" followed by the national healthcare identifier of the organisation nor an OID that identifies the organisation.\nElse, Fail the test if code @codeSystem is not present with the value \"2.16.840.1.113883.12.203\".\nElse, Fail the test if code @codeSystemName is not present with the value \"Identifier Type (HL7)\".\nElse, Fail the test if code is not present with the value \"EI\".\nElse, Pass the test.\n\n","The healthcare provider organisation is identified by the value of the OID in the root attribute and has provided a valid identifer type code for the healthcare provider individual or legal authenticator.","TBD",null,0,{"$f":"IF(AND(BGCol(D68)=48,H68=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-EntId","END:  TS-EntId (Entity identifier)"]
["TS-Entit","START:  TS-Entit (Entitlement)"]
["TS-Entit","Note: The Entitlement data group is defined in the Participation Data Specification [NEHTA-0794:2011] and CDA implementation guides [NEHTACDAIG]."]
["TS-Entit","TC-Types-31","Section 2.74 Entitlement [NEHTA-0794:2011]\nDefinition: The entitlement or right of a participant to act in a given capacity (as defined by Entitlement Type) within a healthcare context.\n\nNote: A participant in a healthcare event belongs to one of these categories [NEHTA-0794:2011]:\n• a person who is a healthcare provider;\n• a person who is not a healthcare provider;\n• an organisation (healthcare provider or otherwise); or\n• a device that authors, sends or receives healthcare information.\n\nNote: An Entitlement contains a mandatory entitlement number (UniqueIdentifier), a mandatory entitlement type (codeableText) and an optional entitlement validity duration (TimeInterval).\n","M",1,"For any data group that is an Entitlement:\n\nFail the step if the entitlement type is not applicable for the type of participant.\nElse, Pass the step.\n","Entitlement data groups have appropriate entitlement types for the type of participants.","TBD",null,{"$f":"IF(H72=\"\",\"0\",IF(H72=\"Pass\",1,IF(H72=\"Fail\",0,IF(H72=\"TBD\",0,IF(H72=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D72)=48,H72=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Entit",null,null,null,2,"For any data group that is an Entitlement:\n\nFail the step if the entitlement number is not present or does not pass the UniqueIdentifier test case in TS-IL.\nElse, Fail the step if the entitlement type is not present or does not pass the CodeableText test case in TS-Coded.\nElse, Fail the step if the entitlement validity duration (if present) does not pass the TimeInterval test case in TS-Cont.\nElse, Pass the step.\n\nNOTE TO TESTER: \n- Above reference to TS-IL indicates individual test case for the UniqueIdentifier location data type in this worksheet above (See TC-Types-11).\n- Above reference to TS-Coded indicates individual test cases for the CodeableText data type in this worksheet above (See TC-Types-04 to 09).\n- Above reference to TS-Cont indicates individual test case for the TimeInterval data type in this worksheet above (See TC-Types-22).\n","Entitlement data groups include a unique entitlement number, a valid entitlement type and an entitlement validity duration with a valid TimeInterval.","TBD",null,{"$f":"IF(H73=\"\",\"0\",IF(H73=\"Pass\",1,IF(H73=\"Fail\",0,IF(H73=\"TBD\",0,IF(H73=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D73)=48,H73=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Entit","TC-Types-32","Section 2.76 Entitlement Type [NEHTA-0794:2011]\nDefinition: The description of the scope of an entitlement.\nData Type: CodeableText\n\nIn the absence of national standard code sets, the code sets used SHALL be registered code sets, i.e. registered through the HL7 code set registration procedure with an appropriate object identifier (OID), and SHALL be publicly available. \n\nWhen national standard code sets become available, they SHALL be used and the non standard code sets SHALL be deprecated.\n","M",1,"For any data group that is an Entitlement:\n\nFail the test if the entitlement type does not pass the TS-UID test case for an OID registered via the HL7® code set registration procedure.\nElse, Pass the test.\n\nNOTE TO TESTER: \nAbove reference to TS-UID indicates an individual test case for OID Registration in this worksheet(See TC-Types-107)\n\n","Entitlement type is an OID registered appropriately via the HL7® code set registration procedure. ","TBD",null,{"$f":"IF(H74=\"\",\"0\",IF(H74=\"Pass\",1,IF(H74=\"Fail\",0,IF(H74=\"TBD\",0,IF(H74=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D74)=48,H74=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Entit","TC-Types-33","Section 2.9 Entity Identifier [NEHTA-0794:2011]\nIf a person's Medicare Number is used as the Entity Identifier, this SHALL also be included as an ENTITLEMENT if the ENTITLEMENT is required, i.e. the Entity Identifier SHALL NOT be relied on to give Medicare entitlement information.\n\nNote: Inclusion of entitlement in a clinical document is optional for all types of documents so the requirement to include the Medicare number in the entitlement data group is interpreted to mean Medicare number will be provided along with any entitlement.\n","M",1,"For any data group that is an Entitlement:\n\nIf a Medicare Number has been included as a local identifier for a person and at least one entitlement is also included then Fail the test if the entitlements do not include either the Medicare card number or the individual Medicare card number.\nElse, Pass the test.\n\nNOTE TO TESTER:\nAn entity identifier includes an individual Medicare card number if it contains an id@root=\"1.2.36.1.5001.1.0.7\". An entitlement with id@root=\"1.2.36.1.5001.1.0.7\" contains an individual Medicare card number and an entitlement with id@root=\"1.2.36.1.5001.1.0.7.1\" contains a Medicare card number. An entity identifier with id@root=\"1.2.36.1.5001.1.0.7.1\" is invalid and would fail one of the TS-EntId test cases.\n","Where a Medicare Number is used as a local identifier for a person, the entitlements data group also contains the Medicare Number or the Individual Medicare Number.","TBD",null,{"$f":"IF(H75=\"\",\"0\",IF(H75=\"Pass\",1,IF(H75=\"Fail\",0,IF(H75=\"TBD\",0,IF(H75=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D75)=48,H75=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Entit","Note: Included below are test cases for specific Entitlement data elements, common to many types of documents, which have requirements additional to the general Entitlement requirements."]
["TS-Entit","TC-Types-34","Medicare number used for an entitlement\n\nNote: Requirements for the displayName are listed in table NCTIS: Admin Codes - Entitlement Type of the CDA implementation guides [NEHTACDAIG] and the object identifier for id@root is listed in the Standards Australia handbook 234 – 2012, section 7.","M",1,"For any data group that is an Entitlement:\n\nIf the data group contains codeSystem \"1.2.36.1.2001.1001.101.104.16047\" and code \"1\" then:\nFail the test if the displayName (if present) is not “Medicare Benefits”.\nElse, Fail the test if the id@root is neither \"1.2.36.1.5001.1.0.7\" nor \"1.2.36.1.5001.1.0.7.1\".\nElse, Fail the test if the id@extension is neither \"10\" nor \"11\" digits which passes the valid check digit.\nElse, Pass the test.\n","'Medicare Benefits' is the displayName when the data group contains the corresponding codeSystem with code = '1' and id@root is a valid id.","TBD",null,{"$f":"IF(H77=\"\",\"0\",IF(H77=\"Pass\",1,IF(H77=\"Fail\",0,IF(H77=\"TBD\",0,IF(H77=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D77)=48,H77=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Entit","TC-Types-35","Centrelink Customer Reference Number used for an entitlement\n\nNote: Requirements for the displayName are listed in table NCTIS: Admin Codes - Entitlement Type of the CDA implementation guides [NEHTACDAIG] and the object identifier for id@root is listed in the Standards Australia handbook 234 – 2012, section 7.","M",1,"For any data group that is an Entitlement:\n\nIf the data group contains codeSystem \"1.2.36.1.2001.1001.101.104.16047\" and code \"2\", \"3\" or \"4\" then:\na. Fail the test if the code is \"2\" and the displayName (if present) is not “Pensioner Concession\",\nb. Else, Fail the test if the code is \"3\" and the displayName (if present) is not “Commonwealth Seniors Health Concession\",\nc. Else, Fail the test if the code is \"4\" and the displayName (if present) is not “Health Care Concession\",\nElse, Fail the test if the id@root is not \"2.16.840.1.113883.3.879.270098\" or \"2.16.840.1.113883.3.879.369274\",\nElse, Pass the test.\n","'Pensioner Concession' is the displayName when the data group contains the corresponding codeSystem with code = '2' and id@root is a valid id.\n\n'Commonwealth Seniors Health Concession' is the displayName when the data group contains the corresponding codeSystem with code = '3' and id@root is a valid id.\n\n'Health Care Concession' is the displayName when the data group contains the corresponding codeSystem with code = '4' and id@root is a valid id.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D78)=48,H78=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Entit","TC-Types-36","DVA file number used for an entitlement\n\nNote: Requirements for the displayName are listed in table NCTIS: Admin Codes - Entitlement Type of the CDA implementation guides [NEHTACDAIG] and the object identifier for id@root is listed in the Standards Australia handbook 234 – 2012, section 7.","M",1,"For any data group that is an Entitlement:\n\nIf the data group contains codeSystem \"1.2.36.1.2001.1001.101.104.16047\" and code \"5\", \"6\" or \"7\" then:\na. Fail the test if the code is \"5\" and the displayName (if present) is not \"Repatriation Health Gold Benefits\",\nb. Else, Fail the test if the code is \"6\" and the displayName (if present) is not \"Repatriation Health White Benefits\",\nc. Else, Fail the test if the code is \"7\" and the displayName (if present) is not \"Repatriation Health Orange Benefits\",\nElse, Fail the test if the id@root is not \"2.16.840.1.113883.3.879.270091\" or \"2.16.840.1.113883.3.879.339127\",\nElse, Pass the test.\n","'Repatriation Health Gold Benefits' is the displayName when the data group contains the corresponding codeSystem with code = '5' and id@root is a valid id.\n\n'Repatriation Health White Benefits' is the displayName when the data group contains the corresponding codeSystem with code = '6' and id@rootis a valid id.\n\n'Repatriation Health Orange Benefits' is the displayName when the data group contains the corresponding codeSystem with code = '7' and id@root is a valid id.\n\n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D79)=48,H79=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Entit","TC-Types-37","Safety Net card number used for an entitlement\n\nNote: Requirements for the displayName are listed in table NCTIS: Admin Codes - Entitlement Type of the CDA implementation guides [NEHTACDAIG] and the object identifier for id@root is listed in the Standards Australia handbook 234 – 2012, section 7.\n","M",1,"For any data group that is an Entitlement:\n\nIf the data group contains codeSystem \"1.2.36.1.2001.1001.101.104.16047\" and code \"8\" or \"9\" then:\nFail the test if the code is \"8\" and the displayName (if present) is not \"Safety Net Concession\".\nElse, Fail the test if the code is \"9\" and the displayName (if present) is not \"Safety Net Entitlement\".\nElse, Fail the test if the id@root is not a registered OID.\nElse, Pass the test.\n","'Safety Net Concession' is the displayName when the data group contains the corresponding codeSystem with code = '8' and id@root is a valid id.\n\n'Safety Net Entitlement' is the displayName when the data group contains the corresponding codeSystem with code = '9' and id@root is a valid id.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D80)=48,H80=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Entit","TC-Types-38","Medicare prescriber number used for an entitlement\n\nNote: Requirements for the displayName are listed in table NCTIS: Admin Codes - Entitlement Type of the CDA implementation guides [NEHTACDAIG] and the object identifier for id@root is listed in the Standards Australia handbook 234 – 2012, section 7.","M",1,"For any data group that is an Entitlement:\n\nIf the data group contains codeSystem \"1.2.36.1.2001.1001.101.104.16047\" and code \"10\" then:\nFail the test if the displayName (if present) is not “Medicare Prescriber Number”.\nElse, Fail the test if the id@root is not \"1.2.36.174030967.0.3\".\nElse, Pass the test.\n","'Medicare Prescriber Number' is the displayName when the data group contains the corresponding codeSystem with code = '10' and id@root is a valid id.","TBD",null,0,{"$f":"IF(AND(BGCol(D81)=48,H81=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Entit","TC-Types-39","Medicare pharmacy approval number used for an entitlement\n\nNote: Requirements for the displayName are listed in table NCTIS: Admin Codes - Entitlement Type of the CDA implementation guides [NEHTACDAIG] and the object identifier for id@root is listed in the Standards Australia handbook 234 – 2012, section 7.","M",1,"For any data group that is an Entitlement:\n\nIf the data group contains codeSystem \"1.2.36.1.2001.1001.101.104.16047\" and code \"11\" then:\nFail the test if the displayName (if present) is not “Medicare Pharmacy Approval Number\".\nElse, Fail the test if the id@root is not \"1.2.36.174030967.1.3.2.1\".\nElse, Pass the test.\n","'Medicare Pharmacy Approval Number' is the displayName when the data group contains the corresponding codeSystem with code = '11' and id@root is  a valid id.","TBD",null,0,{"$f":"IF(AND(BGCol(D82)=48,H82=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Entit","END:  TS-Entit (Entitlement)"]
["TS-AddrDG","START:  TS-AddrDG (Address data group)"]
["TS-AddrDG","Note: The Address data group is defined in the Participation Data Specification [NEHTA-0794:2011] and CDA implementation guides [NEHTACDAIG]."]
["TS-AddrDG","TC-Types-40","Section 3.1 Address [NEHTA-0794:2011]\nThere SHALL NOT be more than two addresses (e.g. one street address and one postal address) associated with any one individual or organisation.","M",1,"For any person or organisation listed in a clinical document:\n\nFail the test if there are more than two addresses.\nElse, Pass the test.\n","Clinical documents contain a maximum of two addresses for any individual or organisation.","TBD",null,{"$f":"IF(H86=\"\",\"0\",IF(H86=\"Pass\",1,IF(H86=\"Fail\",0,IF(H86=\"TBD\",0,IF(H86=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D86)=48,H86=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-AddrDG","TC-Types-41","Section 3.2 No Fixed Address Indicator [NEHTA-0794:2011]\nWhere an ADDRESS has \"No Fixed Address Indicator\" set to \"true\", then there SHALL be a single Unstructured Australian Address Line (in AUSTRALIAN ADDRESS) or International Address Line (in INTERNATIONAL ADDRESS) having the value of \"Unknown\".\n\nNote: \"No Fixed Address Indicator\" is set to \"true\" if the address has a nullFlavor=\"NA\" (i.e. addr/@nullFlavor=\"NA\").\n","M",1,"For any Australian address in a clinical document:\n\nFail the test if addr/@nullFlavor=\"NA\" and there is no value of \"Unknown\" for either a single Unstructured Australian Address Line (in AUSTRALIAN ADDRESS) or International Address Line (in INTERNATIONAL ADDRESS).\nElse, Pass the test. \n","Where there is no Fixed Address provided, a value 'Unknown' is present in either a single Unstructured Australian Address Line or an International Address Line. ","TBD",null,0,{"$f":"IF(AND(BGCol(D87)=48,H87=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-AddrDG","TC-Types-42","Section 3.4 International Address [NEHTA-0794:2011]\nThe children of this data group are all optional, but at least one SHALL be supplied.\n\nNote: The children of International Address are International Address Line, International State/Province, International Postcode and Country.\n","M",1,"For any International address in a clinical document:\n\nFail the test if either 'Unknown' or an International address is included and none of the following elements are present: International Address Line, International State/Province, International Postcode or Country.\nElse, Pass the test.\n","International Address contains at least one of either International Address Line, International State/Province, International Postcode or Country elements.","TBD",null,0,{"$f":"IF(AND(BGCol(D88)=48,H88=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-AddrDG","TC-Types-43","Section 3.10 Australian Address [NEHTA-0794:2011]\nThe children of this data group are all optional, but at least one SHALL be supplied.\n\nNote: The children of Australian Address are Unstructured Australian Address Line, Structured Australian Address Line, Australian Suburb/Town/Locality, Australian State/Territory, Australian Postcode and Australian Delivery Point Identifier.","M",1,"For any Australian address in a clinical document:\n\nFail the test if either 'Unknown' or an address is included and none of the following elements are present: Unstructured Australian Address Line, Structured Australian Address Line, Australian Suburb/Town/Locality, Australian State/Territory, Australian Postcode or Australian Delivery Point Identifier.\n Else, Pass the test.\n","An Australian address contains at least one of either Unstructured Australian Address Line, Structured Australian Address Line, Australian Suburb/Town/Locality, Australian State/Territory, Australian Postcode or Australian Delivery Point Identifier elements.","TBD",null,0,{"$f":"IF(AND(BGCol(D89)=48,H89=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-AddrDG","TC-Types-44","Section 3.11 Unstructured Australian Address Line [NEHTA-0794:2011]\nWhere the STRUCTURED ADDRESS LINE is populated, this item SHOULD be a combination of the following standard address data elements and SHOULD be concatenated in the following sequence:\n• Australian Unit Type\n• Australian Unit Number\n• Australian Address Site Name\n• Australian Level Type\n• Australian Level Number\n• Australian Street Number\n• Australian Lot Number\n• Australian Street Name\n• Australian Street Type Code\n• Australian Street Suffix Code\n• Australian Postal Delivery Type\n• Australian Postal Delivery Number\n\nNote: there is a typing error in the requirement. \"Where the STRUCTURED ADDRESS LINE is populated\" should be \"Where the UNSTRUCTURED AUSTRALIAN ADDRESS LINE is populated\".\n","O",1,"For any address in a clinical document containing an Unstructured Australian Address Line:\n\nFail the test if the Unstructured Australian Address Line contains address elements other than the elements listed in the requirement.\nElse, Fail the test if the address components in the Unstructured Australian Address Line are not in the same order as the order listed in the requirement.\nElse, Pass the test.\n\nNOTE TO TESTER:\nAddress Line details are contained in the <streetAddressLine> element.\n","Unstructured Australian Address Line contains only the address elements listed in the requirement and is in the order indicated.","TBD",null,0,{"$f":"IF(AND(BGCol(D90)=48,H90=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-AddrDG","TC-Types-45","Section 3.21 Australian Lot Number [NEHTA-0794:2011]\nFor identification purposes, the word 'Lot' SHOULD precede the lot number and be separated by a space.\n","O",1,"For any Australian address in a clinical document:\n\nFail the test if the word 'Lot' followed by a space does not precede the lot number,\nElse, Pass the test.\n\nNOTE TO TESTER: \nExamples of valid lot numbers are \"Lot 716\", \"Lot 534A\" and \"Lot 716-718\".\n","Australian Lot Number includes a space between the word 'lot' and the Lot number itself.","TBD",null,0,{"$f":"IF(AND(BGCol(D91)=48,H91=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-AddrDG","TC-Types-46","Section 3.30 Australian Suburb/Town/Locality [NEHTA-0794:2011]\nAustralian Suburb/Town/Locality MAY be a town, city, suburb or commonly used location name such as a large agricultural property or Aboriginal community.\n\nSection 3.31 Australian Suburb/Town/Locality Values [NEHTA-0794:2011]\nValues in this data element SHOULD comply with descriptions in the Australia Post Postcode File.\n\nNote: The Australia Post Postcode File can be accessed via http://www.auspost.com.au/postcodes. The data type for Australian Suburb/Town/Locality is CodeableText.\n","O",1,"For any Australian address in a clinical document:\n\nFail the test if the Suburb/Town/Locality is not one of the values in the Australia Post Postcode File (http://www.auspost.com.au/postcodes).\nElse, Pass the test.\n","Address Suburb/Town/Locality exists in Australia Postcode file.","TBD",null,0,{"$f":"IF(AND(BGCol(D92)=48,H92=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-AddrDG","TC-Types-47","Section 3.34 Australian Postcode [NEHTA-0794:2011]\nData in this data element SHOULD be verified against the locality field contained within the Australia Post Postcode book.\n\nSection 3.35 Australian Postcode Values [NEHTA-0794:2011]\nValues in this data element SHOULD comply with descriptions in the Australia Post Postcode File.\n","O",1,"For any Australian address in a clinical document:\n\nFail the test if the postcode is not the value found by searching for the Australian Suburb/Town/Locality in the Australia Post Postcode File (http://www.auspost.com.au/postcodes).\nElse, Pass the test.\n","Address postcode for the associated Suburb/Town/Locality exists in Australia Postcode file.","TBD",null,0,{"$f":"IF(AND(BGCol(D93)=48,H93=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-AddrDG","END:  TS-AddrDG (Address data group)"]
["TS-NF","START:  TS-NF (NullFlavor)"]
["TS-NF","TC-Types-48","7.1.4 Exceptional Value Detail [ISO21090]\nAll exceptional values shall have a NullFlavor, and the nullFlavor provides more information as to why the value is an exception to the rules.\n","M",1,"For any nullFlavor attribute:\n\nFail the test if the value of the nullFlavor is invalid for the data element where it is used.\nElse, Pass the test.\n\nNOTE TO TESTER: \nAn example is the value NINF for the start of a health event encompassing encounter, as NINF indicates the health event started at negative infinity. A common error is to use nullFlavor NA to indicate there is no information, which may be an assumption that NA means no information is available, whereas it actually means no proper value is applicable (e.g. a male cannot have a menstrual period).\n\nExamples where it is invalid to have a value and a nullFlavor of any type are data elements of the HL7 'BL', 'INT', 'PQ', 'REAL' and 'TS' data types (sections 2.2, 2.26, 2.27, 2.28 and 2.32 of [HL72004b]).\n\nAnother example of where a proper value is provided as well as a nullFlavor value that indicates a proper value is not provided. Such nullFlavor values are UNC, UNK, ASKU, NAV, NASK and MSK.\n","Exceptional values are represented by a valid, corresponding nullFlavor.","TBD",null,{"$f":"IF(H96=\"\",\"0\",IF(H96=\"Pass\",1,IF(H96=\"Fail\",0,IF(H96=\"TBD\",0,IF(H96=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D96)=48,H96=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-NF","TC-Types-49","7.1.4 Null and NullFlavor [ISO21090]\nNot all the NullFlavors can be used with all the different types. The NullFlavors PINF and NINF may only be used with specific types (INT, REAL, PQ and TS). The NullFlavor UNC may only be used with types that have an originalText (CD, QTY, QSET, and specializations). The NullFlavors QS and TRC may only be used with PQ.\n\n7.3.3.3.1 NullFlavor UNC [ISO21090]\nThe NullFlavor UNC shall only be used with any type that has an originalText, and when UNC is used the originalText property shall be populated.","M",1,"For any data element that is not of ISO data type INT, REAL, PQ or TS:\n\nFail the step if the data element contains a nullFlavor PINF or NINF.\nElse, Pass the step.\n\nNOTE TO TESTER: \nThe NEHTA data types Integer, Real, Quantity, DateTime are specializations of the ISO data types INT, REAL, PQ or TS and allow the use of the nullFlavor PINF and NINF. Other NEHTA data types are not specializations of INT, REAL, PQ or TS so they disallow the use of nullFlavor PINF and NINF.\n","PINF and NINF nullFlavors are used with ISO data type INT, REAL, PQ or TS.","TBD",null,{"$f":"IF(H97=\"\",\"0\",IF(H97=\"Pass\",1,IF(H97=\"Fail\",0,IF(H97=\"TBD\",0,IF(H97=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D97)=48,H97=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-NF",null,null,null,2,"Fail the step if a data element is not of ISO data type CD, QTY, QSET or specializations and contains a nullFlavor UNC.\nElse Fail the step if the data element contains nullFlavor UNC without an originalText.\nElse, Pass the step.\n\nNOTE TO TESTER:\nThe NEHTA data types CodeableText and CodedText are specializations of the ISO data types of the ISO data type CD and allow the use of originalText, so they allow the use of the nullFlavor UNC. Other NEHTA data types do not allow the use of nullFlavor UNC.\n","UNC nullFlavor is used with ISO data type CD, QTY, QSET or specializations and OrginalText.","TBD",null,{"$f":"IF(H98=\"\",\"0\",IF(H98=\"Pass\",1,IF(H98=\"Fail\",0,IF(H98=\"TBD\",0,IF(H98=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D98)=48,H98=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-NF",null,null,null,3,"For any data element that is not of ISO data type PQ:\n\nFail the step if the data element contains a nullFlavors QS or TRC.\nElse, Pass the step.\n\nNOTE TO TESTER: \nThe NEHTA data type Quantity is a specialization of the ISO data type PQ and allows the use of the nullFlavor QS or TRC. Other NEHTA data types do not allow the use of nullFlavor QS or TRC.\n\n","QS and TRC nullFlavors are used with ISO data type PQ.","TBD",null,{"$f":"IF(H99=\"\",\"0\",IF(H99=\"Pass\",1,IF(H99=\"Fail\",0,IF(H99=\"TBD\",0,IF(H99=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D99)=48,H99=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-NF","END:  TS-NF (NullFlavor)"]
["TS-BL","START:  TS-BL (Boolean)"]
["TS-BL","TC-Types-50","7.3.4.5 Invariants [ISO21090]\nThe BL shall have a value if it does not have a nullFlavor.\n","M",1,"For any data element of ISO data type BL or the derived type Boolean:\nFail the test if there is no value attribute and no nullFlavor attribute.\nElse, Pass the test.\n\n\n\n","Either the value attribute or the code attribute is present in the code element \n","TBD",null,{"$f":"IF(H102=\"\",\"0\",IF(H102=\"Pass\",1,IF(H102=\"Fail\",0,IF(H102=\"TBD\",0,IF(H102=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D102)=48,H102=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-BL","END:  TS-BL (Boolean)"]
["TS-ED","START:  TS-ED (Encapsulated data)"]
["TS-ED","Note: encapsulated data includes 1) inline data (i.e. data within the clinical document); 2) a document in the CDA package referenced from the clinical document; and 3) a website or document on a network referenced from the clinical document. "]
["TS-ED","The conformance to the requirements for the last two types of encapsulated data is assessed by applying the Conformance Test Specification for CDA Packaging[NEHTA-2065:2015]."]
["TS-ED","TC-Types-51","7.4.2.5 Invariants [ISO21090]\n- Either reference, data, value or xml shall be provided if not nullFlavoured, and at least one byte of data shall be referenced.\n- An integrityCheckAlgorithm shall be provided and may only be provided if an integrityCheck is provided.\n- If a thumbnail is provided, it shall not use a reference.\n- If a thumbnail is provided, it shall not have a thumbnail.\n- Compression can only be specified if data are provided as a binary or as a reference.\n- Mediatype cannot be null.\n\nNote: Requirements for attributes defined for the ED data type but not allowed by the Australian CDA Schema Extension are not listed here.\nNote: Based on current version of Australian CDA schema (v20140219) instead of value attribure it is inline data. \nEg: <originalText> text is here</originalText>\nNote: By default SHA 1 value is included for integrityCheckAlgorithm.\nNote: By default, the Mediatype contains 'text/plain'.\nNote: Attributes indicated in red are currently unsupported.\n","M",1,"For any data element of ISO data type ED:\n\nPass the test if there is either reference, or data, or value, or xml data, or nullFlavor.\nElse, Fail the test.\n\nNOTE TO TESTER: \n1) An originalText element is of the ED data type and is usually used by inserting text as follows:\n<originalText> text is here</originalText>\n\n2) An ED element may contain a reference instead of a value; another way for an originalText to reference data is shown below:\n<originalText>\n               <reference value=\"#a1\"/>\n </originalText>\n\nWhere the reference is to other text in the document, for example it may be to a section narrative or to text within the narrative as indicated by the <content> as follows:\n<content ID=\"a1\">Asthma</content>\n\nGiven the requirement to reference at least one byte it would be an error for there to be no element with the ID=”a1” or for the referenced text to have no characters as follows:\n<content ID=\"a1\"></content>\n\n\n\n","Data element of ISO data type ED, have at least one character or a nullFlavor. ","TBD",null,{"$f":"IF(H107=\"\",\"0\",IF(H107=\"Pass\",1,IF(H107=\"Fail\",0,IF(H107=\"TBD\",0,IF(H107=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D107)=48,H107=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-ED","TC-Types-52","CDA-RS 53 (i) [NEHTA-1199:2012]\nAuthoring Systems SHALL ensure that all attachments referenced in <renderMultimedia> narrative block elements or used for a branding logo, are not inlined in their associated observationMedia entries.\n","M",1,"For every <observationMedia> that is referenced from a <renderMultiMedia> or, every <observationMedia> that contains ID=”LOGO” and is not referenced by a renderMultiMedia:\nFail the test if the <value> element contains inline content.\nElse, Pass the test.\n\nNOTE TO TESTER:\nExamples of a <value> element with inline information are <value xsi:type=\"ED\">inlinecontent</value> and <value xsi:type=\"ED\" mediaType=\"image/png\" integrityCheck=\"Hu0w8156O0MHPmCve6vRJ0XHtMo=\" >inlinecontent<reference value=\"small.png\" /></value>.\n","Clinical document attachment references are not inlined in their associated observationMedia entries.","TBD",null,{"$f":"IF(H108=\"\",\"0\",IF(H108=\"Pass\",1,IF(H108=\"Fail\",0,IF(H108=\"TBD\",0,IF(H108=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D108)=48,H108=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-ED","TC-Types-53","024631 [DH-2481:2017]\nOnly text SHALL be attached inline\n\nAttachments SHALL NOT be inlined in the CDA document's XML content (e.g. do not include base64 encoded binary data in the CDA document).Attachments SHALL NOT be inlined in the CDA document's XML content (e.g. do not include base64 encoded binary data in the CDA document).\n\nNote: This requirement is applicable for the My Health Record system context only.\n\nNote: There are internal and external forms of attachments in CDA. In the internal form, the attachment is base64 encoded and included in the CDA XML document. In the external form, the attachment is referenced using elements of the ED datatype elements. The CDA specification does not stipulate the target of the reference; it could be remote (e.g. on a web server, in a networked location, or in local storage) or packaged with the CDA XML document.\n","C",1,"CONDITION:  The clinical document is to be submitted to the My Health Record system.\n\nFor every attachment: \nFail the test if either the <value> element contains inline content or if the value of the <reference> commences with the character \"#\".\nElse, Pass the test.                                                                                                                                                                                                                                   \n\nNOTE TO TESTER:\nThe character \"#\" is used to reference data in the clinical document. Clinical document elements used for attachments are observationMedia, regionOfInterest, externalAct, externalDocument, externalObservation, and externalProcedure so the test applies to these elements and not to other elements where internal references are allowed, such as originalText. ","Clinical document attachments are not inlined in the clinical document's XML content","TBD",null,{"$f":"IF(H109=\"\",\"0\",IF(H109=\"Pass\",1,IF(H109=\"Fail\",0,IF(H109=\"TBD\",0,IF(H109=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D109)=48,H109=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-ED","TC-Types-54","CDA-RS 53 (j) [NEHTA-1199:2012]\nThe referenced attachments SHALL be included in the CDA Package in accordance with the CDA Package specification [CDAP2011].\n\nNote: This requirement may be overridden for specific types of documents. If there is an override then it will be stated in the conformance profile for a specific type of document.\n",null,null,"No additional test case is defined for these requirements as there are sufficient test cases in the Conformance Test Specification for CDA Packaging [NEHTA-2065:2015]."]
["TS-ED","TC-Types-114","7.4.2.3.5 mediaType [ISO21090]\n\nIdentifies the type of the encapsulated data and can be used to determine a method to interpret or render the content.\n\nThe IANA defined domain of media types is established by the IETF RFCs 2045 and 2046. mediaType has a default value of text/plain and cannot be null. If the media type is different to text/plain, the mediaType attribute shall be populated.\n\nIf the content is compressed using a specified compression algorithm, the mediaType shall refer the mediaType of the uncompressed data, whether the data are accessed by reference or not.\n\nNote: In the My Health Record context there is only a need for the test case to consider the text/plain mediaType, for the following reasons:\n\n1) A data element of the 'ED' data type will either reference data outside of the clinical document, reference data in another data element of the clinical document, or the data will be included in the 'ED' data element.\n\n2) When an 'ED' data element references data outside the clinical document test cases in the Conformance Test Specification for CDA Packaging are used to verify that the mediaType attribute has the correct value.\n\n3) When an 'ED' data element references data in another element of the clinical document or includes the data within the 'ED' element the data is either text or binary, such as multimedia, included using base64 encoding (section 2.4 [HL72004b]). In the My Health Record context binary data cannot be included in a clinical document (requirement 024631 [DH-2481:2017]) so the only option is for the data to be in text format.","C",1,"Condition: For any data element of ISO data type ED or the derived type Encapsulated Data where the mediaType attribute is text/plain and the data element does not reference data outside of the clinical document.\n\n Pass the test if data is included in the data element and it passes TC-Types-56.\n Else Pass the test if the data element references data in another element of the clinical document and that data passes TC-Types-56.\n Else Fail the test.\n\nNOTE TO TESTER: \ntext/plain is the default mediaType so if the mediaType attribute is not explicitly included then its value is text/plain.\n\nThe following options are not included in this test case as they are covered by other test cases in this conformance test specification and the Conformance Test Specification for CDA Packaging:\n\n1) The mediaType is text/plain and the data is external to the clinical document\n2) The mediaType has some other value and the data is either internal or external to the clinical document.\n","Clinical document attachment references are inlined in their associated data element.","TBD",null,{"$f":"IF(H111=\"\",\"0\",IF(H111=\"Pass\",1,IF(H111=\"Fail\",0,IF(H111=\"TBD\",0,IF(H111=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D111)=48,H111=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-ED","TC-Types-119","027766 [DH-2481:2017] \nCompressed attachments\n\nA clinical document SHALL NOT include any reference to any format of compressed files.\n\nAdditional Notes: Examples of compression file format are deflate, gzip, zlib, compress, bzip and z7.\n","C",1,"Condition: For any data element of ISO data type ED or the derived type Encapsulated Data\n\n Fail the test if the clinical document has reference to a compressed file.\n Else Pass the test.\n\n","Compressed file attachments are not referenced in the clinical document.","TBD",null,{"$f":"IF(H112=\"\",\"0\",IF(H112=\"Pass\",1,IF(H112=\"Fail\",0,IF(H112=\"TBD\",0,IF(H112=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D112)=48,H112=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-ED","TC-Types-120","027730 [DH-2481:2017]\n PDF attachment in CDA package\n\nA PDF file that is an attachment to a clinical document SHOULD NOT have any of these features:\n- Encryption;\n- Password protection;\n- Printing or copying restriction;\n- Embedded fonts (as not all PDF viewers support them); or\n- Restrictions on changes (i.e. changes are not allowed regardless of whether this PDF flag is set).\n\n",null,null,"No additional test case is needed as there is no specific requirement that must be met.\n"]
["TS-ED","END:  TS-ED (Encapsulated data)"]
["TS-ST","START:  TS-ST (Character string)"]
["TS-ST","NOTE : According to the HL7 data types specification the SC data type is a specialisation of the ST data type, therefore TS-ST test cases may also be applied to SC data elements."]
["TS-ST","TC-Types-55","7.4.6.1 Invariants [ISO21090]\nA ST shall have at least one character or else have a nullFlavor.\n\nNote: Requirements for attributes defined for the ST data type but not allowed by the Australian CDA Schema Extension are not listed here.\n","M",1,"For any data element of ISO data type ST or the derived type Text:\n\nFail the test if the data element has no characters and does not have a nullFlavor.\nElse, Pass the test\n\nNOTE TO TESTER:\nNo test step has been defined for the translations attribute as it is currently not supported by the Australian CDA Schema Extension [NEHTA-1599:2014].\n","Each data element of ISO data type ST (or the derived type Text), have at least one character or a nullFlavor.","TBD",null,{"$f":"IF(H117=\"\",\"0\",IF(H117=\"Pass\",1,IF(H117=\"Fail\",0,IF(H117=\"TBD\",0,IF(H117=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D117)=48,H117=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-ST","TC-Types-56","6.7.5 ST (Character string) [ISO21090]\nThe character string datatype stands for text data.\n \n6.7.5 Strings and character encoding [ISO21090]\nThe String datatype contains a sequence of logical characters, which is different from carrying a sequence of bytes that encodes a sequence of logical characters. By default, the String type contains Unicode characters.\n\nNote: The character string datatype stands for text data, primarily intended for machine processing (e.g. sorting, querying, indexing, etc.) or direct display.\n\nNote: Section 7.4.6 of ISO21090 states that for the ST data type the mediaType is \"text/plain\". Section 4.1 of the specification [RFC2046] for \"text/plain\" media states \"Plain text does not provide for or allow formatting commands, font attribute specifications, processing instructions, interpretation directives, or content markup.  Plain text is seen simply as a linear sequence of characters, possibly interrupted by line breaks or page breaks.\" For example “line 1<br/>line 2” will  be displayed as “line 1<br/>line 2” as \"<br/>\" is not treated as a formatting command so does not produce a line break. Note that line breaks and page breaks may be provided by the corresponding Unicode characters. For example, the Unicode line feed character can be included using “&#x0A;” [W3C2013], so a line break is included when displaying “line 1&#x0A;line 2”.\n","M",1,"For any data element of ISO data type ST or the derived type Text:\n\nFail the test where the text contains any markup content.\nElse, Fail the test where formatting in a character string does not use  a character escape to include the required unicode characters.\nElse, Pass the test.\n\nNOTE TO TESTER: \nMarkup content includes the content defined in the CDA Rendering specification [NEHTA-1199:2012], RTF markup and other document specifications. Unicode characters used for formatting are allowed.\n","Each data element of ISO data type ST (or the derived type Text), does not contain markup content.","TBD",null,{"$f":"IF(H118=\"\",\"0\",IF(H118=\"Pass\",1,IF(H118=\"Fail\",0,IF(H118=\"TBD\",0,IF(H118=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D118)=48,H118=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-ST","TC-Types-122","7.4.9.6 Invariants [ISO21090]\n\nIf there is a code, there shall also be some content on the SC (and therefore the SC shall not have a nullFlavor).\nThe originalText value of the CD shall be null (the originalText is the SC.value).","M",1,"For any data element of ISO data type SC:\n\nFail if the data element contains a code and either a nullFlavor attribute or no text;\nElse Pass the test.\n\nNOTE TO TESTER:\nThere is no need to test for the present of an originalText element as it is prohibited by the CDA schema.","Each data element of ISO type SC contains text and/or a nullFlavor. If it contains text it may also contain a code, however, if it contains a code no nullFlavor is provided.","TBD",null,{"$f":"IF(H119=\"\",\"0\",IF(H119=\"Pass\",1,IF(H119=\"Fail\",0,IF(H119=\"TBD\",0,IF(H119=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D119)=48,H119=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-ST","END:  TS-ST (Character string)"]
["TS-CD","START:  TS-CD (Concept descriptor)"]
["TS-CD","Note: Many conformance requirements stated in section 8.1 of the CDA implementation guides are not listed here as they are also stated in the Health informatics - Harmonized data types for information interchange [ISO21090]."]
["TS-CD","Where a conformance requirement in section 8.1 of the CDA implementation guides constrains a requirement in the Health informatics - Harmonized data types for information interchange the constraint is listed here. "]
["TS-CD",null,null,null,null,"NOTE TO TESTER: According to the HL7 data types specification, the CD data type has been constrained for the CE, CV and CO data types, i.e. they are specialisations of CD by the removal of some attributes (e.g. CV does not have a 'translation'). TS-CD test cases may be applied to CE, CV and CO data elements by applying the test cases for the attributes that are present in a data element.\n"]
["TS-CD","TC-Types-57","7.5.2 Concept Descriptor [ISO21090]\nA CD represents any kind of concept usually by giving a code defined in a code system. A CD can contain the original text or phrase that served as the basis of the coding and one or more translations into different coding systems. A CD can also contain qualifiers to describe, e.g., the concept of a \"left foot\" as a postcoordinated term built from the primary code \"FOOT\" and the qualifier \"LEFT\". In cases of an exceptional value, the CD need not contain a code but only the original text describing that concept.\n","M",1,"For any data element of the ISO data type CD or the derived type CodeableText:\n\nFail the test if the value of the data element's code (if present) or originalText (if present) is invalid for the data element.\nElse, Pass the test.\n\nNOTE TO TESTER:\nFor example, using an ANZSCO code to describe the role of a healthcare facility is invalid as ANZSCO codes describe the roles or people, not organisations. Using a medication code for a medical history data element is invalid as the medication code should be recorded in a medication data element. Using an ANZSCO code to describe a clinical specialty is not valid as there are clinical specialty code systems (2.16.840.1.113883.3.879.329673 and 2.16.840.1.113883.3.879.532097) available [AIHWCS].\n\nThere is no need to apply this test to data elements of the type CodedText as the value of the data element can only be selected from the specified constrained value domain so it is not possible for the value to be invalid for the data element.  A CodedText data element would fail another test case if its value was not one of the specified values.\n","Each data element of ISO data type CD (or the derived type CodeableText), has a @code and/or originalText value which is appropriate for the data element.","TBD",null,{"$f":"IF(H125=\"\",\"0\",IF(H125=\"Pass\",1,IF(H125=\"Fail\",0,IF(H125=\"TBD\",0,IF(H125=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D125)=48,H125=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-CD","TC-Types-58","7.5.2.6 Invariants [ISO21090]\n- If the value is not null then code or originalText shall have a value;\n- If code has a value then codeSystem shall have a value;\n- codeSystemName can only have a value if codeSystem has a value;\n- codeSystemVersion can only have a value if codeSystem has a value;\n- displayName can only have a value if code has a value;\n- translations cannot have original text;\n- translations cannot have translations.\n\nNote: \na) The first point is further clarified by the following statement in section 7.5.2.1 [ISO21090]: \"A CD with no nullFlavor attribute shall have a code attribute or nonNull originalText attribute.\"\n\nb)Requirements for attributes defined for the CD data type but not allowed by the Australian CDA Schema Extension are not listed with the Invariants here. For \"valueSet\" details see source document [ISO21090].\n\nc) Although every non-NULL CD value has a defined code system, in some circumstances, the ITS representation for the CD value needs not explicitly mention the code system. For example, when the context mandates one and only one code system to be used specifying the code system explicitly would be redundant. However, in that case the codeSystem takes on that context-specific default value and is not NULL. (Section 2.6.2, [ISO21090])\n","M",1,"For any data element of the ISO data type CD or the derived types CodedText or CodeableText:\n\nFail the test if there is no nullFlavor, or code, or originalText with a non-null value.\nElse, Fail the test if there is a code and there is no codeSystem and the context of the data element does not provide a default codeSystem.\nElse, Fail the test if there is a codeSystemName and no codeSystem.\nElse, Fail the test if there is a codeSystemVersion and no codeSystem.\nElse, Fail the test if there is a displayName and no code.\nElse, Fail the test if there is a translation with an originalText.\nElse, Fail the test if there is a translation within a translation.\nElse, Pass the test.\n","Each data element of ISO data type CD, or the derived type CodedText or CodeableText, minimally contain @code, originalText or nullFlavor. All Requirement constraints are followed.","TBD",null,{"$f":"IF(H126=\"\",\"0\",IF(H126=\"Pass\",1,IF(H126=\"Fail\",0,IF(H126=\"TBD\",0,IF(H126=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D126)=48,H126=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-CD","TC-Types-59","7.5.2.4.1 code [ISO21090]\nIf a code is provided, it shall be an exact match to a plain code symbol or expression defined by the code system.\n\nNote: A specification for a code system may state the number and allowed characters in a code. A CD may contain a simple code that is, a reference to a concept defined directly by the referenced code system, or it may contain an expression in some syntax defined by the referenced code system that can be meaningfully evaluated, e.g. the concept of a \"left foot\" as a postcoordinated term built from the primary code \"FOOT\" and the qualifier \"LEFT\". For SNOMED CT and derivatives including SNOMED CT-AU and AMT version 3, the code may either be a concept identifier or an expression using the SNOMED Composition Grammar.\n","M",1,"For any data element of ISO data type CD or the derived types CodedText or CodeableText:\n\nFail the test if a code is present and its value does not have the required number and type of characters allowed by the code system,\nElse, Fail the test if a code is present but its value is neither an exact match to a code in the code system nor is an expression allowed by the code system,\nElse, Pass the test.\n\nNOTE TO TESTER:\nIf the tester does not have a copy of the code system then it may only be possible to verify that the code has the required number and type of characters. If the codeSystemVersion attribute is present then the value of the code is to be matched against the codes in the stated version of the code system, otherwise it is acceptable for the code to be present in any version of the code system (e.g. deprecated codes are allowed for historical records such as for medical history). The test applies to a primary code and any translations. An example of a expression using SNOMED CT-AU codes is code=\"128045006:{363698007=56459004}\".\n","Each data element of ISO data type CD, or the derived type CodedText or CodeableText, has a @code value which is the correct number and type of characters allowed by the code system, and either, an exact match to a code in a code system, or is an expression allowed by the codeSystem.\n\n","TBD",null,{"$f":"IF(H127=\"\",\"0\",IF(H127=\"Pass\",1,IF(H127=\"Fail\",0,IF(H127=\"TBD\",0,IF(H127=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D127)=48,H127=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-CD","TC-Types-60","7.5.2.1 nullFlavor [ISO21090]\nA CD that has a code, codeSystem or originalText attribute but does not meet external constraints of the applicable value set shall have a nullFlavor attribute with a value of \"OTH\".\n\nIf the constraint is extensible (CWE) then a CD that does not have a nullFlavor shall contain either a code that exists in the domain with which the attribute is associated, a code from a locally defined code system, or just some originalText that describes the concept.\n\nNote: The requirement is further clarified by the definition of nullFlavor \"OTH\" in 7.1.4 Null and NullFlavor [ISO21090]:\nThe actual value is not a member of the set of permitted data values in the constrained value domain of a variable (e.g. concept not provided by required code system).\n\nNote: With the derived CodeableText and CodedText data types defined by NEHTA only CodeableText is allowed to have a nullFlavor \"OTH\" [NEHTA-1136:2010].\n","M",1,"For any data element of ISO data type CD or the derived type CodeableText (CodedText does not allow nullFlavor \"OTH\"):\n\nFail the test if the data element contains a code attribute, no nullFlavor \"OTH\" and the value of the code is not a member of the specified value domain,\n Else Fail the test if the data element contains nullFlavor \"OTH\" and the value domain contains a matching code for the concept,\n Else Pass the test.\n\nNOTE TO TESTER: \n- The previous test case ensures the code is a member of the code system but for many data elements the code must also be a member of a value domain which is a subset of the code system. A CD data element may contain both a code and a nullFlavor \"OTH\", such as the following example of an adverse reaction substance/agent data element which indicates that there is an applicable code from the code system but there is no applicable code from the value domain for adverse reaction substance/agent, so the outcome should be a Pass.\n\n <code code=\"129696000\" codeSystem=\"2.16.840.1.113883.6.96\" codeSystemName=\"SNOMED CT-AU\"  nullFlavor=\"OTH\">\n        <originalText>ALLERGY - Latex</originalText>\n    </code>\n\n- The following data element code snippet has a conformance error, the error is that the data element contains nullFlavor \"OTH\" and the value domain contains a matching code for the concept, so the outcome should be a Fail.\n\n<targetSiteCode nullFlavor=\"OTH\" codeSystem=\"2.16.840.1.113883.6.96\">\n<originalText>Chest Nut </originalText>\n</targetSiteCode>\n\nRegarding the test to determine if there is a code for the concept: as the value of the originalText is the display text of the concept to the user that value may be used to determine if there is a code that matches the concept.\n","Each data element of ISO data type CD or the derived type CodeableText, has a @code value which is a member of the specified value domain, or is not a member of the specified domain and has a @nullFlavor value equal to \"OTH\".\n","TBD",null,{"$f":"IF(H128=\"\",\"0\",IF(H128=\"Pass\",1,IF(H128=\"Fail\",0,IF(H128=\"TBD\",0,IF(H128=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D128)=48,H128=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-CD","TC-Types-61","7.5.2.4.2 codeSystem [ISO21090]\nA CD with a NullFlavor OTH indicates that a concept could not be coded in the coding system or value set specified. Thus, for these coding exceptions, the code system or value set that did not contain the appropriate concept shall be provided in codeSystem or valueSet.\n","M",1,"For any data element of ISO data type CD or the derived type CodeableText (CodedText does not allow nullFlavor \"OTH\"):\n\nFail the test if there is a nullFlavor \"OTH\" and no codeSystem or the valueSet is not specified.\nElse, Pass the test.\n","Each data element of ISO data type CD (or the derived type Coded Text or CodeableText), has a @codeSystem value which is the code system that does not contain the concept, and a @nullFlavor value of 'OTH'.","TBD",null,{"$f":"IF(H129=\"\",\"0\",IF(H129=\"Pass\",1,IF(H129=\"Fail\",0,IF(H129=\"TBD\",0,IF(H129=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D129)=48,H129=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-CD","TC-Types-62","7.5.2.4.2 codeSystem [ISO21090]\nCode systems shall be referred to by a UID, which allows unambiguous reference to standard code systems and other local codesystems. Where either ISO or HL7 have assigned UID to code Systems, then these UIDs shall be used. Otherwise, implementations shall use an appropriate ISO Object Identifier (OID) or UUID to construct a globally unique local coding system identifier.\n\nNote: The allowed values for codeSystem are further constrained by the following requirements:\n8.1 code [NEHTACDAIG]\nThe second requirement applies when a data element contains an alternate vocabulary (i.e. a vocabulary not listed in the clinical document specifications):\nWhere used, the codeSystem attribute SHALL contain the OID for the relevant vocabulary.\nThe code element SHALL be used to carry the relevant information from the alternate vocabulary and the alternate vocabulary SHALL be registered with HL7™ and allocated an appropriate OID.\n1.8 Conformance [NEHTACDAIG]\nIn the absence of national standard code sets, the code sets used SHALL be registered code sets, i.e. registered through the HL7™ code set registration procedure with an appropriate object identifier (OID), and SHALL be publicly available.\n","M",1,"For any data element of ISO data type CD or the derived types CodedText or CodeableText:\n\nFail the test if the codeSystem attribute is present and does not pass the OID and UUID format tests in the TS-UID test set,\n Else if the codeSystem is present and has a value not listed in the clinical document specifications then Fail the test if the codeSystem attribute does not pass the TS-UID test case for an OID or UUID registered via the HL7™ code set registration procedure.\n Else Fail the test if the codeSystem is not an identifier of an ISO, HL7 or local coding system.\n Else, Pass the test.\n\nNOTE TO TESTER: \nAbove reference to TS-UID indicates individual test case for UUID & OID Format and Registration data types in this worksheet (See TC-Types-105 to TS-Types-109).\n","Each data element of ISO data type CD (or the derived type CodedText or CodeableText), has a @codeSystem value which is an OID or UUID that is in the correct format, and registered with HL7.","TBD",null,0,{"$f":"IF(AND(BGCol(D130)=48,H130=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-CD","TC-Types-63","7.5.2.4.4 codeSystemVersion [ISO21090]\nDefinition: If applicable, a version descriptor defined specifically for the given code system.\n\nNote: Different versions of one code system shall be compatible. By definition, a code symbol shall have the same meaning throughout all versions of a code system. Between versions, codes may be retired but not withdrawn or re-used. Where the definition of the meaning of a code symbol changes, it must still be compatible (equal) between different code system versions. Whenever a code system changes in an incompatible way, it constitutes a new code system, not simply a different version, regardless of how the vocabulary publisher calls it.\n","C",1,"CONDITION: Data element(s) include codeSystemVersion.\n\nFor any data element of ISO data type CD or the derived types CodedText or CodeableText:\n\nFail the test if the codeSystemVersion is present and does not have a value that is valid for the code system.\nElse, Pass the test.\n\nNOTE TO TESTER:\nThe code system documentation should describe the valid format or values for codeSystemVersion.\nThe publisher of a code system defines the version if there is one and it is invalid for a user of a code system to create a version identifier that was not defined by the publisher. METeOR code systems such as clinical specialty do not have a code system version and revisions are published as a new code system. For example, clinical specialty code system 2.16.840.1.113883.3.879.329673 was revised to create the new code system 2.16.840.1.113883.3.879.532097.\n","Each data element of ISO data type CD (or the derived type CodedText or CodeableText), has a @codeSystemVersion value which is valid for the code system.","TBD",null,0,{"$f":"IF(AND(BGCol(D131)=48,H131=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-CD","TC-Types-64","7.5.2.4.3 codeSystemName [ISO21090]\nDefinition: The common name of the coding system.\n\nSection 10 CodeSystem OIDs [NEHTACDAIG]\nThe value of codeSystemName SHOULD be the name associated with the OID in the HL7 OID Registry.\n\nNote: The allowed values for codeSystemName are also constrained by the following requirement listed in section 8.1 of every CDA implementation guide: \n\nThe codeSystemName MAY be present and, where used, SHALL contain a human readable name for the coding system.\n","C",1,"CONDITION: Data element(s) include codeSystemName.\n\nFor any data element of ISO data type CD or the derived types CodedText or CodeableText:\n\nFail the test if the codeSystemName attribute is present and does not have a human readable value.\nElse if the codeSystem OID commences with \"1.2.36.1.2001.1001.101\" (used by the Agency to define data components) then Fail the test if the codeSystemName is not the name specified by the Agency.\nElse if the codeSystem OID exists in the HL7 OID Registry then Fail the test if the codeSystemName is neither the value specified in the Full Name for Object (Title) field nor is semantically equivalent.\nElse, Pass the test.\n\nNOTE TO TESTER:\nFor example, CDA implementation guides state the codeSystemName is \"NCTIS Entitlement Type Values\" when codeSystem=\"1.2.36.1.2001.1001.101.104.16047\".\n","Each data element of ISO data type CD (or the derived type CodedText or CodeableText), has a @codeSystemName value which is a name associated with the OID in the HL7 OID Registry or is a name specified by the Agency.","TBD",null,0,{"$f":"IF(AND(BGCol(D132)=48,H132=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-CD","TC-Types-65","7.5.2.4.7 displayName [ISO21090]\nIf populated, the displayName shall be a valid human readable representation of the concept as defined by the code system at the time of data entry.\n\nThe displayName shall conform to any rules defined by the codingSystem; if the codeSystem does not define a human representation for the code or expression, then none can be provided.\n\ndisplayName shall not alter the meaning of the code value.\n","C",1,"CONDITION: Data element(s) include displayName.\n\nIf the documentation of the code system provides a human readable value corresponding to the a code but does not mandate the use of the human readable value then fail the test if the displayName attribute is present and does not have value equivalent in meaning to that of the human readable value stated in the code system documentation,\nElse if the rules of the code system specify a name to use as the displayName then fail the test if the displayName attribute is present and does not have the value specified for the version of the code system version used at the time of data entry,\nElse, Pass the test.\n\nNOTE TO TESTER: \nIf the codeSystemVersion attribute is present then the stated version of the code system is to be used for the assessment, otherwise it is acceptable for the code to be present in any version of the code system. If the code system does not have any rules for the displayName then assume that the name is case insensitive and that punctuation may be ignored.\n","Each data element of ISO data type CD (or the derived type CodedText or CodeableText), has a @displayName value which is valid for the code in the code system at the time of data entry and is human readable and does not alter the meaning of the code value.","TBD",null,0,{"$f":"IF(AND(BGCol(D133)=48,H133=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-CD","TC-Types-66","7.5.2.4.8 originalText [ISO21090]\nDefinition: The text as seen and/or selected by the user who entered the data which represents the intended meaning of the user.\n\nIn a situation where the code is assigned sometime after the text was entered, originalText is the text or phrase used as the basis for assigning the code. \n\nTranslations directly encode the concept described in originalText. \n\nNote: The use of originalText is further clarified by the following requirement:\n8.1 code [NEHTACDAIG]\nWhere used, the originalText element SHALL be used to carry the full text associated with this code as selected by, typed by or displayed to the author of this statement. \nIf a vocabulary is specified in this implementation guide and no suitable code can be found, the originalText element SHALL be used to carry the full text as selected by, typed by or displayed to the author of this statement. \nIf a vocabulary is specified in this implementation guide and it is not possible to use this vocabulary, but an alternate vocabulary is in use, the originalText element SHALL be used to carry the full text as selected by, typed by or displayed to the author of this statement. \nThe original text SHALL be an excerpt of the information in the original sources and SHALL be represented in plain text form.\n","C",1,"CONDITION: Data element(s) contain originalText.\n\nFor any data element of ISO data type CD or the derived types CodedText or CodeableText:\n\nFail the test if the concept described by any primary or translation code is inconsistent with the concept described by the originalText.\nElse, Pass the test.\n\nNOTE TO TESTER: \nFor example, a data element which contains the originalText describing a medical condition and a code for a medication would fail the test. Other aspects of the requirements for originalText are assessed in the FS-Auth feature set.\n","Each data element of ISO data type CD (or the derived type CodedText or CodeableText), has an originalText value which is consistent with the concept being described in either the primary @code or translation @code.","TBD",null,0,{"$f":"IF(AND(BGCol(D134)=48,H134=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-CD",null,null,null,2,"Fail the test if a mediaType attribute is present in the originalText and does not have the value 'text/plain'.\nElse Pass the test.\n\nNOTE TO TESTER: \n'text/plain' is the default value when the mediaType is not explicitly stated.\n","Each data element of ISO data type CD (or the derived type CodedText or CodeableText), has an originalText value which is consistent with the concept being described in either the primary @code or translation @code.","TBD",null,{"$f":"IF(H135=\"\",\"0\",IF(H135=\"Pass\",1,IF(H135=\"Fail\",0,IF(H135=\"TBD\",0,IF(H135=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D135)=48,H135=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-CD","TC-Types-67","7.5.2.4.9 translation [ISO21090]\nDefinition: A set of other CDs that each represent a translation of this CD into equivalent codes within the same code system or into corresponding concepts from other code systems.\n\nTranslations shall not contain translations.\n\n7.5.2.4.8 originalText [ISO21090]\nTranslations shall not have an originalText of their own.\n\nNote: The use of translations is further clarified by the following requirements in section 8.1 of every CDA implementation guide which applies if an alternate vocabulary is in use and a translation into the specified code system is available:\n\nThe translation element SHALL be used to indicate the translation code from the specified vocabulary.","C",1,"CONDITION: Data element(s) include a translation.\n\nFor any data element of ISO data type CD or the derived type CodeableText (CodedText does not allow translations):\n\nElse, Fail the test if any translations contain both a code and a nullFlavor \"OTH\".\nElse, Pass the test.\n\nNOTE TO TESTER: \na) Other aspects of the requirement are assessed in TC-Types-58.\nb)The rationale for failing the testing if a translation contains both a code and a nullFlavor \"OTH\" is that in a translation element the code is present if it is the code corresponding to the concept and a nullFlavor \"OTH\" indicates there is no code for the concept (section 7.5.2.4.2 [ISO21090]) so having both a code and a nullFlavor \"OTH\" in a translation is a contradiction.\n","Each data element of ISO data type CD (or the derived type CodedText or CodeableText) with a translation does not have: embedded translations, and/or an originalText and/or, a @code value in conjunction with a @nullFlavor equal to \"OTH\". ","TBD",null,0,{"$f":"IF(AND(BGCol(D136)=48,H136=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-CD",null,null,null,2,"CONDITION: Data element(s) include a translation.\n\nPass the test if the translation code is equivalent to the concept identified in the primary code.\nElse, Fail the test.\n","A translated code element is  identified by the primary code when translated between systems. ","TBD",null,{"$f":"IF(H137=\"\",\"0\",IF(H137=\"Pass\",1,IF(H137=\"Fail\",0,IF(H137=\"TBD\",0,IF(H137=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D137)=48,H137=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-CD","TC-Types-68","2.6.8 Qualifier [HL72004]\nDefinition: Specifies additional codes that increase the specificity of the  primary code.\n\nThe primary code and all the qualifiers together make up one concept. A CD with qualifiers is also called a code phrase or postcoordinated expression.\n\nQualifiers constrain the meaning of the primary code, but cannot negate it or change it's meaning to that of another value in the primary coding system.\n\nIt is important to note that the allowable qualifiers are specified by the code system. \n\nNote:  In the case where the data element being qualified contains a SNOMED CT-AU code then the data element is referred to as a concept and the effect of the qualification is a refinement of the concept. A refinement is valid only when it results in a subtype of the concept (see section 8.1.7.4 of the SNOMED CT Technical Implementation Guide [IHTSDO2014]).  Therefore if the qualifier is present then it must have a SNOMED CT-AU code, not have a nullFlavor and the outcome of applying the qualifier to the original concept must result in a code that is a subtype of the original concept.\n","C",1,"CONDITION: Data element(s) include a qualifier.\n\nFor any data element of ISO data type CD or the derived type CodeableText:\n\nFail the test if the data element contains a qualifier and the data element's code system does not allow the use of qualifiers.\nElse, Fail the test if the qualifier negates or changes the meaning of the primary code rather than constraining the meaning of the primary code.\nElse, Pass the test.\n\nNOTE TO TESTER: \nIf the date element's code system is SNOMED CT or a derivative code system such as AMT version 3 or SNOMED CT-AU (codeSystem 2.16.840.1.113883.6.96) then the rules for applying a qualifier [IHTSDO2014] mean that the following apply:\na. Fail the test if the qualifier/value attribute contains a nullFlavor.\nb. Fail the test if the qualifier/value attribute does not contain a code.","Each data element of ISO data type CD (or the derived type CodeableText) with a qualifier is allowed to have a qualifier (according to the specific data element's code system), and the qualifier serves to constrain (but not negate or change) the meaning of the primary code. ","TBD",null,0,{"$f":"IF(AND(BGCol(D138)=48,H138=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-CD",null,"Qualifiers can only be used according to well-defined rules of post-coordination. A value of type CD may only have qualifiers if it's code system defines the use of such qualifiers or if there is a third code system that specifies how other code systems may be combined. \n\nAgain, note that the allowable qualifiers are specified by the code system. \n",null,2,"CONDITION: Data element(s) include a qualifier.\n\nFor any data element of ISO data type CD or the derived type CodeableText:\n\nFail the test if the qualifier is inconsistent with the rules of the data element's code system.\nElse, Pass the test.\n\nNOTE TO TESTER: \nIf the date element's code system is SNOMED CT or a derivative code system such as AMT version 3 or SNOMED CT-AU (codeSystem 2.16.840.1.113883.6.96) then the rules for applying a qualifier [IHTSDO2014] mean that the following apply:\nFail the test if the outcome of applying the qualifier to the code in the data element does not result in a subtype of the original code.","Each data element of ISO data type CD (or the derived type CodeableText) with a qualifier is consistent with the rules of the code system. ","TBD",null,{"$f":"IF(H139=\"\",\"0\",IF(H139=\"Pass\",1,IF(H139=\"Fail\",0,IF(H139=\"TBD\",0,IF(H139=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D139)=48,H139=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-CD",null,"Note: A qualifier has the Concept Role data type (section 2.6.8 [HL72004]). A Concept type has the child elements name, value and inverted, where name and inverted are optional and if name is present then both the name and value codes must be defined by the coding system of the CD containing the concept qualifier (section 2.7 [HL72004]). The value has the CD data type so there may be a nested series of qualifiers. ",null,3,"CONDITION: Data element(s) include a qualifier.\n\nFor any data element of ISO data type CD or the derived type CodeableText:\n\nFail the test if the name or value of a qualifier, including any nested qualifier, do not contain a code from the same code system used by the CD data element that the qualifier applies to.\n Else, Pass the test.\n\nNOTE TO TESTER: \nFor example, when a CD data element that the qualifier applies to has a code from the SNOMED CT-AU code system the qualifier value and name (if present) must also have a code and the code must be from the SNOMED CT-AU code system. \n","Each data element of ISO data type CD (or the derived type CodeableText) with a qualifier including any nested qualifier, contain a code from the same code system used by the CD data element that the qualifier applies to.","TBD",null,{"$f":"IF(H140=\"\",\"0\",IF(H140=\"Pass\",1,IF(H140=\"Fail\",0,IF(H140=\"TBD\",0,IF(H140=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D140)=48,H140=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-CD","END:  TS-CD (Concept descriptor)"]
["TS-TEL","START:  TS-TEL (Telecommunications address)"]
["TS-TEL","TC-Types-69","7.6.2.5 Invariants [ISO21090]\nValue shall be provided.\n\nNote: the value attribute is needed even if a nullFlavor is included, as explained in section 7.6.2.3.1 of [ISO21090] which states \"If the TEL has a nullFlavor, it is not necessary for the value to contain a valid URL. For instance, if the flavor is UNK, the value may be just \"tel:\" to indicate that what is unknown is a telephone number\".\n\n<example xsi:type=\"TEL\" nullFlavor=\"UNK\" value=\"tel:\" use=\"H\"/>\n\n\n","M",1,"For any data element of ISO data type TEL :\nMark the test as N/A if there is no value attribute and no nullFlavor attribute.\nElse, Pass the test.\n\nNote: The 'value' attribute for the data element of ISO data type TEL is optional (though it is stated in the ISO 21090 requirements for TEL that value attribute is mandatory). The HL7 Reference Information Model states that the <telecom> element has the TEL data type however the HL7 Reference Information Model uses version 1 of the HL7 data types specification rather than ISO 21090, and in version 1 of the HL7 data types specification it is optional to include the value attribute.\n","Either the value attribute or the code attribute is present in the element that represents the TEL data type.","TBD",null,{"$f":"IF(H143=\"\",\"0\",IF(H143=\"Pass\",1,IF(H143=\"Fail\",0,IF(H143=\"TBD\",0,IF(H143=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D143)=48,H143=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-TEL","TC-Types-118","7.6.2.1 Description [ISO21090]\n\nThe value attribute is constrained to be a uniform resource locator specified according to IETF RFC 1738 and\nIETF RFC 3966 when used in this datatype.\n\nNote: The specification states that the reference to a locatable resource may be a URI specified according to RFC 3986 https://www.ietf.org/rfc/rfc3986.txt, as long as the resource identified is always be locatable.\n","M",1,"Pass the test if the value attribute is not present.\nElse Pass the test if the value attribute is a uniform resource locator or a uniform resource identifier that references a locatable resource.\nElse Fail the test.","The value attribute is a uniform resource locator or a uniform resource identifier that references a locatable resource","TBD",null,{"$f":"IF(H144=\"\",\"0\",IF(H144=\"Pass\",1,IF(H144=\"Fail\",0,IF(H144=\"TBD\",0,IF(H144=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D144)=48,H144=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-TEL","END:  TS-TEL (Telecommunications address)"]
["TS-II","START:  TS-II (Instance identifier)"]
["TS-II","Note: Many conformance requirements stated in section 8.2 of the CDA implementation guides are not listed here as they are also stated in the Health informatics - Harmonized data types for information interchange [ISO21090]. "]
["TS-II","Where a conformance requirement in section 8.2 id of the CDA implementation guides constrains a requirement in the Health informatics - Harmonized data types for information interchange the constraint is listed here. "]
["TS-II","TC-Types-70","7.6.7.5 Invariants [ISO21090]\nA root shall be present if the II (Instance Identifier) is not nullFlavored.\n","M",1,"Pass the test if either a root or a nullFlavor attribute are present.\nElse Fail the test.\n\nNOTE TO TESTER: \nThe requirement allows both a root and nullFlavor attribute to be present.\n","Root is present if the Instance Identifier is not nullFlavored.","TBD",null,{"$f":"IF(H149=\"\",\"0\",IF(H149=\"Pass\",1,IF(H149=\"Fail\",0,IF(H149=\"TBD\",0,IF(H149=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D149)=48,H149=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-72","8.2 id [NEHTACDAIG]\nThe root attribute is REQUIRED and is a unique identifier that guarantees the global uniqueness of the instance identifier.\n\nNote: The root attribute in an II (Instance Identifier) data type is optional [ISO21090] [HL72004], but section 8.2 of every CDA implementation guide makes it mandatory . It may be omitted only if explicitly allowed in the mapping table of the implementation guide or the conformance profile for the specific clinical document.\n","M",1,"For any data element of ISO data type II or the derived type UniqueIdentifier:\n\nFail the test if the data element contains an extension attribute and no root attribute and the clinical document specification does not relax the mandatory requirement for the root attribute to be present.\nElse, Pass the test.\n\nNOTE TO TESTER: \nA nullFlavor may be used instead of a root attribute. However, where an extension attribute is provided with the identifier, the identifier namespace must be known, meaning that if an extension attribute is provided then the identifier must also contain a root attribute. Therefore, if a nullFlavor is used for an identifier, then neither a root nor an extention may be provided. \n","Each data element of ISO data type II (or the derived type UniqueIdentifier), has a @root attribute.","TBD",null,{"$f":"IF(H150=\"\",\"0\",IF(H150=\"Pass\",1,IF(H150=\"Fail\",0,IF(H150=\"TBD\",0,IF(H150=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D150)=48,H150=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-71","7.6.7.3.1 root [ISO21090]\nThis field can be either a DCE (Distributed Computing Environment) UUID, an Object Identifier (OID) or a special identifier taken from lists that may be published by ISO or HL7.\n\nNote: The above requirement is constrained by the following requirement listed in section 8.2 of every CDA implementation guide:\n\nThe root attribute SHALL be a UUID or OID.\n\nNote: Some older versions may state, 'The root attribute may be a UUID or OID'.\n","M",1,"For any data element of ISO data type II or the derived type UniqueIdentifier:\n\nFail the test if the root attribute does not pass the test cases for a valid UUID or a valid OID, in TS-UID.\nElse, Pass the test.\n\nNOTE TO TESTER: \nAbove reference to TS-UID indicates individual test cases for OID data types in this worksheet (See TC-Types-105 to TS-Types-109).\n","Each data element of ISO data type II (or the derived type UniqueIdentifier), has a @root value which is a valid UUID or OID.","TBD",null,0,{"$f":"IF(AND(BGCol(D151)=48,H151=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-73","7.6.7.3.1 root [ISO21090]\nDefinition: A unique identifier that guarantees the global uniqueness of the instance identifier.\n\nIf root is populated, and there is no nullFlavor or extension, then the root is a globally unique identifier in its own right. In the presence of a non-null extension, the root is the unique identifier for the \"namespace\" of the identifier in the extension. This does not necessarily correlate with the organization that manages the issuing of the identifiers. A given organization may manage multiple identifier namespaces, and control over a given namespace may transfer from organization to organization over time while the root remains the same.\n\n","M",1,"For any data element of ISO data type II or the derived type UniqueIdentifier:\n\nFail the test if a non-null extension is present and the value of the root attribute is neither a UUID nor a registered OID that identifies a namespace (rather than an identifier of an object).\nElse, Fail the test if a non-null extension is present and the value of the root attribute does not define the namespace applicable for the extension.\nElse, Pass the test.\n\nNOTE TO TESTER:\n If the root attribute is a UUID then it is not possible to determine from the clinical document if the UUID identifies a namespace, so it is suggested that a Pass be recorded in this case. If the value of the root attribute is an OID then the Registered OID test in the TS-UID test set must be applied. If the outcome of the Registered OID test is that the OID identifies an object rather than a namespace then the data element fails this test.\n\nAn example of the use of an OID that does not identify the applicable namespace is the OID for an organisation other than the one that manages a local identifier.\n","Each data element of ISO data type II (or the derived type UniqueIdentifier), has a non-null @extension and the @root value is a UUID or a registered OID (that identifies a namespace), and the @root value defines the namespace applicable for the extension.","TBD",null,0,{"$f":"IF(AND(BGCol(D152)=48,H152=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-75","7.6.7.3.2 extension [ISO21090]\nDefinition: A character string as a unique identifier within the scope of the identifier root.\n\nThe root and extension scheme means that the concatenation of root and extension shall be a globally unique identifier for the item that this II (Instance Identifier) value identifies.\n\nNote: A character string as a unique identifier within the scope of the identifier root\" and the requirement \"The root and extension scheme means that the concatenation of root and extension shall be a globally unique identifier for the item that this II value identifies.\n","M",1,"For any data element of ISO data type II or the derived type UniqueIdentifier:\n\nFail the step if the concatenation of root and extension has been used to identify more than one object.\nElse, Pass the step. \n","Each data element of ISO data type II (or the derived type UniqueIdentifier), has no @nullFlavor, and, the concatenated @root and @extension are used to identify one object only. ","TBD",null,0,{"$f":"IF(AND(BGCol(D153)=48,H153=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II",null,null,"C",2,"CONDITION: The root OID defines a namespace and the requirements for that namespace are publically available.\n\nFor any data element of ISO data type II or the derived type UniqueIdentifier:\n\nFail the step if extension is present and its value does not match a value associated with the identifier root, \nElse, Pass the step. \n","Each data element of ISO data type II (or the derived type UniqueIdentifier), matches a value associated with the root identifier.","TBD",null,0,{"$f":"IF(AND(BGCol(D154)=48,H154=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-74","7.6.7.3.2 extension [ISO21090]\nDefinition: A character string as a unique identifier within the scope of the identifier root.\n\nThe root and extension scheme means that the concatenation of root and extension shall be a globally unique identifier for the item that this II value identifies.\n\nIf no extension attribute is provided in a non-null II (Instance Identifier), then the root is the complete unique identifier. If the root is not a complete unique identifier, and the extension is not known, then the II shall have a nullFlavor even if the root is populated.\n","M",1,"For any data element of ISO data type II or the derived type UniqueIdentifier:\n\nPass the test if no extension is present and the root is used as the complete unique identifier, or  \nElse, Pass the step if the extension is unknown and a nullFlavor is  present,\nElse, Pass the step if the extension is present and the concatenation of root and extension is a unique identifier,\n Else, Fail the test.\n\n\nNOTE TO TESTER: \nIf the root attribute passes the TS-UID test case for a valid UUID then it can be assumed to be globally unique. If the root OID identifies a namespace only then it is not a globally unique identifier.\n","Each data element of ISO data type II (or the derived type UniqueIdentifier), has a valid Global unique identifier or a nullFlavor, should @extension be null or not provided.","TBD",null,0,{"$f":"IF(AND(BGCol(D155)=48,H155=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-76","2.17 assigningAuthorityName [HL72004]\nDefinition: A human readable name or mnemonic for the assigning authority.\n\nNote: Requirements for assigningAuthorityName are stated in section 8.4 of every CDA implementation guide (N.B. wording of the following may vary slightly between Implementation Guides):\n\nAttribute @assigningAuthorityName SHOULD be used and, if it is used, SHALL be a human readable name for the namespace represented in the root that is populated with the issuer, or identifier type, or a concatenation of both as appropriate. This SHOULD NOT be used for machine readability purposes.\n\nFor some namespaces identified by the root OID the assigningAuthorityName is mandatory. The requirements for the derived type UniqueIdentifier state that assigningAuthorityName cannot be present unless the UniqueIdentifier is within an EntityIdentifier.\n","C",1,"CONDITION: assigningAuthorityName is Present and being used.\n\nFor any data element of ISO data type II or the derived type UniqueIdentifier:\n\nFail the test if assigningAuthorityName value is not a human readable name for the namespace represented in the root.\nElse, Pass the test. \n\nNOTE TO TESTER: \nThe name of the namespace is found by applying the Registered OID test in the TS-UID test set. \nWhere a namespace's requirements mandate the presence of assigningAuthorityName, conformance to this requirement is tested in the test cases for that namespace.\n","Each data element of ISO data type II (or the derived type UniqueIdentifier), has an @assigningAuthorityName value which is the human readable name for the namespace represented in the root. ","TBD",null,0,{"$f":"IF(AND(BGCol(D156)=48,H156=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","Note: Included below are test cases for namespaces often used in instance identifiers in clinical documents.\n"]
["TS-II","TC-Types-77","National healthcare identifier (OID \"1.2.36.1.2001.1003.0\") [HL72015]\nDescription: An identifier issued by the HI Service - IHI, HPI-I, or HPI-O.\n\nNote: Requirements for national healthcare identifiers are listed in Use of HIs in Health Software Systems - Conformance Requirements [NEHTA-1732:2014].","M",1,"For any instance identifier in the clinical document where the value of the root attribute is an OID commencing with “1.2.36.1.2001.1003.0”: \n\nFail the test if there is no arc following “1.2.36.1.2001.1003.0” or if the arc is not a national healthcare identifier consisting of a numeric string of sixteen digits commencing with “80036” followed by '0', '1' or '2' with a check digit whose value is calculated according to the Luhn algorithm.\nElse, Fail the test if there are any arcs after the national healthcare identifier.\nElse, Fail the test if there is an extension attribute.\nElse, Pass the test.\n\nNOTE TO TESTER: \nThe application of the Luhn check digit algorithm to national healthcare identifiers is described in Use of Healthcare Identifiers in Use of HIs in Health Software Systems - Conformance Requirements [NEHTA-1732:2014]. \n","Each instance identifier with a @root value starting with “1.2.36.1.2001.1003.0”, has only one arc, which is a valid 16 digit identifier assigned by the My Health Record system, and has no @extension attribute.\n","TBD",null,{"$f":"IF(H158=\"\",\"0\",IF(H158=\"Pass\",1,IF(H158=\"Fail\",0,IF(H158=\"TBD\",0,IF(H158=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D158)=48,H158=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-78","PCEHR Assigned Identifier - Organisation (PAI-O) - (OID \"1.2.36.1.2001.1007.1\") [HL72015]\n\nNote: Within the scope of the My Health Record system, additional identifiers are required for connections or documents originating from organisations that are not eligible for an HPI-O, or where a document is authored by a device rather than a person. These identifiers are assigned by the My Health Record system operator, and not the HI Service. These identifier types have been designated as PCEHR Assigned Identifiers (PAI).","C",1,"CONDITION: Identifier types have been designated as PAI-O - the value of the root attribute is an OID commencing with “1.2.36.1.2001.1007.1”: \n\nFail the test if there is no arc following “1.2.36.1.2001.1007.1” or if the arc is not an identifier consisting of a numeric string of sixteen digits commencing with  “8003640001” with a check digit whose value is calculated according to the Luhn algorithm.\nElse, Fail the test if there are any arcs after the identifier.\nElse, Fail the test if there is an extension attribute.\nElse, Pass the test.\n\nNOTE TO TESTER: \nThe ability to use these types of identifiers is stated in the Participation Data Specification [NEHTA-0794:2011] (sections 2.8 and 2.18), as well as HL7 Clinical Document Architecture Release 2 [HL7CDAR2] (Section 4.2.2).\n","Each instance identifier with a @root value starting with “1.2.36.1.2001.1007.1”, has only one arc, which is a valid 16 digit digital health record Assigned identifier and has no @extension attribute.","TBD",null,0,{"$f":"IF(AND(BGCol(D159)=48,H159=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-111","PCEHR Assigned Identifier - Care Agency Employee Identifier (CAE-I ) - (OID \"1.2.36.1.2001.1007.4\") [HL72015]\n\nNote: Within the scope of the My Health Record system, additional identifiers are required for connections or documents originating from organisations that are not eligible for an HPI-O, or where a document is authored by a device rather than a person. These identifiers are assigned by the My Health Record system operator, and not the HI Service. These identifier types have been designated as PCEHR Assigned Identifiers (PAI).\n","C",1,"CONDITION: Identifier types have been designated as CAE-I - the value of the root attribute is an OID commencing with “1.2.36.1.2001.1007.4”: \n\nFail the test if there is no arc following “1.2.36.1.2001.1007.4” or if the arc is not an identifier consisting of a numeric string of sixteen digits commencing with “9” and then 15 digits,\nElse, Fail the test if there are any arcs after the identifier.\nElse, Fail the test if there is an extension attribute.\nElse, Pass the test.\n\nNOTE TO TESTER: \nThe ability to use these types of identifiers is stated in the Participation Data Specification [NEHTA-0794:2011] (sections 2.8 and 2.18), as well as HL7 Clinical Document Architecture Release 2 [HL7CDAR2] (Section 4.2.2).\n","Each instance identifier with a @root value starting with “1.2.36.1.2001.1007.4”, has only one arc, has 16 digit identifier starting with '9' and has no @extension attribute.","TBD",null,0,{"$f":"IF(AND(BGCol(D160)=48,H160=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-79","PCEHR Assigned Identifier - Repository (PAI-R) - (OID \"1.2.36.1.2001.1007.10\") [HL72015]\n\nNote: Within the scope of the My Health Record system, additional identifiers are required for connections or documents originating from organisations that are not eligible for an HPI-O, or where a document is authored by a device rather than a person. These identifiers are assigned by the My Health Record system operator, and not the HI Service. These identifier types have been designated as PCEHR Assigned Identifiers (PAI).\n","C",1,"CONDITION: Identifier types have been designated as PAI-R and the value of the root attribute is an OID commencing with “1.2.36.1.2001.1007.10”.\nFail the test if there is no arc following “1.2.36.1.2001.1007.10” or if the arc is not an identifier consisting of a numeric string of sixteen digits commencing with  “8003640002” with a check digit whose value is calculated according to the Luhn algorithm.\nElse, Fail the test if there are any arcs after the identifier.\nElse, Fail the test if there is an extension attribute.\nElse, Pass the test.\n\nNOTE TO TESTER: \nThe ability to use these types of identifiers is stated in the Participation Data Specification [NEHTA-0794:2011] (sections 2.8 and 2.18), as well as HL7 Clinical Document Architecture Release 2 [HL7CDAR2] (Section 4.2.2).\n","Each instance identifier with a @root value starting with “1.2.36.1.2001.1007.10”, has only one arc, which is a valid 16 digit identifier assigned by the My Health Record system, and has no @extension attribute.","TBD",null,0,{"$f":"IF(AND(BGCol(D161)=48,H161=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-80","PCEHR Assigned Identifier - Delegated Repository  (PAI-delegated) - (OID \"1.2.36.1.2001.1007.11\") [HL72015]\n\nNote: Within the scope of the My Health Record system, additional identifiers are required for connections or documents originating from organisations that are not eligible for an HPI-O, or where a document is authored by a device rather than a person. These identifiers are assigned by the My Health Record system operator, and not the HI Service. These identifier types have been designated as PCEHR Assigned Identifiers (PAI).\n","C",1,"CONDITION: Identifier types have been designated as PAI-delegated - the value of the root attribute is an OID commencing with “1.2.36.1.2001.1007.11”.\n\nFail the test if there is no arc following “1.2.36.1.2001.1007.11” or if the arc is not an identifier consisting of a numeric string of sixteen digits commencing with  “8003640002” with a check digit whose value is calculated according to the Luhn algorithm.\nElse, Fail the test if there are no arcs after the identifier.\nElse, Fail the test if there is an extension attribute.\nElse, Pass the test.\n\nNOTE TO TESTER: \nThe ability to use these types of identifiers is stated in the Participation Data Specification [NEHTA-0794:2011] (sections 2.8 and 2.18), as well as HL7 Clinical Document Architecture Release 2 [HL7CDAR2] (Section 4.2.2).\n","Each instance identifier with a @root value starting with “1.2.36.1.2001.1007.11”,  which is a valid 16 digit identifier assigned by the My Health Record system, and has no @extension attribute. All additional arcs expected are present after the identifier.","TBD",null,0,{"$f":"IF(AND(BGCol(D162)=48,H162=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-81","PCEHR Assigned Identifier - Device (PAI-D) - (OID \"1.2.36.1.2001.1007.20\") [HL72015]\n\nNote: Within the scope of the My Health Record system, additional identifiers are required for connections or documents originating from organisations that are not eligible for an HPI-O, or where a document is authored by a device rather than a person. These identifiers are assigned by the My Health Record system operator, and not the HI Service. These identifier types have been designated as PCEHR Assigned Identifiers (PAI).\n","C",1,"CONDITION: Identifier types have been designated as PAI-D - the value of the root attribute is an OID commencing with “1.2.36.1.2001.1007.20”.\n\nFail the test if there is no arc following “1.2.36.1.2001.1007.20” or if the arc is not an identifier consisting of a numeric string of sixteen digits commencing with  “8003640003” with a check digit whose value is calculated according to the Luhn algorithm.\nElse, Fail the test if there are any arcs after the identifier.\nElse, Fail the test if there is an extension attribute.\nElse, Pass the test.\n\nNOTE TO TESTER: \nThe ability to use these types of identifiers is stated in the Participation Data Specification [NEHTA-0794:2011] (sections 2.8 and 2.18), as well as HL7 Clinical Document Architecture Release 2 [HL7CDAR2] (Section 4.2.2).\n","Each instance identifier with a @root value starting with “1.2.36.1.2001.1007.20”, has only one arc, which is a valid 16 digit identifier assigned by the My Health Record system, and has no @extension attribute.","TBD",null,0,{"$f":"IF(AND(BGCol(D163)=48,H163=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-83","Prescription Identifier scoped by an HPI-O (OID \"1.2.36.1.2001.1005.50\") [HL72015]\nDescription: This OID is used as a the root of an arc that organisations can use for their own internal prescription IDs.\n\n","C",1,"CONDITION: Prescription Identifier scoped by an HPI-O - Instance identifier in the clinical document where the value of the root attribute is an OID commencing with \"1.2.36.1.2001.1005.50\".\n\nFail the step if there is no arc or if the arc is not a national healthcare identifier (HPI-O) consisting of a numeric string of sixteen digits commencing with “800362” with a check digit whose value is calculated according to the Luhn algorithm,\nElse, Fail the step if the extension attribute is either a null string or absent and there is no nullFlavor,\nElse, Pass the step.\n\nNOTE TO TESTER: There may be arcs following the HPI-O as they may be used by the healthcare provider to distinguish different information systems that manage local identifiers. In general, the inclusion of a nullFlavor instead of an extension may be used to indicate the local identifier is unknown and some data elements may require the extension to be known. This applies to test steps.\n","Each instance identifier with a @root value starting with “1.2.36.1.2001.1005.50”  has an arc which is a valid 16 digit HPI-O and either an@extension value which is a non-null string or @nullFlavor value instead of an @extension.","TBD",null,0,{"$f":"IF(AND(BGCol(D164)=48,H164=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II",null,"Dispense Record Identifier scoped by an HPI-O (OID \"1.2.36.1.2001.1005.51\") [HL72015]\nDescription: This OID is used as a the root of an arc that organisations can use for their own internal dispense record IDs.",null,2,"CONDITION: Dispense Record  Identifier scoped by an HPI-O -Instance identifier in the clinical document where the value of the root attribute is an OID commencing with \"1.2.36.1.2001.1005.51\".\n\nFail the step if there is no arc or if the arc is not a national healthcare identifier (HPI-O) consisting of a numeric string of sixteen digits commencing with “800362” with a check digit whose value is calculated according to the Luhn algorithm,\nElse, Fail the step if the extension attribute is either a null string or absent and there is no nullFlavor,\nElse, Pass the step.\n","Each instance identifier with a @root value starting with “1.2.36.1.2001.1005.51”  has an arc which is a valid 16 digit HPI-O and either an@extension value which is a non-null string or @nullFlavor value instead of an @extension.","TBD",null,{"$f":"IF(H165=\"\",\"0\",IF(H165=\"Pass\",1,IF(H165=\"Fail\",0,IF(H165=\"TBD\",0,IF(H165=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D165)=48,H165=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II",null,"HPI-O based Local Order Identifier (OID \"1.2.36.1.2001.1005.52\") [HL72015]\nDescription: This OID is used as the root of an arc that organisations can use for their own local order IDs.",null,3,"CONDITION:HPI-O based Local Order Identifier - Instance identifier in the clinical document where the value of the root attribute is an OID commencing with \"1.2.36.1.2001.1005.52\".\n\nFail the step if there is no arc or if the arc is not a national healthcare identifier (HPI-O) consisting of a numeric string of sixteen digits commencing with “800362” with a check digit whose value is calculated according to the Luhn algorithm,\nElse, Fail the step if the extension attribute is either a null string or absent and there is no nullFlavor,\nElse, Pass the step.\n","Each instance identifier with a @root value starting with “1.2.36.1.2001.1005.52”  has an arc which is a valid 16 digit HPI-O and either an@extension value which is a non-null string or @nullFlavor value instead of an @extension.","TBD",null,{"$f":"IF(H166=\"\",\"0\",IF(H166=\"Pass\",1,IF(H166=\"Fail\",0,IF(H166=\"TBD\",0,IF(H166=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D166)=48,H166=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II",null,"HPI-O based Accession Number (OID \"1.2.36.1.2001.1005.53\") [HL72015]\nDescription: This OID is used as the root of an arc that organisations can use to issue accession numbers in accordance with the DICOM standard.",null,4,"CONDITION: HPI-O based Accession Number scoped by an HPI-O Instance identifier in the clinical document where the value of the root attribute is an OID commencing with \"1.2.36.1.2001.1005.53\".\n\nFail the step if there is no arc or if the arc is not a national healthcare identifier (HPI-O) consisting of a numeric string of sixteen digits commencing with “800362” with a check digit whose value is calculated according to the Luhn algorithm,\nElse, Fail the step if the extension attribute is either a null string or absent and there is no nullFlavor,\nElse, Pass the step.\n","Each instance identifier with a @root value starting with “1.2.36.1.2001.1005.53”  has an arc which is a valid 16 digit HPI-O and either an@extension value which is a non-null string or @nullFlavor value instead of an @extension.","TBD",null,{"$f":"IF(H167=\"\",\"0\",IF(H167=\"Pass\",1,IF(H167=\"Fail\",0,IF(H167=\"TBD\",0,IF(H167=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D167)=48,H167=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II",null,"HPI-O based Report Identifier (OID \"1.2.36.1.2001.1005.54\") [HL72015]\nDescription: This OID is used as the root of an arc that organisations can use for their local report identifiers.",null,5,"CONDITION: HPI-O based report Identifier  - Instance identifier in the clinical document where the value of the root attribute is an OID commencing with \"1.2.36.1.2001.1005.54\".\n\nFail the step if there is no arc or if the arc is not a national healthcare identifier (HPI-O) consisting of a numeric string of sixteen digits commencing with “800362” with a check digit whose value is calculated according to the Luhn algorithm,\nElse, Fail the step if the extension attribute is either a null string or absent and there is no nullFlavor,\nElse, Pass the step.\n","Each instance identifier with a @root value starting with “1.2.36.1.2001.1005.54”  has an arc which is a valid 16 digit HPI-O and either an@extension value which is a non-null string or @nullFlavor value instead of an @extension.","TBD",null,{"$f":"IF(H168=\"\",\"0\",IF(H168=\"Pass\",1,IF(H168=\"Fail\",0,IF(H168=\"TBD\",0,IF(H168=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D168)=48,H168=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-84","Individual Medicare Card Number (OID \"1.2.36.1.5001.1.0.7\") [HL72015]\nDescription: A person identifier allocated by Medicare Australia to eligible persons under the Medicare scheme.\n\nNote: The attributes are defined in AS 5017-2006 Health Care Client Identification [SA2006a].\n","M",1,"For any instance identifier in the clinical document where the value of the root attribute is the OID  ”1.2.36.1.5001.1.0.7”:\n\nFail the test if the extension attribute is not present and there is no nullFlavor or if the extension attribute is not a string of 11 numeric characters,\nElse, Fail the test if the extension attribute value is not one of the special values \"00000000009\", \"00000000000\", \"99999999999\" or \"88888888888\", or  has not had the value calculated by applying the Medicare check digit algorithm, \nElse, Pass the test.\n\nNOTE TO TESTER: \nThe value of the extension attribute is the individual Medicare card number, which is the Medicare card number appended with the individual reference number. The check digit algorithm is described in NEHTA-1732:2014 - Use of HIs in Health Software Systems - Conformance Requirements v3.1. The special values for the individual Medicare card number are :\n• \"00000000009\" for a person that is ineligible for Medicare\n• \"00000000000\" for a person that is eligible but unregistered\n• \"99999999999\" for person that is registered but card is unavailable\n• \"88888888888\" for a person whose Medicare card number is unknown.\n","Each instance identifier with a @root value for Medicare Card, “1.2.36.1.5001.1.0.7”, has an @extension attribute of 11 numeric characters or a nullFlavor. The value is either created by a Medicare check digit algorithm or is one of the specified special values for individual Medicare card numbers.","TBD",null,0,{"$f":"IF(AND(BGCol(D169)=48,H169=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-85","Medicare Card Number (OID \"1.2.36.1.5001.1.0.7.1\") [HL72015]\nDescription: The Medicare card number is printed on a Medicare card and is used to access Medicare records for an eligible person.\n\nNote: The requirements for the attributes are defined in AS 5017-2006 Health Care Client Identification [SA2006a].\n\n","M",1,"For any instance identifier in the clinical document where the value of the root attribute is the OID ”1.2.36.1.5001.1.0.7.1”:\n\nFail the test if the extension attribute is not present and there is no nullFlavor or if the extension attribute is not a string of 10 numeric characters,\nElse, Fail the test if the extension attribute value is not one of the special values \"0000000000\", \"9999999999\" or \"8888888888\", or  has had the value calculated by applying the Medicare check digit algorithm, \nElse, Pass the test.\n\nNOTE TO TESTER: \nThe value of the extension attribute is the Medicare card number. The check digit algorithm is described on the Medicare website.\n","Each instance identifier with a @root value for Medicare Card, “1.2.36.1.5001.1.0.7.1”, has an @extension attribute of 10 numeric characters or a nullFlavor. The value is either a Medicare check digit algorithm or one of the specified special values for individual Medicare card numbers.","TBD",null,0,{"$f":"IF(AND(BGCol(D170)=48,H170=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-86","Department of Veterans' Affairs File Number (OID \"2.16.840.1.113883.3.879.270091\") [AIHW2015]\n\nThe OID 2.16.840.1.113883.3.879 denotes the Metadata Online Registry (METeOR) and arc “270091” is allocated by METeOR.  The attributes are defined in AS 5017-2006 Health Care Client Identification [SA2006a].\n\nDescription: A unique personal identifier issued to a veteran by the Department of Veterans' Affairs.\n","M",1,"For any instance identifier in the clinical document where the value of the root attribute is the OID ”2.16.840.1.113883.3.879.270091”:\n\nFail the test if the extension attribute is not present and there is no nullFlavor or if the extension attribute is not a string of either 8 or 9 alphanumeric characters,\nElse, Fail the test if the extension attribute's first (State Code) character is not one of 'N', 'V', 'Q', 'W', 'S', or 'T',\nElse, Fail the test if the extension attribute's next seven characters are not one of the following options:\ni) A War Code of 1 alpha character followed by 6 digits (ANNNNNN), or\nii) A War Code of 2 alpha characters followed by 5 digits (AANNNNN), or\niii) A War Code of 3 alpha characters followed by 4 digits (AAANNNN), or\nElse, Pass the test.\n\nNOTE TO TESTER: \nThe value of the extension attribute is the Department of Veterans' Affairs file number. The first character is the State Code (an alpha), being either ‘N’ (for NSW), ‘V’ (for Victoria), ‘Q’ (for Queensland), ‘W’ (for Western Australia), ‘S’ (for South Australia) or ‘T’ (for Tasmania). Veterans in the ACT are given the NSW state code ‘N’ and veterans in the Northern Territory are given the South Australian state code ‘S’. The next seven characters are the File Number, made up of a War Code and numeric digits. The ninth character is optional and if present is an alpha. The ninth character represents members related to the veteran. It is a code generated in the order that cards are issued, such as 'A', 'B', 'C', 'D' etc. \n","Each instance identifier with a @root value for Department of Veterans' Affairs , ”2.16.840.1.113883.3.879.270091”, has an @extension attribute of 8 or 9  numeric characters, or a valid @nullFlavor.  Where @extension is present, the value's first character is a State Code and the next 7 characters are one of the specified War Code values.","TBD",null,0,{"$f":"IF(AND(BGCol(D171)=48,H171=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II",null,"Department of Veterans' Affairs File Number (OID \"2.16.840.1.113883.3.879.339127\") [AIHW2015]\n\nThe OID 2.16.840.1.113883.3.879 denotes the Metadata Online Registry (METeOR) and arc “339127”  is allocated by METeOR.  The attributes are defined in AS 5017-2006 Health Care Client Identification [SA2006a].\n\nDescription: A unique personal identifier issued to a veteran by the Department of Veterans' Affairs.\n",null,2,"For any instance identifier in the clinical document where the value of the root attribute is the OID ”2.16.840.1.113883.3.879.339127”:\n\nFail the test if the extension attribute is not present and there is no nullFlavor or if the extension attribute is not a string of either 8 or 9 alphanumeric characters,\nElse, Fail the test if the extension attribute's first (State Code) character is not one of 'N', 'V', 'Q', 'W', 'S', or 'T',\nElse, Fail the test if the extension attribute's next seven characters are not one of the following options:\ni) A War Code of 1 alpha character followed by 6 digits (ANNNNNN), or\nii) A War Code of 2 alpha characters followed by 5 digits (AANNNNN), or\niii) A War Code of 3 alpha characters followed by 4 digits (AAANNNN), or \niv) There is no  War Code - A blank character followed by 6 digits ( NNNNNN)\nElse, Pass the test.\n\nNOTE TO TESTER: \nThe value of the extension attribute is the Department of Veterans' Affairs file number. The first character is the State Code (an alpha), being either ‘N’ (for NSW), ‘V’ (for Victoria), ‘Q’ (for Queensland), ‘W’ (for Western Australia), ‘S’ (for South Australia) or ‘T’ (for Tasmania). Veterans in the ACT are given the NSW state code ‘N’ and veterans in the Northern Territory are given the South Australian state code ‘S’. The next seven characters are the File Number, made up of a War Code and numeric digits. The ninth character is optional and if present is an alpha. The ninth character is always an alphabetic character, generated in the order the cards are issued, such as 'A', 'B', 'C', 'D' etc. \n","Each instance identifier with a @root value for Department of Veterans' Affairs , ”2.16.840.1.113883.3.879.339127”, has an @extension attribute of 8 or 9  numeric characters, or a valid @nullFlavor.  Where @extension is present, the value's first character is a State Code and the next 7 characters are one of the specified War Code values.","TBD",null,{"$f":"IF(H172=\"\",\"0\",IF(H172=\"Pass\",1,IF(H172=\"Fail\",0,IF(H172=\"TBD\",0,IF(H172=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D172)=48,H172=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-87","Centrelink customer reference number (OID ”2.16.840.1.113883.3.879.270098”) [AIHW2015]\n\nThe OID 2.16.840.1.113883.3.879 denotes the Metadata Online Registry (METeOR) and arc “270098” is allocated by METeOR. The attributes are defined in AS 5017-2006 Health Care Client Identification [SA2006a].\n\nDescription: A personal identifier assigned by Centrelink for the purposes of identifying people (and organisations) eligible for specific services, including some public health care services, such as oral health services.\n\nCentrelink customer reference number (OID ”2.16.840.1.113883.3.879.369274”) [AIHW2015]\n\nThe OID 2.16.840.1.113883.3.879 denotes the Metadata Online Registry (METeOR) and arc “369274” is allocated by METeOR.\n\nDescription: A personal identifier assigned by Centrelink for the purposes of identifying people (and organisations) eligible for specific services, including some public health care services, such as oral health services.\n","M",1,"For any instance identifier in the clinical document where the value of the root attribute is the OID ”2.16.840.1.113883.3.879.270098”:\n\nFail the test if the extension attribute is not present and there is no nullFlavor or if the extension attribute is not a string of 10 alpha-numeric characters.\nElse, Fail the test if the extension attribute is present and does not comprise of a string of nine numeric characters followed by an alphabetical characters (i.e. 10 characters in total).\nElse, Pass the test.\n\nNOTE TO TESTER: \nThe source document which defines the attributes (i.e. AS 5017-2006 Health Care Client Identification [SA2006a]), section \"2.3.4 Centrelink Customer Reference Number\" states:\nField size: 10\nData type: Alphanumeric\nRepresentational layout: NNNNNNNNNA\nData domain: The reference number is comprised of 9 numeric characters and one alphabetic character.\n","Each instance identifier with a @root value for Centrelink customer,  ”2.16.840.1.113883.3.879.270098”, has a valid arc and an @extension attribute of 10 characters, or a nullFlavor. The value's first 9 characters are numeric followed by an alphanumeric character.","TBD",null,0,{"$f":"IF(AND(BGCol(D173)=48,H173=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II",null,null,null,2,"For any instance identifier in the clinical document where the value of the root attribute is the OID ”2.16.840.1.113883.3.879.369274”:\n\nFail the test if the extension attribute is not present and there is no nullFlavor or if the extension attribute is not a string of 10 alpha-numeric characters.\n Else, Fail the test if the extension attribute is present and does not comprise of a string of nine numeric characters followed by an alphabetical characters (i.e. 10 characters in total).\n Else, Pass the test.\n\nNOTE TO TESTER: \n The webpage for METeOR states:\n Data type: String\n Format: N(9)A\n Maximum character length: 10\n Data type: Alphanumeric\n","Each instance identifier with a @root value for Centrelink customer,  ”2.16.840.1.113883.3.879.369274”, has a valid arc and an @extension attribute of 10 characters, or a nullFlavor. The value's first 9 characters are numeric followed by an alphanumeric character.","TBD",null,{"$f":"IF(H174=\"\",\"0\",IF(H174=\"Pass\",1,IF(H174=\"Fail\",0,IF(H174=\"TBD\",0,IF(H174=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D174)=48,H174=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-88","Medicare Provider Number (OID \"1.2.36.174030967.0.2\") [HL72015]\nDescription: An identifier assigned to an individual at a specific location by Medicare Australia that identifies the right to act as a healthcare provider under the Medicare Benefits scheme.\n\nNOTE : A Medicare provider number consists of digits only and has a maximum of 6 digits. Refer to http://meteor.aihw.gov.au/content/index.phtml/itemId/601809.","M",1,"For any instance identifier in the clinical document where the value of the root attribute is the OID ”1.2.36.174030967.0.2”:\n\nFail the test if the extension attribute is a null string.\nElse, Fail the test if the extension is absent and there is no nullFlavor.\nElse, Fail the test if the extension is present and value of the extension attribute is not in the format NNNNNN (where N is a numeric character whose value can range from 0 to 9).\nElse, Fail the test if there is an arc following the OID '1.2.36.174030967.0.2'.\nElse, Pass the test.\n\nNOTE TO TESTER: \nThe value of the extension attribute is the Medicare provider number. \n","1. Each instance identifier with a @root value for Medicare Provider,  ”1.2.36.174030967.0.2”, has a valid arc and @extension attribute. \n2.\na. extension attribute is absent but the instance identifier has a valid nullFlavor attribute.\n(or) \nb. extension attribute is present and its value is in the format NNNNNN (where N is a numeric character whose value can range from 0 to 9).\n","TBD",null,0,{"$f":"IF(AND(BGCol(D175)=48,H175=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-89","Medicare Prescriber Number (OID \"1.2.36.174030967.0.3\") [HL72015]\nDescription: An identifier assigned to an individual by Medicare Australia that identifies the right to act as a prescriber under the Pharmaceutical Benefits scheme.\n","M",1,"For any instance identifier in the clinical document where the value of the root attribute is the OID ”1.2.36.174030967.0.3”:\n\nFail the test if the extension attribute is a null string.\nElse, Fail the test if the extension is absent and there is no nullFlavor.\nElse, Fail the test if there is an arc following the OID ”1.2.36.174030967.0.3”.\nElse, Pass the test.\n\nNOTE TO TESTER: \nThe value of the extension attribute is the Medicare Prescriber Number. The test case does not assess the format of the Medicare prescriber number.\n","Each instance identifier with a @root value for Medicare Prescriber,  ”1.2.36.174030967.0.3”,  has a valid arc and @extension attribute. Alternatively, no @extension but with a valid @nullFlavor. ","TBD",null,0,{"$f":"IF(AND(BGCol(D176)=48,H176=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-90","Pharmacy Approval Number (OID \"1.2.36.174030967.1.3.2.1\") [HL72015]\nDescription: This number allows the pharmacy to do PBS scripts and claim, and is granted once a pharmacy is registered as a business and has approval from the pharmacy board. The number is valid so long as the pharmacy ownership and location remain the same. \n","M",1,"For any instance identifier in the clinical document where the value of the root attribute is the OID ”1.2.36.174030967.1.3.2.1”:\n\nFail the test if the extension attribute is a null string.\nElse, Fail the test if the extension is absent and there is no nullFlavor.\nElse, Fail the test if there is an arc following the OID ”1.2.36.174030967.1.3.2.1”.\nElse, Pass the test.\n\nNOTE TO TESTER: \nThe value of the extension attribute is the Pharmacy Approval Number. The test case does not assess the format of the Medicare pharmacy approval number.\n","Each instance identifier with a @root value for Pharmacy Approval,  ”1.2.36.174030967.1.3.2.1”,  has a valid arc and @extension attribute. Alternatively, no @extension but with a valid @nullFlavor. ","TBD",null,0,{"$f":"IF(AND(BGCol(D177)=48,H177=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-91","NATA Lab Accreditation Number (OID \"1.2.36.1.2001.1005.12\") [HL72015]\nDescription: NATA issues unique identifiers to laboratories when they are accredited. These numbers are used in v2 messages and CDA documents in order to identify the lab that is the source of a pathology report and the detailed items in it. This OID identifies that NATA lab accreditation number.\n","M",1,"For any instance identifier in the clinical document where the value of the root attribute is the OID ”1.2.36.1.2001.1005.12”:\n\nFail the test if the extension attribute is a null string.\nElse, Fail the test if the extension is absent and there is no nullFlavor.\nElse, Fail the test if there is an arc following the OID '1.2.36.1.2001.1005.12'\nElse, Pass the test.\n\nNOTE TO TESTER:\nThe value of the extension attribute is the NATA lab accreditation number. The test case does not assess the format of the NATA lab accreditation number.\n","Each instance identifier with a @root value for NATA Lab Accreditation,  ”1.2.36.1.2001.1005.12”,  has a valid @extension attribute. Alternatively, no @extension but with a valid @nullFlavor. ","TBD",null,{"$f":"IF(H178=\"\",\"0\",IF(H178=\"Pass\",1,IF(H178=\"Fail\",0,IF(H178=\"TBD\",0,IF(H178=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D178)=48,H178=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","TC-Types-92","Diagnostic Imaging Provider location specific practice number (OID \"1.2.36.1.2001.1005.48\") [HL72015]\nDescription: The Department of health issues location specific practice numbers (LSPN's) to Diagnostic Imaging providers in the accreditation program. A unique LSPN's is issued to diagnostic providers when they are accredited. These numbers are used in v2 messages and CDA documents in order to identify the diagnostic imaging provider that is the source of a diagnostic imaging report and the detailed items in it. This OID identifies that LSPN number.\n","M",1,"For any instance identifier in the clinical document where the value of the root attribute is the OID ”1.2.36.1.2001.1005.48”:\n\nFail the test if the extension attribute is a null string.\nElse, Fail the test if the extension is absent and there is no nullFlavor.\nElse, Fail the test if there is an arc following the OID ”1.2.36.1.2001.1005.48”.\nElse, Pass the test.\n\nNOTE TO TESTER:\nThe value of the extension attribute is the LSPN number. The test case does not assess the format of the LSPN number.\n","Each instance identifier with a @root value for Diagnostic Imaging Provider location specific practice,  ”1.2.36.1.2001.1005.48”,  has a valid arc and @extension attribute. Alternatively, no @extension but with a valid @nullFlavor. ","TBD",null,{"$f":"IF(H179=\"\",\"0\",IF(H179=\"Pass\",1,IF(H179=\"Fail\",0,IF(H179=\"TBD\",0,IF(H179=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D179)=48,H179=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-II","END:  TS-II (Instance identifier)"]
["TS-PQ","START:  TS-PQ (Physical quantity)"]
["TS-PQ","TC-Types-93","7.8.9.3.2 unit [ISO21090]\nDefinition: The unit of measure specified in the Unified Code for Units of Measure (UCUM).\n\nUCUM defines two forms of expression, case sensitive and case insensitive. PQ uses the case sensitive codes.\n","M",1,"For any data element of ISO data type PQ or the derived type Quantity:\n\nFail the test if the unit of measure is not specified in the United Code for units of Measure (UCUM).\nElse, Fail the test if the value of unit is a case insensitive code.\nElse, Pass the test.\n\nNOTE TO TESTER: \nIn the UCUM specification the case insensitive codes are listed under the heading \"c/i\" and case sensitive codes are listed under the heading \"c/s\". Specification can be found under http://unitsofmeasure.org/trac\n","Each data element of ISO data type PQ or the derived type Quantity is present and code value is case sensitive","TBD",null,{"$f":"IF(H182=\"\",\"0\",IF(H182=\"Pass\",1,IF(H182=\"Fail\",0,IF(H182=\"TBD\",0,IF(H182=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D182)=48,H182=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-PQ","TC-Types-94","7.8.9.5 Invariants [ISO21090]\n- A value SHALL be provided if not nullFlavored;\n\nNote: Requirements for attributes defined for the PQ data type but not allowed by the Australian CDA Schema Extension are not listed here.\n","M",1,"For any data element of ISO data type PQ or the derived type Quantity:\n\nFail the test if both value and nullFlavor are omitted.\nElse, Pass the test.\n\nNOTE TO TESTER: \nThis test is not performed by the Australian CDA Schema Extension [NEHTA-1599:2014].\n"," ISO data type PQ or the derived type Quantity has a value or a nullFlavor.","TBD",null,{"$f":"IF(H183=\"\",\"0\",IF(H183=\"Pass\",1,IF(H183=\"Fail\",0,IF(H183=\"TBD\",0,IF(H183=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D183)=48,H183=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-PQ","END:  TS-PQ (Physical quantity)"]
["TS-INT","START:  TS-INT (Integer)"]
["TS-INT","TC-Types-95","7.8.3.5 Invariants [ISO21090]\n- A value SHALL be provided if not nullFlavored;\n\nNote: Requirements for attributes defined for the INT data type but not allowed by the Australian CDA Schema Extension are not listed here.\n","M",1,"For any data element of ISO data type INT or the derived type Integer:\nFail the test if there is no value attribute and no nullFlavor attribute.\nElse, Pass the test.\n","Either the value attribute or the code attribute is present in the code element. \n","TBD",null,{"$f":"IF(H186=\"\",\"0\",IF(H186=\"Pass\",1,IF(H186=\"Fail\",0,IF(H186=\"TBD\",0,IF(H186=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D186)=48,H186=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-INT","END:  TS-INT (Integer)"]
["TS-REAL","START:  TS-REAL (Real)"]
["TS-REAL","TC-Types-96","7.8.7.6 Invariants [ISO21090]\n- A value SHALL be provided if not nullFlavored;\n\nNote: Requirements for attributes defined for the REAL data type but not allowed by the Australian CDA Schema Extension are not listed here.\n","M",1,"For any data element of ISO data type REAL or the derived type Real:\nFail the test if there is no value attribute and no nullFlavor attribute.\nElse, Pass the test.\n","Either the value attribute or the code attribute is present in the code element. \n","TBD",null,{"$f":"IF(H189=\"\",\"0\",IF(H189=\"Pass\",1,IF(H189=\"Fail\",0,IF(H189=\"TBD\",0,IF(H189=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D189)=48,H189=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-REAL","END:  TS-REAL (Real)"]
["TS-RTO","START:  TS-RTO (Ratio)"]
["TS-RTO","TC-Types-97","7.8.8.4 Invariants [ISO21090]\n- If the RTO is not nullFlavored, both a numerator and a denominator are required;\n- Neither numerator nor denominator may be of type TS.\n\nNote: Requirements for attributes defined for the RTO data type, which are not allowed by the Australian CDA Schema Extension are not listed here.\n","M",1,"For any data element of ISO data type RTO or the derived type QuantityRatio:\n\nIf the data element contains a nullFlavor then Pass the test.\nElse, Fail the test if both the numerator and denominator attributes are not present.\nElse, Fail the test if either or both the numerator and denominator attributes are of type \"TS\".\nElse, Pass the test.\n\nNOTE TO TESTER: \nThis test is not performed by the Australian CDA Schema Extension [NEHTA-1599:2014].\n\nThe following valid example shows a ratio of US$103/day:\n\n<example xsi:type=\"RTO\"> \n        <numerator xsi:type=\"MO\" value=\"103.00\" currency=\"USD\"/> \n       <denominator xsi:type=\"PQ\" value=\"1\" unit=\"day\"/> \n</example> \n","For any data element of ISO data type RTO or the derived type QuantityRatio both the numerator and denominator attributes are present and neither is type \"TS\", or the data element has a nullFlavor.\n","TBD",null,{"$f":"IF(H192=\"\",\"0\",IF(H192=\"Pass\",1,IF(H192=\"Fail\",0,IF(H192=\"TBD\",0,IF(H192=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D192)=48,H192=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-RTO","END:  TS-RTO (Ratio)"]
["TS-PQ.TIME","START:  TS-PQ.TIME (Period of Time)"]
["TS-PQ.TIME","TC-Types-98","7.8.10.1 Description [ISO21090]\n◾PQ.TIME constraints PQ so that it shall have units that describe a period of time\n\n7.8.10.2 Invariants [ISO21090]\n◾The units SHALL be a measure of time.\n\nNote: . The UCUM name (and code) for the commonly used units for time are: second (\"s\"), minute (\"min\"), hour (\"h\"), day (\"d\"), week (\"wk\"), month (\"mo\") and year (\"a\"). \n\n","M",1,"For any data element of ISO data type PQ.TIME or the derived type Duration:\n\nFail the test if the data element fails any test case in TS-PQ.\nElse Fail the test if the unit attribute is not present.\nElse Fail the test if the unit attribute is present and does not have one of the values for measuring time.\nElse, Pass the test.\n\n","ISO data type PQ.TIME (or the derived type Duration), has a unit attribute with a value which is a valid unit of time.","TBD",null,{"$f":"IF(H195=\"\",\"0\",IF(H195=\"Pass\",1,IF(H195=\"Fail\",0,IF(H195=\"TBD\",0,IF(H195=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D195)=48,H195=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-PQ.TIME","END:  TS-PQ.TIME  (Period of Time)"]
["TS-TS","START:  TS-TS (Time stamp)"]
["TS-TS","TC-Types-99","7.8.13.3.1 value [ISO21090]\nTS (Point in time) Attributes:\nThe value of the TS is a string with the format \"YYYY[MM[DD[HH[MM[SS[.U[U[U[U]]]]]]]]][+|-ZZzz]\" that conforms to the constrained ISO 8601 defined in ISO/IEC 8824 (all parts) (ASN.1) under Clause 32 (generalized time).\n","M",1,"For any data element of ISO data type TS or the derived type DateTime:\n\nFail the test if the character string does not meet any of the following criteria:\na. Consists only of the characters \"0\", \"1\", \"2\", \"3\", \"4\", \"5\", \"6\", \"7\", \"8\", \"9\", \"+\", \"-\", \".\".\nb. If there is no \"+\" or \"-\" then the number of digits is either 4, 6, 8, 12, 14 or more.\nc. If there is a \"+\" or \"-\" then the number of digits before the \"+\" or \"-\" is either 12, 14 or more.\nd. If there is a character following the time then it is either a \"+\" or \"-\".\ne. Following the \"+\" or \"-\" is a set of four digits.\nf. The year \"YYYY\" has a value from \"0\" to \"9\" for each \"Y\".\ng. The month \"MM\" (if present) has a value from \"01\" to \"12\".\nh. The day \"DD\" (if present) has a value from \"01\" to \"31\" and is a valid value for the month.\ni. The hours \"HH\" (if present) has a value from \"00\" to \"23\"\nj. The minutes \"MM\" (if present) has a value from \"00\" to \"59\".\nk. The seconds \"SS\" (if present) has a value from \"00\" to \"59\".\nl. The timezone hours \"ZZ\" (if present) has a value from \"00\" to \"14\". \nm. The timezone minutes \"zz\" (if present) has a value from \"00\" to \"59\".\nn. If the millisecond prefix \".\" is present, then hours, minutes and seconds are present before \".\".\nElse, Pass the test.\n\nNOTE TO TESTER: \nThe rationale for (b) is that there are four digits if only a year is stated, 6 digits if a month is also stated, 8 digits if a day is also stated, 12 digits if the hours and minutes are also stated, and 14 digits if seconds are also stated. The string representation is not allowed to have only 10 digits due to the requirement that if hours are stated then minutes must be stated as well. The rationale for (k) is that there is no timezone offset greater than 14 hours\n","ISO  data type TS (or derived type DateTime), has DateTime attribute which is a valid unit of time.\n","TBD",null,{"$f":"IF(H198=\"\",\"0\",IF(H198=\"Pass\",1,IF(H198=\"Fail\",0,IF(H198=\"TBD\",0,IF(H198=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D198)=48,H198=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-TS",null,null,null,2,"Fail the test if the string representation contains a date only (i.e. eight digits or less) and the timezone (i.e. without Time) is present.\nElse, Pass the test.\n","ISO data type TS (or the derived type DateTime), has timezone details only when a time is given.","TBD",null,{"$f":"IF(H199=\"\",\"0\",IF(H199=\"Pass\",1,IF(H199=\"Fail\",0,IF(H199=\"TBD\",0,IF(H199=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D199)=48,H199=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-TS","TC-Types-100","7.8.13.5 Invariants [ISO21090]\n- If the TS is not nullFlavored, a value SHALL be present;\n- If a value is present, at least a full year SHALL be specified;\n\nNote: Requirements for attributes defined for the TS data type but not allowed by the Australian CDA Schema Extension are not listed here.\n","M",1,"For any data element of ISO data type TS or the derived type DateTime:\n\nFail the test if neither nullFlavor nor a value attribute is present.\nElse, Fail the test if a value attribute is present and does not include at least a full year.\nElse, Pass the test.\n\nNOTE TO TESTER:\nA full year means each digit of YYYY contains a value. \nThe validity of the year in the value attribute is tested in TC-Types-99 (f).\n","Data element of ISO data type TS (or the derived type DateTime) are either nullFlavored or contain at least a full year.","TBD",null,{"$f":"IF(H200=\"\",\"0\",IF(H200=\"Pass\",1,IF(H200=\"Fail\",0,IF(H200=\"TBD\",0,IF(H200=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D200)=48,H200=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-TS","TC-Types-101","Section 8.3 time [NEHTACDAIG]\nWhen a time value is supplied it SHALL include hours and minutes.\nWhen a time value is supplied it MAY include seconds and fractions of seconds.\nWhen a time value is supplied it SHALL include a time zone.\n\nNote: The conditions of use or definition of a data element in the Structured Content Specification or Participation Data Specification may state that a data element is to specify a time, otherwise the presence of the time is optional.  In the context of the DateTime data element, the time value contains the hours and minutes, and optionally seconds and decimal fractions of seconds. \n","M",1,"For any data element of ISO data type TS or the derived type DateTime:\n\nWhere the conditions of use or definition of a data element states that the data element is to specify a time, then:\nFail the test if the time value does not include hours and minutes.\nElse, Fail the test if the time value does not include a four digit timezone.\nElse, Pass the test.\n\nNOTE TO TESTER:\nThe appropriate format is YYYYMMDDHHMM[SS[.U[U[U[U]]]]]+|-ZZzz, where only seconds and fractions of seconds are optional.\n","ISO data type TS or the derived type DateTime value includes hours, minutes and a timezone. Seconds and fractions of a second can be included.","TBD",null,{"$f":"IF(H201=\"\",\"0\",IF(H201=\"Pass\",1,IF(H201=\"Fail\",0,IF(H201=\"TBD\",0,IF(H201=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D201)=48,H201=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-TS","END:  TS-TS (Time stamp)"]
["TS-IVL","START:  TS-IVL (Interval)"]
["TS-IVL","TC-Types-102","7.10.9.3.1 low [ISO21090]\nThis is the low limit. If the low limit is not known, a nullFlavor may be specified. The low limit SHALL NOT be positive infinity.\n","M",1,"For any data element of ISO data type IVL or the derived types QuantityRange or TimeInterval:\n\nFail the test if the low limit contains nullFlavor PINF.\nElse, Pass the test.\n\nNOTE TO TESTER: \nlow limit may contain nullFlavors but not PINF \n","ISO data type IVL or the derived types QuantityRange or TimeInterval low limit does not contain nullflavor 'PINF'.","TBD",null,{"$f":"IF(H204=\"\",\"0\",IF(H204=\"Pass\",1,IF(H204=\"Fail\",0,IF(H204=\"TBD\",0,IF(H204=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D204)=48,H204=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-IVL","TC-Types-103","7.10.9.3.3 high [ISO21090]\nThis is the high limit. If the high limit is not known, a nullFlavor may be specified. The high limit SHALL not be negative infinity, and SHALL be higher than the low limit if one exists.\n","M",1,"For any data element of ISO data type IVL or the derived types QuantityRange or TimeInterval:\n\nFail the test if the high limit contains nullFlavor NINF.\nElse, Fail the test of the value of the high limit is not higher than the value of the low limit.\nElse, Pass the test.\n\nNOTE TO TESTER:\n high limit may contain nullFlavors but not NINF.\n","ISO data type IVL or the derived types QuantityRange or TimeInterval high limit does not contain nullflavor 'NINF' and the value of the high limit is higher than the value of the low limit.","TBD",null,{"$f":"IF(H205=\"\",\"0\",IF(H205=\"Pass\",1,IF(H205=\"Fail\",0,IF(H205=\"TBD\",0,IF(H205=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D205)=48,H205=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-IVL","TC-Types-104","7.10.9.5 Invariants [ISO21090]\n- lowClosed and highClosed can only be used if low or high are used;\n- low and high SHALL be comparable.\n- Either the IVL is nullFlavored, has a width, any, or has low and/or high. 'any and/or width' and 'low and/or high' cannot be mixed\n\nNote: The last requirement means that the unit of measure for both high and low are required to be compatible and represent the same kind of unit, for example mass, volume, length.\n\nNote: The lowClosed and highClosed attributes are instantiated in XML as the ‘inclusive’ attribute in the low or high boundary so there is no need to test conformance to the requirements for the lowClosed and highClosed attributes.\n\nNote: According to section 3.8.1 of [HL72004], an interval of time, which has the IVL_TS subtype of the HL7 IVL data type, may be represented using a value attribute.\n\n","M",1,"For any data element of ISO data type IVL or the derived types QuantityRange or TimeInterval:\n\nFail the test if low and high contain units of measure that are not comparable.\nElse Fail the test if the low or high contain a different unit of measure from the interval.\nElse, Fail the test if IVL values contain any or width together with either low or high.\nElse, if the interval is an interval of time then Fail the test if there is no value, nullFlavor, width, any, low or high.\nElse, if the interval is not an interval of time then Fail the test if there is no nullFlavor, width, any, low or high.\nElse, Pass the test.\n\nNOTE TO TESTER: \nThe unit of measure is the value of the unit attribute. When the interval is an interval of physical quantities, the unit may be recorded in the interval as an alternative to recording the unit in the low and high elements.  If the unit is present it applies to the low and high boundaries. (Section 3.7 [HL72004]).\n\nComparable quantities do not have to have the same unit of measure. Section 7.10.9 of ISO 21090 states that comparable quantities are quantities of the same physical dimension, e.g. Millimetres and metres are comparable whereas metres and seconds are not.","Data elements of ISO data type IVL (or the derived types QuantityRange or TimeInterval) are either nullFlavored or have compatible units of measure. ","TBD","                                                                ",{"$f":"IF(H206=\"\",\"0\",IF(H206=\"Pass\",1,IF(H206=\"Fail\",0,IF(H206=\"TBD\",0,IF(H206=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D206)=48,H206=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-IVL","END:  TS-IVL (Interval)"]
["TS-Class","START:  TS-Class (Reference information model classes)"]
["TS-Class","TC-Types-110","3.1.13.1 Observation.value [HL72013]\nDefinition: Information that is assigned or determined by the observation action.\nData Type: ANY (0..*)\n\nThe appropriate data type of the Observation.value varies with the kind of Observation and can generally be described in Observation definitions or in a simple relation that pairs Act.codes to value data types.\n\n3.1.1.4 Act.code [HL72013]\nDefinition: The particular kind of Act that the Act-instance represents within its class. \nData Type: CD (0..1)\n\nNote: The Observation class is specialization of the Act class. The statement above means that the value of the Observation.value must be consistent with the value of Observation.code. For example the data type for Individual Pathology Test Result Value (the Observation.value) is selected based on the value of the Individual Pathology Test Result Name (the Observation.code). The data type for Individual Pathology Test Result Value is not stated in the clinical document specifications as it depends on the Individual Pathology Test Result Name.\n","M",1,"For any Observation.value where the structured content specification does not specify the type:\n\nFail the test if the data type of Observation.value is inconsistent with the kind of observation (indicated by Observation.code).\nElse, Pass the test.\n\nNOTE TO TESTER: \nFor most observation.value data elements the clinical document structured content specification states the data type. Therefore this test need only be applied for those data types where the structured content specification states a set of possible data types and any observation.value data elements that are extensions to the clinical document specifications. For example, in the Event Summary structured content specification the data type is specified for most data elements except Individual Pathology Test Result Value which may be CodeableText, QuantityRange or Quantity.\n\nGuidance for selecting the correct data type for observation.value is provided in section 6.36.1 of the HL7 Reference Information Model [HL72013]. For example, if the kind of observation is a measurement of a physical quantity then an appropriate data type for Observation.value is PQ, which is a real number with a unit. Numeric values should not be communicated as simply a character string (ST) as the number and unit cannot be read from a character string and processed by a clinical decision support system.\n","Observation.value is consistent with the Observation.code","TBD",null,{"$f":"IF(H209=\"\",\"0\",IF(H209=\"Pass\",1,IF(H209=\"Fail\",0,IF(H209=\"TBD\",0,IF(H209=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D209)=48,H209=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Class","END:  TS-Class (Reference information model classes)"]
["TS-CS","START:  TS-CS (Coded Simple)"]
["TS-CS","TC-Types-115","7.5.4.5 Invariants [ISO21090]\n  - There shall be a code if not nullFlavored.\n\nNote: Coded Simple data is data in its simplest form, where only the code is not predetermined. The code system and code system version are implied and fixed by the context in which the CS value occurs.","M",1,"For any data element of ISO data type CS:\n\nFail the test if neither nullFlavor nor code are present.\nElse, Pass the test.","Each data element of ISO data type CS has a nullFlavor if there is no code.","TBD",null,{"$f":"IF(H212=\"\",\"0\",IF(H212=\"Pass\",1,IF(H212=\"Fail\",0,IF(H212=\"TBD\",0,IF(H212=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D212)=48,H212=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-CS","TC-Types-116","7.5.4.3.1 code [ISO21090]\nThe plain code symbol defined by the code system. if the code value is empty or null, then there is no code in the code system that represents the concept. Code shall only contain characters that are either a letter, a digit or one of '.', '-', '_' or ':'. Code systems that are used with CS shall not define code symbols or expression syntaxes that contain whitespace or any other characters not in this list.\n\nNote: Although a CS does not carry a codeSystem as an attribute, there shall always be an applicable codeSystem specified by the context in which CS is used (section 7.5.4.6.1 [ISO21090]).\n","M",1,"For any data element of ISO data type CS:\n\nFail the test if a code is present and contains characters other than letters, digits, '.', '-', '_' or ':'.\nElse, Fail the test if the code attribute has a value that is not permitted by the codeSystem.\nElse, Pass the test.\n\nNOTE TO TESTER: \nAn example is the statusCode data element within substanceAdministration which is a derivative of the RIM SubstanceAdministration class (section 4.3.6.8 [HL7CDAR2]) which in turn is a derivative of the Act class (section 3.1.1 [HL72013]) and the statusCode has the CS data type with the CNE (Coded, No Extensions) coding strength and the ActStatus vocabulary domain (section 3.1.1.9 [HL72013]). As XML is case sensitive the value of the statusCode code attribute must be one of the values in the ActStatus vocabulary domain with the same case.","If a code is present in a data element of ISO data type CS the code has only the allowed characters.","TBD",null,{"$f":"IF(H213=\"\",\"0\",IF(H213=\"Pass\",1,IF(H213=\"Fail\",0,IF(H213=\"TBD\",0,IF(H213=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D213)=48,H213=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-CS","END:  TS-CS (Coded Simple)"]
["TS-PIVL","START:   TS-PIVL (Periodic Interval)"]
["TS-PIVL","TC-Types-117","7.10.13.4 Invariants [ISO21090]\n- if PIVL is not nullFlavored, only one of period and frequency may be specified;\n- the width of the phase shall be less or equal to the period.\n\nNote: There are separate requirements for individual PIVL attributes such as phase (IVL_TS), period (PQ), and frequency (RTO), based on the data types of these attributes. Tests for conformance to these requirements are applied in the TS-IVL, TS-PQ and TS-RTO test sets.\n","M",1,"For any data element of ISO data type PIVL:\n\nFail the test if neither nullFlavor, period nor frequency are present.\nElse, Fail the test if both period and frequency are present.\nElse, Fail the test if the width of the phase is greater than the period.\nElse, Pass the test.\n\nNOTE TO TESTER: \nThe following valid example means twice a day (every 12 h) for 10 min.\n<example xsi:type='PIVL_TS'>\n<phase>\n<width xsi:type=\"PQ\" value='10' unit='min'/>\n</phase>\n<period value='12' unit='h'/>\n</example>\n","ISO data type PIVL has either nullFlavor, period nor frequency  and width of the phase is NOT greater than the period.","TBD",null,{"$f":"IF(H216=\"\",\"0\",IF(H216=\"Pass\",1,IF(H216=\"Fail\",0,IF(H216=\"TBD\",0,IF(H216=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D216)=48,H216=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-PIVL","END:  TS-CS  TS-PIVL (Periodic Interval)"]
["TS-SLIST","START:  TS-SLIST (LIST)"]
["TS-SLIST","TC-Types-121","7.9.6.5 Invariants [ISO21090]\n- scale shall be a difference from the origin;\n- if the SLIST is not nullFlavored, an origin and at least one digit is required.\n","C",1,"CONDITION: Data element of ISO data type SLIST is present in the clinical document.\n\nIf a nullFlavor is present, Pass the test\nElse, Fail the test if an origin element and at least on digit element are not present,\nElse, Fail the test if the value of the scale element is not a difference from the value of the origin element,\nElse, Pass the test.\n\nNOTE TO TESTER: \nFor the scale to be a difference from the origin the units for the scale must be appropriate for the origin. If the origin is a quantity then the unit for the scale must be comparable to the unit for the origin (e.g. the origin could be \"1 g\" and the scale could be \"1 mg\"). If the origin is a time stamp then the scale must have a unit of time (e.g. the origin may be \"20191129100000+1000\" and the scale could be \"10 s\").\n\n","Data elements of ISO data type SLIST have either a nullFlavor, or an origin and at least one digit, where the scale is a difference from the origin.\n","TBD",null,{"$f":"IF(H219=\"\",\"0\",IF(H219=\"Pass\",1,IF(H219=\"Fail\",0,IF(H219=\"TBD\",0,IF(H219=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D219)=48,H219=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-SLIST","END:  TS-SLIST (LIST)"]
[]
[null,null,null,null,null,null,null,"TBD","Total Tests",{"$f":"SUM(J223:J224)","v":131}]
[null,null,null,null,null,null,null,"Fail","Tests Failed or TBD",{"$f":"COUNTIF(J1:J220,\"0\")","v":131}]
[null,null,null,null,null,null,null,"N/A","Tests Passed or N/A",{"$f":"COUNTIF(J1:J220,\"1\")","v":0}]
[null,null,null,null,null,null,null,"Pass","%Passed or N/A",{"$f":"SUM(J224/J222)","v":0}]

{"sheet":"FS-Auth","index":8,"n_rows":95,"n_cols":11,"rows_kept":95,"cut":false,"hidden":false,"merged":[[9,2,10,2],[17,2,18,2],[19,2,20,2],[86,2,88,2],[0,0,0,1],[1,0,1,1],[0,2,0,5],[2,2,2,4],[2,5,3,5],[2,0,2,1],[3,0,3,1],[3,2,3,4],[1,2,1,5]]}
["Feature set identifier:",null,"FS-Auth (Authoring systems)"]
["Objective:",null,"To assess the conformance of a clinical document authoring system to the applicable requirements for the behaviour of the authoring system, where the requirements apply regardless of the type of clinical document being authored."]
["Strategy:",null,"The digital health specifications include requirements for the behaviour of an authoring system regardless of the type of document being authored. The conformance of an authoring system to these requirements is assessed by accessing the authoring system and applying the test cases defined here. Not in scope in these tests are test cases that verify the conformance of clinical documents created by the authoring system, as such test cases are included in the FS-Doc, FS-Narr and FS-Types feature sets.\n\nNote: The terms 'authoring system', 'CIS producer' and 'clinical document producers' are all used in the conformance requirements and have the same meaning. Similarly, 'CDA document' and 'clinical document' are used interchangeably.\n",null,null,"The following Test Sets have been defined.\n\nTS-Behav (Behaviour): derived from general requirements for document review and approval, packaging and signing. None of the test cases in this test set require the clinical document to be examined, except for those that apply to the clinical package.\nTS-Content (Clinical document content): derived from requirements for the alignment between information in a clinical document and the information either contained within an authoring system or entered into the authoring system, plus test cases for to assess how an authoring system includes attachments to a clinical document.\nTS-Ident (Identification, revisions & addenda): derived from requirements for identifying a clinical document as a new document, replacement document or addendum. These complement the TS-DocIdent test set in the FS-Doc feature set.\nTS-Pers (Person): derived from requirements for data components that represent people.\nTS-eComm (Electronic communication detail): derived from requirements for electronic communication details.\nTS-Addr (Address): derived from requirements for addresses.\n\n"]
["Traceability:",null,"Traceability References 1-17 (scroll down for full list)\n1. Clinical Documents - Common Conformance Profile [DH-2481:2017]\n2. CDA Rendering Specification [NEHTA-1199:2012]\n3. PCEHR Connecting Systems - Conformance Assessment Scheme [NEHTA-1294:2012]\n4. Data Types in NEHTA Specifications [NEHTA-1136:2010]\n5. PCEHR Document Exchange Service - Logical Service Specification [NEHTA-1970:2014]\n6. P2P Document Delivery - Technical Service Specification [NEHTA-1227:2012]\n7. CDA implementation guides [NEHTACDAIG]\n8. Structured content specifications [NEHTASCS]\n9. HL7 Clinical Document Architecture, Release 2 [HL7CDAR2]\n10. HL7 Version 3 Standard: Data Types - Abstract Specification, Release 1, HL7.org [HL72004]\n11. Use of HIs in Health Software Systems - Conformance Requirements v3.1 [ NEHTA-1732:2014 ]\n12. Clinical Documents - CDA Package v1.0 [NEHTA-1229:2011 ]\n13. Participation Data Specification - Data Specification v3.2 [NEHTA-0794:2011 ]\n14. PCEHR Connecting Systems - Conformance Test Specification v1.6 [NEHTA-1299:2012 ] (TC-Auth-01 Test Step and Expected results only)\n15. Clinical Documents - Conformance Test Specification for CDA Rendering v1.4 [NEHTA-2064:2016]  (TC-Auth-04, 05 & 06 - Test Step and Expected results only)\n16. Australian CDA Schema Extension 3.0 - CDA Schema v20140219 [NEHTA-1599:2014 ] TC-Auth-27 - Test Step only)\n17. PCEHR Connecting Systems - Conformance Requirements v1.5 [NEHTA-1297:2012] \n\n"]
[]
["THIS HEADER CAN BE COLLAPSED BY CLICKING THE '-' SYMBOL ON THE LEFT."]
["TEST SET ID","TEST CASE ID","CONFORMANCE REQUIREMENT","PRIORITY","STEP NO.","TEST STEP","EXPECTED RESULT","TEST RESULT","TESTER COMMENTS","CALC.","MANDATORY AND N/A"]
["TS-Behav","START:  TS-Behav (Behaviour)"]
["TS-Behav","TC-Auth-01","(This requirement applies to the My Health Record system context only)\n023873 [DH-2481:2017] \nCIS to conform to the mandatory requirements for the role of a CIS producing system\n\nIf the software producing a clinical document is a clinical information system, the software SHALL conform to the mandatory requirements for the role of a CIS producing system.\n\n(This requirement applies to the My Health Record system only)\n023874 [DH-2481:2017]\nCSP to conform to the mandatory requirements relevant for the scope of the CSP system\n\nIf the software producing a clinical document is a CSP system, the software SHALL conform to the mandatory requirements for the role of a CIS producing system that are relevant for the scope of the CSP system.\n\nNote: A CIS producer is a clinical document authoring system that creates and uploads clinical documents to the My Health Record system. The use cases that apply are described in the PCEHR Connecting Systems - Conformance Assessment Scheme [NEHTA-1294:2012].\n","C",1,"CONDITION: The Authoring System is a Clinical Information System (CIS) or a Contracted Service Provider (CSP) system and intention is to send clinical documents to the My Health Record system.\n\nExecute all the mandatory (and relevant conditional) tests from the PCEHR Connecting Systems - Conformance Test Specification [NEHTA-1299:2012], worksheets as follows:\nUC.CIS.001  Check if an advertised digital health record exists; \nUC.CIS.201  Upload a Clinical Document; \nUC.CIS.202  Supersede a clinical document; and\nUC.CIS.203  Remove a Clinical Document.\n\nMark the test N/A where the Authoring System is not a CIS or CSP, or the Authoring System is a CIS or CSP but the context is not My Health Record system (i.e. the context is P2P).  \nPass the test where the Authoring System is a CIS or CSP and the context is My Health Record system and all the mandatory (and relevant conditional) tests from: PCEHR Connecting Systems - Conformance Test Specification [NEHTA-1299:2012], worksheets:  UC.CIS.001, UC.CIS.201, UC.CIS.202, and UC.CIS.203 have passed.\nElse, Fail the test.\n","A CIS or CSP Authoring System which sends the clinical document to the My Health Record system, pass all the mandatory (and relevant conditional) tests from: PCEHR Connecting Systems - Conformance Test Specification [NEHTA-1299:2012], worksheet UC.CIS.001, UC.CIS.201, UC.CIS.202, and UC.CIS.203","TBD",null,{"$f":"IF(H9=\"\",\"0\",IF(H9=\"Pass\",1,IF(H9=\"Fail\",0,IF(H9=\"TBD\",0,IF(H9=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D9)=48,H9=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Behav","TC-Auth-02.1","023732 [DH-2481:2017]\nAuthenticate the person identified as the approver recorded in the eSignature\nIf an approver is to be recorded in the eSignature, prior to recording the approver in the eSignature, the producing system SHALL authenticate the person identified as the approver.  The approver SHALL NOT be recorded in the eSignature if they cannot be authenticated.\n\n023733 [DH-2481:2017]\nRecord approver's approval of the contents of the clinical document\nIf an approver is to be recorded in the eSignature, the producing system SHALL have previously received an indication of the approver’s approval of the contents of the clinical document. If an authenticated person has not indicated their approval of the content of the clinical document, the approver SHALL NOT be recorded in the eSignature.\n\n023730 [DH-2481:2017]\nThe value of the personId to identify a person in the eSignature\nIf an approver is to be recorded in the eSignature, the value of the personId attribute SHALL identify a person and the value SHALL consist of a domain namespace followed by an identifier that is valid for the domain namespace.\n\n\n023877 [DH-2481:2017]\nPersonId details if an identifier is used for the eSignature approver\nIf an identifier is used for the eSignature approver personId, the personId SHALL include the domain namespace of the organisation that manages the approver’s identifier, followed by the value of the identifier.\n\nNote: The following XML fragment for personId is an example when the local identifier is ‘localID’ and the organisation domain name is goodhospital.com.au:\n     <q1:personId>\n          http://goodhospital.com.au/id/cda/userid/1.0/localID\n     </q1:personId>\n","C",1,"CONDITION: The Authoring System produces CDA packages with the name and identifier of the approver in the eSignature.\n\nMark the step N/A where the Authoring System does not produce CDA packages with the name and identifier of the approver in the eSignature.\nPass the step where the Authoring System produces CDA packages with the name and identifier of the approver in the eSignature and it authenticates the approver either before, or during the review and approval of the clinical document.\nElse, Fail the step.\n\nNOTE TO TESTER: Examples of authentication methods are:\na) a desktop system where the approver logs into the operating system with an identifier and password, \nb) when approving a clinical document, a dialogue box is displayed asking the approver to enter an identifier and password. \nCDA packages sent to the My Health Record system are allowed to have one eSignature only, whereas those sent from one healthcare provider to another are allowed to have multiple eSignatures. \nAs each eSignature can only have the name of one approver, then a maximum of one approver can be recorded in a CDA package sent to the My Health Record system whereas any number of approvers may be recorded in a CDA package sent from one healthcare provider to another. \n\n","An Authoring System which produces CDA packages with the name and identifier of the approver in the eSignature, authenticates the approver either before, or during the review and approval of the clinical document.\n","TBD",null,{"$f":"IF(H10=\"\",\"0\",IF(H10=\"Pass\",1,IF(H10=\"Fail\",0,IF(H10=\"TBD\",0,IF(H10=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D10)=48,H10=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Behav",null,null,null,2,"CONDITION - The Authoring System requires the approver to indicate their approval of the clinical document.\n\nMark the step N/A where the Authoring System does not produce CDA packages with the name and identifier of the approver in the eSignature.\nPass the step where the Authoring System produces CDA packages with the name and identifier of the approver in the eSignature and  it requires them to indicate their approval.\nElse, Fail the step.\n\nNOTE TO TESTER:\nThe conformance requirement does not state anything about content of the clinical document. \nAn authoring system may render the clinical document for review and approval, or the content may be in a different format. For example:\n1. The digital health record conformance profile for Shared Health Summary specifies that the final version (i.e. the clinical document version) must be displayed for review and approval.\n2. Diagnostic Imaging Reports and Pathology Reports contain the content in a PDF file, so the authoring system may present the PDF file for review and approval.\n3. For other types of clinical documents the content may be presented for review and approval prior to transformation into a CDA format.\n","An Authoring System which produces CDA packages with the name and identifier of the approver in the eSignature, requires the approver to indicate their approval of the clinical document.","TBD",null,0,{"$f":"IF(AND(BGCol(D11)=48,H11=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Behav",null,null,null,3,"CONDITION - The approver has been authenticated and has approved the clinical document.\n\nMark the step N/A where the Authoring System does not produce CDA packages with the name and identifier of the approver in the eSignature.\nPass the step where the authoring system produces CDA packages with the name and identifier of the approver in the eSignature and it creates a CDA package which records the approver in an eSignature (i.e. the name and identifier of the person).\nElse, Fail the step.\n","An Authoring System which produces CDA packages with the name and identifier of the approver, records the approver in the eSignature (i.e. the name and identifier of the person). This is observed in the clinical document.","TBD",null,0,{"$f":"IF(AND(BGCol(D12)=48,H12=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Behav",null,null,null,4,"CONDITION - Authoring System is capable of including the approver's national healthcare identifier in the eSignature approver <personId> element.\n\nPass the step where:\na) the Authoring System is capable of including the approver's national healthcare identifier for the eSignature approver <personId> element; and\nb) the first part of the element contains the correct domain namespace for the national healthcare identifier; and\nc) the last part of the element contains the national healthcare identifier for the person that approved the clinical document.\nElse, Fail the step.\n\nNOTE TO TESTER: The domain namespace to use when the national healthcare identifier is an HPI-I is \"http://ns.electronichealth.net.au/id/hi/hpii/1.0/\", and when the national healthcare identifier is an IHI is \"http://ns.electronichealth.net.au/id/hi/ihi/1.0/\".\n","An Authoring System capable of using a national healthcare identifier for the eSignature approver <personId> element, contains the correct domain namespace (first part) and the national healthcare identifier (last part). This is observed in the clinical document.","TBD",null,0,{"$f":"IF(AND(BGCol(D13)=48,H13=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Behav",null,null,null,5,"CONDITION - Authoring System is capable of including the approver's local identifier in the eSignature approver <personId> element.\n\nPass the step where:\na) The Authoring System is capable of including the approver's local identifier for the eSignature approver <personId> element; and\nb) the first part of the element contains the domain namespace of the organisation that manages the approver's local identifier; and\nc) the last part of the element contains the local identifier for the person that approved the clinical document.\nElse, Fail the step.\n","An Authoring System capable of using a local identifier for the eSignature approver <personId> element, contains the domain namespace of the organisation that manages the approver's local identifier (first part),and the local identifier (last part). This is observed in the clinical document.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D14)=48,H14=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Behav","TC-Auth-02.2","023732 [DH-2481:2017]\nAuthenticate the person identified as the approver recorded in the eSignature\nIf an approver is to be recorded in the eSignature, prior to recording the approver in the eSignature, the producing system SHALL authenticate the person identified as the approver. The approver SHALL NOT be recorded in the eSignature if they cannot be authenticated.\n\n023731 [DH-2481:2017]\nThe value of the personId if approver is not recorded in the eSignature\nIf the approver is not recorded in the eSignature the value of personId SHALL be http://ns.electronichealth.net.au/id/null/person/1.0 and the value of familyName SHALL be NA.\n","C",1,"CONDITION: Authoring System produces CDA packages without authenticating the approver.\n\nPass the test where:\na) The Authoring System produces CDA packages without authenticating the approver; and \nb) the eSignature in the CDA package does not contain the name and identifier of the person that created the clinical document, i.e. the value of <personId> is \"http://ns.electronichealth.net.au/id/null/person/1.0\" and the value of <familyName> is be \"NA\".\nElse, Fail the test.\n","An Authoring System which produces CDA packages without authentication does not record the approver in the eSignature (i.e. the name and identifier of the person).\n\ni.e. the value of <personId> is \"http://ns.electronichealth.net.au/id/null/person/1.0\" and the value of <familyName> is be \"NA\".","TBD",null,0,{"$f":"IF(AND(BGCol(D15)=48,H15=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Behav","TC-Auth-02.3","023733 [DH-2481:2017]\nRecord approver's approval of the contents of the clinical document\nIf an authenticated person has not indicated their approval of the content of the clinical document, the approver SHALL NOT be recorded in the eSignature.\n\n023731 [DH-2481:2017]\nThe value of the personId if approver is not recorded in the eSignature\nIf the approver is not recorded in the eSignature the value of personId SHALL be http://ns.electronichealth.net.au/id/null/person/1.0 and the value of familyName SHALL be NA.\n","C",1,"CONDITION: Authoring System produces CDA packages where an authenticated person has not indicated their approval of the clinical document.\n\nPass the test where:\na)  The Authoring System produces CDA packages where an authenticated person has not indicated their approval of the clinical document; and \nb) the approver is not recorded in the eSignature (i.e. the name and identifier of the person that accessed the Authoring System to create the clinical document); i.e. the value of <personId> is \"http://ns.electronichealth.net.au/id/null/person/1.0\" and the value of <familyName> is be \"NA\".\nElse, Fail the test.\n","An Authoring System capable of producing CDA packages where an authenticated person has not indicated their approval of the clinical document does not record the approver in the eSignature (i.e. the name and identifier of the person).\n\ni.e. the value of <personId> is \"http://ns.electronichealth.net.au/id/null/person/1.0\" and the value of <familyName> is be \"NA\".","TBD",null,0,{"$f":"IF(AND(BGCol(D16)=48,H16=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Behav","TC-Auth-03","CDA-RS 3 (a) [NEHTA-1199:2012]\nAuthoring Systems SHALL implement controls and maintain records in order to provide evidence that the Author of the document is responsible for its content.\n","M",1,"Pass the test where The Authoring System:\na)  requires the Author to approve the content of the clinical document and stores/maintains a record of their approval; or\nb) is accompanied by documentation explaining that the Author of a clinical document is responsible for its content.\nElse, Fail the test.\n\nNOTE TO TESTER: Documentation may include, but is not limited to, training manuals, business process documents, requirements/system architecture or system design documents.\n","The Authoring System has Author approval of the content of the clinical document and maintains a record of the approval or is accompanied by documentation explaining that the author of a clinical document is responsible for its content.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D17)=48,H17=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Behav","TC-Auth-04","CDA-RS 2 [NEHTA-1199:2012]\nIf a CDA Implementation Guide requires a minimum version of this specification, Authoring Systems SHALL produce documents that render correctly to the Author using a Rendering System compliant with the version of this specification required in the CDA Implementation Guide.\n\nNote: The specification referred to in the requirement is the CDA Rendering Specification [NEHTA-1199:2012].\n\n","M",1,"Determine if a minimum version of the CDA Rendering Specification is required for the clinical document(s) being authored (e.g. eReferral), by checking section '1.8 Conformance' of the corresponding CDA Implementation Guide.  If no minimum version is specified, then assume the required version is 1.0.\n"]
["TS-Behav",null,null,null,2,"Pass the step where a rendering system that is compliant with the version of the CDA Rendering specification required in the CDA Implementation Guide, displays to the author and without rendering errors, clinical documents created by the authoring system.\nElse, Fail the step.\n\nNOTE TO TESTER: A conformant Rendering System is one that has been previously determined to pass the mandatory and relevant conditional test cases in the Conformance Test Specification for CDA Rendering [NEHTA-2064:2016]. \n","A clinical document produced by the Authoring System is rendered to the Author without rendering errors.","TBD",null,{"$f":"IF(H19=\"\",\"0\",IF(H19=\"Pass\",1,IF(H19=\"Fail\",0,IF(H19=\"TBD\",0,IF(H19=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D19)=48,H19=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Behav","TC-Auth-05","CDA-RS 67 [NEHTA-1199:2012]\nAuthoring Systems SHALL produce documents that render correctly to the Author when processed by a Rendering System that is compliant with the version of this specification asserted in the clinical document.\n\nNote: The specification referred to in the requirement is the CDA Rendering Specification [NEHTA-1199:2012].\n","M",1,"Determine the CDA Rendering Specification version number stated in clinical document(s) by checking the <templateId> element with a @root equal to '1.2.36.1.2001.1001.100.149'.  The value of the @extension is the version number.\nE.g.  <templateId root=\"1.2.36.1.2001.1001.100.149\" extension=\"1.0\" />.\n"]
["TS-Behav",null,null,null,2,"Pass the step where a Rendering System that is compliant with the version of the CDA specification described in the last step displays to the author and without rendering errors, clinical documents created by the authoring system.\nElse, Fail the step.\n\nNOTE TO TESTER: A conformant Rendering System is one that has been previously determined to pass the mandatory and relevant conditional test cases in Conformance Test Specification for CDA Rendering [NEHTA-2064:2016]. \n","A clinical document produced by the Authoring System is rendered to the Author without rendering errors. ","TBD",null,{"$f":"IF(H21=\"\",\"0\",IF(H21=\"Pass\",1,IF(H21=\"Fail\",0,IF(H21=\"TBD\",0,IF(H21=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D21)=48,H21=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Behav","TC-Auth-06","CDA-RS 3 (b) [NEHTA-1199:2012]\nAuthoring Systems SHOULD display a rendered view of the document using a conformant Rendering System.\n\nNote: the requirement states that it is optional for the authoring system to have a rendering capability, but if it does, then it should conform to the requirements for rendering systems. It may not be necessary for the rendering capability to conform to all requirements for rendering systems, because for authoring systems, it is only expected to be able to render the types of documents produced by the authoring system.\n","C",1,"CONDITION: Authoring System is a conformant Rendering System.\n\nPass the test where the Authoring System passes the test cases for rendering clinical documents (of the type created by the Authoring System, e.g. eReferrals only).\nElse, Fail the test.\n\nNOTE TO TESTER: The test cases are listed in the Conformance Test Specification for CDA Rendering [NEHTA-2064:2016]. There is no requirement for the Authoring System to render elements of a type that are not created by the Authoring System but it is expected that the Rendering System should have passed the CDA Rendering CTS for all types of documents that produced by the Authoring System. \n","An Authoring System with rendering capability passes the test cases for rendering clinical documents (of the type created by the Authoring System).","TBD",null,{"$f":"IF(H22=\"\",\"0\",IF(H22=\"Pass\",1,IF(H22=\"Fail\",0,IF(H22=\"TBD\",0,IF(H22=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D22)=48,H22=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Behav","END:  TS-Behav (Behaviour)"]
["TS-Content","START:  TS-Content (Clinical document content)"]
["TS-Content","TC-Auth-15","1.3.2 CDA Conformance, Originator Responsibilities [HL7CDAR2]\n\n1.3.2 CDA Conformance, Originator Responsibilities [HL7CDAR2]\nIf the CDA Body is structured, the attested narrative contents of a section must be placed in the Section.text field, regardless of whether information is also conveyed in CDA entries. Attested multimedia referenced in the narrative must be added as ObservationMedia and/or RegionOfInterest CDA entries.\n\n4.3.2 CDA Conformance, Originator Responsibilities [HL7CDAR2]\nThe narrative of each Section, together with the multimedia content referenced in the narrative, comprises the complete authenticated content of the Section..\n\nSection 4.3.5.2 [HL7CDAR2]  \nMultimedia that is integral to a document, and part of the attestable content of the document requires the use of the ObservationMedia CDA entry, which is referenced by the <renderMultiMedia> element. Multimedia that is simply referenced by the document and not an integral part of the document can use <linkHtml>.","M",1,"Pass the step where it is observed that information in the CDA narrative is a complete and accurate version of the information held in or entered into the software system and is therefore attestable content.\nElse, Pass the step where the narrative contents of a section are placed within a CDA text field within that section.\nElse, Pass the step where multimedia that is part of the attested content is added using renderMultimedia and included in the <entry> elements as either ObservationMedia and/or RegionOfInterest data element.\nElse, Pass the step where the multimedia that is not part of the attested content is added in the narrative using linkHtml and included in the <entry> elements using externalDocument, externalProcedure, externalAct or externalObservation [HL7CDAR2].\nElse, Fail the step.\n\nNOTE TO TESTER: Consider, for example, an Event Summary medications section with a narrative generated by the authoring system after the user selects a medication. It is an error if the Authoring System automatically includes the medication change type (e.g. prescribed, ceased, unchanged) without providing the user with an opportunity to review and confirm the change type (confirmation may be implied by not cancelling the Event Summary).\n\nIf the clinical information entered into a software system includes any qualifying information then the qualifying information must also be included in the clinical document. Examples of qualifiers are:\n-A medical condition’s laterality (also known as side) such as ‘left’, ‘right’ or ‘bilateral’.\n-Acuity, i.e. whether the condition is acute or chronic.\n-The severity of a medical condition\n","1. The information included in the narrative has been provided and selected by the operator of the software system or entered into the system by the operator for the purposes of including in the clinical document.\n2. The narrative contents of a section are placed within a CDA text field within that section.\n3. The multimedia that is part of the attested content is added using renderMultimedia and included in the <entry> elements as either ObservationMedia and/or RegionOfInterest data element.\n4. The multimedia that is not part of the attested content is added in the narrative using linkHtml and included in the <entry> elements using externalDocument, externalProcedure, externalAct or externalObservation [HL7CDAR2].","TBD",null,{"$f":"IF(H25=\"\",\"0\",IF(H25=\"Pass\",1,IF(H25=\"Fail\",0,IF(H25=\"TBD\",0,IF(H25=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D25)=48,H25=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Content",null,"Note: For the information to be authenticated there needs to be the person in the healthcare organisation that created the document that attests that the information is correct. That may be done when a person enters or selects information in the authoring system, or the system displays information to a person allowing them to confirm that the information is correct.  It is possible for a clinical document narrative to be automatically generated from information entered or selected by the user, for example a narrative may be generated by the authoring system after a user selects a medication and the change type \"prescribed\". Another option is for an authoring system to automatically generate clinical information, such as pathology test results, and a person attests to the correct operation of the software that generates the clinical information rather reviewing every instance of the information. \n\nThe information that needs to be authenticated is clinical information entered, selected or create by a healthcare provider and does not include administrative information such as a subject of care's contact details. In the case where an authoring system is a contracted service provider (CSP) system that simply transforms clinical information into a CDA format, authentication of the clinical information is performed by a person in the source healthcare provider organisation and not by the CSP operator.\n","C",2,"CONDITION: Authoring System generates clinical documents of the type that may contain global exclusion statements.\n\nIf the exclusion statement \"not asked\" is in the document then pass the test if the document author indicated to the authoring system that they did not ask or the patient was unable to be asked. \nElse, if the exclusion statement \"none known\" is in the document then pass the test if the document author indicated to the authoring system that no information about the item is known. \nElse, Fail the test.\n\n\nNOTE TO TESTER: \nThe global exclusion statements are specified in the CDA implementation guides and have the displayName values \"none supplied\", \"none known\" and \"not asked\". Text in the narrative may be semantically equivalent, and need not be identical, to these displayName values. Of these global exclusion statements, \"none known\" and \"not asked\" are positive assertions by the document author whereas \"none supplied\" is not a positive assertion as it simply states that information has not been provided. \n\nFor example, if the information entered into the Authoring System or displayed by the authoring system to a user included current medications then the Authoring System would fail the test if a narrative states that no current medication information is known. In this case the Authoring System would also fail the test if a narrative states that the user did not ask about current medication. However the authoring system would pass the test if a narrative states that information about current medication is not supplied.\n","A clinical document that contains global exclusion statements do not have contradictory information in the Authoring System or displayed by the authoring system to the user. This includes any multimedia referenced by <renderMultimedia> tags in the narrative.","TBD",null,{"$f":"IF(H26=\"\",\"0\",IF(H26=\"Pass\",1,IF(H26=\"Fail\",0,IF(H26=\"TBD\",0,IF(H26=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D26)=48,H26=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Content","TC-Auth-17","CDA-RS 25 [NEHTA-1199:2012]\nAuthoring Systems MAY include a GIF, JPEG or PNG organisational logo (or branding image) in the header Details display.",null,null,"No additional test case is needed."]
["TS-Content","TC-Auth-18","CDA-RS 26 (a) [NEHTA-1199:2012]\nAuthoring Systems SHALL include the organisational logo image as an attachment in accordance with the CDA Package specification.\n","C",1,"CONDITION: Authoring System includes a logo in clinical documents.\n\nPass the test where the <observationMedia> that references the logo has an XML ID attribute with the value of “LOGO”.\nElse, Fail the test.\n","An Authoring System that includes a logo in the clinical documents has associated observationMedia with an XML ID 'LOGO' value.","TBD",null,{"$f":"IF(H28=\"\",\"0\",IF(H28=\"Pass\",1,IF(H28=\"Fail\",0,IF(H28=\"TBD\",0,IF(H28=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D28)=48,H28=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Content","TC-Auth-19","CDA-RS 26 (c) [NEHTA-1199:2012]\nAuthoring Systems SHALL ensure that the organisational logo’s associated <observationMedia> entry has an XML ID attribute with an assigned value of “LOGO”.\n",null,null,"No additional test case is needed as test case TC-Doc-26 already tests CDA-RS-26 (c)."]
["TS-Content","TC-Auth-12","CDA-RS 46 [NEHTA-1199:2012]\nAuthoring Systems SHOULD represent single ordered or unordered (where the item type or grouping is implicit or not relevant) lists of data items in <list> narrative block elements.\n\nNote: The required listType attribute specifies whether the <list> is ordered or unordered (with unordered being the default).  [4.3.5.8 of the HL7 CDA R2 specification]\n","O",1,"Mark the test N/A where the Authoring System does not use lists.\nFail the test if any information either entered into the authoring system or displayed by the authoring system to a user includes ordered or unordered lists but the same information in the narrative blocks is not contained within <list> narrative block elements. \nElse, Pass the test.\n","Authoring Systems representing single ordered or unordered lists of data lists are listed in the narrative block.","TBD",null,{"$f":"IF(H30=\"\",\"0\",IF(H30=\"Pass\",1,IF(H30=\"Fail\",0,IF(H30=\"TBD\",0,IF(H30=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D30)=48,H30=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Content","TC-Auth-20","CDA-RS 52 (l) [NEHTA-1199:2012]\nAuthoring Systems MAY use the listType attribute of the <list> narrative block element to specify an ordered list.\n\nNote: The list is ordered if the <list> element has the attribute listType=”ordered”. The list is unordered if listType=”unordered” or if the listType attribute is not present.\n","C",1,"CONDITION: Authoring System has the capability of creating a clinical document containing an ordered list.\n\nPass the test if a clinical document contains an original <list> element, and:\n- the <list> element contains listType=\"ordered and an ordered list was entered into the Authoring System, or\n- the <list> element contains listType=\"unordered\".\nElse, Fail the test.\n","Authoring Systems creating a clinical document containing an ordered list has appropriate <list> element containing listType = 'ordered'  if ordered was entered into the Authoring System and is 'unordered' if not entered.","TBD",null,0,{"$f":"IF(AND(BGCol(D31)=48,H31=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Content","TC-Auth-13","CDA-RS 48 [NEHTA-1199:2012]\nAuthoring Systems SHOULD represent a collection of data items with each consisting of multiple fields in a <table> narrative block element.\n","O",1,"Mark the test N/A where the Authoring System does not use tabular type data.\nFail the test if any information either entered into the authoring system or displayed by the authoring system to a user includes a collection of data items with each consisting of multiple fields but the same information in the narrative blocks is not contained within <table> narrative block elements. \nElse, Pass the test.\n","Authoring Systems representing a collection of data items with each consisting of multiple fields is contained in a <table> narrative block element. ","TBD",null,{"$f":"IF(H32=\"\",\"0\",IF(H32=\"Pass\",1,IF(H32=\"Fail\",0,IF(H32=\"TBD\",0,IF(H32=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D32)=48,H32=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Content","TC-Auth-08","CDA-RS 53 (f) [NEHTA-1199:2012]\nAuthoring Systems SHALL NOT include references to attachments which contain executable code (e.g. JavaScript code in HTML documents).\n","C",1,"CONDITION: Authoring System has the capability of creating a clinical document containing a reference to an attachment.\n\nPass the test where the Authoring System does not have attachments which contain executable code from being referenced in the clinical document.\nElse, Fail the test.\n","The Authoring System does not allow the clinical document to reference attachments which contain executable code","TBD",null,0,{"$f":"IF(AND(BGCol(D33)=48,H33=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Content","TC-Auth-09","CDA-RS 53 (g) [NEHTA-1199:2012]\nAuthoring Systems SHALL NOT include references to attachments which require resources to be downloaded from external network locations (e.g. HTML document attachments which contain images to be loaded from external web servers).\n\nNote: This requirement may be overridden for specific types of documents. If there is an override then it will be stated in the conformance profile for the specific type of document.\n","C",1,"CONDITION: Authoring System has the capability of creating a clinical document containing a reference to an attachment.\n\nPass the test where the clinical document being authored is not one of the specific types where this requirement may be overridden and the Authoring System does not reference attachments downloaded from an external network location,\nElse, Pass the test where the clinical document being authored is one of the types where this requirement can be overridden.\nElse, Fail the test.\n\nNOTE TO TESTER: \nA URL contained in text is part of the text and is not a reference, as when the text is displayed there is no selectable link. That is, including a URL in the narrative text does not result in a document that requires resources to be downloaded.\n","The Authoring System does not allow the clinical document to reference attachments which require resources to be downloaded from an external network location unless the document is one of the specific types that can be overridden.","TBD",null,0,{"$f":"IF(AND(BGCol(D34)=48,H34=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Content","TC-Auth-21","Section 8.1 code [NEHTACDAIG]\nWhere used, the code attribute SHALL contain a code from the relevant vocabulary.\n\nWhere used, the originalText element SHALL be used to carry the full text associated with this code as selected, typed or seen by the author of this statement.\n\nAppendix A. CDA Narratives [NEHTACDAIG]\nIn accordance with the requirement to completely represent section contents, values of codedText or codeableText data elements defined in the SCS SHALL include an originalText or a displayName component (or both). \n\n [ISO 21090]:\n\n1) Definition of 'code' in section 7.5.2.4.1 \"The plain code symbol defined by the code system, or an expression in a syntax defined by the code system which describes the concept\". (Note: the concept is the information entered or selected in the user interface.)\n\n2) Definition of 'translation' in section 7.5.2.4.9 \"A set of other CDs that each represent a translation of this CD into equivalent codes within the same code system or into corresponding concepts from other code systems\".\n","C",1,"CONDITION: Authoring System uses a vocabulary to select a code corresponding to information selected, typed or seen by the user.\n\nFor a data element with a defined vocabulary, select or enter information for which there is a corresponding code.\n\nFail the test if there is no code attribute in the code element or if the value does not correspond to the information selected, typed or seen by the user.\nElse, Fail the test if an originalText element is present and the value of the originalText is not the text selected, typed or seen by the user.\nElse, Fail the test if the data element is within a <section>  and neither an originalText nor displayName are present.\nElse, Pass the test.\n\nNOTE TO TESTER: Conformance to other aspects of this requirement is assessed in the TS-Coded test set in the FS-Types feature set. The vocabulary may be one specified in the CDA implementation guide or an alternative vocabulary.\n\nA code corresponding to information entered or selected in the user interface must be recorded in the clinical document as the primary code and if there are any mappings then they must be included in a translation element\". \n","Clinical documents created through an Authoring Systems that uses a vocabulary to select a code corresponding to information provided by the user has a code element. If an originalText exists, then it corresponds to the code element. Also, if the displayName is omitted, either the originalText or displayName is present if the data element is within a <section>.","TBD",null,0,{"$f":"IF(AND(BGCol(D35)=48,H35=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Content","TC-Auth-22","Section 8.1 code [NEHTACDAIG]\nIf a vocabulary is specified in this guide and no suitable code can be found the originalText element SHALL be used to carry the full text as selected, typed or seen by the author of this statement.\n\nNote: In the code element a nullFlavor is used to indicate there is no suitable code - see Data Types in NEHTA Specifications [NEHTA-1136:2010]. If the data element's data type is CodedText then the code element must contain a nullFlavor if there is no suitable code, due to the definition \"Coded text without exceptions; text with code mappings\" whereas if the data type is CodeableText then a nullFlavor need not be present, due to the definition \"Coded text with exceptions; a flexible data type to support various ways of holding text, both free text and coded text\"  [NEHTASCS].\n","C",1,"CONDITION: Authoring System does not use a defined vocabulary for a data element of the type CodeableText.\n\nSelect or enter information for the data element:\n\nFail the test if the user of the authoring system enters or selects information and that information is not included in an originalText element,\nElse, Pass the step.\n\nNOTE TO TESTER: Information entered by the user may either be represented using a nullFlavor (e.g. <originalText nullFlavor=\"UNK\" />) or as a character string (e.g. <originalText>character_string</originalText>). \n","Clinical documents created through Authoring Systems that do not use a defined vocabulary for a data element of the type CodeableText has originalText element present with the corresponding value of the user provided information. ","TBD",null,0,{"$f":"IF(AND(BGCol(D36)=48,H36=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Content","TC-Auth-55","Section 8.1 code [NEHTACDAIG]\nWhere used, the codeSystem attribute SHALL contain the OID for the relevant vocabulary. Values for coding systems can be obtained from the HL7® OID registry accessible from the HL7® home web page at www.hl7.org.\n\n\n","C",1,"CONDITION: Authoring System uses a vocabulary to select a code corresponding to information selected, typed or seen by the user and there is codeSystem attribute in the code element. \n\nFor a data element with a defined vocabulary, select or enter information for which there is a corresponding code.\n\nFail the test if the value of the codeSystem attribute does not represent the vocabulary used by the authoring system when selecting a code or nullFlavor.\nElse, Pass the test.\n\nNOTE TO TESTER: Values for coding systems may be obtained from the HL7® OID registry accessible from the HL7® home web page at www.hl7.org, so the HL7® OID registry may be used to verify the value of the codeSystem attribute.\n\n","CodeSystem attribute represents the vocabulary used by the authoring system.","TBD",null,{"$f":"IF(H37=\"\",\"0\",IF(H37=\"Pass\",1,IF(H37=\"Fail\",0,IF(H37=\"TBD\",0,IF(H37=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D37)=48,H37=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Content","TC-Auth-23\n","Section 8.1 code [NEHTACDAIG]\nIf a vocabulary is specified in this guide and it is not possible to use this vocabulary, but an alternate vocabulary is in use, the originalText element SHALL be used to carry the full text as selected, typed or seen by the author of this statement. The code element SHALL be used to carry the relevant information from the alternate vocabulary and the alternate vocabulary shall be registered with HL7 and allocated an appropriate OID.\n\nAppendix A. CDA Narratives [NEHTACDAIG]\nIn accordance with the requirement to completely represent section contents, values of codedText or codeableText data elements defined in the SCS SHALL include an originalText or a displayName component (or both). \n",null,null,"No additional test case is needed as it is sufficient to apply test case TC-Auth-21 and test set TS-Conc in the FS-Types feature set."]
["TS-Content","TC-Auth-24\n","Section 8.1 code [NEHTACDAIG]\nIf an alternate vocabulary is in use and a translation into the specified code system is available, the originalText element SHALL be used to carry the full text as selected, typed or seen by the author of this statement. The code element SHALL be used to carry the relevant information from the alternate vocabulary and the alternate vocabulary must be registered with HL7 and allocated an appropriate OID. The translation element SHALL be used to indicate the translation code from the specified vocabulary.\n\nAppendix A. CDA Narratives [NEHTACDAIG]\nIn accordance with the requirement to completely represent section contents, values of codedText or codeableText data elements defined in the SCS SHALL include an originalText or a displayName component (or both). \n\nNote: An alternative vocabulary is a vocabulary that is used as the primary code system instead of the vocabulary stated in the clinical document specifications.\n","C",1,"CONDITION: An alternative code system is in use for the primary code system for a data element and concepts in the alternative code system are mapped to the specified code system.\n\nPass the step if an originalText element is present with a valid translation element.\nElse, Fail the step.\n\nNOTE TO TESTER: Test step applies when there is a code in the alternative code system corresponding to information entered or selected by the user and test case TC-Auth-22 applies when there is no corresponding code in the alternative code system.\n","Translation elements are present in the clinical document and originalText elements are not present when alternative code systems are used as the primary code system and specified code system is the alternative code system.","TBD",null,0,{"$f":"IF(AND(BGCol(D39)=48,H39=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Content",null,null,null,2,"CONDITION: An alternative code system is in use for the primary code system for a data element and concepts in the alternative code system are mapped to the specified code system.\n\nFor a data element with a defined vocabulary, select or enter information for which there is a corresponding code in the alternative code system and a corresponding code in the specified code system.\n\nFail the step if there is no code attribute in the code element or if the value does not correspond to the information selected, typed or seen by the user.\nElse, Fail the step if an originalText element is present in the code element and the value of the originalText is not the text selected, typed or seen by the user.\nElse, Fail the step if there is no code attribute in the translation element or if the value does not correspond to the information selected, typed or seen by the user.\nElse,  Fail the step if the data element is within a <section> and neither an originalText nor displayName are present.\nElse, Pass the step.\n\nNOTE TO TESTER: Conformance to other aspects of this requirement are assessed in the TS-Conc test set in the FS-Types feature set. \n","Code attributes in the code and translation elements have corresponding values when alternative code systems are used as the primary code system and specified code system is the alternative code system. \n\nAny originalText element present in the code element is the value of the originalText selected, typed or seen by the user. \n\nElements within a section have either originalText or displayName present.","TBD",null,0,{"$f":"IF(AND(BGCol(D40)=48,H40=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Content","TC-Auth-07\n","2.36 Point in Time (TS) [HL72004]\nDefinition of Precision: The number of significant digits of the calendar expression representation. The purpose of precision is to faithfully capture the whole information presented to humans in a calendar expression. A TS representation must not produce more or less significant digits than were originally in that value.\n\nNote: Precision is only the precision of a decimal digit representation, not the accuracy. In the structured data a point in time is recorded using the nonextended format specified by the standard for Health informatics - Harmonized data types for information interchange [ISO21090], i.e. YYYY[MM[DD[HH[MM[SS[.U[U[U[U]]]]]]]]][+|-ZZzz].\n","M",1,"Pass the test where each data element in clinical documents created by the Authoring System, providing date and time information, has the same precision (i.e. number of significant digits) that was presented to, or recorded by, the Authoring System.\nElse, Fail the test. \n\nNOTE TO TESTER: For example, if a healthcare provider enters the date and time of an event as 26 July 2015 then the data element in the clinical document must have the value \"20150726\". In contrast, it is an error for the value in the clinical document to be \"201507260000+1000\" as that means the event occurred at midnight on the 26 July 2015, which is a more precise specification of the date and time than the information entered by the healthcare provider.\n\nEvery type of clinical document contains Point in Time data elements, regardless of the conformance level. In a structured content specification the Point in Time data elements are listed with the data type DateTime or TimeInterval (the start and end of a time interval is a point in time). The HL7 Version 3 Standard: Data Types - Abstract Specification, Release 1 specification [HL72004] uses the symbol 'TS' to refer to a Point in Time data element.\n","The Point in Time information for each DateTime and TimeInterval data element in the clinical document, has the same precision (i.e. number of significant digits) that was presented to or recorded by the Authoring System. \n","TBD",null,0,{"$f":"IF(AND(BGCol(D41)=48,H41=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Content","END:  TS-Content (Clinical document content)"]
["TS-Ident","START:  TS-Ident (Identification, revisions & addenda)"]
["TS-Ident","TC-Auth-26","4.2.3.1 ParentDocument [HL7CDAR2]\nDocument Identification, Revisions, and Addenda\n\nA replacement document is a new version of the parent document. The parent document is considered superseded, but a system MAY retain it for historical or auditing purposes. The parent document being replaced is referenced via act relationship relatedDocument, where relatedDocument.typeCode is set to equal \"RPLC\" (for \"replaces\"). \n","C",1,"CONDITION: The Authoring System has the ability to supersede a clinical document.\n\nIf the ClinicalDocument/relatedDocument/parentDocument element is present in the replacement document then:\nPass the test if there is a parentDocument element with typeCode = \"RPLC\";\nElse Fail the test.\n\nNOTE TO TESTER: A related test case is included in the TS-Docident test set in the FS-Doc feature set.\n","1. The ClinicalDocument/relatedDocument/parentDocument element (if present) in the original (parent) document shall not have a typeCodeattribute whose value is \"RPLC\".\n\n2. The ClinicalDocument/relatedDocument/parentDocument element in the replacement document shall have a typeCode attribute with a value of \"RPLC\".\n","TBD",null,{"$f":"IF(H44=\"\",\"0\",IF(H44=\"Pass\",1,IF(H44=\"Fail\",0,IF(H44=\"TBD\",0,IF(H44=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D44)=48,H44=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Ident","TC-Auth-27","4.2.3.1 ParentDocument [HL7CDAR2]\nDocument Identification, Revisions, and Addenda\n\nAn addendum is a separate document that references the parent document, and MAY extend or alter the observations in the prior document. The parent document remains a current component of the patient record, and the addendum and its parent are both read by report recipients. The parent report (represented by the ParentDocument class) being appended is referenced via act relationship relatedDocument, where relatedDocument.typeCode is set to equal \"APND\" (for \"appends\").\n","C",1,"CONDITION: The Authoring System has the ability to append a clinical document then. Create a clinical document (the 'original document') and a new document (the 'addendum') to append the first document.\n\nPass the test where both parent and replacement documents are current, and:\n- the ClinicalDocument/relatedDocument/parentDocument element is present in the original document and does not have a typeCode attribute with a value of \"APND\"; and\n- the ClinicalDocument/relatedDocument/parentDocument element is present in the addendum and has a typeCode attribute with a value of \"APND\".\nElse, Fail the test.\n\nNOTE TO TESTER:  In the My Health Record system context there is a requirement that appended documents must not be uploaded to the My Health Record system - Australian CDA Schema Extension 3.0 - CDA Schema [NEHTA-1599:2014]. A related test case is included in the TS-DocIdent test set in the FS-Doc feature set.\n","Additional document is created to the original and this additional document carries the typeCode \"APND\". The new document cannot be uploaded to the My Health Record system an the original is retained in the My Health Record system. ","TBD",null,{"$f":"IF(H45=\"\",\"0\",IF(H45=\"Pass\",1,IF(H45=\"Fail\",0,IF(H45=\"TBD\",0,IF(H45=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D45)=48,H45=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Ident","END:  TS-Ident (Identification, revisions & addenda)"]
["TS-Pers","START:  TS-Pers (Person)"]
["TS-Pers","TC-Auth-28","Section 8.5 Person Name Usage [NEHTACDAIG]\nIf both Preferred Name Indicator and Person Name Usage have been provided, the use attribute SHALL include them as space separated list of codes.\n",null,null,"No additional test case is needed until HL7 have provided the preferred name indicators. A code for representing “preferred name” has been requested from HL7® International but is not currently available."]
["TS-Pers","TC-Auth-29","Section 2.27 Name Title [NEHTA-0794:2011]\nDefinition: An honorific form of address commencing a name. \nData Type: CodedText\nValue Domain: AS 5017 (2006) - Healthcare Client Identification: Name Title; AS 4846 (2006) - Healthcare Provider Identification: Name Title\n\nThe order is significant and SHALL always be maintained. Name title SHOULD NOT be confused with job title. Mixed case SHOULD be used (rather than upper case only). Multiple Name Titles MAY be recorded. Title of ‘Master’ SHOULD only be used for clients less than 15 years of age. Title of ‘Doctor’ and ‘Professor’ SHOULD only be applicable to clients of greater than 20 years of age.\n","C",1,"CONDITION: Authoring System records multiple name titles for a person in a clinical document.\n\nPass the step if the name titles in a clinical document are in the same order as the name titles recorded in the Authoring System.\nElse, Fail the step.\n","Clinical document created by an Authoring System which include multiple name titles for a person have name titles in the clinical document as recorded in the Authoring System.","TBD",null,{"$f":"IF(H49=\"\",\"0\",IF(H49=\"Pass\",1,IF(H49=\"Fail\",0,IF(H49=\"TBD\",0,IF(H49=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D49)=48,H49=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers","TC-Auth-30\n\n","Section 2.29 Family Name [NEHTA-0794:2011]\nDefinition: That part of a name a person usually has in common with some other members of his/her family, as distinguished from his/her given names. \n\nIf this data element is not supplied, a null flavour SHALL be available, and the recipient will not be able to identify the participant through the national Healthcare Identifiers Service (HI Service).\n\nNote: When a person has a single name only then that name is used as the family name when searching the HI Service (see requirement 008526 of Use of HIs in Health Software Systems - Conformance Requirements [NEHTA-1732:2014]).\n\nAn example of when a clinical document may be uploaded to the My Health Record system for a person whose family name is not known is when a digital health record has been created for a newborn that does not yet have a name. They must have a temporary name for an IHI to have been created but as the temporary name is neither a given name nor a family name then it need not be included in a clinical document. \n","M",1,"When the Authoring System has a record of a person's family name then:\n\nPass the step when the person's family name is the value of the family element within the higher level name element. i.e.<name><family>.\nElse, Pass the step when the clinical document contains a nullFlavor with an appropriate value instead of the family name.\nElse, Fail the step.\n\nNOTE TO TESTER: If the person's family name is recorded in the authoring  system then appropriate values for a nullFlavor are \"NI\" (no information is provided) and \"MSK\" (information is known but is masked). \n","Clinical document created by an Authoring System with a record of a person's family name has family name attributes or nullFlavor of the appropriate value.","TBD",null,0,{"$f":"IF(AND(BGCol(D50)=48,H50=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers",null,null,null,2,"When Authoring System has a record of a person's name and they have a single name only then:\n\nPass the step when the person's family name is the value of the single name attribute.\nElse, Pass the step when the clinical document contains a nullFlavor with an appropriate value instead of the family name.\nElse, Fail the step.\n\nNOTE TO TESTER: If the person's name recorded in the authoring system then appropriate values for a nullFlavor are \"NI\" (no information is provided) and \"MSK\" (information is known but is masked). \n","Clinical document created by an Authoring System with a record of a person's family name has name attribute or nullFlavor of the appropriate value.","TBD",null,0,{"$f":"IF(AND(BGCol(D51)=48,H51=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers",null,null,"C",3,"CONDITION: Authoring System is capable of creating a clinical document for a newborn with only a temporary name.\n\nWhen the Authoring System has no record of a person's family name then:\n\nPass the step when the person's temporary name is the value of the family name attribute.\nElse, Pass the step when the clinical document contains a nullFlavor with an appropriate value instead of the family name attribute.\nElse , Fail the step.\n\nNOTE TO TESTER: For a person with a temporary name only then appropriate values for a nullFlavor are \"NI\" (no information is provided) and \"UNK\" (unknown).\n","Clinical document created by an Authoring System with no record of a person's name has temporary name attribute or nullFlavor of the appropriate value.","TBD",null,0,{"$f":"IF(AND(BGCol(D52)=48,H52=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers","TC-Auth-31\n\n","Section 2.30 Given Name [NEHTA-0794:2011]\nDefinition: The person’s identifying names within the family group or by which the person is uniquely socially identified. \n\nAll given names SHOULD be recorded in the correct sequence. Initials MAY be recorded in lieu of name.\n","M",1,"Pass the step if the information in the Authoring System includes one or more given names for a person and: \n- the corresponding names are included in the name/given data elements in the clinical document; and\n- there is a separate given name in the clinical document for each given name in the authoring system.\nElse, Pass the step if the Authoring System has a person's initials instead of given names and the initials are recorded in separate given and name elements in the clinical document.\nElse, Pass the step if the Authoring System has no information about a person's given names and the clinical document does not contain any given and name values for the person.\nElse, Fail the step.\n\nNOTE TO TESTER:\nThe person's given name is the value of the given element within the higher level name element. i.e.<name><given>.\n","Information in the Authoring System that contains one or more names for a person have corresponding names included in separate given name elements. This also applies to initials.\n\nIf there is no name information available then the clinical document will not contain any given name information.   ","TBD",null,0,{"$f":"IF(AND(BGCol(D53)=48,H53=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers",null,null,"O",2,"Pass the step when the givenName values in the clinical document are in the same order as the given names (or initials) in the Authoring System,\nElse, Fail the step.\n","given name values in the clinical document are in the same order as the given names (or initials) provided by the Authoring System","TBD",null,0,{"$f":"IF(AND(BGCol(D54)=48,H54=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers","TC-Auth-32\n\n","Section 2.31 Name Suffix [NEHTA-0794:2011]\nDefinition: The additional term used following a person's name to identify that person. \nData Type: CodedText\nValue Domain: AS 5017 (2006) - Healthcare Client Identification: Name Suffix; AS 4846 (2006) -Healthcare Provider Identification: Name Suffix\n\nThe order is significant and SHALL always be maintained.\n","C",1,"CONDITION:  Authoring System records multiple name suffixes for a person in a clinical document.\n\nPass the step if the name suffixes in a clinical document are in the same order as the name suffixes recorded in the Authoring System, \nElse, Fail the step.\n","Multiple suffix values in the clinical document are in the same order as recorded in the Authoring System","TBD",null,0,{"$f":"IF(AND(BGCol(D55)=48,H55=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers","TC-Auth-33\n\n","Section 2.32 Name Suffix Values [NEHTA-0794:2011]\nDefinition: The set of values for the additional terms that may be used following a person's name to identify that person. \n\nMultiple Name Suffixes MAY be recorded. Mixed case SHOULD be used (rather than upper case only).\n","O",1,"CONDITION: Authoring System is capable of creating clinical documents that include the optional name suffix value data element.\n\nPass the test if the information in the Authoring System includes one or more name suffixes for a person and the corresponding name suffix values are included in the clinical document and have the case recorded in the Authoring system,\nElse, Fail the test.\n","Any suffix values are included in the clinical document when recorded in the Authoring System. ","TBD",null,0,{"$f":"IF(AND(BGCol(D56)=48,H56=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers","TC-Auth-34\n\n","Section 2.34 Person Name Usage [NEHTA-0794:2011]\nDefinition: The classification that enables differentiation between recorded names for a person.\nData Type: CodedText\n","C",1,"CONDITION: Authoring System is capable of creating clinical documents that include the optional person name usage data element.\n\nPass the test if the information in the Authoring System includes the person name usage and the corresponding person name usage value is included in the clinical document.\nElse, Pass the test if the Authoring System has no information about person name usage and the person name usage data element is not included in the clinical document.\nElse, Fail the test.\n\nNOTE TO TESTER: The permissible values are stated in section 10.2 of the CDA implementation guides, and are \"L\" (Legal Name or Registered Name), \"C\" (License Name or Reporting Name), \"NB\" (Newborn Name), \"A\" (Artist/Stage Name or Professional or Business Name), \"M\" (Maiden Name or Name at birth) and \"P\" (Pseudonym or Other Name).\n","Name usage is included in the clinical document when recorded in the Authoring System. If no information is recorded then there is no name usage element in the clinical document.","TBD",null,0,{"$f":"IF(AND(BGCol(D57)=48,H57=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers","TC-Auth-35\n","Section 2.45 Sex [NEHTA-0794:2011]\nDefinition: The biological distinction between male and female. \nData Type: CodedText\n\nIf this data element is not supplied, a null flavour SHALL be available, and the recipient will not be able to identify the participant through the national Healthcare Identifiers Service (HI Service).\n\nNote: Values correspond with permissible values in section 10.2 of [NEHTACDAIG]: \n1 = \"M\" (Male), \n2 = \"F\" (Female),\n3 =  \"I\" (Intersex or Indeterminate) and,\n4 =  \"N\" (Not Stated/Inadequately Described)\n","M",1,"Pass the test if the information in the authoring system includes a person's sex and the clinical document contains either the corresponding value for the person's sex or an appropriate nullFlavor.\nElse, Pass the test if the authoring system has no information about a person's sex and an appropriate nullFlavor is included the clinical document.\nElse, Fail the test.\n\nNOTE TO TESTER: If the person's sex is known then appropriate values for a nullFlavor are \"NI\" (no information is provided) and \"MSK\" (information is known but is masked). If the person's sex is not known then then appropriate values for a nullFlavor are \"NI\" (no information is provided), \"UNK\" (unknown), \"ASKU\" (asked but unknown), \"NASK\" (not asked) and \"NAV\" (the information is temporarily unavailable). The values \"ASKU\" and \"NASK\" are appropriate only if the authoring system allows the user to record if they have asked or not asked.\n","Sex information in the clinical document corresponds with the information included in the Authoring System. If no information was available then appropriate nullflavor is included in the clinical document.","TBD",null,0,{"$f":"IF(AND(BGCol(D58)=48,H58=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers","TC-Auth-36\n\n","Section 2.47 Date of Birth Detail [NEHTA-0794:2011]\nDefinition: Details of the accuracy, origin and value of a person's date of birth. \n\nIf this data group is not supplied, a null flavour SHALL be available, and the recipient will not be able to identify the participant through the national Healthcare Identifiers Service (HI Service).\n",null,null,"No additional test case is needed as this logical data component has no mapping to CDA."]
["TS-Pers","TC-Auth-37\n","Section 2.48 Date of Birth [NEHTA-0794:2011]\nDefinition: The date of birth of the person. \n\nIf this data element is not supplied, a null flavour SHALL be available, and the recipient will not be able to identify the participant through the national Healthcare Identifiers Service (HI Service).\n\nNote: Where the Date of Birth is not known an estimated date is permitted.\n","M",1,"When the Authoring System has a record of a person's date of birth or if the authoring system calculates the date of birth from a person's age then:\nPass the test if a clinical document created by the authoring system contains the date of birth or if it contains a nullFlavor with an appropriate value instead of the date of birth; or\nIf the Authoring System has no record of a person's date of birth and does not calculate it from their age, the clinical document contains a nullFlavor with an appropriate value instead of the date of birth and the Calculated From Age data element is omitted.\nElse, Fail the test.\n\nNOTE TO TESTER: If the Authoring System has a record of a person's date of birth or if the authoring system calculates the date of birth from a person's age then appropriate values for a nullFlavor are \"NI\" (no information is provided) and \"MSK\" (masked for security, privacy or other reasons), otherwise appropriate values for a nullFlavor are \"NI\" (no information is provided), \"UNK\" (unknown), \"ASKU\" (asked but unknown), \"NASK\" (not asked), \"NAV\" (the information is temporarily unavailable) and \"MSK\" (masked for security, privacy or other reasons). The values \"ASKU\" and \"NASK\" are appropriate only if the Authoring System allows the user to record if they have asked or not asked.\n","The date of birth is provided in the clinical document. Where no date of birth is provided, the clinical document date of birth is calculated from the age information calculated in the Authoring System. If no age is available then appropriate  nullflavor is included in the clinical document and Age data element is omitted.","TBD",null,{"$f":"IF(H60=\"\",\"0\",IF(H60=\"Pass\",1,IF(H60=\"Fail\",0,IF(H60=\"TBD\",0,IF(H60=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D60)=48,H60=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers","TC-Auth-38\n\n","Section 2.49 Date of Birth is Calculated From Age [NEHTA-0794:2011]\nDefinition: Indicates whether or not a person's date of birth has been derived from the value in the Age data element. \n\nWhere the date of birth is derived from the age:\n1. only the year SHOULD be supplied;\n2. the date accuracy indicator for the year SHOULD be the same as the Age Accuracy Indicator; and\n3. the date accuracy indicators for the month and day SHOULD be “false”.\n","M",1,"Pass the step if the Authoring System has a record of the person's date of birth and the Date of Birth is Calculated From Age data element in the clinical document is omitted or has the value \"false\".\nElse, Pass the step if the Authoring System calculated the date of birth from the person's age and the Date of Birth is Calculated From Age data element in the clinical document has the value \"true\".\nElse, Pass the step if the Calculated From Age data element is omitted or has the value \"false\" (i.e. the clinical document contains a nullFlavor instead of a date of birth).\nElse, Fail the step.\n","The date of birth is provided in the clinical document,  derived from the age element, the person's age (or a person's age of nullFlavor) in the Authoring System. \n\n","TBD",null,0,{"$f":"IF(AND(BGCol(D61)=48,H61=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers","TC-Auth-39\n","Section 2.50 Date of Birth Accuracy Indicator [NEHTA-0794:2011]\nDefinition: The level of certainty or estimation of a person's date of birth. \n\nIf no value is supplied, a null flavour SHALL be available, and the accuracy is unknown.\n","C",1,"CONDITION: Authoring System creates clinical documents that include the Date of Birth Accuracy Indicator & the Date of Birth Accuracy Indicator data element in a clinical document has a nullFlavor.\n\nPass the step if an appropriate value has been used for the nullFlavor.\nElse, Fail the step.\n\n\nNOTE TO TESTER: Appropriate values for a nullFlavor are \"NI\" (no information is provided), \"UNK\" (unknown), \"ASKU\" (asked but unknown), \"NASK\" (not asked), \"NAV\" (the information is temporarily unavailable) and \"MSK\" (masked for security, privacy or other reasons). The values \"ASKU\" and \"NASK\" are appropriate only if the authoring system allows the user to record if they have asked or not asked.\n","Clinical document has Date of Birth Accuracy indicator data element with appropriate nullFlavor when Authoring Systems included a Date of Birth Accuracy Indicator with no value.  ","TBD",null,0,{"$f":"IF(AND(BGCol(D62)=48,H62=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers",null,null,null,2,"CONDITION: Authoring system creates clinical documents that include the Date of Birth Accuracy Indicator & a clinical document has the value \"A\", \"E\" or \"U\" for the Date of Birth Day Accuracy.\n\n- The clinical document has the value \"A\" for the Date of Birth Day Accuracy Indicator:\nPass the step if the clinical document contains a date of birth day and if the date of birth entered into the Authoring System includes the day and with either an indication that the day is accurately known or an absence or an indication that the day is estimated.\nElse, Fail the step.\n\n- The clinical document has the value \"E\" for the Date of Birth Day Accuracy Indicator:\nPass the step if the clinical document contains a date of birth day and if either the date of birth entered into the Authoring System included an indication that the day is estimated or if the authoring system calculated the day from other information (e.g. the age).\nElse, Fail the step.\n\n- The clinical document has the value \"U\" for the Date of Birth Day Accuracy Indicator:\nPass the step if the date of birth entered into the Authoring System included an indication that the accuracy of the day is unknown.\nElse, Pass the step if no date of birth was included in the clinical document or if the date of birth included in the clinical document did not contain a day.\nElse, Fail the step.\n","The date of birth entered into the Authoring System including the day and with either an indication that the day is accurately known or an absence or an indication that the day is estimated has clinical document Date of Birth Day Accuracy Indicator \"A\" and contains a date of birth day. \n\nThe date of birth entered into the Authoring System including the day and with either an indication that the day is estimated or calculated from other information has clinical document Date of Birth Day Accuracy Indicator \"E\" and contains a date of birth day. \n\nThe date of birth entered into the Authoring System including the day and with an indication that the day is unknown has clinical document Date of Birth Day Accuracy Indicator \"U\" and does not contain date of birth day. \n","TBD",null,0,{"$f":"IF(AND(BGCol(D63)=48,H63=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers",null,null,null,3,"CONDITION: Authoring System creates clinical documents that include the Date of Birth Accuracy Indicator & a clinical document has the value \"A\", \"E\" or \"U for the Date of Birth Month Accuracy Indicator.\n\n- The clinical document has the value \"A\" for the Date of Birth Month Accuracy Indicator:\nPass the step if the clinical document contains a date of birth month and if the date of birth entered into the Authoring System includes the month and with either an indication that the month is accurately known or an absence of an indication that the month is estimated,\nElse, Fail the step.\n\n- The clinical document has the value \"E\" for the Date of Birth Month Accuracy Indicator:\nPass the step if the clinical document contains a date of birth month and if either the date of birth entered into the Authoring System included an indication that the month is estimated of if the Authoring System calculated the month from other information (e.g. the age),\nElse, Fail the step.\n\n- The clinical document has the value \"U\" for the Date of Birth Month Accuracy Indicator:\nPass the step if the date of birth entered into the Authoring System included an indication that the accuracy of the month is unknown,\nElse, Pass the step if no date of birth was included in the clinical document or if the date of birth included in the clinical document did not contain a month,\nElse, Fail the step.\n","The date of birth entered into the Authoring System including the month and with either an indication that the month is accurately known or an absence or an indication that the month is estimated has clinical document Date of Birth Month Accuracy Indicator \"A\" and contains a date of birth month. \n\nThe date of birth entered into the Authoring System including the month and with either an indication that the month is estimated or calculated from other information has clinical document Date of Birth Month Accuracy Indicator \"E\" and contains a date of birth month. \n\nThe date of birth entered into the Authoring System including the month and with an indication that the month is unknown has clinical document Date of Birth Month Accuracy Indicator \"U\" and does not contain date of birth month. \n","TBD",null,0,{"$f":"IF(AND(BGCol(D64)=48,H64=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers",null,null,null,4,"CONDITION: Authoring System creates clinical documents that include the Date of Birth Accuracy Indicator & a clinical document has the value \"A\", \"E\" or \"U\" for the Date of Birth Year Accuracy Indicator.\n\n- The clinical document has the value \"A\" for the Date of Birth Year Accuracy Indicator:\nPass the if the date of birth entered into the Authoring System includes the year and with either an indication that the year is accurately know or an absence of an indication that the year is estimated.\nElse, Fail the step.\n\n- The clinical document has the value \"E\" for the Date of Birth Year Accuracy Indicator:\nPass the step if either the date of birth entered into the Authoring System included an indication that the year is estimated of if the Authoring System calculated the year from other information (e.g. the age).\nElse, Fail the step.\n\n- The clinical document has the value \"U\" for the Date of Birth Year Accuracy Indicator:\nPass the step if the date of birth entered into the Authoring System included an indication that the accuracy of the year is unknown.\nElse, Pass the step if no date of birth was included in the clinical document.\nElse, Fail the step.\n\nNOTE TO TESTER: If a date of birth is included in the clinical document then it is mandatory to include a year whereas month and day are optional.\n","The date of birth entered into the Authoring System including the year and with either an indication that the year is accurately known or an absence or an indication that the year is estimated has clinical document Date of Birth Year Accuracy Indicator \"A\" and contains a date of birth year. \n\nThe date of birth entered into the Authoring System including the year and with either an indication that the year is estimated or calculated from other information has clinical document Date of Birth Year Accuracy Indicator \"E\" and contains a date of birth year. \n\nThe date of birth entered into the Authoring System including the year and with an indication that the year is unknown has clinical document Date of Birth Year Accuracy Indicator \"U\" and does not contain date of birth year. \n","TBD",null,0,{"$f":"IF(AND(BGCol(D65)=48,H65=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers","TC-Auth-40","Section 2.54 Age Detail [NEHTA-0794:2011]\nDefinition: Details of the accuracy and value of a person's age. \n\nIf age details are provided then date of birth details SHALL either be provided, or the date of birth details SHALL be calculated and indicated.\n",null,null,"No additional test case is needed as this logical data component has no mapping to CDA."]
["TS-Pers","TC-Auth-41","Section 2.56 Age Accuracy Indicator [NEHTA-0794:2011]\nDefinition: The accuracy of a person's age. \n\nA true or positive value indicates that the information supplied is accurate. A false or negative value indicates that the information supplied is not accurate or has been estimated. If no value is supplied, a null flavour SHALL be available, and the accuracy is unknown.\n","C",1,"CONDITION: Authoring System creates clinical documents that include the Age Accuracy Indicator.\n\nPass the test if the Age Accuracy Indicator in a clinical document created by the authoring system has a value that reflects the accuracy of the record in the Authoring System.\nElse, Pass the test if the Age Accuracy Indicator has a nullFlavor with an appropriate value.\nElse, Fail the test.\n\nNOTE TO TESTER: If the Authoring System has a record of a person's age then appropriate values for a nullFlavor are \"NI\" (no information is provided) and \"MSK\" (masked for security, privacy or other reasons), otherwise appropriate values for a nullFlavor are \"NI\" (no information is provided), \"UNK\" (unknown), \"ASKU\" (asked but unknown), \"NASK\" (not asked), \"NAV\" (the information is temporarily unavailable) and \"MSK\" (masked for security, privacy or other reasons). The values \"ASKU\" and \"NASK\" are appropriate only if the authoring system allows the user to record if they have asked or not asked.\n","Clinical documents created from Authoring systems which included an Age Accuracy Indicator have that Age Accuracy Indicator value or appropriate nullFlavor.","TBD",null,{"$f":"IF(H67=\"\",\"0\",IF(H67=\"Pass\",1,IF(H67=\"Fail\",0,IF(H67=\"TBD\",0,IF(H67=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D67)=48,H67=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers","TC-Auth-42","Section 2.61 Date of Death Accuracy Indicator [NEHTA-0794:2011]\nDefinition: The level of certainty or estimation of a person's date of death. \n\nA true or positive value indicates that the information supplied is accurate. A false or negative value indicates that the information supplied is not accurate or has been estimated. If no value is supplied, a null flavour SHALL be available, and the accuracy is unknown.\n","C",1,"CONDITION: Authoring System creates clinical documents that include the Date of Death Accuracy Indicator & Date of Death Accuracy Indicator data element in a clinical document has a nullFlavor.\n\nPass the step if an appropriate value has been used for the nullFlavor.\nElse, Fail the step.\n\n\nNOTE TO TESTER: Appropriate values for a nullFlavor are \"NI\" (no information is provided), \"UNK\" (unknown), \"ASKU\" (asked but unknown), \"NASK\" (not asked), \"NAV\" (the information is temporarily unavailable) and \"MSK\" (masked for security, privacy or other reasons). The values \"ASKU\" and \"NASK\" are appropriate only if the authoring system allows the user to record if they have asked or not asked.\n","Clinical documents created from Authoring Systems which included a Date of Death Indicator have Date of Death Indicator or appropriate nullFlavor when applicable.  ","TBD",null,0,{"$f":"IF(AND(BGCol(D68)=48,H68=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers",null,null,null,2,"CONDITION: Authoring System creates clinical documents that include the Date of Death Accuracy Indicator & clinical document has the value \"A\", \"E\", or \"U\" for the Date of Death Day Accuracy Indicator.\n\n- The clinical document has the value \"A\" for the Date of Death Day Accuracy Indicator:\nPass the step if the clinical document contains a date of death day and if the date of death entered into the Authoring System includes the day and with either an indication that the day is accurately know or an absence of an indication that the day is estimated.\nElse, Fail the step.\n\n- The clinical document has the value \"E\" for the Date of Death Day Accuracy Indicator:\nPass the step if the clinical document contains a date of death day and if either the date of death entered into the Authoring System included an indication that the day is estimated of if the Authoring System calculated the day from other information (e.g. the age).\nElse, Fail the step.\n\n- The clinical document has the value \"U\" for the Date of Death Day Accuracy Indicator:\nPass the step if the date of death entered into the Authoring System included an indication that the accuracy of the day is unknown.\nElse, Pass the step if no date of death was included in the clinical document or if the date of death included in the clinical document did not contain a day.\nElse, Fail the step.\n","The date of death entered into the Authoring System including the day and with either an indication that the day is accurately known or an absence or an indication that the day is estimated has clinical document Date of DeathDay Accuracy Indicator \"A\" and contains a date of death day. \n\nThe date of death entered into the Authoring System including the day and with either an indication that the day is estimated or calculated from other information has clinical document Date of Death Day Accuracy Indicator \"E\" and contains a date of death day. \n\nThe date of death entered into the Authoring System including the day and with an indication that the day is unknown has clinical document Date of Death Day Accuracy Indicator \"U\" and does not contain date of death day. \n","TBD",null,0,{"$f":"IF(AND(BGCol(D69)=48,H69=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers",null,null,null,3,"CONDITION: Authoring System creates clinical documents that include the Date of Death Accuracy Indicator & clinical document has the value \"A\", \"E\", or \"U\" for the Date of Death Month Accuracy Indicator.\n\n- The clinical document has the value \"A\" for the Date of Death Month Accuracy Indicator:\nPass the step if the clinical document contains a date of death month and if the date of death entered into the Authoring System includes the month and with either an indication that the month is accurately know or an absence of an indication that the month is estimated.\nElse, Fail the step.\n\n- The clinical document has the value \"E\" for the Date of Death Month Accuracy Indicator:\na. Pass the step if the clinical document contains a date of death month and if either the date of death entered into the Authoring System included an indication that the month is estimated of if the Authoring System calculated the month from other information (e.g. the age).\nElse, Fail the step.\n\n- The clinical document has the value \"U\" for the Date of Death Month Accuracy Indicator:\nPass the step if the date of death entered into the Authoring System included an indication that the accuracy of the month is unknown.\nElse, Pass the step if no date of death was included in the clinical document or if the date of death included in the clinical document did not contain a month.\nElse, Fail the step.\n","The date of death entered into the Authoring System including the month and with either an indication that the month is accurately known or an absence or an indication that the month is estimated has clinical document Date of Death Month Accuracy Indicator \"A\" and contains a date of death month. \n\nThe date of death entered into the Authoring System including the month and with either an indication that the month is estimated or calculated from other information has clinical document Date of Death Month Accuracy Indicator \"E\" and contains a date of death month. \n\nThe date of death entered into the Authoring System including the month and with an indication that the month is unknown has clinical document Date of Death Month Accuracy Indicator \"U\" and does not contain date of death month. \n","TBD",null,0,{"$f":"IF(AND(BGCol(D70)=48,H70=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers",null,null,null,4,"CONDITION: Authoring System creates clinical documents that include the Date of Death Accuracy Indicator & clinical document has the value \"A\", \"E\", or \"U\" for the Date of Death Year Accuracy Indicator.\n\n- The clinical document has the value \"A\" for the Date of Death Year Accuracy Indicator:\nPass the if the date of death entered into the Authoring System includes the year and with either an indication that the year is accurately know or an absence of an indication that the year is estimated.\nElse, Fail the step.\n\n- The clinical document has the value \"E\" for the Date of Death Year Accuracy Indicator:\na. Pass the step if either the date of death entered into the Authoring System included an indication that the year is estimated of if the Authoring System calculated the year from other information (e.g. the age).\nElse, Fail the step.\n\n- The clinical document has the value \"U\" for the Date of Death Year Accuracy Indicator:\nPass the step if the date of death entered into the Authoring System included an indication that the accuracy of the year is unknown.\nElse, Pass the step if no date of death was included in the clinical document.\nElse, Fail the step.\n\nNOTE TO TESTER: If a date of death is included in the clinical document then it is mandatory to include a year whereas month and day are optional.\n","The date of death entered into the Authoring System including the year and with either an indication that the year is accurately known or an absence or an indication that the year is estimated has clinical document Date of Death Year Accuracy Indicator \"A\" and contains a date of death year. \n\nThe date of death entered into the Authoring System including the year and with either an indication that the year is estimated or calculated from other information has clinical document Date of Death Year Accuracy Indicator \"E\" and contains a date of death year. \n\nThe date of death entered into the Authoring System including the year and with an indication that the year is unknown has clinical document Date of death Year Accuracy Indicator \"U\" and does not contain date of death year. \n","TBD",null,0,{"$f":"IF(AND(BGCol(D71)=48,H71=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers","TC-Auth-43","Section 2.65 Source of Death Notification [NEHTA-0794:2011]\nDefinition: The person, location, organisation or other originator of information relating to the date of death.\nData Type: CodedText\n","C",1,"CONDITION: Authoring system is capable of creating clinical documents that include the Source of Death Notification.\n\nThe authoring system has a record of a person's source of death notification:\nPass the test if the Source of Death Notification in a clinical document created by the authoring system is one of the permissible values and reflects the record in the authoring system. \nElse, Fail the test.\n\nThe authoring system has no record of a person's source of death notification:\nPass the test if the Source of Death Notification in a clinical document created by the authoring system has a code attribute with the value \"U\".\nElse, Fail the test.\n\nNOTE TO TESTER: The permissible values are stated in section 10.5 of the CDA implementation guides and are \"D\" (Official death certificate or death register), \"H\" (Health Care Provider), \"R\" (Relative), \"O\" (Other) and \"U\" (Unknown). When comparing values for the Source of Death Notification the case is insensitive.\n","Source of Death Notification in the clinical document reflects a permissible value in the Authoring System.","TBD",null,0,{"$f":"IF(AND(BGCol(D72)=48,H72=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers","TC-Auth-44","Section 2.70 State/Territory of Birth [NEHTA-0794:2011]\nDefinition: The identifier of the Australian state or territory where a person is born.\nData Type: CodedText\n","C",1,"CONDITION: Authoring system is capable of creating clinical documents that include the State/Territory of Birth.\n\nThe Authoring System has a record of a person's Australian state or territory of birth:\nPass the test if the State/Territory of Birth in a clinical document created by the Authoring System is either omitted or is one of the permissible values and reflects the record in the Authoring System.\nElse, Fail the test.\n\nThe Authoring System has a record of a person's overseas location of birth:\nPass the test if the State/Territory of Birth in a clinical document created by the Authoring System is omitted.\nElse, Fail the test.\n\nThe Authoring System has no record of a person's Australian state or territory of birth):\nPass the test if the State/Territory of Birth in a clinical document created by the Authoring System is either omitted or has code attribute with the value \"U\".\nElse, Fail the test.\n\n\nNOTE TO TESTER: The permissible values are stated in section 10.10 of the CDA implementation guides, and are \"NSW\" (New South Wales), \"VIC\" (Victoria), \"QLD\" (Queensland), \"SA\" (South Australia), \"WA\" (Western Australia), \"TAS\" (Tasmania), \"NT\" (Northern Territory), \"ACT\" (Australian Capital Territory) and \"U\" (Unknown).\n","State/Territory of Birth in the clinical document reflects permissible values in the Authoring System or is omitted if Authoring System has a record of overseas location of birth. ","TBD",null,0,{"$f":"IF(AND(BGCol(D73)=48,H73=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers","TC-Auth-45","Section 2.72 Indigenous Status [NEHTA-0794:2011]\nDefinition: Indigenous Status is a measure of whether a person identifies as being of Aboriginal or Torres Strait Islander origin.\nData Type: CodedText\n","M",1,"Pass the test if the Indigenous Status in a clinical document created by the authoring system has one of the permissible values and reflects the record in the authoring system.\nElse, Pass the test if the Indigenous Status in a clinical document created by the authoring system that had no record of a person's indigenous status, has the value \"9\".\nElse, Fail the test.\n\nNOTE TO TESTER: The permissible values are \"1\" (Aboriginal but not Torres Strait Islander origin), \"2\" (Torres Strait Islander but not Aboriginal origin), \"3\" (Both Aboriginal and Torres Strait Islander origin), \"4\" (Neither Aboriginal nor Torres Strait Islander origin) and \"9\" (Not stated/inadequately described).\n","Indigenous status in the clinical document reflects a permissible value in the Authoring System. If no record is available then the clinical document has a value '9.","TBD",null,0,{"$f":"IF(AND(BGCol(D74)=48,H74=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers","TC-Auth-46","Section 2.3 Role [NEHTA-0794:2011]\nDefinition: The involvement or role of the participant in the related action from a healthcare perspective rather than the specific participation perspective.\nDataType: CodeableText\n\nNote: A participant may be a person, organisation or device. The Australian and New Zealand Standard Classification of Occupations (ANZSCO) code system [ABS2009] may be used when a participant is a person and when a participant is an organisation the Australian and New Zealand Standard Industrial Classification (ANZSIC) [ABS2013] or the HL7 Service Delivery Location Role Type [HL72014] code systems may be used. \n","C",1,"CONDITION: Authoring System includes a code for a participant's role.\n\nPass the test if the code is for a role that is appropriate for the participant.\nElse, Fail the test.\n\nNOTE TO TESTER: ANZSCO documentation describes how to select a six digit code for an occupation group [ABS2009]. This is comprised of a four digit group code, together with a two digit occupation specification. An ANZSCO code ending in '99' is an assertion that the occupation is known but is not one of the ANZSCO occupation specifications. \n","Clinical documents created from Authoring Systems which included a participant's role have appropriate role code associated to type of participant.","TBD",null,{"$f":"IF(H75=\"\",\"0\",IF(H75=\"Pass\",1,IF(H75=\"Fail\",0,IF(H75=\"TBD\",0,IF(H75=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D75)=48,H75=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers","TC-Auth-47","Section 2.40 Occupation [NEHTA-0794:2011]\nDefinition: A descriptor of the class of job based on similarities in the tasks undertaken.\nDataType: CodeableText\nValue Domain: 1220.0 - ANZSCO - Australian and New Zealand Standard Classification of Occupations\n","C",1,"CONDITION: Authoring System includes a code for a person's occupation.\n\nPass the test if the code is for an occupation that is appropriate for the person.\nElse, Fail the test.\n\nNOTE TO TESTER: ANZSCO documentation describes how to select a six digit code for an occupation group [ABS2009]. This is comprised of a four digit group code, together with a two digit occupation specification. An ANZSCO code ending in '99' is an assertion that the occupation is known but is not one of the ANZSCO occupation specifications. \n","Clinical documents created from Authoring Systems which included a person's occupation have appropriate occupation for that person.","TBD",null,{"$f":"IF(H76=\"\",\"0\",IF(H76=\"Pass\",1,IF(H76=\"Fail\",0,IF(H76=\"TBD\",0,IF(H76=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D76)=48,H76=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers","TC-Auth-48","Section 2.42 Position In Organisation [NEHTA-0794:2011]\nDefinition: A descriptor of the job or the job role based on the management hierarchy of the organisation.\nDataType: CodeableText\nValue Domain: 1220.0 - ANZSCO - Australian and New Zealand Standard Classification of Occupations\n","C",1,"CONDITION: Authoring System includes a code for a person's position in an organisation.\n\nPass the test if the code is for an organisational position that is appropriate for the person.\nElse, Fail the test.\n\nNOTE TO TESTER: ANZSCO documentation describes how to select a six digit code for an occupation group [ABS2009]. This is comprised of a four digit group code, together with a two digit occupation specification. An ANZSCO code ending in '99' is an assertion that the occupation is known but is not one of the ANZSCO occupation specifications. \n","Clinical documents created from Authoring Systems which included a person's position in an organisation have appropriate organisation position for that person.","TBD",null,{"$f":"IF(H77=\"\",\"0\",IF(H77=\"Pass\",1,IF(H77=\"Fail\",0,IF(H77=\"TBD\",0,IF(H77=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D77)=48,H77=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Pers","END:  TS-Pers (Person)"]
["TS-eComm","START:  TS-eComm (Electronic communication detail)"]
["TS-eComm","TC-Auth-49","Section 2.12 Electronic Communication Medium [NEHTA-0794:2011]\nDefinition: A code representing a type of communication mechanism.\nData Type: CodedText\n","C",1,"CONDITION: Authoring System is capable of including an electronic communication address into a clinical document.\n\nFail the test if the electronic communication medium associated with an electronic communication address in a clinical document is not one of the permissible values.\nElse, Fail the test if the electronic communication medium is not appropriate for the electronic communication address unless the medium code was selected by the user.\nElse, Pass the test.\n\nNOTE TO TESTER: The permissible values are stated in section 10.8 of the CDA implementation guides, and are \"tel\" Telephone, which includes mobile (cellular) and pager), \"fax\" (Fax), \"mailto\" (Email), \"file\" (Host-specific local file name), \"ftp\" (File Transfer Protocol), \"http\" (Hypertext Transfer Protocol), \"mllp\" (Minimal Lower Layer Protocol), \"modem\", \"nfs\" (Network File System protocol) and \"telnet\".\n","Electronic communication address in the clinical document reflects associated electronic communication medium used in the Authoring System and is of a permissible value. ","TBD",null,{"$f":"IF(H80=\"\",\"0\",IF(H80=\"Pass\",1,IF(H80=\"Fail\",0,IF(H80=\"TBD\",0,IF(H80=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D80)=48,H80=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-eComm","TC-Auth-50","Section 2.14 Electronic Communication Usage Code [NEHTA-0794:2011]\nDefinition: The manner of use that is applied to an electronic communication medium.\nData Type: CodedText\n\n","C",1,"CONDITION: Authoring System is capable of including the electronic communication usage code into a clinical document.\n\nFail the test if the usage code associated with an electronic communication address in a clinical document is not one of the permissible values.\nElse, Fail the test if the usage code is not appropriate for the electronic communication address unless the usage code was selected by the user.\nElse, Pass the test.\n\nNOTE TO TESTER: The test of appropriateness is included as an authoring system may use a default usage code. If so then the default value must be appropriate. For example, a usage code of \"WP\" is appropriate for a hospital's address whereas \"H\" is not. The permissible values are stated in section 10.9 of the CDA implementation guides, and are \"WP\" (Work place), \"H\" (Home address) and \"WP H\" (Both Work place and Home address).\n","Electronic communication address in the clinical document reflects associated electronic communication usage code used in the Authoring System and is of a permissible value. ","TBD",null,{"$f":"IF(H81=\"\",\"0\",IF(H81=\"Pass\",1,IF(H81=\"Fail\",0,IF(H81=\"TBD\",0,IF(H81=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D81)=48,H81=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-eComm","TC-Auth-51","Section 2.16 Electronic Communication Address [NEHTA-0794:2011]\nDefinition: A unique combination of characters used as input to electronic telecommunication equipment for the purpose of contacting an entity.\nData Type: Text\n","C",1,"CONDITION: Authoring System is capable of including an electronic communication address into a clinical document.\n\nFail the test if the electronic communication address entered into the authoring system is not assigned to the corresponding data elements in a clinical document generated by the Authoring System, except where the user indicates the address is not to be included.\nElse, Fail the test if the clinical document contains an electronic communication address that was not entered into the Authoring System.\nElse, Pass the test.\n","Electronic communication address in the clinical document corresponds to the associated electronic communication address used in the Authoring System.","TBD",null,{"$f":"IF(H82=\"\",\"0\",IF(H82=\"Pass\",1,IF(H82=\"Fail\",0,IF(H82=\"TBD\",0,IF(H82=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D82)=48,H82=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-eComm","END:  TS-eComm (Electronic communication detail)"]
["TS-Addr","START:  TS-Addr (Address)"]
["TS-Addr","TC-Auth-52","Section 3.1 Address [NEHTA-0794:2011]\nDefinition: The description of a location where an entity is located or can be otherwise reached or found and a description of the purpose for which that address is primarily used by that entity.\n\nNote: The Participation Data Specification lists the permissible values for the following CodedText data elements: Australian Unit Type, Australian Level Type, Australian Street Type, Australian Street Suffix, Australian Postal Delivery Type, Australian State/Territory and Australian Postcode.","M",1,"Fail the test if the components of an address entered into the authoring system are not assigned to the corresponding data elements in a clinical document generated by the Authoring System, except where the user indicates the address is not to be included,\nElse, Fail the test if the clinical document contains an address data element with a value that was not entered into the Authoring System.\nElse, Fail the test if an address component of the type CodedText has a value that is not one of the permissible values.\nElse, Pass the test.\n\nNOTE TO TESTER: The address components are listed in the Participation Data Specification and in the CDA implementation guides. For example, an Australian address may contain a street address in an unstructured format, and additional data elements for suburb, state, postcode.\n","Where indicated for inclusion, components of an address entered into the Authoring System are assigned to the corresponding data elements in the clinical document and address data elements reflect values entered into the Authoring System with CodedText of a permissible value. ","TBD",null,{"$f":"IF(H85=\"\",\"0\",IF(H85=\"Pass\",1,IF(H85=\"Fail\",0,IF(H85=\"TBD\",0,IF(H85=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D85)=48,H85=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Addr","TC-Auth-53","Section 3.37 Address Purpose [NEHTA-0794:2011]\nDefinition: The purpose for which the address is being used by the entity.\nData Type: CodedText\n","M",1,"Fail the test if the address purpose associated with an address in a clinical document is not one of the permissible values, \nElse, Fail the test if the address purpose is not appropriate for the associated participant unless the address purpose was selected by the user.\nElse, Pass the test.\n\nNOTE TO TESTER: The test of appropriateness is included as an authoring system may use a default address purpose. If so then the default value must be appropriate. For example, an address purpose of \"WP\" is appropriate for a hospital's address whereas \"H\" is not. The permissible values are stated in section 10.6 of the CDA implementation guides, and are \"WP\" (Business), \"PST\" (Mailing or Postal), \"TMP\" (Temporary Accommodation) and \"H\" (Residential (permanent)). \n","Address purpose in the clinical document corresponds to the associated participant or the alternative purpose selected by the authoring user.","TBD",null,{"$f":"IF(H86=\"\",\"0\",IF(H86=\"Pass\",1,IF(H86=\"Fail\",0,IF(H86=\"TBD\",0,IF(H86=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D86)=48,H86=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Addr","TC-Auth-54","Section 8.6 Address [NEHTACDAIG]\nIn an event where the Address of the Subject of Care is 'Unknown' or 'Masked / Not to be disclosed for privacy reason', the following conditions SHOULD be applied.\nThe nullFlavor = \"UNK\" SHOULD be permitted if the value of address is not known.\nThe nullFlavor = \"MSK\" SHOULD be permitted if the value of address is requested to be masked.\nThe nullFlavor = \"NA\" SHOULD be permitted if value of 'No Fixed Address Indicator' is true. (This is the same as the current CDA IG constraint).\nThe value of the <addr> data group SHALL be populated in all other circumstances.\n\nNote: Some CDA implementation guides do not allow all these values to be used for a nullFlavor for an address.\n","O",1,"Pass the step if the authoring system user indicates an address is unknown and the <addr> data group contains the nullFlavor \"UNK\".\nElse, Fail the step.\n","<addr> contains nullFlavor 'UNK' in the clinical document when Authoring System indicated address is unknown.","TBD",null,{"$f":"IF(H87=\"\",\"0\",IF(H87=\"Pass\",1,IF(H87=\"Fail\",0,IF(H87=\"TBD\",0,IF(H87=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D87)=48,H87=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Addr",null,null,null,2,"Pass the step if the authoring system user indicates an address is known but will not be included in the clinical document for security, privacy or other reasons, and the <addr> data group contains the nullFlavor \"MSK\".\nElse, Fail the step.\n","<addr> contains nullFlavor 'MSK' in the clinical document when Authoring System indicated address is known but not to be included for security reasons etc.\n","TBD",null,{"$f":"IF(H88=\"\",\"0\",IF(H88=\"Pass\",1,IF(H88=\"Fail\",0,IF(H88=\"TBD\",0,IF(H88=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D88)=48,H88=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Addr",null,null,null,3,"Pass the step if the authoring system user indicates there is no fixed address and the <addr> data group contains the nullFlavor \"NA\".\nElse, Fail the step.\n","<addr> contains nullFlavor 'NA' in the clinical document when Authoring System indicated no fixed address.","TBD",null,{"$f":"IF(H89=\"\",\"0\",IF(H89=\"Pass\",1,IF(H89=\"Fail\",0,IF(H89=\"TBD\",0,IF(H89=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D89)=48,H89=\"N/A\"),1,0)","v":{"$error":"#NAME?"}}]
["TS-Addr","END:  TS-Addr (Address)"]
[]
[null,null,null,null,null,null,null,"TBD","Total Steps",{"$f":"SUM(J93:J94)","v":63}]
[null,null,null,null,null,null,null,"Fail","Tests Not Started, Failed or TBD",{"$f":"COUNTIF(J1:J90,\"0\")","v":63}]
[null,null,null,null,null,null,null,"N/A","Tests Passed or N/A",{"$f":"COUNTIF(J1:J90,\"1\")","v":0}]
[null,null,null,null,null,null,null,"Pass","%Passed or N/A",{"$f":"SUM(J94/J92)","v":0}]

{"sheet":"References","index":9,"n_rows":45,"n_cols":4,"rows_kept":45,"cut":false,"hidden":false,"merged":[]}
[]
[]
[null,"References and Related Documents"]
[null,"Identifier","Date","Name"]
[null,"NEHTA-0794:2011","2011-07-20","NEHTA-0794:2011 Participation Data Specification - Data Specification v3.2"]
[null,"NEHTA-1136:2010","2010-09-07","NEHTA-1136:2010 Data Types in NEHTA Specifications - A Profile of ISO 21090 Specification v1.0"]
[null,"NEHTA-1199:2012","2012-03-06","NEHTA-1199:2012 Clinical Documents - CDA Rendering Specification v1.0"]
[null,"NEHTA-1227:2012","2012-03-14","NEHTA-1227:2012 P2P Document Delivery - Technical Service Specification v1.1"]
[null,"NEHTA-1229:2011","2011-11-29","NEHTA-1229:2011 Clinical Documents - CDA Package v1.0"]
[null,"NEHTA-1294:2012","2012-07-23","NEHTA-1294:2012 PCEHR Connecting Systems - Conformance Assessment Scheme v1.1"]
[null,"NEHTA-1297:2012","2012-09-06","NEHTA-1297:2012 PCEHR Connecting Systems - Conformance Requirements v1.5"]
[null,"NEHTA-1299:2012","2012-09-27","NEHTA-1299:2012 PCEHR Connecting Systems - Conformance Test Specification v1.6"]
[null,"NEHTA-2064:2016","2012-09-11","NEHTA-2064:2016 Clinical Documents - Conformance Test Specification for CDA Rendering v1.4"]
[null,"NEHTA 1448:2013","2013-10-09","NEHTA-1448:2013 eDischarge Summary - PCEHR Conformance Profile v1.5"]
[null,"NEHTA-1599:2014","2014-02-19","NEHTA-1599:2014 Australian CDA Schema Extension 3.0 - CDA Schema v20140219"]
[null,"NEHTA-1732:2014","2014-10-31","NEHTA-1732:2014 Use of HIs in Health Software Systems - Conformance Requirements v3.1"]
[null,"DH-2481:2017","2017-12-21","DH-2481:2017 Clinical Documents - Common Conformance Profile v1.7"]
[null,"NEHTA-1970:2014","2014-12-31","NEHTA-1970:2014 PCEHR Document Exchange Service - Logical Service Specification v1.3.1"]
[null,"NEHTA-1971:2014","2014-12-31","NEHTA-1971:2014 PCEHR Document Exchange Service - Technical Service Specification v1.5.1"]
[null,"NEHTA-2065:2015","2015-07-15","NEHTA-2065:2015 Clinical Documents - Conformance Test Specification for CDA Packaging v1.5"]
[null,"DH-2758:2018","2018-09-24","Clinical Terminology - Guidance for Use in Healthcare Software"]
[null,"DH-2759:2018","2018-09-24","Clinical Terminology Guidance for use of Medical Nomenclatures in Information Exchange"]
[null,"NEHTACDAIG","Various","NEHTA - CDA Implementation Guides"]
[null,"NEHTASCS","Various","NEHTA - Structured content specifications"]
[null,"AIHW2015","2005-07-07","Metadata Online Registry"]
[null,"AIHWCS","Website","Australian Institute of Health and Welfare, Clinical Specialties: Various references to this website\nMetadata Online Registry, home page - http://meteor.aihw.gov.au/content/index.phtml/itemId/"]
[null,"ASIC2015","Website","Australian Securities and Investment Commission\nHome page - www.asic.gov.au"]
[null,"HL7CDAR2","2004-12-12","HL7 Clinical Document Architecture, Release 2"]
[null,"HL72004","2004-11-29","HL7 Version 3 Standard: Data Types - Abstract Specification, Release 1 - http://www.hl7.org/\nNote: HL7 documents can only be obtained by creating a user account with HL7.  At the time of writing, the Release 1 document can be accessed as part of the Health Level Seven Version 3 (V3) Normative Edition. Find the HL7 Version 3 Product Suite and download: HL7 Version 3 Normative Edition, 2015."]
[null,"HL72004b","2004-08-04","XML Implementation Technology Specification - Data Types - http://www.hl7.org/. Note: HL7 documents can only be obtained by creating a user account with HL7.  "]
[null,"HL72013","2013-06-08","HL7 Reference Information Model, Release 6 - http://www.hl7.org/\nNote: HL7 documents can only be obtained by creating a user account with HL7.  At the time of writing, the Release 6 document can be accessed as part of the Health Level Seven Version 3 (V3) Normative Edition. Find the HL7 Version 3 Product Suite and download: HL7 Version 3 Normative Edition, 2015"]
[null,"HL72015","2005-07-07","OID Registry - HL7 Object Identifier (OID) Registry"]
[null,"ISO21090","2011-02-15","ISO 21090:2011 Health informatics -- Harmonized data types for information interchange - https://www.iso.org\nNote: Only informative sections of standards are publicly available. To view the full content, you will need to purchase the standard by clicking on the \"Buy\" button."]
[null,"ITU2004","2004-09-13","ITU-T X.667 “Information technology – Open Systems Interconnection – Procedures for the operation of OSI Registration Authorities: Generation and registration of Universally Unique Identifiers (UUIDs) and their use as ASN.1 object identifier components\" - https://www.itu.int/ITU-T/studygroups/com17/oid/X.667-E.pdf"]
[null,"OG1997","2005-06-19","The Open Group, CDE 1.1 Remote Procedure Call specification\nUniversal Unique Identifier (UUID) - http://pubs.opengroup.org/onlinepubs/9629399/apdxa.htm"]
[null,"OIDR2015",null,"Object Identifier (OID) Repository - http://www.oid-info.com/"]
[null,"RFC3986","Jan 2005","Uniform Resource Identifier (URI): Generic Syntax"]
[null,"SA2006a","2006-06-30","AS 5017-2006 Health Care Client Identification - http://infostore.saiglobal.com/store/\nNote: This Australian Standard® can be obtained by creating a user account with SAI Global. "]
[null,"SA2006b","2006-06-30","AS 4846-2006 Health Care Provider Identification - http://infostore.saiglobal.com/store/\nNote: This Australian Standard® can be obtained by creating a user account with SAI Global. "]
[null,"SA2012 ","2012-12-10","SA HB 234-2012 Healthcare identifier HL7 implementation guide \nhttp://infostore.saiglobal.com/store/\nNote: This Australian Standard® can be obtained by creating a user account with SAI Global.\n"]
[null,"UCUM","2015-11-13","The Unified Code for Units of Measure"]
[null,"W3C2008","2008-11-26","Extensible Markup Language (XML) 1.0 (Fifth Edition)"]
[null,"W3C2010","2010-08-12","Using character escapes in markup and CSS"]
[null,"W3C2013","2013-01-24","Unicode in XML and other Markup Languages"]
[null,"W3C2018","2018-06-19","CSS Color Module Level 3"]

{"sheet":"Change log","index":10,"n_rows":55,"n_cols":5,"rows_kept":55,"cut":false,"hidden":false,"merged":[]}
["Test Case ID","Change in Version","Change Request ID","Description Of Change","Comments"]
["TC-Doc-01","v1.2","CCP V1.7","Minor wording changes only to requirement 023706. No changes to test case."]
["TC-Doc-04","v1.2","CCA-1803","Test case changed to require attribute values to be consistent with RIM"]
["TC-Doc-08","v1.2","CCP V1.7","Minor wording changes only to requirement 025254. No changes to test case."]
["TC-Doc-17","v1.2","CCP V1.7","Test case updated to reflect changes to requirement 024482 in CCP v1.7"]
["TC-Doc-10","v1.2","CCP V1.7","Test case removed as requirement deleted in CCP v1.7"]
["TC-Doc-23","v1.2","CCA-1599","Test case rewritten to correct errors in conditions and tests, merging test steps."]
["TC-Doc-24","v1.2","CCP V1.7","Test case amended to reflect changes to requirment 025054 in CCP v1.7"]
["TC-Doc-25","v1.2","CCP V1.7","New test to accommodate new requirement 027731 in CCP v1.7. It replaces previous test case based on changed requirement 025054."]
["TC-Doc-41","v1.2","CCA-1741","Clarification of requirement referencing CDA IG Section 6.1 and ensuring correct coverage across document types."]
["TC-Doc-42","v1.2","CCP V1.7","Test case added to accommodate new requirement 027732 in CCP v1.7"]
["TC-Doc-43","v1.2","CCP V1.7","Test case added to accommodate new requirement 027734 in CCP v1.7"]
["TC-Doc 44","v1.2","CCP V1.7","Test case added to accommodate new requirement 027735 in CCP v1.7"]
["TC-Auth-01","v1.2","CCP V1.7","Minor wording changes only to requirement 023873 & 023874. No changes to test case."]
["TC-Auth-02.1","v1.2","CCP V1.7","Minor wording changes only to requirement 023733. No changes to test case."]
["TC-Auth-09","v1.2","CCA-1884","Note to Tester added to clarify references to URLs."]
["TC-Auth-56","v1.2","N/A","Test case is removed from Authoring CTS, as related to eSignature not CDA document"]
["TC-Narr-09 Step 4","v1.2","CCA-1676","Test case changed to remove inconsistencies in testing dateTime."]
["TC-Narr-72","v1.2","CCA-1644","Add note to requirement to clarify coding of colour style codes."]
["TC-Narr-73","v1.2","CCA-1644","Add note to requirement to clarify coding of colour style codes."]
["TS-ST","v1.2","CCA-1805","Note updated to reflect correct support for \"SC\" data type."]
["TS-CD","v1.2","CCA-1806","Note updated to reflect correct support for code type specialisations."]
["TC-Types-04","v1.2","CCA-1782","Clarification added for translation element."]
["TC-Types-04 step 2","v1.2","CCA-1861","Correct the expected result"]
["TC-Types-06","v1.2","CCA-1828","Minor changes to condition and expected results to cover \"NS\" vocab statement."]
["TC-Types-08","v1.2","CCA-1771","Condition changed to reflect testing of nullFlavor"]
["TC-Types-13","v1.2","CCA-1834","Update test case to check for decimal value."]
["TC-Types-13","v1.2","CCA-1835","Update fail test related to TS-PQ."]
["TC-Types-17","v1.2`","CCA-1870","Change to remove redundant fail tests."]
["TC-Types-17","v1.2","CCA-1871","Update test case to check for decimal value."]
["TC-Types-21","v1.2","CCA-1816","Note added that data type has to be xsi:type=\"IVL_PQ\""]
["TC-Types-29","v1.2","CCP V1.7","Original requirement 023876 removed and replaced by CCP v1.7 requirements: \n027736, 027737 & 027738."]
["TC-Types-29","v1.2","CCA-1707","Correct reference to codeSystemName value."]
["TC-Types-30","v1.2","CCP V1.7","Original requirement 023877 removed and replaced by CCP v1.7 requirements: \n027789 & 027790."]
["TC-Types-30","v1.2","CCA-1708","Correct reference to codeSystemName value."]
["TC-Types-53","v1.2","CCP V1.7","Minor wording changes only to requirement 024631. No changes to test case."]
["TC-Types-64","v1.2","CCA-1620","Changes to clarify OID test and replace \"NEHTA\" with \"Agency\"."]
["TC-Types-72","v1.2","CCA-1632","Correction to allow test for extention attribute."]
["TC-Types-82","v1.2","CCP V1.7","Original requirement 023876 removed and replaced by CCP v1.7 requirements: \n027791 & 027792.\nTest case moved from Instance Identifier Test Set to Entity Identifier Test Set."]
["TC-Types-97","v1.2","CCA-1833","Correct pass and fail tests for ratio attributes."]
["TC-Types-97","v1.2","CCA-1840","Correct pass and fail tests for ratio attributes."]
["TC-Types-98","v1.2","CCA-1869","Change to correctly test the time element and attributes."]
["TC-Types-99","v1.2","CCA-1842","Correct test for number of digits for time value."]
["TC-Types-99","v1.2","CCA-1847","Add test to check validity of year (YYYY)."]
["TC-Types-100","v1.2","CCA-1845","Change test to ensure \"full year\" is tested."]
["TC-Types-100","v1.2","CCA-1854","Change test to properly test nullFlavor."]
["TC-Types-101","v1.2","CCA-1844","Clarification of time value."]
["TC-Types-104","v1.2","CCA-1733","Correct quantity comparison test."]
["TC-Types-107\nTC-Types-109","v1.2","CCA-1885","Correct tests for ABN and ACN numbers in OIDs."]
["TC-Types-110","v1.2","CCA-1800","Correction to Conformance Requirements to show correct document section references"]
["TC-Types-116","v1.2","CCA-1819","Updated to correct and clarify test for code values and attributes."]
["TC-Types-119","v1.2","CCP V1.7","New test case added to accommodate new requirement 027766 in CCP v1.7"]
["TC-Types-120","v1.2","CCP V1.7","New test case added to accommodate new requirement 027730 in CCP v1.7"]
["TC-Types-121","v1.2","CCA-1807","New test case added to support HL7 SLIST data type"]
["TC-Types-122","v1.2","CCA-1805","New test case added to support HL7 SC data type invariants"]