{"text_format":"1","workbook":"xlsx","n_sheets":13,"sheets":["Cover","Intro","TP-NewDoc","TP-Consent","TP-Supersede","TP-Remove","TP-DIR","FS-DIRDoc ","FS-DIRProc","Process models","TSR","Traceability","References"],"not_rendered":{"charts":0,"images":8,"macros":1,"external_links":5,"defined_names":36,"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":29,"n_cols":9,"rows_kept":29,"cut":false,"hidden":false,"merged":[[25,1,25,3],[26,1,26,3],[27,1,27,3],[28,1,28,3],[4,1,4,4],[16,3,16,4],[20,1,20,3],[21,1,21,3],[23,1,23,3],[24,1,24,3],[22,1,22,3]]}
[]
[]
[null,null," "]
[]
[null,"Diagnostic Imaging Report "]
[null,"Conformance Test Specification"]
[]
[null,"Version 1.0"]
[null,"2017-06-16"]
[]
[null,"Approved for external use"]
[null,"Document ID: DH-2526:2017"]
[]
[]
[null,"Product version history"]
[null,"Version","Date","Comments"]
[null,1,"2017-06-16","Approved for release"]
[]
[]
[null,null,null,null,null,null,null,null," "]
[null,"Acknowledgements"]
[null,"Council of Australian Governments\nThe Australian Digital Health Agency is jointly funded by the Australian Government and all state and territory governments.\n"]
[null,"IHTSDO (SNOMED CT)\nThis material includes SNOMED Clinical Terms™ (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, (http://www.ihtsdo.org/).\n\nHL7 International\nThis document includes excerpts of HL7™ 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 (see 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.\n"]
[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 © 2016 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."]

{"sheet":"Intro","index":1,"n_rows":121,"n_cols":5,"rows_kept":121,"cut":false,"hidden":false,"merged":[[103,1,103,2],[83,1,83,2],[2,1,2,2],[12,1,12,2],[14,1,14,2],[15,1,15,2],[16,1,16,2],[25,1,25,2],[30,1,30,2],[31,1,31,2],[32,1,32,2],[45,1,45,2],[63,1,63,2]]}
[null,"Australian Digital Health Agency",null,"Document information"]
[null,"Introduction",null,"Owner:","Head of Product Delivery"]
[null,"The information in this section will:\na.  help you determine what test material you need to apply for Diagnostic Imaging Report - this will be based on the type of \"user\" you are.\nb.  give you an overview of the individual worksheets and their structure i.e. what the columns mean and how to record the Test Results (i.e. Pass, Fail etc.).\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:","The Agency 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 for Test Procedures"]
[4,"Worksheet structure for Feature Sets"]
[5,"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 tests cases need to be applied. "]
[null,"Table 1: What test material do I need?","`"]
[null,"USER 1:  I want to test the authoring of Diagnostic Imaging Reports created by my Authoring System."]
[null,"In this scenario, you have developed an Authoring System that creates Diagnostic Imaging Reports, and you want to test the conformance of the Diagnostic Imaging Reports produced by the system against the eHealth requirements.\n"]
[null,"Tests to apply to the Diagnostic Imaging Report Authoring System:"]
[null,null,"From the Diagnostic Imaging Report Conformance Test Specification (this specification):"]
[null,null,"TP-NewDoc"]
[null,null,"TP-Consent"]
[null,null,"TP-Supersede"]
[null,null,"TP-Remove"]
[null,null,"                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       "]
[null,null,"Use cases containing the tests that are commencing with the identifier \"UC.CIS\"  are listed in the PCEHR Connecting Systems - Conformance Test Specification [NEHTA-1299:2012]."]
[]
[null,"Tests to apply to Diagnostic Imaging Report documents:"]
[null,null,"From the Diagnostic Imaging Report Conformance Test Specification (this specification):"]
[null,null,"TP-DIR"]
[]
[]
[null,"USER 2:  I want to test the Diagnostic Imaging Report clinical documents that were downloaded from My Health Record system."]
[null,"In this scenario, you have a Diagnostic Imaging Report - but no knowledge of the Authoring System which produced it - and you want to test the document’s conformance against the eHealth requirements."]
[null,"Tests to apply to Diagnostic Imaging Report clinical documents:"]
[null,null,"From the Diagnostic Imaging Report Conformance Test Specification (this specification):"]
[null,null,"FS-DIRDoc"]
[]
[null,null,"From the Authoring Systems Conformance Test Specification [NEHTA-2209:2015]:"]
[null,null,"FS-Doc"]
[null,null,"FS-Narr"]
[null,null,"FS-Types"]
[]
[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","TEST PROCEDURE and PURPOSE"]
[null,"TP-NewDoc","Full name: Author a new Diagnostic Imaging Report function\nObjective: To assess the conformance of a Diagnostic Imaging Report authoring system to the requirements that apply to the process of creating a new Diagnostic Imaging Report.\n"]
[null,"TP-Consent","Full name: Change consent setting function\nObjective: To assess the conformance of a Diagnostic Imaging Report authoring system to the requirements that apply to the receipt of an indication of consent.\n"]
[null,"TP-Supersede","Full name: Supersede a Diagnostic Imaging Report function\nObjective: To assess the conformance of a Diagnostic Imaging Report authoring system to the requirements that apply to the process of superseding a Diagnostic Imaging Report that was uploaded to the My Health Record system.\n"]
[null,"TP-Remove","Full name: Remove a Diagnostic Imaging Report function\nObjective: To assess the conformance of a Diagnostic Imaging Report authoring system to the requirements that apply to the process of removing a Diagnostic Imaging Report from the My Health Record system.\n"]
[null,"TP-DIR","Full name: Diagnostic Imaging Report information content\nObjective: To assess the ability of a Diagnostic Imaging Report authoring system to create Diagnostic Imaging Reports with a variety of information content that may be used specifically for that type of clinical document.\n"]
[null,"FS-DIRDoc","Full name: FS-DIRDoc: Diagnostic Imaging Report clinical document\nObjective: To assess the conformance of a Diagnostic Imaging Report clinical document to the requirements specified in the Common Conformance profile and the requirements specified in Diagnostic Imaging Report Conformance Profile.\n"]
[null,"FS-DIRProc","Full name: Business processes for the authoring system\nObjective: To assess the conformance to the process requirements for an Authoring System that creates Diagnostic Imaging Reports. These are requirements for creating, superseding and removing Diagnostic Imaging Reports, consent management and record keeping. These requirements are additional to the requirements that apply to the Diagnostic Imaging Reports created by an Authoring System.\n"]
[null,"Process models","Process models diagramatically represent an indicative business workflow to act as a basis for the test scenarios. Process models list process requirements which are conformance requirements related to the following business processes:\n• Author a new Diagnostic Imaging Report\n• Store or upload to the My Health Record system\n• Change consent setting\n• Supersede a Diagnostic Imaging Report\n• Remove a Diagnostic Imaging Report\n• Retrieve records\n\n"]
[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."]
[null,"Traceability","This worksheet contains a list of requirements and specifications which shows requirements coverage over the feature sets.\n"]
[null,"References","This worksheet contains a list of documents that are referenced directly from this document and other documents that are related to this document.\n"]
[null,"Return to top"]
[]
[]
[3,"Worksheet structure for Test Procedures"]
[null,"Table 3 below describes the structure of the five Test procedures:  TP-NewDoc, TP-Consent, TP-Supersede, TP-Remove and TP-DIR.  \nFeature sets FS-DIRDoc and FS-DIRProc are described in section 4 below."]
[null,"Table 3: Worksheet structure for Test Procedures"]
[null,"LABEL NAME","DESCRIPTION"]
[null,"Test procedure","A logical grouping of test cases to be executed for a given Authoring System scenario.\n"]
[null,"Overview","Briefly describes the focus or objective for these test procedures, and includes the implementation of the conformance strategy.\n"]
[null,"Instructions","Explains important data elements used in the test scenarios and contains information on how to apply."]
[null,"Scenario ","Provides an individual identifier and a short description of the test scenario."]
[null,"Objective","Identifies and briefly describes the special focus or objective for the each scenario."]
[null,"Priority","Specifies whether the scenario exercised by this test procedure is mandatory or conditional."]
[null,"Pre-requisites","Describes the actions necessary to prepare for the execution of the scenario."]
[null,"PERFORM THIS TASK","Specific scenario description."]
[null,"RUN THESE TEST SETS/TEST CASES","A list of the test cases to be executed for this scenario."]
[null,"TEST STEP/CASE DESCRIPTION","A brief test case description."]
[null,"ACTUAL TEST RESULT","Result of the test (Pass, Fail, N/A or TBD pick list). \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 \ni.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. Inclusion of \"TESTER COMMENTS\" by the tester is optional.\n"]
[null,"Scenario result","Result status of the scenario exercised by this test procedure. Automatically populated, either \"Incomplete\" or\" Complete\""]
[null,"Return to top"]
[]
[]
[4,"Worksheet structure for Feature Sets"]
[null,"Table 4 below describes the final 2 feature set worksheets:  FS-DIRDoc and FS-DIRProc."]
[null,"Table 4: Worksheet structure for Feature Sets"]
[null,"LABEL NAME","DESCRIPTION"]
[null,"Feature set identifier","A logical grouping of features to be tested for the Authoring System."]
[null,"Objective","Briefly describes the focus or objective for the feature set."]
[null,"Strategy","Specifies the implementation of the strategy for this feature set."]
[null,"Traceability","Lists the documents which contain the requirements on which the feature set test cases are based.\n"]
[null,"TEST SET ID","Unique identifier which distinguishes each test case from within the entire set of test specifications."]
[null,"TEST CASE ID","A unique value to identify the test case."]
[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."]
[null,"TEST STEP","The evaluation required for applying the test case."]
[null,"EXPECTED RESULT","The expected outcome of the test step."]
[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 \ni.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. Inclusion of \"TESTER COMMENTS\" by the tester is optional."]
[null,"TEST CASE ID","A unique value to identify the test case."]
[null,"Return to top"]
[]
[5,"Acronyms"]
[null,"Table 5 lists acronyms and terms used in the CTS."]
[null,"Table 5: Acronyms"]
[null,"ACRONYM","MEANING"]
[null,"CDA","Clinical Document Architecture"]
[null,"CIS","clinical information system"]
[null,"CTS","conformance test specification"]
[null,"FS","feature set"]
[null,"HI","Healthcare Identifier"]
[null,"HPI","Healthcare Provider Identifier (O-Organisation, I-individual)"]
[null,"IHI","IHI – Individual Healthcare Identifier"]
[null,"NEHTA","National E-Health Transition Authority"]
[null,"PCEHR","Personally Controlled Electronic Health Record. PCEHR is now known as My Health Record."]
[null,"PDF","Portable Document Format"]
[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,"Return to top"]

{"sheet":"TP-NewDoc","index":2,"n_rows":467,"n_cols":9,"rows_kept":467,"cut":false,"hidden":false,"merged":[[4,2,4,6],[2,2,2,6],[1,2,1,6],[0,2,0,6],[161,2,161,6],[5,2,5,6],[7,2,7,6],[6,2,6,6],[55,2,55,6],[56,2,56,6],[162,2,162,6],[218,2,218,6],[217,2,217,6],[57,2,57,6],[58,2,58,6],[110,2,110,6],[109,2,109,6],[108,2,108,6],[111,2,111,6],[159,2,159,6],[160,2,160,6],[216,2,216,6],[215,2,215,6],[398,2,398,6],[399,2,399,6],[400,2,400,6],[401,2,401,6],[264,2,264,6],[308,2,308,6],[309,2,309,6],[310,2,310,6],[354,2,354,6],[355,2,355,6],[356,2,356,6],[261,2,261,6],[262,2,262,6],[263,2,263,6],[311,2,311,6],[353,2,353,6]]}
[null,"Test procedure:","TP-NewDoc: Author a new Diagnostic Imaging Report function"]
[null,"Overview:","To assess the conformance of a diagnostic imaging report authoring system to the requirements that apply to the process of creating a new Diagnostic Imaging Report.\n\nThe business process of authoring a new diagnostic imaging report is initiated when a request for diagnostic imaging services is received and includes requirements for managing consent and record keeping, as well as creating the report and CDA package to be sent to the My Health Record system.\n\nConformance to the requirements associated with the business process is assessed through a set of test scenarios, where each scenario corresponds to a path through the model documented in the \"Process models\" worksheet. Test scenarios have been selected to achieve complete coverage of every sequence flow in the model, while reducing the duplication of tests.\n\nA test procedure has been developed for each scenario, where the procedure involves a set of activities and the application of selected test cases. Some test cases used in the scenarios have a \"conditional\" priority. Should the condition apply in the context of the test scenario they should be considered mandatory and be marked as Pass or Fail and not N/A. \n\nEach test scenario is passed when all the specified test cases have a status of \"Pass\".\n\nNote: The terms \"software system\", \"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 as are \"healthcare consumer\" and \"healthcare individual\".\n\n"]
[null,"Instructions:","A test scenario with the priority of \"Mandatory\" must be applied and passed by the software system before it may be declared conformant to the requirements. Any \"conditional\" test scenario is to be applied if the software system has the functionality required to support the test. For the \"conditional\" test scenario, if the software system does not have the required functionality then the test result to be recorded is \"N/A\" (not applicable). The overall test result is calculated from the result of each test scenario.\n\nThe test scenarios refer to test cases as follows, Test Cases commencing with the identifier:\n1. \"TC-DIRProc\" are listed in the FS-DIRProc feature set within this conformance test specification.\n2. \"TC-DIRDoc\" are listed in the FS-DIRDoc feature set within this conformance test specification.\n3. \"PCEHR_CIS\" are listed in the PCEHR Connecting Systems - Conformance Test Specification v1.6 [NEHTA-1299:2012].\n\nTasks surrounded by brackets, for example \"(A2: Record \"No Withdrawn consent\") \", are assumed to be automatically performed by the software system without requiring any action by the tester. Test cases to be applied often have a \"conditional\" status as they apply only in a specific context. As the scenarios have been designed to select that context then the test cases for each scenario must be applied and have a result of \"Pass\" before the software system can be declared as conformant. \n"]
[]
[null,"Scenario:","TP-NewDoc-01 - New DI Report uploaded (Consent provided)"]
[null,"Objective:","For a recipient of healthcare services who has indicated their consent to upload clinical documents to the My Health Record system using the software system to author a new Diagnostic Imaging Report that includes one Diagnostic Imaging Examination Result.\n\nDemonstrate that the software system has the ability to:\n1. Record the consent setting as \"No withdrawn consent\".\n2. Upload the Diagnostic Imaging Report to the My Health Record system.\n3. Create a conformant Diagnostic Imaging Report.\n4. Verify the original consent information is recorded as \"No withdrawn consent\".\n\nBusiness process models A, B & G. \nPath: Start -> A9 -> A2 -> A8 -> A6 -> A7 -> B3 -> B5  -> B12 -> G1 -> End\n"]
[null,"Priority:","Mandatory."]
[null,"Pre-requisites:","1. The healthcare individual has an IHI and a digital health record.\n2. The request for the diagnostic services states that the healthcare individual has indicated consent to upload the clinical documents to the My Health Record system.\n3. The request for the diagnostic services states the healthcare individual's name and sufficient demographic information is present in the request that is needed to successfully search the HI Service to obtain their IHI.\n4. The software system has been set up to successfully upload the diagnostic imaging reports to the My Health Record system.\n\n"]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,null,"A9: Enter the request details","-",null,"TBD",null,{"$f":"IF(F10=\"\",\"0\",IF(F10=\"Pass\",1,IF(F10=\"Fail\",0,IF(F10=\"TBD\",0,IF(F10=\"N/A\",1)))))","v":0}]
[null,"TP-NewDoc-01","(A2: Record \"No Withdrawn consent\")","TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded","TBD",null,{"$f":"IF(F11=\"\",\"0\",IF(F11=\"Pass\",1,IF(F11=\"Fail\",0,IF(F11=\"TBD\",0,IF(F11=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-DIRProc-15.1","Record the original and changed withdrawal of consent indicator values","TBD",null,0]
[null,null,"(A8: Record \"digital health record exists\")","Test cases for UC.CIS.001\n(PCEHR connecting systems requirement 019100 [NEHTA-1299:2012])",null,"TBD",null,0]
[null,null,"A6: Perform diagnostic tests ","-",null,"TBD",null,0]
[null,null,"A7: Author a Diagnostic Imaging Report","-",null,"TBD",null,0]
[null,null,"(B3: Prepare for upload)","TC-DIRDoc-07","Mandatory Document Author Values used","TBD",null,0]
[null,null,null,"TC-DIRDoc-08","Mandatory Reporting Radiologist Values used","TBD",null,0]
[null,null,null,"TC-DIRDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I","TBD",null,0]
[null,null,null,"TC-DIRDoc-12","Reporting Radiologist > Participant > Entity Identifier value SHALL be an HPI-I","TBD",null,0]
[null,null,"(B5: UC.CIS.201 Upload a clinical document)",null,"Diagnostic Imaging Report is uploaded successfully","TBD",null,0]
[null,null,null,"Test cases for UC.CIS.201 (note that requirement 024885 overrides PCEHR connecting systems requirement 019100)","Upload a Clinical Document","TBD",null,0]
[null,null,"(B12: Record \"Document uploaded\")","TC-DIRProc-06","\"Document uploaded\" indicator is recorded","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-DIRProc-16\n","The record shows that the original consent setting is \"No withdrawn consent\"","TBD",null,0]
[null,null,"Assess the conformance of the listed Diagnostic Imaging Report & CIS requirements","TC-DIRDoc-01","Conform to the requirements for one, and only one, of the following conformance levels: 3A or 3B as defined in the Common Conformance Profile for Clinical Documents.","TBD",null,0]
[null,null,null,"TC-DIRDoc-02","Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TBD",null,0]
[null,null,null,"TC-DIRDoc-03","The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.","TBD",null,0]
[null,null,null,"TC-DIRDoc-04","Various Diagnostic Imaging Report Results and Documents not nullflavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-05","SNOMED-CT-AU not nullFlavor","TBD",null,0]
[null,null,null,"TC-DIRDoc-06","Sort test results","TBD",null,0]
[null,null,null,"TC-DIRDoc-20","Check the narrative and section title","TBD",null,0]
[null,null,null,"TC-DIRDoc-09","References in CDA Package","TBD",null,0]
[null,null,null,"TC-DIRDoc-10","References in CDA Package","TBD",null,0]
[null,null,null,"TC-DIRDoc-13","Report Date Time","TBD",null,0]
[null,null,null,"TC-DIRDoc-14","Anatomical Location Instance.","TBD",null,0]
[null,null,null,"TC-DIRDoc-15","Anatomical Region is Name of Location.","TBD",null,0]
[null,null,null,"TC-DIRDoc-16","Appropriate Image Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-17","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-18","Image Location: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-19","Document target: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRProc-01","Clinical document producer SHALL NOT be a  registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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. ","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers","TBD",null,0]
[null,null,null,"TC-DIRProc-15.2","Record the original and changed withdrawal of consent indicator values","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.001)","CIS uses IHI","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.001)","CIS Audit","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.201)","CIS uses IHI","TBD",null,0]
[null,null,null,"PCEHR_CIS_019429 (UC.CIS.201)","CIS uses HPI-I","TBD",null,0]
[null,null,null,"PCEHR_CIS_019042 (UC.CIS.201)","Withdraw Consent","TBD",null,0]
[null,null,null,"PCEHR_CIS_017842a (UC.CIS.201)","CIS Identifies Uploads","TBD",null,0]
[null,null,null,"PCEHR_CIS_017841a (UC.CIS.201)","CIS Retains Clinical info","TBD",null,0]
[null,null,null,"PCEHR_CIS_017839 (UC.CIS.201)","Clinical Document explicit command","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.201)","CIS Audit","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I54=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM($H10:$H53) / (COUNT($H10:$H53))","v":0}]
[]
[null,"Scenario:","TP-NewDoc-02 - New DI Report uploaded (Consent not provided and  healthcare Individual digital health record exists in the My Health Record system)"]
[null,"Objective:","For a recipient of healthcare services who has not provided any consent information to upload clinical documents to the My Health Record system: \nUsing the software system, author a new Diagnostic Imaging Report that includes one Diagnostic Imaging Examination Result. The My Health Record system reports that the healthcare individual has a digital health record (see pre-requisites). The author of the Diagnostic Imaging Report performs an action to upload the report to the My Health Record system.\n\nDemonstrate that the software system has the ability to:\n1. Record the consent setting as \"No withdrawn consent\".\n2. Upload the Diagnostic Imaging Report to the My Health Record system.\n3. Verify the original consent information is recorded as \"No withdrawn consent\".\n\nBusiness process models A, B & G. \nPath : Start ->  A9 -> A4 -> A2 -> A8 -> A6 -> A7 -> B3 -> B5  -> B12 -> G1 -> End"]
[null,"Priority:","Mandatory."]
[null,"Pre-requisites:","1. The healthcare individual has an IHI and a digital health record.\n2. The request for the diagnostic services contains no information about consent.\n3. The request for the diagnostic services states the healthcare individual's name and sufficient demographic information is present in the request that is needed to successfully search the HI Service to obtain their IHI.\n4. The search for the healthcare Individual digital health record in the My Health Record system returns \"digital health record found\".\n5. The software system has been set up to successfully upload the diagnostic imaging reports to the My Health Record system."]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,null,"A9: Enter the request details","-",null,"TBD",null,{"$f":"IF(F61=\"\",\"0\",IF(F61=\"Pass\",1,IF(F61=\"Fail\",0,IF(F61=\"TBD\",0,IF(F61=\"N/A\",1)))))","v":0}]
[null,"TP-NewDoc-02","(A4. UC.CIS.001 Check if an advertised digital health record exists via doesPCEHRexist web service call)","TC-DIRProc-09, Test cases for UC.CIS.001 \n(note: requirement 024885 overrides PCEHR connecting systems requirement 019100)","\nInvoke doesPCEHRexist web service.\nUpload the clinical document.","TBD",null,{"$f":"IF(F62=\"\",\"0\",IF(F62=\"Pass\",1,IF(F62=\"Fail\",0,IF(F62=\"TBD\",0,IF(F62=\"N/A\",1)))))","v":0}]
[null,null,"(A2: Record \"No Withdrawn consent\")",null,null,"TBD",null,0]
[null,null,null,"TC-DIRProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,"(A8: Record \"digital health record exists\")","Test cases for UC.CIS.001\n(PCEHR connecting systems requirement 019100)",null,"TBD",null,0]
[null,null,"A6: Perform diagnostic tests ","-",null,"TBD",null,0]
[null,null,"A7: Author a Diagnostic Imaging Report","-",null,"TBD",null,0]
[null,null,"(B3: Prepare for upload)","TC-DIRDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-08","Mandatory Reporting Radiologist Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-12","Reporting Radiologist > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-01","Conform to the requirements for one, and only one, of the following conformance levels: 3A or 3B as defined in the Common Conformance Profile for Clinical Documents.","TBD",null,0]
[null,null,"(B5: UC.CIS.201 Upload a clinical document)","TC-DIRProc-08","Software system permits the report to be uploaded to the My Health Record system.","TBD",null,0]
[null,null,null,"Test cases for UC.CIS.201 \n(note that requirement 024885 overrides PCEHR connecting systems requirement 019100)","Upload the clinical document.","TBD",null,0]
[null,null,"(B12: Record \"Document uploaded\")","TC-DIRProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-DIRProc-16","The record shows that the consent setting is \"No withdrawn consent\".","TBD",null,0]
[null,null,"Assess the conformance of the listed Diagnostic Imaging Report & CIS requirements","TC-DIRDoc-02","Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TBD",null,0]
[null,null,null,"TC-DIRDoc-03","The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.\n","TBD",null,0]
[null,null,null,"TC-DIRDoc-04","Various Diagnostic Imaging Report Results and Documents not nullflavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-05","SNOMED-CT-AU not nullFlavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-DIRDoc-20","Check the narrative and section title.","TBD",null,0]
[null,null,null,"TC-DIRDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-10","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-13","Report Date Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-14","Anatomical Location Instance.","TBD",null,0]
[null,null,null,"TC-DIRDoc-15","Anatomical Region is Name of Location.","TBD",null,0]
[null,null,null,"TC-DIRDoc-16","Appropriate Image Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-17","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-18","Image Location: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-19","Document target: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRProc-01","Clinical document producer SHALL NOT be a  registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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. ","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-DIRProc-15.2","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.001)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.001)","CIS Audit.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.201)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019429 (UC.CIS.201)","CIS uses HPI-I.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019042 (UC.CIS.201)","Withdraw Consent.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017842a (UC.CIS.201)","CIS Identifies Uploads.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017841a (UC.CIS.201)","CIS Retains Clinical info.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017839 (UC.CIS.201)","Clinical Document explicit command.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.201)","CIS Audit.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I107=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM($H61:$H106) / (COUNT($H61:$H106))","v":0}]
[]
[null,"Scenario:","TP-NewDoc-03 - New Report Not Uploaded to My Health Record System (Consent Provided - Health Record System Error)"]
[null,"Objective:","For a recipient of healthcare services who has indicated their consent to upload clinical documents to the My Health Record system:\nUsing the software system, author a new Diagnostic Imaging Report that includes one Diagnostic Imaging Examination Result. The author of the Diagnostic Imaging Report performs an action to upload the report to the My Health Record system.  The software system fails to upload the Diagnostic Imaging Report to the My Health Record system.\n\nDemonstrate that the software system has the ability to:\n1. Record the consent setting as \"No withdrawn consent\".\n2. Record that an error occurred during the upload of the Diagnostic Imaging Report to the My Health Record system.\n3. Record the original consent information as \"No withdrawn consent\".\n\nBusiness process models A, B & G. \nPath: Start -> A9 ->  A2 -> A8 -> A6 -> A7 -> B3 -> B5  -> B6 -> B13 -> G1 -> End\n"]
[null,"Priority:","Mandatory."]
[null,"Pre-requisites:","1. The healthcare individual has an IHI and a digital health record.\n2. The request for the diagnostic services states that the healthcare individual has indicated consent to upload Diagnostic Imaging Report to the My Health Record system.\n3. The request for the diagnostic services states the healthcare individual's name and sufficient demographic information is present in the request that is needed to successfully search the HI Service to obtain their IHI.\n4. The software system has been set up so that an attempt to upload a Diagnostic Imaging Report to the My Health Record system results in an error.\n\n"]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,null,"A9: Enter the request details","-",null,"TBD",null,{"$f":"IF(F114=\"\",\"0\",IF(F114=\"Pass\",1,IF(F114=\"Fail\",0,IF(F114=\"TBD\",0,IF(F114=\"N/A\",1)))))","v":0}]
[null,"TP-NewDoc-03","(A2: Record \"No Withdrawn consent\")","TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,{"$f":"IF(F115=\"\",\"0\",IF(F115=\"Pass\",1,IF(F115=\"Fail\",0,IF(F115=\"TBD\",0,IF(F115=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-DIRProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,"(A8: Record \"digital health record exists\")","Test cases for UC.CIS.001\n(PCEHR connecting systems requirement 019100)",null,"TBD",null,0]
[null,null,"A6: Perform diagnostic tests ","-",null,"TBD",null,0]
[null,null,"A7: Author a Diagnostic Imaging Report","-",null,"TBD",null,0]
[null,null,"(B3: Prepare for upload)","TC-DIRDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-08","Mandatory Reporting Radiologist Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-12","Reporting Radiologist > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-01","Conform to the requirements for one, and only one, of the following conformance levels: 3A or 3B as defined in the Common Conformance Profile for Clinical Documents.","TBD",null,0]
[null,null,"(B5: UC.CIS.201 Upload a clinical document)",null,"Diagnostic Imaging Report is uploaded successfully.","TBD",null,0]
[null,null,null,"Test cases for UC.CIS.201 \n(note that requirement 024885 overrides PCEHR connecting systems requirement 019100)","Upload the clinical document.","TBD",null,0]
[null,null,"(B6: Record upload failure)","TC-DIRProc-11","Record upload failure.","TBD",null,0]
[null,null,"(B13: Record \"Document not uploaded\")","TC-DIRProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-DIRProc-16","The record has information about the failure to upload the report.","TBD",null,0]
[null,null,"Assess the conformance of the listed Diagnostic Imaging Report & CIS requirements","TC-DIRDoc-02","Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TBD",null,0]
[null,null,null,"TC-DIRDoc-03","The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.","TBD",null,0]
[null,null,null,"TC-DIRDoc-04","Various Diagnostic Imaging Report Results and Documents not nullflavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-05","SNOMED-CT-AU not nullFlavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-DIRDoc-20","Check the narrative and section title.","TBD",null,0]
[null,null,null,"TC-DIRDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-10","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-13","Report Date Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-14","Anatomical Location Instance.","TBD",null,0]
[null,null,null,"TC-DIRDoc-15","Anatomical Region is Name of Location.","TBD",null,0]
[null,null,null,"TC-DIRDoc-16","Appropriate Image Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-17","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-18","Image Location: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-19","Document target: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRProc-01","Clinical document producer SHALL NOT be a  registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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. ","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-DIRProc-15.2","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.001)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.001)","CIS  Audit.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.201)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019429 (UC.CIS.201)","CIS uses HPI-I.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019042 (UC.CIS.201)","Withdraw Consent.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017841a (UC.CIS.201)","CIS Retains Clinical info.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017839 (UC.CIS.201)","Clinical Document explicit command.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.201)","CIS Audit.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I158=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H114:H157) / (COUNT(H114:H157))","v":0}]
[]
[null,"Scenario:","TP-NewDoc-04  - New Diagnostic Imaging Report - Upload to My Health Record System (Initially Withheld & Not Uploaded, then Reversed Withhold decision & Uploaded)"]
[null,"Objective:","For a recipient of healthcare services who has indicated their consent to upload clinical documents to the My Health Record system:\nUsing the software system, author a new Diagnostic Imaging Report that includes one Diagnostic Imaging Examination Result. The author of the Diagnostic Imaging Report performs an action to withhold the document from being uploaded to the My Health Record system. The author then reverses the decision to withhold the Diagnostic Imaging Report from uploading to the My Health Record system.  The author performs an action to upload the report to the My Health Record system. The Diagnostic Imaging Report is uploaded to the My Health Record system successfully.\n\nDemonstrate that the software system has the ability to:\n1. Record the consent setting as \"No withdrawn consent\".\n2. Withhold the Diagnostic Imaging Report from being uploaded to the My Health Record system.\n3. Reverse the withhold decision to upload to the My Health Record system.\n4. Upload the Diagnostic Imaging Report to the My Health Record system.\n5. Record the original consent information as \"No withdrawn consent\".\n\nBusiness process models A, B & G. \nPath:  Start -> A9 -> A2 -> A8 -> A6 -> A7 -> B3 -> B5  -> B7 -> B13 -> B8 -> B5 -> B12 ->  G1 -> End\n\n"]
[null,"Priority:","Mandatory."]
[null,"Pre-requisites:","1. The healthcare individual has an IHI and a digital health record.\n2. The request for the diagnostic services states that the healthcare individual has indicated consent to upload to the My Health Record system.\n3. The request for the diagnostic services states the healthcare individual's name and sufficient demographic information is present in the request that is needed to successfully search the HI Service to obtain their IHI.\n4. The software system has been set up to successfully upload the diagnostic imaging reports to the My Health Record system.\n\n"]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,null,"A9: Enter the request details","-",null,"TBD",null,{"$f":"IF(F165=\"\",\"0\",IF(F165=\"Pass\",1,IF(F165=\"Fail\",0,IF(F165=\"TBD\",0,IF(F165=\"N/A\",1)))))","v":0}]
[null,"TP-NewDoc-04","(A2: Record \"No Withdrawn consent\")","TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,{"$f":"IF(F166=\"\",\"0\",IF(F166=\"Pass\",1,IF(F166=\"Fail\",0,IF(F166=\"TBD\",0,IF(F166=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-DIRProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,"(A8: Record \"digital health record exists\")","Test cases for UC.CIS.001\n(PCEHR connecting systems requirement 019100)",null,"TBD",null,0]
[null,null,"A6: Perform diagnostic tests ","-",null,"TBD",null,0]
[null,null,"A7: Author a Diagnostic Imaging Report","-",null,"TBD",null,0]
[null,null,"(B3: Prepare for upload)","TC-DIRDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-08","Mandatory Reporting Radiologist Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-12","Reporting Radiologist > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-01","Conform to the requirements for one, and only one, of the following conformance levels: 3A or 3B as defined in the Common Conformance Profile for Clinical Documents.","TBD",null,0]
[null,null,"Withhold the report from being uploaded to the My Health Record system","-",null,"TBD",null,0]
[null,null,"(B7. Withhold the report)","TC-DIRProc-13","Record a decision to not upload a diagnostic report.","TBD",null,0]
[null,null,null,null,"Diagnostic Imaging Report is uploaded successfully. ","TBD",null,0]
[null,null,"(B13: Record \"Document not uploaded\")","TC-DIRProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"(B8. Reverse a withhold decision)","TC-DIRProc-14","Record the reversal of a decision by a diagnostic service provider to not upload a diagnostic report.","TBD",null,{"$f":"IF(F180=\"\",\"0\",IF(F180=\"Pass\",1,IF(F180=\"Fail\",0,IF(F180=\"TBD\",0,IF(F180=\"N/A\",1)))))","v":0}]
[null,null,"(B5: UC.CIS.201 Upload a clinical document)",null,"Diagnostic Imaging Report is uploaded successfully. ","TBD",null,0]
[null,null,null,"Test cases for UC.CIS.201 \n(note that requirement 024885 overrides PCEHR connecting systems requirement 019100)","Upload the clinical document.","TBD",null,0]
[null,null,"(B12: Record \"Document uploaded\")","TC-DIRProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-DIRProc-16","The record has information about the decision to withhold the report, and the subsequent decision to reverse the decision to withhold the report.","TBD",null,0]
[null,null,"Assess the conformance of the listed Diagnostic Imaging Report & CIS requirements","TC-DIRDoc-02","Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TBD",null,0]
[null,null,null,"TC-DIRDoc-03","The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.\n","TBD",null,0]
[null,null,null,"TC-DIRDoc-04","Various Diagnostic Imaging Report Results and Documents not nullflavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-05","SNOMED-CT-AU not nullFlavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-DIRDoc-20","Check the narrative and section title.","TBD",null,0]
[null,null,null,"TC-DIRDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-10","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-13","Report Date Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-14","Anatomical Location Instance.","TBD",null,0]
[null,null,null,"TC-DIRDoc-15","Anatomical Region is Name of Location.","TBD",null,0]
[null,null,null,"TC-DIRDoc-16","Appropriate Image Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-17","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-18","Image Location: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-19","Document target: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRProc-01","Clinical document producer SHALL NOT be a  registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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. ","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-DIRProc-15.2","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.001)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.001)","CIS Audit.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.201)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019429 (UC.CIS.201)","CIS uses HPI-I.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019042 (UC.CIS.201)","Withdraw Consent.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017842a (UC.CIS.201)","CIS Identifies Uploads.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017841a (UC.CIS.201)","CIS Retains Clinical info.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017839 (UC.CIS.201)","Clinical Document explicit command.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.201)","CIS Audit.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I214=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H165:H213) / (COUNT(H165:H213))","v":0}]
[]
[null,"Scenario:","TP-NewDoc-05 - New Diagnostic Imaging Report Not Uploaded to My Health Record System (Consent Provided - Healthcare Identifier Failure)"]
[null,"Objective:","For a recipient of healthcare services who has indicated their consent to upload clinical documents to the My Health Record system: \nUsing the software system, author a new Diagnostic Imaging Report that includes one Diagnostic Imaging Examination Result. The author of the Diagnostic Imaging Report performs an action to upload the report to the My Health Record system. During the upload process, the software system finds the IHI in the request does not match the IHI in the HI Service for the healthcare individual.\n\nDemonstrate that the software system has the ability to:\n1. Check the healthcare identifiers to be used in the Diagnostic Imaging Report and prevent the Diagnostic Imaging Report from being uploaded to the My Health Record system in the event that the healthcare identifiers are found to be invalid. \n2. Record the original consent information as \"No withdrawn consent\".\n\nBusiness process models A, B & G. \nPath:  Start ->  A9 -> A2 -> A8 -> A6 -> A7 -> B3 -> B10 -> B13 -> G1 -> End \n"]
[null,"Priority:","Conditional (Validating an IHI received in a request for diagnostic imaging services is mandatory if the request is paper-based and if the software system allows the manual entry of the IHI, and optional if the request is electronic.)"]
[null,"Pre-requisites:","1. The healthcare individual has an IHI and a digital health record.\n2. The request for the diagnostic services states that the healthcare individual has indicated consent to upload to the My Health Record system.\n3. The request for the diagnostic services includes an IHI and the healthcare individual's demographic information.  When the healthcare individual's demographic information is looked up in the HI Service, the IHI found in the lookup DOES NOT match the IHI stated in the request.\n4. The software system has been set up to successfully upload the diagnostic imaging reports to the My Health Record system.\n\n\n"]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,null,"A9: Enter the request details","-",null,"TBD",null,{"$f":"IF(F221=\"\",\"0\",IF(F221=\"Pass\",1,IF(F221=\"Fail\",0,IF(F221=\"TBD\",0,IF(F221=\"N/A\",1)))))","v":0}]
[null,"TP-NewDoc-05","(A2: Record \"Withdrawn consent\")","TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,{"$f":"IF(F222=\"\",\"0\",IF(F222=\"Pass\",1,IF(F222=\"Fail\",0,IF(F222=\"TBD\",0,IF(F222=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-DIRProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,"(A8: Record \"digital health record exists\")","Test cases for UC.CIS.001\n(PCEHR connecting systems requirement 019100)",null,"TBD",null,0]
[null,null,"A6: Perform diagnostic tests ","-",null,"TBD",null,0]
[null,null,"A7: Author a Diagnostic Imaging Report","-",null,"TBD",null,0]
[null,null,"(B3: Prepare for upload)","TC-DIRDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-08","Mandatory Reporting Radiologist Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-12","Reporting Radiologist > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-01","Conform to the requirements for one, and only one, of the following conformance levels: 3A or 3B as defined in the Common Conformance Profile for Clinical Documents.","TBD",null,0]
[null,null,"(B10. Record any healthcare identifier failure)","TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,"(B13: Record \"Document not uploaded\")","TC-DIRProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-DIRProc-16","The record has information about the failure to upload the report due to an invalid healthcare identifier.","TBD",null,0]
[null,null,"Assess the conformance of the listed Diagnostic Imaging Report & CIS requirements","TC-DIRDoc-02","Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TBD",null,0]
[null,null,null,"TC-DIRDoc-03","The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.","TBD",null,0]
[null,null,null,"TC-DIRDoc-04","Various Diagnostic Imaging Report Results and Documents not nullflavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-05","SNOMED-CT-AU not nullFlavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-DIRDoc-20","Check the narrative and section title.","TBD",null,0]
[null,null,null,"TC-DIRDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-10","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-13","Report Date Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-14","Anatomical Location Instance.","TBD",null,0]
[null,null,null,"TC-DIRDoc-15","Anatomical Region is Name of Location.","TBD",null,0]
[null,null,null,"TC-DIRDoc-16","Appropriate Image Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-17","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-18","Image Location: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-19","Document target: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRProc-01","Clinical document producer SHALL NOT be a  registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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. ","TBD",null,0]
[null,null,null,"TC-DIRProc-15.2","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.001)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.001)","CIS Audit.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.201)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019429 (UC.CIS.201)","CIS uses HPI-I.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019042 (UC.CIS.201)","Withdraw Consent.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.201)","CIS Audit.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I260=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H221:H259) / (COUNT(H221:H259))","v":0}]
[]
[null,"Scenario:","TP-NewDoc-06  - New Diagnostic Imaging Report Not Uploaded to My Health Record System (Withdrawn Consent) - Copy Stored for Future use"]
[null,"Objective:","For a recipient of healthcare services who has stated the withdrawal of consent for the upload of documents to the My Health Record system: \nUsing the software system,  author a new Diagnostic Imaging Report that includes one Diagnostic Imaging Examination Result. \n\nDemonstrate that the software system has the ability to:\n1. Record the consent setting as \"Withdrawn consent\". \n2. Store a copy of the Diagnostic Imaging Report in the software system.\n3. Record the original consent information as \"Withdrawn consent\". \n\nBusiness process models A, B & G. \nPath:  Start -> A9 -> A3-> A8 ->  A6 -> A7 -> B2 -> B13 -> G1 -> End"]
[null,"Priority:","Mandatory"]
[null,"Pre-requisites:","1. The healthcare individual has an IHI and a digital health record.\n2. The request for the diagnostic services states that the healthcare individual has withdrawn the consent to upload to the My Health Record system.\n3. The request for the diagnostic services states the healthcare individual's name and sufficient demographic information is present in the request that is needed to successfully search the HI Service to obtain their IHI.\n4. The software system has been set up to successfully upload the diagnostic imaging reports to the My Health Record system.\n"]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,null,"A9: Enter the request details","-",null,"TBD",null,{"$f":"IF(F267=\"\",\"0\",IF(F267=\"Pass\",1,IF(F267=\"Fail\",0,IF(F267=\"TBD\",0,IF(F267=\"N/A\",1)))))","v":0}]
[null,"TP-NewDoc-06","(A3: Record \"Withdrawn consent\")","TC-DIRProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,{"$f":"IF(F268=\"\",\"0\",IF(F268=\"Pass\",1,IF(F268=\"Fail\",0,IF(F268=\"TBD\",0,IF(F268=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-DIRProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,"(A8: Record \"digital health record exists\")","Test cases for UC.CIS.001\n(PCEHR connecting systems requirement 019100)",null,"TBD",null,0]
[null,null,"A6: Perform diagnostic tests ","-",null,"TBD",null,0]
[null,null,"A7: Author a Diagnostic Imaging Report","-",null,"TBD",null,0]
[null,null,"(B2. Store a Diagnostic Imaging Report for a future upload)","TC-DIRProc-07","The Diagnostic Imaging Report is not uploaded to My Health Record system. \nA copy of the Diagnostic Imaging Report is saved to software system.","TBD",null,0]
[null,null,"(B13: Record \"Document not uploaded\")","TC-DIRProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-DIRProc-16","The record shows that the original consent setting is \"Withdrawn consent\".","TBD",null,0]
[null,null,"Assess the conformance of the listed Diagnostic Imaging Report & CIS requirements","TC-DIRDoc-02","Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TBD",null,0]
[null,null,null,"TC-DIRDoc-03","The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.","TBD",null,0]
[null,null,null,"TC-DIRDoc-04","Various Diagnostic Imaging Report Results and Documents not nullflavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-05","SNOMED-CT-AU not nullFlavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-DIRDoc-20","Check the narrative and section title.","TBD",null,0]
[null,null,null,"TC-DIRDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-08","Mandatory Reporting Radiologist Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-10","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-12","Reporting Radiologist > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-13","Report Date Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-14","Anatomical Location Instance.","TBD",null,0]
[null,null,null,"TC-DIRDoc-15","Anatomical Region is Name of Location.","TBD",null,0]
[null,null,null,"TC-DIRDoc-16","Appropriate Image Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-17","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-18","Image Location: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-19","Document target: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRProc-01","Clinical document producer SHALL NOT be a  registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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. ","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-DIRProc-15.2","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.001)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.001)","CIS Audit.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.201)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019429 (UC.CIS.201)","CIS uses HPI-I.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019042 (UC.CIS.201)","Withdraw Consent.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.201)","CIS Audit.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I307=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H267:H306) / (COUNT(H267:H306))","v":0}]
[]
[null,"Scenario:","TP-NewDoc-07 - New Diagnostic Imaging Report  Not Uploaded to My Health Record System (No Consent information - Digital Health Record Not Found in the My Health Record system)"]
[null,"Objective:","Using the software system, create a new Diagnostic Imaging Report for a recipient of healthcare services who has not provided any information of the consent in the request made to the software system. The search for the healthcare individual's health record in the My Health Record system returns \"digital health record not found\".\n\nDemonstrate that the software system has the ability to:\n1. Record the consent setting as \"No withdrawn consent\" when the recipient of the healthcare services has not provided any information on the consent in request made to the software system and the search for the healthcare Individual's health record in the My Health Record system returns \"digital health record not found\".\n2. Record the original consent information as \"No withdrawn consent\".\n\nBusiness process model A .\nPath:  Start -> A9 -> A4 -> A5 -> A6 -> A7 -> G1 -> End"]
[null,"Priority:","Mandatory"]
[null,"Pre-requisites:","1. The healthcare individual has an IHI and has no health record in the My Health Record system.\n2. The request for the diagnostic services states that the healthcare individual has not provided any information on the consent.\n"]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,null,"A9: Enter the request details","-",null,"TBD",null,{"$f":"IF(F314=\"\",\"0\",IF(F314=\"Pass\",1,IF(F314=\"Fail\",0,IF(F314=\"TBD\",0,IF(F314=\"N/A\",1)))))","v":0}]
[null,"TP-NewDoc-07","(A4. UC.CIS.001 Check if an advertised digital health record exists via doesPCEHRexist web service call)","TC-DIRProc-09, Test cases for UC.CIS.001 \n(note: requirement 024885 overrides PCEHR connecting systems requirement 019100)","\nInvoke doesPCEHRexist web service.\n","TBD",null,0]
[null,null,"(A5: Record \"No withdrawn consent\").",null,null,"TBD",null,0]
[null,null,null,"TC-DIRProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,"A6: Perform diagnostic tests ","-",null,"TBD",null,0]
[null,null,"A7: Author a Diagnostic Imaging Report","-","Diagnostic Imaging Report is not uploaded to the My Health Record system.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-DIRProc-16\n","The record shows that the original consent setting is \"No withdrawn consent\".","TBD",null,0]
[null,null,"Assess the conformance of the listed Diagnostic Imaging Report & CIS requirements","TC-DIRDoc-02","Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TBD",null,0]
[null,null,null,"TC-DIRDoc-03","The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.\n","TBD",null,0]
[null,null,null,"TC-DIRDoc-04","Various Diagnostic Imaging Report Results and Documents not nullflavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-05","SNOMED-CT-AU not nullFlavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-DIRDoc-20","Check the narrative and section title.","TBD",null,0]
[null,null,null,"TC-DIRDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-08","Mandatory Reporting Radiologist Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-10","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-12","Reporting Radiologist > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-13","Report Date Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-14","Anatomical Location Instance.","TBD",null,0]
[null,null,null,"TC-DIRDoc-15","Anatomical Region is Name of Location.","TBD",null,0]
[null,null,null,"TC-DIRDoc-16","Appropriate Image Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-17","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-18","Image Location: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-19","Document target: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRProc-01","Clinical document producer SHALL NOT be a  registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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. ","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-DIRProc-15.2","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.001)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.001)","CIS Audit.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.201)","CIS uses IHI","TBD",null,0]
[null,null,null,"PCEHR_CIS_019429 (UC.CIS.201)","CIS uses HPI-I.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019042 (UC.CIS.201)","Withdraw Consent.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.201)","CIS Audit.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I352=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H314:H351) / (COUNT(H314:H351))","v":0}]
[]
[null,"Scenario:","TP-NewDoc-08  - New Diagnostic Imaging Report Not Uploaded to My Health Record System (No Consent - My Health Record System returns an error)"]
[null,"Objective:","Using the software system, create a new Diagnostic Imaging Report for a recipient of healthcare services who has not provided any information of the consent in the request made to the software system. The search for the healthcare individual's health record in the My Health Record system returns an error. (The doesPCEHRExist service will return an error of PCEHR_ERROR_0004 if the healthcare provider organisation [i.e. the prescribing organisation] is not a PCEHR participant.)\n\nDemonstrate that the software system has the ability to:\n1. Record the consent setting as \"No withdrawn consent\" when the recipient of the healthcare services has not provided any information on the consent in request made to the software system and the search for the healthcare individual's health record in the My Health Record system returns an error.\n2. Record the original consent information as \"No withdrawn consent\".\n\nBusiness process model A & G. \n\nPath:  Start -> A9 -> A4 -> A5 -> A6 -> A7 -> G1 -> End\n"]
[null,"Priority:","Mandatory"]
[null,"Pre-requisites:","1. The healthcare individual has an IHI and has a health record in the My Health Record system.\n2. The request for the diagnostic services states that the healthcare individual has not provided any information on the consent.\n3. The software system is set up to return an error when the healthcare individual's health record is searched on the My Health Record system.\n"]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,null,"A9: Enter the request details","-",null,"TBD",null,{"$f":"IF(F359=\"\",\"0\",IF(F359=\"Pass\",1,IF(F359=\"Fail\",0,IF(F359=\"TBD\",0,IF(F359=\"N/A\",1)))))","v":0}]
[null,"TP-NewDoc-08","(A4. UC.CIS.001 Check if an advertised digital health record exists via doesPCEHRexist web service call)","TC-DIRProc-09, Test cases for UC.CIS.001 \n(note: requirement 024885 overrides PCEHR connecting systems requirement 019100)","Invoke doesPCEHRexist web service.\n","TBD",null,0]
[null,null,"(A5: Record \"No withdrawn consent\")",null,null,"TBD",null,0]
[null,null,null,"TC-DIRProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,"A6: Perform diagnostic tests ","-",null,"TBD",null,0]
[null,null,"A7: Author a Diagnostic Imaging Report","-","Diagnostic Imaging Report is not uploaded to the My Health Record system.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-DIRProc-16\n","The record shows that the original consent setting is \"No withdrawn consent\".","TBD",null,0]
[null,null,"Assess the conformance of the listed Diagnostic Imaging Report & CIS requirements","TC-DIRDoc-02","Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TBD",null,0]
[null,null,null,"TC-DIRDoc-03","The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.","TBD",null,0]
[null,null,null,"TC-DIRDoc-04","Various Diagnostic Imaging Report Results and Documents not nullflavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-05","SNOMED-CT-AU not nullFlavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-DIRDoc-20","Check the narrative and section title.","TBD",null,0]
[null,null,null,"TC-DIRDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-08","Mandatory Reporting Radiologist Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-10","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-12","Reporting Radiologist > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-13","Report Date Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-14","Anatomical Location Instance.","TBD",null,0]
[null,null,null,"TC-DIRDoc-15","Anatomical Region is Name of Location.","TBD",null,0]
[null,null,null,"TC-DIRDoc-16","Appropriate Image Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-17","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-18","Image Location: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-19","Document target: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRProc-01","Clinical document producer SHALL NOT be a  registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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. ","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-DIRProc-15.2","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.001)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.001)","CIS Audit.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.201)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019429 (UC.CIS.201)","CIS uses HPI-I.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019042 (UC.CIS.201)","Withdraw Consent.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.201)","CIS Audit.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I397=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H359:H396) / (COUNT(H359:H396))","v":0}]
[]
[null,"Scenario:","TP-NewDoc-09 - New Diagnostic Imaging Report Uploaded to My Health Record  (Consent Provided) - 2 Exam Results"]
[null,"Objective:","Using the software system, create a new Diagnostic Imaging Report containing two Diagnostic Imaging Examination results for a recipient of healthcare services who has indicated their consent to upload clinical documents to the My Health Record system. The author of the Diagnostic Imaging Report performs an action to upload the report to the My Health Record system. The Diagnostic Imaging Report is uploaded to the My Health Record system successfully.\n\nDemonstrate that the software system has the ability to:\n1. Create a conformant Diagnostic Imaging Report that has two Diagnostic Imaging Examination results.\n2. Store the Diagnostic Imaging Report on the software system.\n3. Upload the Diagnostic Imaging Report to the My Health Record system.\n\nBusiness process models A, B & G. \nPath: Start -> A9 -> A2 -> A8 -> A6  -> A7 -> B3 -> B5  -> B12 -> G1 -> End\n\n"]
[null,"Priority:","Conditional (Software system has the ability to provide multiple test results in the same document.)"]
[null,"Pre-requisites:","1. The healthcare individual has an IHI and a digital health record.\n2. The request for the diagnostic services states that the healthcare individual has indicated consent to upload the clinical documents to the My Health Record system.\n3. The request for the diagnostic services states the healthcare individual's name and sufficient demographic information is present in the request that is needed to successfully search the HI Service to obtain their IHI.\n4. The software system has been set up to successfully upload the diagnostic imaging reports to the My Health Record system.\n\n"]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,null,"A9: Enter the request details","-",null,"TBD",null,{"$f":"IF(F404=\"\",\"0\",IF(F404=\"Pass\",1,IF(F404=\"Fail\",0,IF(F404=\"TBD\",0,IF(F404=\"N/A\",1)))))","v":0}]
[null,"TP-NewDoc-09","(A2: Record \"No withdrawn consent\")","TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,{"$f":"IF(F405=\"\",\"0\",IF(F405=\"Pass\",1,IF(F405=\"Fail\",0,IF(F405=\"TBD\",0,IF(F405=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-DIRProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,"(A8: Record \"digital health record exists\")","Test cases for UC.CIS.001\n(PCEHR connecting systems requirement 019100)",null,"TBD",null,0]
[null,null,"A6: Perform diagnostic tests ","-",null,"TBD",null,0]
[null,null,"A6: Perform diagnostic tests ","-",null,"TBD",null,0]
[null,null,"A7: Author a Diagnostic Imaging Report","-",null,"TBD",null,0]
[null,null,"(B3: Prepare for upload)","TC-DIRDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-08","Mandatory Reporting Radiologist Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-12","Reporting Radiologist > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-01","Conform to the requirements for one, and only one, of the following conformance levels: 3A or 3B as defined in the Common Conformance Profile for Clinical Documents.","TBD",null,0]
[null,null,"(B5: UC.CIS.201 Upload a clinical document)",null,"1. Diagnostic Imaging Report has two Diagnostic Imaging Examination results. \n2. Diagnostic Imaging Report is uploaded successfully. \n","TBD",null,0]
[null,null,null,"Test cases for UC.CIS.201 \n(note that requirement 024885 overrides PCEHR connecting systems requirement 019100)","Upload the clinical document.","TBD",null,0]
[null,null,"(B12: Record \"Document uploaded\")","TC-DIRProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-DIRProc-16","The record shows that the original consent setting is \"No withdrawn consent\".","TBD",null,0]
[null,null,"Assess the conformance of the listed Diagnostic Imaging Report & CIS requirements","TC-DIRDoc-02","Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TBD",null,0]
[null,null,null,"TC-DIRDoc-03","The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.","TBD",null,0]
[null,null,null,"TC-DIRDoc-04","Various Diagnostic Imaging Report Results and Documents not nullflavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-05","SNOMED-CT-AU not nullFlavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-DIRDoc-20","Check the narrative and section title.","TBD",null,0]
[null,null,null,"TC-DIRDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-10","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-13","Report Date Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-14","Anatomical Location Instance.","TBD",null,0]
[null,null,null,"TC-DIRDoc-15","Anatomical Region is Name of Location.","TBD",null,0]
[null,null,null,"TC-DIRDoc-16","Appropriate Image Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-17","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-18","Image Location: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-19","Document target: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRProc-01","Clinical document producer SHALL NOT be a  registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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. ","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-DIRProc-15.2","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.001)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.001)","CIS Audit.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.201)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019429 (UC.CIS.201)","CIS uses HPI-I.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019042 (UC.CIS.201)","Withdraw Consent.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017842a (UC.CIS.201)","CIS Identifies Uploads.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017841a (UC.CIS.201)","CIS Retains Clinical info.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017839 (UC.CIS.201)","Clinical Document explicit command.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.201)","CIS Audit.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I449=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H404:H448) / (COUNT(H404:H448))","v":0}]
[]
[]
[]
[null,"Scenario","Percentage complete","Scenario status",null,{"$f":"COUNTIF($H$10:$H449,\"0\")","v":383},"Test Cases Failed or TBD","Fail"]
[null,"TP-NewDoc-01",{"$f":"I54","v":0},{"$f":"C54","v":"Incomplete"},null,{"$f":"COUNTIF($H$10:$H449,\"1\")","v":0},"Test cases Passed or N/A","Pass"]
[null,"TP-NewDoc-02",{"$f":"I107","v":0},{"$f":"C107","v":"Incomplete"},null,{"$f":"COUNTIF(H10:H449,\">=0\")","v":383},"Total Test cases","N/A"]
[null,"TP-NewDoc-03",{"$f":"I158","v":0},{"$f":"C158","v":"Incomplete"},null,{"$f":"SUM($F454/$F455)","v":0},"Test case % Passed or N/A","TBD"]
[null,"TP-NewDoc-04",{"$f":"I214","v":0},{"$f":"C214","v":"Incomplete"}]
[null,"TP-NewDoc-05",{"$f":"I260","v":0},{"$f":"C260","v":"Incomplete"}]
[null,"TP-NewDoc-06",{"$f":"I307","v":0},{"$f":"C307","v":"Incomplete"}]
[null,"TP-NewDoc-07",{"$f":"I352","v":0},{"$f":"C352","v":"Incomplete"}]
[null,"TP-NewDoc-08",{"$f":"I397","v":0},{"$f":"C397","v":"Incomplete"}]
[null,"TP-NewDoc-09",{"$f":"I449","v":0},{"$f":"C449","v":"Incomplete"}]
[]
[null,null,{"$f":"COUNTIF(D454:D462,\"Complete\")","v":0},"Scenarios Complete"]
[null,null,{"$f":"COUNTIF(D454:D462,\"Incomplete\")","v":9},"Scenarios Not Complete"]
[null,null,{"$f":"SUM($C$464:$C$465)","v":9},"Total Scenarios"]
[null,null,{"$f":"SUM($C$464)/($C$466)","v":0},"Scenario Completed (percentage)"]

{"sheet":"TP-Consent","index":3,"n_rows":156,"n_cols":9,"rows_kept":156,"cut":false,"hidden":false,"merged":[[126,2,126,6],[127,2,127,6],[128,2,128,6],[2,2,2,6],[4,2,4,6],[69,2,69,6],[125,2,125,6],[0,2,0,6],[1,2,1,6],[66,2,66,6],[67,2,67,6],[68,2,68,6],[28,2,28,6],[5,2,5,6],[6,2,6,6],[7,2,7,6],[27,2,27,6],[26,2,26,6],[25,2,25,6]]}
[null,"Test procedure:","TP-Consent: Change consent setting function"]
[null,"Overview:","To assess the conformance of a Diagnostic Imaging Report authoring system to the requirements that apply with the receipt of an indication of consent.\n\nThis business process is initiated upon the receipt of an indication of consent related to a previously received request for diagnostic imaging services. This business process includes requirements for managing consent, record keeping and uploading of stored Diagnostic Imaging Reports.\n\nConformance to the requirements associated with the business process is assessed through a set of test scenarios, where each scenario corresponds to a path through the model documented in the \"Process models\" worksheet. Test scenarios have been selected to achieve complete coverage of every sequence flow in the model, while reducing the duplication of tests. \n\nA test procedure has been developed for each scenario, where the procedure involved a set of activities and the application of selected test cases. Some test cases used in the scenarios have a \"conditional\" priority. Should the condition apply in the context of the test scenario they should be considered mandatory and be marked as Pass or Fail and not N/A. \n\nEach test scenario is passed when all the specified test cases have a status of \"Pass\".\n\nThe test scenarios apply test cases documented in this conformance test specification and in the Authoring Systems Conformance Test Specification [NEHTA-2209:2016].\n\nNote: The terms \"software system\", \"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 as are \"healthcare consumer\" and \"healthcare individual\"."]
[null,"Instructions:","A test scenario with the priority of \"Mandatory\" must be applied and passed by the software system before it may be declared conformant to the requirements. Any \"conditional\" test scenario is to be applied if the software system has the functionality required to support the test. For the \"conditional\" test scenario, if the software system does not have the required functionality then the test result to be recorded is \"N/A\" (not applicable). The overall test result is calculated from the result of each test scenario.\n\nThe test scenarios refer to test cases as follows, Test Cases commencing with the identifier:\n1. \"TC-DIRProc\" are listed in the FS-DIRProc feature set within this conformance test specification.\n2. \"TC-DIRDoc\" are listed in the FS-DIRDoc feature set within this conformance test specification.\n3. \"PCEHR_CIS\" are listed in the PCEHR Connecting Systems - Conformance Test Specification v1.6 [NEHTA-1299:2012].\n\nTasks surrounded by brackets, for example \"(A2: Record \"No Withdrawn consent\") \", are assumed to be automatically performed by the software system without requiring any action by the tester. Test cases to be applied often have a \"conditional\" status as they apply only in a specific context. As the scenarios have been designed to select that context then the test cases for each scenario must be applied and have a result of \"Pass\" before the software system can be declared as conformant. \n"]
[]
[null,"Scenario:","TP-Consent-01 - Change \"Withdrawn consent\" indicator from \"No withdrawn consent\" to \"Withdrawn consent\"."]
[null,"Objective:","Within the context of a single diagnostic services request, when there are no Diagnostic Imaging Reports resulting from the diagnostic services request that have been uploaded to the My Health Record system, demonstrate using the software system to change the consent setting from \"No Withdrawn consent\" to  \"Withdrawn consent\".\n\nWithin the context of a single diagnostic services request, change the consent setting from \"No Withdrawn consent\" to  \"Withdrawn consent\" for the healthcare individual who has no Diagnostic Imaging Reports present on the My Health Record system.\n\nBusiness process models D & G Path: Start -> D7 -> D6 -> G1 -> End"]
[null,"Priority:","Mandatory."]
[null,"Pre-requisites:","1. The healthcare individual has an IHI and a digital health record.\n2. The consent setting recorded for the healthcare individual is \"No Withdrawn consent\".\n3. The healthcare individual has no Diagnostic Imaging Reports present on the My Health Record system.\n"]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,null,"D7: Enter the indication of consent","-",null,"TBD",null,{"$f":"IF(F10=\"\",\"0\",IF(F10=\"Pass\",1,IF(F10=\"Fail\",0,IF(F10=\"TBD\",0,IF(F10=\"N/A\",1)))))","v":0}]
[null,"TP-Consent-01","Receive an indication of consent as \"Withdrawn consent\"","-",null,"TBD",null,0]
[null,null,"(D6: Record \"Withdrawn consent\")",null,null,"TBD",null,0]
[null,null,null,"TC-DIRProc-15.2","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-DIRProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-DIRProc-16","The record has information about the change of consent.","TBD",null,0]
[null,null,"Assess the conformance of the listed Diagnostic Imaging Report & CIS requirements","TC-DIRProc-01","Clinical document producer SHALL NOT be a  registered consumer portal or registered provider portal.","TBD",null,{"$f":"IF(F17=\"\",\"0\",IF(F17=\"Pass\",1,IF(F17=\"Fail\",0,IF(F17=\"TBD\",0,IF(F17=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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. ","TBD",null,0]
[null,null,null,"TC-DIRProc-10","Changing \"Withdrawn consent\" indicator.","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.001)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.001)","CIS Audit.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I24=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H10:H23) / (COUNT(H10:H23))","v":0}]
[]
[null,"Scenario:","TP-Consent-02  - Restrict the change in \"Withdrawn consent\" indicator value from \"No withdrawn consent\" to \"Withdrawn consent\",  where there exists one or more Diagnostic Imaging reports in My Health Record system."]
[null,"Objective:","Within the context of a single diagnostic services request, demonstrate that the software system has the ability to:\n1. Restrict the change in consent setting from \"No withdrawn consent\" to \"Withdrawn consent\" when there are one or more Diagnostic Imaging Reports resulting from the diagnostic services request that have been previously uploaded to the My Health Record system. \n\nWithin the context of a single diagnostic services request, change the consent setting from \"No withdrawn consent\" to \"Withdrawn consent\" for the healthcare individual who has one or more diagnostic reports resulting from the diagnostic services request have been previously uploaded to the My Health Record system.\n\nBusiness process model D & G. Path: Start -> D7 ->  G1 -> End"]
[null,"Priority:","Mandatory."]
[null,"Pre-requisites:","1. The healthcare individual has an IHI and a health record in the My Health Record system.\n2. The consent setting recorded for the healthcare individual is \"No withdrawn consent\". \n3. The healthcare individual has one or more Diagnostic Imaging Reports present (previously uploaded) on the My Health Record system.\n"]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,null,"D7: Enter the indication of consent (indicating the consent is withdrawn)","-",null,"TBD",null,{"$f":"IF(F31=\"\",\"0\",IF(F31=\"Pass\",1,IF(F31=\"Fail\",0,IF(F31=\"TBD\",0,IF(F31=\"N/A\",1)))))","v":0}]
[null,"TP-Consent-02","Receive an indication of consent as \"Withdrawn consent\"",null,"Changing \"Withdrawn consent\" indicator.\n","TBD",null,0]
[null,null,"(The software system determines that consent cannot be withdrawn)","-",null,"TBD",null,0]
[null,null,"Inform the user that consent cannot be withdrawn","-",null,"TBD",null,0]
[null,null,"Verify that the setting is \"No withdrawn consent\" ","-",null,"TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-DIRProc-16","Recorded information about Setting Changes available.","TBD",null,0]
[null,null,"Assess the conformance of the listed Diagnostic Imaging Report & CIS requirements","TC-DIRDoc-02","Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TBD",null,0]
[null,null,null,"TC-DIRDoc-03","The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.","TBD",null,0]
[null,null,null,"TC-DIRDoc-04","Various Diagnostic Imaging Report Results and Documents not nullflavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-05","SNOMED-CT-AU not nullFlavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-DIRDoc-20","Check the narrative and section title.","TBD",null,0]
[null,null,null,"TC-DIRDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-08","Mandatory Reporting Radiologist Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-10","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-12","Reporting Radiologist > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-13","Report Date Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-14","Anatomical Location Instance.","TBD",null,0]
[null,null,null,"TC-DIRDoc-15","Anatomical Region is Name of Location.","TBD",null,0]
[null,null,null,"TC-DIRDoc-16","Appropriate Image Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-17","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-18","Image Location: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-19","Document target: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRProc-01","Clinical document producer SHALL NOT be a  registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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. ","TBD",null,0]
[null,null,null,"TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-DIRProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"TC-DIRProc-15.2","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.001)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.001)","CIS Audit.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I65=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H31:H64) / (COUNT(H31:H64))","v":0}]
[]
[null,"Scenario:","TP-Consent-03 - Two encounters - Change the \"Withdrawn consent\" indicator value from \"Withdrawn consent\" to \"No withdrawn consent\". Upload latest version of Diagnostic Imaging Report to My Health Record system from the second encounter."]
[null,"Objective:","While testing the healthcare services software in the context of two diagnostic service requests, demonstrate that the software system has the ability to:\n1. Change the consent setting from \"Withdrawn consent\" to \"No withdrawn consent\" in the second diagnostic service request.\n2. Upload the Diagnostic Imaging Report to the My Health Record system from the second diagnostic service request.\n\nin the first diagnostic service request, create a new Diagnostic Imaging Report (call it as Document A) for a recipient of healthcare services who has withdrawn the consent to upload clinical documents to the My Health Record system. For the same recipient, in the second diagnostic service request, create a second Diagnostic Imaging Report (call it as Document B). The healthcare recipient changes the consent setting from \"Withdrawn consent\" to \"No withdrawn consent\" in the second diagnostic service request. The software shall upload the second Diagnostic Imaging Report (Document B) and not the first Diagnostic Imaging Report (Document A). \n\nBusiness process model D, B & G. Path: Start -> D7 -> D2 -> D4 -> B3 -> B5 -> B12 -> G1 -> End\n\n"]
[null,"Priority:","Mandatory."]
[null,"Pre-requisites:","1. The healthcare individual has an IHI and a health record in the My Health Record system.\n2. The consent setting recorded for the healthcare individual is \"Withdrawn consent\".\n"]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,null,"Create a new diagnostic service request (First diagnostic service request)","-",null,"TBD",null,{"$f":"IF(F72=\"\",\"0\",IF(F72=\"Pass\",1,IF(F72=\"Fail\",0,IF(F72=\"TBD\",0,IF(F72=\"N/A\",1)))))","v":0}]
[null,"TP-Consent-03","D7: Enter the indication of consent (as  \"Withdrawn consent\")","-",null,"TBD",null,0]
[null,null,"Receive an indication of consent as \"No withdrawn consent\"","TC-DIRProc-10","Changing \"Withdrawn consent\" indicator.\n","TBD",null,0]
[null,null,"(D2: Record \"Withdrawn consent\")",null,null,"TBD",null,0]
[null,null,null,"TC-DIRProc-15.2","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-DIRProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,"A6: Perform diagnostic tests (First diagnostic service request)","-",null,"TBD"]
[null,null,"A7: Author a Diagnostic Imaging Report\n(Call it as Document A)","-",null,"TBD",null,{"$f":"IF(F80=\"\",\"0\",IF(F80=\"Pass\",1,IF(F80=\"Fail\",0,IF(F80=\"TBD\",0,IF(F80=\"N/A\",1)))))","v":0}]
[null,null,"Create a new diagnostic service request (Second diagnostic service request)","-",null,"TBD",null,0]
[null,null,"A6: Perform diagnostic tests (Second diagnostic service request)","-",null,"TBD",null,0]
[null,null,"A7: Author a Diagnostic Imaging Report\n(Call it as Document B)","TC-DIRProc-05","\"Withdrawn consent\" indicator value is recorded as \"Withdrawn consent\".","TBD",null,0]
[null,null,"D7: Enter the indication of consent (of  \"No withdrawn consent\")","-",null,"TBD",null,{"$f":"IF(F84=\"\",\"0\",IF(F84=\"Pass\",1,IF(F84=\"Fail\",0,IF(F84=\"TBD\",0,IF(F84=\"N/A\",1)))))","v":0}]
[null,null,"Receive an indication of consent as \"No withdrawn consent\"","TC-DIRProc-10","Changing \"Withdrawn consent\" indicator.\n","TBD",null,0]
[null,null,"(D2: Record \"No withdrawn consent\")","-",null,"TBD",null,0]
[null,null,null,"TC-DIRProc-15.2","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-DIRProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,"(D4: Select the latest version of the Diagnostic Imaging Report (task))","-","Diagnostic Imaging Report (Document B) from the second diagnostic service request is selected for the upload.","TBD",null,0]
[null,null,"(B3: Prepare for upload)","TC-DIRDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-08","Mandatory Reporting Radiologist Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-12","Reporting Radiologist > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-01","Conform to the requirements for one, and only one, of the following conformance levels: 3A or 3B as defined in the Common Conformance Profile for Clinical Documents.","TBD",null,0]
[null,null,"(B5: UC.CIS.201 Upload a clinical document)",null,"Upload the Diagnostic Imaging Report to the My Health Record system from the second diagnostic service request.","TBD",null,0]
[null,null,null,"Test cases for UC.CIS.201 \n(note that requirement 024885 overrides PCEHR connecting systems requirement 019100)","Upload the clinical document.","TBD",null,0]
[null,null,"(B12: Record \"Document uploaded\")","TC-DIRProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-DIRProc-16","The record has information about the change of consent.","TBD",null,0]
[null,null,"Assess the conformance of the listed Diagnostic Imaging Report & CIS requirements","TC-DIRDoc-02","Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TBD",null,0]
[null,null,null,"TC-DIRDoc-03","The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.","TBD",null,0]
[null,null,null,"TC-DIRDoc-04","Various Diagnostic Imaging Report Results and Documents not nullflavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-05","SNOMED-CT-AU not nullFlavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-DIRDoc-20","Check the narrative and section title.","TBD",null,0]
[null,null,null,"TC-DIRDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-10","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-13","Report Date Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-14","Anatomical Location Instance.","TBD",null,0]
[null,null,null,"TC-DIRDoc-15","Anatomical Region is Name of Location.","TBD",null,0]
[null,null,null,"TC-DIRDoc-16","Appropriate Image Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-17","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-18","Image Location: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-19","Document target: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRProc-01","Clinical document producer SHALL NOT be a  registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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. ","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.001)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.001)","CIS Audit.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017842a (UC.CIS.201)","CIS Identifies Uploads.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017841a (UC.CIS.201)","CIS Retains Clinical info.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017839 (UC.CIS.201)","Clinical Document explicit command.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I124=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H73:H123) / (COUNT(H73:H123))","v":0}]
[]
[null,"Scenario:","TP-Consent-04 - Change \"Withdrawn consent\" indicator value from \"Withdrawn consent\" to \"No withdrawn consent\" when no Diagnostic Imaging Reports are stored on the software system."]
[null,"Objective:","Within the context of a single diagnostic services request, demonstrate that the software system has the ability to:\n1. Change the consent setting from \"Withdrawn consent\" to \"No withdrawn consent\".\n\nWithin the context of a single diagnostic services request, change the consent setting from  \"Withdrawn consent\" to \"No withdrawn consent\" for the healthcare individual when no Diagnostic Imaging Reports resulting from the diagnostic services request have been stored on the software system. \n\nBusiness process models D & G. Path: Start -> D7 -> D2 -> G1 -> End\n\n"]
[null,"Priority:","Mandatory."]
[null,"Pre-requisites:","1. The healthcare individual has an IHI and a health record in the My Health Record system.\n2. The consent setting recorded for the healthcare individual is \"Withdrawn consent\".\n3. The healthcare individual has no Diagnostic Imaging Reports stored on the software system.\n"]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,null,"D7: Enter the indication of consent (of  \"No withdrawn consent\")","-",null,"TBD",null,{"$f":"IF(F131=\"\",\"0\",IF(F131=\"Pass\",1,IF(F131=\"Fail\",0,IF(F131=\"TBD\",0,IF(F131=\"N/A\",1)))))","v":0}]
[null,"TP-Consent-04","Receive an indication of consent as \"No withdrawn consent\"","TC-DIRProc-10","Changing \"Withdrawn consent\" indicator.\n","TBD",null,{"$f":"IF(F132=\"\",\"0\",IF(F132=\"Pass\",1,IF(F132=\"Fail\",0,IF(F132=\"TBD\",0,IF(F132=\"N/A\",1)))))","v":0}]
[null,null,"(D2: Record \"No withdrawn consent\")",null,null,"TBD",null,0]
[null,null,null,"TC-DIRProc-15.2","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-DIRProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-DIRProc-16","The record has information about the change of consent.","TBD",null,0]
[null,null,"Assess the conformance of the listed Diagnostic Imaging Report & CIS requirements","TC-DIRProc-01","Clinical document producer SHALL NOT be a  registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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. ","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.001)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.001)","CIS Audit.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I144=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H131:H143) / (COUNT(H131:H143))","v":0}]
[]
[]
[null,"Scenario","Percentage complete","Scenario status",null,{"$f":"COUNTIF($H$10:$H144,\"0\")","v":112},"Test Cases Failed or TBD","Fail"]
[null,"TP-Consent-01",{"$f":"I24","v":0},{"$f":"C24","v":"Incomplete"},null,{"$f":"COUNTIF($H$10:$H144,\"1\")","v":0},"Test cases Passed or N/A","Pass"]
[null,"TP-Consent-02",{"$f":"I65","v":0},{"$f":"C65","v":"Incomplete"},null,{"$f":"COUNTIF($H$10:$H144,\">=0\")","v":112},"Total Test cases","N/A"]
[null,"TP-Consent-03",{"$f":"I124","v":0},{"$f":"C124","v":"Incomplete"},null,{"$f":"SUM($F148/$F149)","v":0},"Test case % Passed or N/A","TBD"]
[null,"TP-Consent-04",{"$f":"I144","v":0},{"$f":"C144","v":"Incomplete"}]
[]
[null,null,{"$f":"COUNTIF($D$148:$D$151,\"Complete\")","v":0},"Scenarios Complete"]
[null,null,{"$f":"COUNTIF($D$148:$D$151,\"Incomplete\")","v":4},"Scenarios Not Complete"]
[null,null,{"$f":"SUM($C$153:$C$154)","v":4},"Total Scenarios"]
[null,null,{"$f":"$C$153/$C$155","v":0},"Scenarios percentage Completed."]

{"sheet":"TP-Supersede","index":4,"n_rows":155,"n_cols":9,"rows_kept":155,"cut":false,"hidden":false,"merged":[[102,2,102,6],[103,2,103,6],[104,2,104,6],[105,2,105,6],[0,2,0,6],[1,2,1,6],[2,2,2,6],[4,2,4,6],[6,2,6,6],[50,2,50,6],[51,2,51,6],[52,2,52,6],[53,2,53,6],[5,2,5,6],[7,2,7,6]]}
[null,"Test procedure:","TP-Supersede: Supersede a Diagnostic Imaging Report function"]
[null,"Overview:","To assess the conformance of a Diagnostic Imaging Report authoring system to the requirements that apply to the process of superseding a Diagnostic Imaging Report that was uploaded to the My Health Record system.\n\nThe business process of superseding a Diagnostic Imaging Report is initiated when an author of a previously created diagnostic imaging report decides to create a new report to replace the previous one. The process includes requirements for managing consent and record keeping, as well as creating the replacement Diagnostic Imaging Report and CDA package to be sent to the My Health Record system. \n\nConformance to the requirements associated with the business process is assessed through a set of test scenarios, where each scenario corresponds to a path through the model documented in the \"Process models\" worksheet. Test scenarios have been selected to achieve complete coverage of every sequence flow in the model, while reducing the duplication of tests. \n\nA test procedure has been developed for each scenario, where the procedure involved a set of activities and the application of selected test cases. Some test cases used in the scenarios have a \"conditional\" priority.  Should the condition apply in the context of the test scenario they should be considered mandatory and be marked as Pass or Fail and not N/A.  Each test scenario is passed when all the specified test cases have a status of \"Pass\".\n\nNote: The terms \"software system\", \"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 as are \"healthcare consumer\" and \"healthcare individual\"."]
[null,"Instructions:","A test scenario with the priority of \"Mandatory\" must be applied and passed by the software system before it may be declared conformant to the requirements. Any \"conditional\" test scenario is to be applied if the software system has the functionality required to support the test. For the \"conditional\" test scenario, if the software system does not have the required functionality then the test result to be recorded is \"N/A\" (not applicable). The overall test result is calculated from the result of each test scenario.\n\nThe test scenarios refer to test cases as follows, Test Cases commencing with the identifier:\n1. \"TC-DIRProc\" are listed in the FS-DIRProc feature set within this conformance test specification.\n2. \"TC-DIRDoc\" are listed in the FS-DIRDoc feature set within this conformance test specification.\n3. \"PCEHR_CIS\" are listed in the PCEHR Connecting Systems - Conformance Test Specification v1.6 [NEHTA-1299:2012].\n\nTasks surrounded by brackets, for example \"(A2: Record \"No Withdrawn consent\") \", are assumed to be automatically performed by the software system without requiring any action by the tester. Test cases to be applied often have a \"conditional\" status as they apply only in a specific context. As the scenarios have been designed to select that context then the test cases for each scenario must be applied and have a result of \"Pass\" before the software system can be declared as conformant. \n"]
[]
[null,"Scenario:","TP-Supersede-01 - Create a replacement Diagnostic Imaging Report - Store the report  on the software system and upload it to My Health Record system."]
[null,"Objective:","To demonstrate that the software system has the ability to:\n1. Create a replacement Diagnostic Imaging Report to supersede an existing Diagnostic Imaging Report that was previously uploaded to the My Health Record system.\n2. Store the replacement Diagnostic Imaging Report on the software system.\n3. Upload the replacement Diagnostic Imaging Report to the My Health Record system.\n\nUsing the software system, for a healthcare individual, create a replacement Diagnostic Imaging Report to supersede an existing Diagnostic Imaging Report that was previously uploaded to the My Health Record system. The healthcare individual has indicated their consent to upload clinical documents to the My Health Record system. The author performs an action to upload the replacement Diagnostic Imaging Report to the My Health Record system. \n\nBusiness process model E , B & G. Path: Start -> E1 -> B3 -> B9 -> B12 -> G1 -> End"]
[null,"Priority:","Mandatory."]
[null,"Pre-requisites:","To apply this test scenario, a Diagnostic Imaging Report must previously have been created by the software system and uploaded to the My Health Record system.\n1. The healthcare individual has an IHI and a health record in the My Health Record system.\n2. The request for the diagnostic services states that the healthcare individual has indicated consent to upload to the My Health Record system.\n3. The request for the diagnostic services states the healthcare individual's name and sufficient demographic information is present in the request, as is needed to successfully search the HI Service to obtain their IHI.\n4. The request for the diagnostic services states the healthcare individual has at least one previously uploaded Diagnostic Imaging Report in the My Health Record system.\n5 The software system has been set up to successfully upload the diagnostic imaging reports to the My Health Record system.\n"]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,"TP-Supersede-01","E1: Create a replacement Diagnostic Imaging Report","TC-DIRDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,{"$f":"IF(F10=\"\",\"0\",IF(F10=\"Pass\",1,IF(F10=\"Fail\",0,IF(F10=\"TBD\",0,IF(F10=\"N/A\",1)))))","v":0}]
[null,null,"(B3: Prepare for upload)","TC-DIRDoc-07","Mandatory Document Author Values used.","TBD",null,{"$f":"IF(F11=\"\",\"0\",IF(F11=\"Pass\",1,IF(F11=\"Fail\",0,IF(F11=\"TBD\",0,IF(F11=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-DIRDoc-08","Mandatory Reporting Radiologist Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-12","Reporting Radiologist > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-01","Conform to the requirements for one, and only one, of the following conformance levels: 3A or 3B as defined in the Common Conformance Profile for Clinical Documents.","TBD",null,0]
[null,null,"B9: UC.CIS.202 Supersede a clinical document",null,null,"TBD",null,0]
[null,null,null,"Test cases for UC.CIS.202 \n(note that requirement 024885 overrides PCEHR connecting systems requirement 019100)","Supersede a clinical document.","TBD",null,0]
[null,null,"(B12: Record \"Document uploaded\")","TC-DIRProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-DIRProc-16","The record shows that the original consent setting is \"No withdrawn consent\".","TBD",null,0]
[null,null,"Assess the conformance of the listed Diagnostic Imaging Report & CIS requirements","TC-DIRDoc-02","Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TBD",null,0]
[null,null,null,"TC-DIRDoc-03","The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.","TBD",null,0]
[null,null,null,"TC-DIRDoc-04","Various Diagnostic Imaging Report Results and Documents not nullflavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-05","SNOMED-CT-AU not nullFlavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-DIRDoc-20","Check the narrative and section title.","TBD",null,0]
[null,null,null,"TC-DIRDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-10","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-13","Report Date Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-14","Anatomical Location Instance.","TBD",null,0]
[null,null,null,"TC-DIRDoc-15","Anatomical Region is Name of Location.","TBD",null,0]
[null,null,null,"TC-DIRDoc-16","Appropriate Image Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-17","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-18","Image Location: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-19","Document target: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRProc-01","Clinical document producer SHALL NOT be a  registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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.","TBD",null,0]
[null,null,null,"TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-DIRProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"TC-DIRProc-15.2","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.001)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.001)","CIS Audit.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019429 (UC.CIS.202)","CIS uses HPI-I.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019042 (UC.CIS.202)","Withdraw Consent.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017842b (UC.CIS.202)","CIS Identifies Uploads.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017841b (UC.CIS.202)","CIS Retains Clinical info.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017839 (UC.CIS.202)","Clinical Document explicit command.","TBD",null,0]
[null,null,null,"PCEHR_CIS_018338 (UC.CIS.202)","CIS Supersede.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I49=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H10:H48) / (COUNT(H10:H48))","v":0}]
[]
[null,"Scenario:","TP-Supersede-02 - Create a replacement Diagnostic Imaging Report - Upload to My Health Record System (Initially Withheld & Not Uploaded, then Reversed Withhold decision & Uploaded to My Health Record system)"]
[null,"Objective:","To demonstrate that the software system has the ability to:\n1. Create a replacement Diagnostic Imaging Report to supersede an existing Diagnostic Imaging Report that was previously uploaded to the My Health Record system.\n2. Allow the author to withhold the Diagnostic Imaging Report from uploading to the My Health Record system.\n3. Allow the author to reverse the withhold decision.\n4. Upload the replacement Diagnostic Imaging Report to the My Health Record system.\n\nUsing the software system, for a healthcare individual, create a replacement Diagnostic Imaging Report to supersede an existing Diagnostic Imaging Report that was previously uploaded to the My Health Record system. The healthcare individual has indicated their consent to upload clinical documents to the My Health Record system. The author performs an action to withhold the document from being uploaded to the My Health Record system. The author then reverses his decision to withhold the Diagnostic Imaging Report  from uploading to the My Health Record system. The replacement Diagnostic Imaging Report is successfully uploaded to the My Health Record system and the decision to withhold the report, and then reverse the decision, is recorded.\n\nBusiness process model E, B & G. Path: Start -> E1 -> B3 -> B9 -> B7 -> B13 -> B8 -> B9 -> B12 ->  G1 -> End\n"]
[null,"Priority:","Mandatory."]
[null,"Pre-requisites:","To apply this test scenario a Diagnostic Imaging Report must previously have been created by the software system and uploaded to the My Health Record system.\n1. The healthcare individual has an IHI and a health record in the My Health Record system.\n2. The request for the diagnostic services states that the healthcare individual has indicated consent to upload to the My Health Record system.\n3. The request for the diagnostic services states the healthcare individual's name and sufficient demographic information is present in the request, that is needed to successfully search the HI Service to obtain their IHI.\n4. The request for the diagnostic services states the healthcare individual has at least one previously uploaded diagnostic imaging report in My Health Record system.\n5. The software system has been set up to successfully upload the diagnostic imaging reports to the My Health Record system.\n"]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,"TP-Supersede-02","E1: Create a replacement Diagnostic Imaging Report","TC-DIRDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,{"$f":"IF(F56=\"\",\"0\",IF(F56=\"Pass\",1,IF(F56=\"Fail\",0,IF(F56=\"TBD\",0,IF(F56=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-DIRDoc-08","Mandatory Reporting Radiologist Values used.","TBD",null,{"$f":"IF(F57=\"\",\"0\",IF(F57=\"Pass\",1,IF(F57=\"Fail\",0,IF(F57=\"TBD\",0,IF(F57=\"N/A\",1)))))","v":0}]
[null,null,"(B3: Prepare for upload)","TC-DIRDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-12","Appropriate  Reporting Radiologist, Participant, Entity Identifier Value.","TBD",null,0]
[null,null,null,"TC-DIRDoc-01","Conform to the requirements for one, and only one, of the following conformance levels: 3A or 3B as defined in the Common Conformance Profile for Clinical Documents.","TBD",null,0]
[null,null,"B9: UC.CIS.202 Supersede a clinical document",null,null,"TBD",null,0]
[null,null,null,"Test cases for UC.CIS.202 (note that requirement 024885 overrides PCEHR connecting systems requirement 019100)",null,"TBD",null,0]
[null,null,"B7: Withhold the report",null,null,"TBD",null,0]
[null,null,null,"TC-DIRProc-13","Record a decision to not upload a diagnostic report.","TBD",null,0]
[null,null,"(B13: Record \"Document not uploaded\")",null,null,"TBD",null,0]
[null,null,"B8. Reverse a withhold decision","TC-DIRProc-14","Record the reversal of a decision by a diagnostic service provider to not upload a diagnostic report.","TBD",null,{"$f":"IF(F66=\"\",\"0\",IF(F66=\"Pass\",1,IF(F66=\"Fail\",0,IF(F66=\"TBD\",0,IF(F66=\"N/A\",1)))))","v":0}]
[null,null,"B9: UC.CIS.202 Supersede a clinical document",null,"1. Diagnostic Imaging Report upload decision withheld.\n2. Diagnostic Imaging Report upload withheld decision is reversed.\n3. Diagnostic Imaging Report is uploaded successfully.","TBD",null,0]
[null,null,null,"Test cases for UC.CIS.202 (note that requirement 024885 overrides PCEHR connecting systems requirement 019100)","Supersede a clinical document.","TBD",null,0]
[null,null,"(B12: Record \"Document uploaded\")","TC-DIRProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-DIRProc-16","The record has information about the decision to withhold the report, and the subsequent decision to reverse the decision to withhold the report.","TBD",null,0]
[null,null,"Assess the conformance of the listed Diagnostic Imaging Report & CIS requirements","TC-DIRDoc-02","Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TBD",null,0]
[null,null,null,"TC-DIRDoc-03","The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.","TBD",null,0]
[null,null,null,"TC-DIRDoc-04","Various Diagnostic Imaging Report Results and Documents not nullflavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-05","SNOMED-CT-AU not nullFlavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-DIRDoc-20","Check the narrative and section title.","TBD",null,0]
[null,null,null,"TC-DIRDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-10","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-13","Report Date Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-14","Anatomical Location Instance.","TBD",null,0]
[null,null,null,"TC-DIRDoc-15","Anatomical Region is Name of Location.","TBD",null,0]
[null,null,null,"TC-DIRDoc-16","Appropriate Image Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-17","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-18","Image Location: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-19","Document target: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRProc-01","Clinical document producer SHALL NOT be a  registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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. ","TBD",null,0]
[null,null,null,"TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-DIRProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"TC-DIRProc-15.2","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.001)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.001)","CIS Audit.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019429 (UC.CIS.202)","CIS uses HPI-I.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019042 (UC.CIS.202)","Withdraw Consent.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017842b (UC.CIS.202)","CIS Identifies Uploads.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017841b (UC.CIS.202)","CIS Retains Clinical info.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017839 (UC.CIS.202)","Clinical Document explicit command.","TBD",null,0]
[null,null,null,"PCEHR_CIS_018338 (UC.CIS.202)","CIS Supersede.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I101=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H56:H100) / (COUNT(H56:H100))","v":0}]
[]
[null,"Scenario:","TP-Supersede-03 - Replace a previously stored Diagnostic Imaging Report and store the replacement Diagnostic Imaging Report on the software system."]
[null,"Objective:","To demonstrate that the software system has the ability to:\n1. Find a previously stored Diagnostic Imaging Report.\n2. Create a replacement Diagnostic Imaging Report to supersede a Diagnostic Imaging Report stored by the software system.\n3. Store the replacement Diagnostic Imaging Report.\n\nUsing the software system, for a healthcare individual, create a replacement Diagnostic Imaging Report to supersede an existing Diagnostic Imaging Report that is stored by the software system. The healthcare individual has indicated his withdrawal of  consent to upload clinical documents to the My Health Record system.  The replacement Diagnostic Imaging Report is successfully stored to the software system.\n\nBusiness process model E , B & G. Path: Start -> E1 -> B2 -> B13 -> G1 -> End\n"]
[null,"Priority:","Mandatory"]
[null,"Pre-requisites:","To apply this test scenario a Diagnostic Imaging Report must previously have been created by the software system.\n1. The healthcare individual has an IHI and a health record in the My Health Record system.\n2. The request for the diagnostic services states that the healthcare individual has withdrawn the consent to upload to the My Health Record system.\n3. The request for the diagnostic services states the healthcare individual's name and sufficient demographic information is present in the request, that is needed to successfully search the HI Service to obtain their IHI.\n4. The request for the diagnostic services states the healthcare individual has at least one previously uploaded diagnostic imaging report in My Health Record system.\n5. The software system has been set up to successfully upload the diagnostic imaging reports to the My Health Record system.\n"]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,"TP-Supersede-03","E1: Create a replacement Diagnostic Imaging Report","TC-DIRDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,{"$f":"IF(F108=\"\",\"0\",IF(F108=\"Pass\",1,IF(F108=\"Fail\",0,IF(F108=\"TBD\",0,IF(F108=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-DIRDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-08","Mandatory Reporting Radiologist Values used.","TBD",null,0]
[null,null,"(B2: Store a Diagnostic Imaging Report for a future upload)","TC-DIRProc-07","The Diagnostic Imaging Report is not uploaded to My Health Record system. A copy of the Diagnostic Imaging Report is saved to software system.","TBD",null,0]
[null,null,"(B13: Record \"Document not uploaded\")","TC-DIRProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-DIRProc-16","The record has information about the decision to withhold the report, and the subsequent decision to reverse the decision to withhold the report.","TBD",null,0]
[null,null,"Assess the conformance of the listed Diagnostic Imaging Report & CIS requirements","TC-DIRDoc-02","Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TBD",null,0]
[null,null,null,"TC-DIRDoc-03","The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.","TBD",null,0]
[null,null,null,"TC-DIRDoc-04","Various Diagnostic Imaging Report Results and Documents not nullflavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-05","SNOMED-CT-AU not nullFlavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-DIRDoc-20","Check the narrative and section title.","TBD",null,0]
[null,null,null,"TC-DIRDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-10","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-12","Reporting Radiologist > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-13","Report Date Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-14","Anatomical Location Instance.","TBD",null,0]
[null,null,null,"TC-DIRDoc-15","Anatomical Region is Name of Location.","TBD",null,0]
[null,null,null,"TC-DIRDoc-16","Appropriate Image Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-17","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-18","Image Location: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-19","Document target: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRProc-01","Clinical document producer SHALL NOT be a  registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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.","TBD",null,0]
[null,null,null,"TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-DIRProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"TC-DIRProc-15.2","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.001)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.001)","CIS Audit.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019429 (UC.CIS.202)","CIS uses HPI-I.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019042 (UC.CIS.202)","Withdraw Consent.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017841b (UC.CIS.202)","CIS Retains Clinical info.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017839 (UC.CIS.202)","Clinical Document explicit command.","TBD",null,0]
[null,null,null,"PCEHR_CIS_018338 (UC.CIS.202)","CIS Supersede.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I144=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H108:H143) / (COUNT(H108:H143))","v":0}]
[]
[]
[null,"Scenario","Percentage complete","Scenario status",null,{"$f":"COUNTIF($H$10:$H144,\"0\")","v":120},"Test Cases Failed or TBD","Fail"]
[null,"TP-Supersede-01",{"$f":"I49","v":0},{"$f":"C49","v":"Incomplete"},null,{"$f":"COUNTIF($H$10:$H144,\"1\")","v":0},"Test cases Passed or N/A","Pass"]
[null,"TP-Supersede-02",{"$f":"I101","v":0},{"$f":"C101","v":"Incomplete"},null,{"$f":"COUNTIF($H$10:$H144,\">=0\")","v":120},"Total Test cases","N/A"]
[null,"TP-Supersede-03",{"$f":"I144","v":0},{"$f":"C144","v":"Incomplete"},null,{"$f":"SUM($F148/$F149)","v":0},"Test case % Passed or N/A","TBD"]
[]
[null,null,{"$f":"COUNTIF(D148:D150,\"Complete\")","v":0},"Scenarios Complete"]
[null,null,{"$f":"COUNTIF(D148:D150,\"Incomplete\")","v":3},"Scenarios Not Complete"]
[null,null,{"$f":"SUM(C152:C153)","v":3},"Total Scenarios"]
[null,null,{"$f":"SUM(C152) / (C154)","v":0},"Scenarios percentage Completed."]

{"sheet":"TP-Remove","index":5,"n_rows":32,"n_cols":9,"rows_kept":32,"cut":false,"hidden":false,"merged":[[7,2,7,6],[0,2,0,6],[1,2,1,6],[2,2,2,6],[6,2,6,6],[5,2,5,6],[4,2,4,6]]}
[null,"Test procedure:","TP-Remove: Remove a Diagnostic Imaging Report function"]
[null,"Overview:","To assess the conformance of a diagnostic imaging report authoring system to the requirements that apply to the process of removing a diagnostic imaging report from the My Health Record system.\n\nThe business process of removing a diagnostic imaging report is initiated by the report author, the requester for diagnostic imaging service, or the healthcare individual.\n\nConformance to the requirements associated with the business process is assessed through test scenarios, where each scenario corresponds to a path through the model documented in the \"Process models\" worksheet. Test scenarios have been selected to achieve complete coverage of every sequence flow in the model, while reducing the duplication of tests. \n\nA test procedure has been developed for each scenario, where the procedure involves a set of activities and the application of selected test cases. Some test cases used in the scenarios have a \"conditional\" priority. Should the condition apply in the context of the test scenario they should be considered mandatory and be marked as Pass or Fail and not N/A.  Each test scenario is passed when all the specified test cases have a status of \"Pass\".\n\nNote: The terms \"software system\", \"authoring system\", \"CIS producer\" and \"clinical document producers\" are used in the conformance requirements and have the same meaning.  Similarly, \"CDA document\" and \"clinical document\" are used interchangeably as are \"healthcare consumer\" and \"healthcare individual\".\n\n"]
[null,"Instructions:","A test scenario with the priority of \"Mandatory\" must be applied and passed by the software system before it may be declared as conformant to the requirements. Any \"conditional\" test scenario is to be applied if the software system has the functionality required to support the test. For the \"conditional\" test scenario, if the software system does not have the required functionality then the test result to be recorded is \"N/A\" (not applicable). The overall test result is calculated from the result of each test scenario.\n\nThe test scenarios refer to test cases as follows, test cases commencing with the identifier:\n1. \"TC-DIRProc\" are listed in the FS-DIRProc feature set within this conformance test specification.\n2. \"TC-DIRDoc\" are listed in the FS-DIRDoc feature set within this conformance test specification.\n3. \"PCEHR_CIS\" are listed in the PCEHR Connecting Systems - Conformance Test Specification v1.6 [NEHTA-1299:2012].\n\nTasks surrounded by brackets, for example \"(A2: Record \"No Withdrawn consent\")\", are assumed to be automatically performed by the software system without requiring any action by the tester. Test cases to be applied often have a \"conditional\" status as they apply only in a specific context. As the scenarios have been designed to select that context, then the test cases for each scenario must be applied and have a result of \"Pass\" before the software system can be declared as conformant. \n"]
[]
[null,"Scenario:","TP-Remove-01 - Remove an existing Diagnostic Imaging Report that was previously uploaded to the My Health Record system."]
[null,"Objective:","To demonstrate that the software system has the ability to:\n1. Remove an existing Diagnostic Imaging Report that was previously uploaded to the My Health Record system.\n\nSelect a Diagnostic Imaging Report that was uploaded to the My Health Record system, then use the software system to remove the Diagnostic Imaging Report from the My Health Record system.\n\nBusiness process model F. Path: Start -> F3 -> F1 -> F2 -> End"]
[null,"Priority:","Mandatory."]
[null,"Pre-requisites:","To apply this test scenario a Diagnostic Imaging Report must previously have been created by the software system and uploaded to the My Health Record system.\n1. The healthcare individual has an IHI and a health record in the My Health Record system.\n2. The request for the diagnostic services states that the healthcare individual has indicated consent to upload to the My Health Record system.\n3. The request for the diagnostic services states the healthcare individual's name and sufficient demographic information needed to successfully search the HI Service to obtain their IHI.\n4. The request for the diagnostic services states the healthcare individual has at least one previously uploaded diagnostic imaging report in My Health Record system.\n5. The software system has been set up to successfully remove the diagnostic imaging reports from the My Health Record system.\n"]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,null,"F3: Select a document to remove","-",null,"TBD",null,{"$f":"IF(F10=\"\",\"0\",IF(F10=\"Pass\",1,IF(F10=\"Fail\",0,IF(F10=\"TBD\",0,IF(F10=\"N/A\",1)))))","v":0}]
[null,"TP-Remove-01","(F1. Obtain/validate healthcare identifiers)","-",null,"TBD",null,{"$f":"IF(F11=\"\",\"0\",IF(F11=\"Pass\",1,IF(F11=\"Fail\",0,IF(F11=\"TBD\",0,IF(F11=\"N/A\",1)))))","v":0}]
[null,null,"F2. UC.CIS.203 Remove a clinical document","Test cases for UC.CIS.203 (note that requirement 024885 overrides PCEHR connecting systems requirement 019100)","Remove a Clinical Document.","TBD",null,0]
[null,null,"G1: Retrieve recorded information",null,null,"TBD",null,0]
[null,null,"Assess the conformance of the listed Diagnostic Imaging Report & CIS requirements","TC-DIRProc-01","Clinical document producer SHALL NOT be a  registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.001)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.001)","CIS Audit.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019100  (UC.CIS.203)","CIS uses IHI.","TBD",null,0]
[null,null,null,"PCEHR_CIS_017887 (UC.CIS.203)","Identify remove documents.","TBD",null,0]
[null,null,null,"PCEHR_CIS_019377 (UC.CIS.203)","Remove documents.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I23=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H10:H22) / (COUNT(H10:H22))","v":0}]
[]
[]
[null,"Scenario","Percentage complete","Scenario status",null,{"$f":"COUNTIF($H$7:$H23,\"0\")","v":13},"Test Cases Failed or TBD","Fail"]
[null,"TP-Remove-01",{"$f":"I23","v":0},{"$f":"C23","v":"Incomplete"},null,{"$f":"COUNTIF($H$7:$H23,\"1\")","v":0},"Test cases Passed or N/A","Pass"]
[null,null,null,null,null,{"$f":"COUNTIF($H$7:$H23,\">=0\")","v":13},"Total Test cases","N/A"]
[null,null,{"$f":"COUNTIF(D27:D28,\"Complete\")","v":0},"Scenarios Complete",null,{"$f":"SUM($F27/$F28)","v":0},"Test case % Passed or N/A","TBD"]
[null,null,{"$f":"COUNTIF(D27:D28,\"Incomplete\")","v":1},"Scenarios Not Complete"]
[null,null,{"$f":"SUM($C29:$C30)","v":1},"Total Scenarios"]
[null,null,{"$f":"SUM(C29) / (C31)","v":0},"Scenarios percentage Completed."]

{"sheet":"TP-DIR","index":6,"n_rows":200,"n_cols":9,"rows_kept":200,"cut":false,"hidden":false,"merged":[[64,2,64,6],[2,2,2,6],[7,2,7,6],[153,2,153,6],[150,2,150,6],[151,2,151,6],[152,2,152,6],[118,2,118,6],[119,2,119,6],[120,2,120,6],[121,2,121,6],[1,2,1,6],[0,2,0,6],[5,2,5,6],[6,2,6,6],[4,2,4,6],[91,1,115,1],[91,2,115,2],[155,1,185,1],[155,2,185,2],[9,1,33,1],[9,2,33,2],[34,1,58,1],[34,2,58,2],[66,1,90,1],[66,2,90,2],[123,1,147,1],[123,2,147,2],[61,2,61,6],[62,2,62,6],[90,3,90,4],[63,2,63,6]]}
[null,"Test procedure:","TP-DIR: Diagnostic Imaging Report information content"]
[null,"Overview:","Assess the ability of a Diagnostic Imaging Report authoring system to create Diagnostic Imaging Reports with a variety of information content that may be used specifically for this type of clinical document.\n\nA set of test scenarios guide the tester to use an authoring system to create Diagnostic Imaging Reports with specific types of content.  \nThe conformance of the  Diagnostic Imaging Reports can then be assessed using selected test cases. \nThe test scenarios defined here apply specifically to Diagnostic Imaging Reports.\nThe test scenarios are not intended to be comprehensive. Instead, they are intended to include the most common types of information content supported by a Diagnostic Imaging Report authoring system.\n\nNote: The terms \"software system\", \"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 as are \"healthcare consumer\" and \"healthcare individual\"."]
[null,"Instructions:","A test scenario with the priority of \"Mandatory\" must be applied and passed by the software system before it may be declared conformant to the requirements. Any \"conditional\" test scenarios are to be applied if the software system has the functionality required to support the test. If the software system does not have the required functionality then the test result to be recorded is \"N/A\" (not applicable). The overall test result will be automatically calculated from the result of each test scenario.\n\nThe scenarios refer to test cases in other worksheets of this specification. Test cases commencing with the identifier:\n1. \"TC-DIRProc\" are listed in the FS-DIRProc feature set within this conformance test specification.\n2. \"TC-DIRDoc\" are listed in the FS-DIRDoc feature set within this conformance test specification.\n\nTasks surrounded by brackets, for example \"(A2: Record \"No Withdrawn consent\")\", are assumed to be automatically performed by the software system without requiring any action by the tester. Test cases to be applied often have a \"conditional\" status as they apply only in a specific context. As the scenarios have been designed to select that context, then the test cases for each scenario must be applied and have a result of \"Pass\" before the software system can be declared as conformant. "]
[]
[null,"Scenario:","\nTP-DIR-01 - Create one Diagnostic Imaging Report where Imaging Examination Result contains a reference to a website. \n                        Create one Diagnostic Imaging Report where Imaging Examination Result contains a reference to an image on a website.\n"]
[null,"Objective:","CONDITION: Recipient of healthcare services has indicated their consent to upload clinical documents to the My Health Record system.\nFor a recipient of healthcare services, using the software system, author a Diagnostic Imaging Report that contains a reference to a website. For the same healthcare services recipient, author a Diagnostic Imaging Report that contains a reference to an image on a website.\n1. Demonstrate the use of the software system to create a Diagnostic Imaging Report where the Imaging Examination Result contains a reference to a website.\n2. Demonstrate the use of the software system to create a Diagnostic Imaging Report where the Imaging Examination Result contains a reference to an image on a website.\n"]
[null,"Priority:","  Conditional."]
[null,"Pre-requisites:","  Not applicable."]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null," TP-DIR-01.1","Create a Diagnostic Imaging Report where the Imaging Examination Result contains a reference to a website.","Indicate if this scenario is applicable to your software system in the \nACTUAL TEST RESULT","A Diagnostic Imaging Report has been created with an Imaging Examination Result containing a reference to a website.","TBD",null,{"$f":"IF(F10=\"\",\"0\",IF(F10=\"Pass\",1,IF(F10=\"Fail\",0,IF(F10=\"TBD\",0,IF(F10=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-DIRDoc-01","Conform to the requirements for one, and only one, of the following conformance levels: 3A or 3B as defined in the Common Conformance Profile for Clinical Documents.","TBD",null,{"$f":"IF(F11=\"\",\"0\",IF(F11=\"Pass\",1,IF(F11=\"Fail\",0,IF(F11=\"TBD\",0,IF(F11=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-DIRDoc-19","Document Target: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-02","Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TBD",null,0]
[null,null,null,"TC-DIRDoc-03","The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.","TBD",null,0]
[null,null,null,"TC-DIRDoc-04","Various Diagnostic Imaging Report Results and Documents not nullflavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-05","SNOMED-CT-AU not nullFlavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-DIRDoc-20","Check the narrative and section title.","TBD",null,0]
[null,null,null,"TC-DIRDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-08","Mandatory Reporting Radiologist Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-10","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-12","Reporting Radiologist > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-13","Report Date Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-14","Anatomical Location Instance.","TBD",null,0]
[null,null,null,"TC-DIRDoc-15","Anatomical Region is Name of Location.","TBD",null,0]
[null,null,null,"TC-DIRDoc-16","Appropriate Image Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-17","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRProc-01","Clinical document producer SHALL NOT be a registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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. ","TBD",null,0]
[null,null,null,"TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,{"$f":"IF(F34=\"\",\"0\",IF(F34=\"Pass\",1,IF(F34=\"Fail\",0,IF(F34=\"TBD\",0,IF(F34=\"N/A\",1)))))","v":0}]
[null,"TP-DIR-01.2","Create a Diagnostic Imaging Report where the Imaging Examination Result contains a reference to an image on a website.","Indicate if this scenario is applicable to your software system in the \nACTUAL TEST RESULT","Diagnostic Imaging Report has been created with an Imaging Examination Result containing a reference to an image on a website.","TBD",null,0]
[null,null,null,"TC-DIRDoc-18","Image Location: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-19","Document Target: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-02","Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TBD",null,0]
[null,null,null,"TC-DIRDoc-03","The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.","TBD",null,0]
[null,null,null,"TC-DIRDoc-04","Various Diagnostic Imaging Report Results and Documents not nullflavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-05","SNOMED-CT-AU not nullFlavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-DIRDoc-20","Check the narrative and section title.","TBD",null,0]
[null,null,null,"TC-DIRDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-08","Mandatory Reporting Radiologist Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-10","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-12","Reporting Radiologist > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-13","Report Date Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-14","Anatomical Location Instance.","TBD",null,0]
[null,null,null,"TC-DIRDoc-15","Anatomical Region is Name of Location.","TBD",null,0]
[null,null,null,"TC-DIRDoc-16","Appropriate Image Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-17","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRProc-01","Clinical document producer SHALL NOT be a registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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. ","TBD",null,0]
[null,null,null,"TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I60=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H10:H59) / (COUNT(H10:H59))","v":0}]
[]
[null,"Scenario:","TP-DIR-02 - Create one Diagnostic Imaging Report with multiple Imaging Examination Results reported by a single Reporting Radiologist.\n                       Create one Diagnostic Imaging Report with multiple Imaging Examination Results reported by different Reporting Radiologists.  "]
[null,"Objective:","CONDITION: Recipient of healthcare services has indicated their consent to upload clinical documents to the My Health Record system.\nFor a recipient of healthcare services, using the software system, author a Diagnostic Imaging Report that has multiple Imaging Examination Results  reported by a single Reporting Radiologist. For the same recipient of healthcare services, author a Diagnostic Imaging Report that has multiple Imaging Examination Results reported by a different Reporting Radiologist.\n1. Demonstrate that the software system is capable of creating a Diagnostic Imaging Report with multiple Imaging Examination Results reported by a single Reporting Radiologist.\n2. Demonstrate that the software system is capable of creating a Diagnostic Imaging Report with multiple Imaging Examination Results reported by different Reporting Radiologists.\n"]
[null,"Priority:","  Conditional."]
[null,"Pre-requisites:","  Not applicable."]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,"TP-DIR-02.1","Create a Diagnostic Imaging Report that has multiple Imaging Examination Results where all the Imaging Examination Results are reported by single Reporting Radiologist.","Indicate if this scenario is applicable to your software system in the \nACTUAL TEST RESULT","Diagnostic Imaging Report has been created with multiple Imaging Examination Results details where all the results are reported by one Reporting Radiologist.","TBD",null,{"$f":"IF(F67=\"\",\"0\",IF(F67=\"Pass\",1,IF(F67=\"Fail\",0,IF(F67=\"TBD\",0,IF(F67=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-DIRDoc-12","Reporting Radiologist > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-08","Mandatory Reporting Radiologist Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-05","SNOMED-CT-AU not nullFlavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-04","Various Diagnostic Imaging Report Results and Documents not nullflavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-14","Anatomical Location Instance.","TBD",null,0]
[null,null,null,"TC-DIRDoc-15","Anatomical Region is Name of Location.","TBD",null,0]
[null,null,null,"TC-DIRDoc-16","Appropriate Image Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-17","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-02","Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TBD",null,0]
[null,null,null,"TC-DIRDoc-03","The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.","TBD",null,0]
[null,null,null,"TC-DIRDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-DIRDoc-20","Check the Check the narrative and section title.","TBD",null,0]
[null,null,null,"TC-DIRDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-10","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-13","Report Date Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-18","Image Location: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-19","Document Target: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRProc-01","Clinical document producer SHALL NOT be a registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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. ","TBD",null,0]
[null,null,null,"TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"TP-DIR-02.2","Create a Diagnostic Imaging Report that has multiple Imaging Examination Results where each of the Imaging Examination Result is reported by a different Reporting Radiologist.","Indicate if this scenario is applicable to your software system in the \nACTUAL TEST RESULT","Diagnostic Imaging Report has been created with multiple Imaging Examination Results  where each result is reported by a different Reporting Radiologist.","TBD",null,0]
[null,null,null,"TC-DIRDoc-12","Reporting Radiologist > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-08","Mandatory Reporting Radiologist Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-05","SNOMED-CT-AU not nullFlavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-04","Various Diagnostic Imaging Report Results and Documents not nullflavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-14","Anatomical Location Instance.","TBD",null,0]
[null,null,null,"TC-DIRDoc-15","Anatomical Region is Name of Location.","TBD",null,0]
[null,null,null,"TC-DIRDoc-16","Appropriate Image Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-17","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-02","Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TBD",null,0]
[null,null,null,"TC-DIRDoc-03","The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.","TBD",null,0]
[null,null,null,"TC-DIRDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-DIRDoc-20","Check the narrative and section title.","TBD",null,0]
[null,null,null,"TC-DIRDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-10","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-13","Report Date Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-18","Image Location: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-19","Document Target: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRProc-01","Clinical document producer SHALL NOT be a registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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. ","TBD",null,0]
[null,null,null,"TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,{"$f":"IF(F116=\"\",\"0\",IF(F116=\"Pass\",1,IF(F116=\"Fail\",0,IF(F116=\"TBD\",0,IF(F116=\"N/A\",1)))))","v":0}]
[null,"Scenario result:",{"$f":"IF(I117=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H67:H116) / (COUNT(H67:H116))","v":0}]
[]
[null,"Scenario:","TP-DIR-03 - Create a Diagnostic Imaging Report with the Requestor's entity identifier, address & contact details, Requestor's employer entity identifier. "]
[null,"Objective:","Demonstrate the software system's ability to create a Diagnostic Imaging Report with the Requestor's entity identifier, address and contact details, and the Requestor's employer entity identifier."]
[null,"Priority:","  Mandatory"]
[null,"Pre-requisites:","  Not applicable."]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,"TP-DIR-03","Create a Diagnostic Imaging Report with Requester's entity identifier, address and contact details.\n","-","Diagnostic Imaging Report has been created with Requester's entity identifier, address and contact details.","TBD",null,{"$f":"IF(F124=\"\",\"0\",IF(F124=\"Pass\",1,IF(F124=\"Fail\",0,IF(F124=\"TBD\",0,IF(F124=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-DIRDoc-04","Various Diagnostic Imaging Report Results and Documents not nullflavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-02","Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TBD",null,0]
[null,null,null,"TC-DIRDoc-03","The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.","TBD",null,0]
[null,null,null,"TC-DIRDoc-05","SNOMED-CT-AU not nullFlavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-DIRDoc-20","Check the narrative and section title.","TBD",null,0]
[null,null,null,"TC-DIRDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-08","Mandatory Reporting Radiologist Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-10","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-12","Reporting Radiologist > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-13","Report Date Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-14","Anatomical Location Instance.","TBD",null,0]
[null,null,null,"TC-DIRDoc-15","Anatomical Region is Name of Location.","TBD",null,0]
[null,null,null,"TC-DIRDoc-16","Appropriate Image Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-17","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-18","Image Location: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-19","Document Target: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRProc-01","Clinical document producer SHALL NOT be a registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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. ","TBD",null,0]
[null,null,null,"TC-DIRProc-05","Store \"Withdrawn consent\" indicator.","TBD",null,0]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I149=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H124:H148) / (COUNT(H124:H148))","v":0}]
[]
[null,"Scenario:","  TP-DIR-04 - Create a Diagnostic Imaging Report to test all the mandatory requirements and the applicable conditional requirements defined in the Diagnostic Imaging Report Conformance Profile."]
[null,"Objective:","  Demonstrate the software system conforms to all the mandatory requirements and the applicable conditional requirements defined in the Diagnostic Imaging Report Conformance Profile."]
[null,"Priority:","  Mandatory."]
[null,"Pre-requisites:","  Not applicable."]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null," TP-DIR-04","Create one or more Diagnostic Imaging Reports that satisfy the criteria that all the mandatory requirements and the applicable conditional requirements defined in the Diagnostic Imaging Report Conformance Profile can be verified.\n\n","-","One or more Diagnostic Imaging Reports have been created. \n","TBD",null,{"$f":"IF(F156=\"\",\"0\",IF(F156=\"Pass\",1,IF(F156=\"Fail\",0,IF(F156=\"TBD\",0,IF(F156=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-DIRDoc-01","Conform to the requirements for one, and only one, of the following conformance levels: 3A or 3B as defined in the Common Conformance Profile for Clinical Documents.","TBD",null,0]
[null,null,null,"TC-DIRDoc-02","Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TBD",null,0]
[null,null,null,"TC-DIRDoc-03","The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.","TBD",null,0]
[null,null,null,"TC-DIRDoc-04","Various Diagnostic Imaging Report Results and Documents not nullflavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-05","SNOMED-CT-AU not nullFlavor.","TBD",null,0]
[null,null,null,"TC-DIRDoc-20","Check the narrative and section title.","TBD",null,0]
[null,null,null,"TC-DIRDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-08","Mandatory Reporting Radiologist Values used.","TBD",null,0]
[null,null,null,"TC-DIRDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-10","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-DIRDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-12","Reporting Radiologist > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-DIRDoc-13","Report Date Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-14","Anatomical Location Instance.","TBD",null,0]
[null,null,null,"TC-DIRDoc-15","Anatomical Region is Name of Location.","TBD",null,0]
[null,null,null,"TC-DIRDoc-16","Appropriate Image Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-17","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-DIRDoc-18","Image Location: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRDoc-19","Document Target: URL Referenced - Link in the corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-DIRProc-01","Clinical document producer SHALL NOT be a registered consumer portal or registered provider portal.","TBD",null,0]
[null,null,null,"TC-DIRProc-02","Clinical document producer 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. ","TBD",null,0]
[null,null,null,"TC-DIRProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-DIRProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,{"$f":"IF(F179=\"\",\"0\",IF(F179=\"Pass\",1,IF(F179=\"Fail\",0,IF(F179=\"TBD\",0,IF(F179=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-DIRProc-07","The Diagnostic Imaging Report is not uploaded to My Health Record system. \nA copy of the Diagnostic Imaging Report is saved to software system.","TBD",null,0]
[null,null,null,"TC-DIRProc-08","software system permits the report to be uploaded to the My Health Record system.","TBD",null,{"$f":"IF(F181=\"\",\"0\",IF(F181=\"Pass\",1,IF(F181=\"Fail\",0,IF(F181=\"TBD\",0,IF(F181=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-DIRProc-10","Changing \"Withdrawn consent\" indicator.","TBD",null,{"$f":"IF(F182=\"\",\"0\",IF(F182=\"Pass\",1,IF(F182=\"Fail\",0,IF(F182=\"TBD\",0,IF(F182=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-DIRProc-11","Record upload failure.","TBD",null,{"$f":"IF(F183=\"\",\"0\",IF(F183=\"Pass\",1,IF(F183=\"Fail\",0,IF(F183=\"TBD\",0,IF(F183=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-DIRProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-DIRProc-13","Record a decision to not upload a diagnostic report.","TBD",null,0]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA Authoring.",null,"TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I187=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H156:H186) / (COUNT(H156:H186))","v":0}]
[]
[]
[]
[null,"Scenario","Percentage complete","Scenario status",null,{"$f":"COUNTIF(H10:H187,\"0\")","v":156},"Test Cases Failed or TBD","Fail"]
[null,"TP-DIR-01",{"$f":"I60","v":0},{"$f":"C60","v":"Incomplete"},null,{"$f":"COUNTIF(H10:H187,\"1\")","v":0},"Test cases Passed or N/A","Pass"]
[null,"TP-DIR-02",{"$f":"I117","v":0},{"$f":"C117","v":"Incomplete"},null,{"$f":"COUNTIF(H10:H187,\">=0\")","v":156},"Total Test cases","N/A"]
[null,"TP-DIR-03",{"$f":"I149","v":0},{"$f":"C149","v":"Incomplete"},null,{"$f":"SUM(F192/F193)","v":0},"Test case % Passed or N/A","TBD"]
[null,"TP-DIR-04",{"$f":"I187","v":0},{"$f":"C187","v":"Incomplete"}]
[]
[null,null,{"$f":"COUNTIF($D$192:$D$195,\"Complete\")","v":0},"Scenarios Complete"]
[null,null,{"$f":"COUNTIF($D$192:$D$195,\"Incomplete\")","v":4},"Scenarios Not Complete"]
[null,null,{"$f":"SUM($C$197:$C$198)","v":4},"Total Scenarios"]
[null,null,{"$f":"'TP-DIR'!C205","v":0},"Scenarios percentage Completed."]

{"sheet":"FS-DIRDoc ","index":7,"n_rows":36,"n_cols":11,"rows_kept":36,"cut":false,"hidden":false,"merged":[[0,0,0,1],[3,0,3,1],[22,1,23,1],[22,2,23,2],[0,2,0,5],[1,2,1,5],[2,2,2,5],[3,2,3,5],[1,0,1,1],[2,0,2,1],[20,2,21,2],[20,1,21,1]]}
["Feature set identifier:",null,"FS-DIRDoc (Diagnostic Imaging Report clinical document)"]
["Objective:",null,"To assess the conformance of a Diagnostic Imaging Report clinical document to the requirements specified in the Common Conformance profile and the requirements specified in Diagnostic Imaging Report Conformance Profile.\n"]
["Strategy:",null,"A Diagnostic Imaging Report clinical document to be tested may be obtained from any source, such as an software 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 whereever practical.  The test cases listed here are to be used in conjunction with the test cases in the Conformance Test Specification for Authoring Systems [NEHTA-2209:2016], which apply to all types of clinical documents.\n\nIn general, test cases have not been defined for the conformance requirements in the \"Conditions of Use\" for each data element listed in the Diagnostic Imaging Report structured content specification as it is assumed the template packages will assess conformance to these requirements. The exception is the Anatomical Location Conditions of Use, which has been included due to the requirement being often misunderstood.\n\nSome conformance requirements are recommendations, indicated by the keywords SHOULD or SHOULD NOT. The test case that is marked as \"optional\"  indicates that, it need to be applied if the developer of the software system claims to have implemented the recommended requirement.\n\n\nNote: The terms \"software system\", \"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 as are \"healthcare consumer\" and \"healthcare individual\".\n"]
["Traceability:",null,"1. eHealth Diagnostic Imaging Report - PCEHR Conformance Profile [NEHTA-1978:2015]\n2. Clinical Documents - Common Conformance Profile [NEHTA-1850:2015]\n3. Diagnostic Imaging Report - Structured Content Specification v1.0 [NEHTA-1527:2014]\n4. Diagnostic Imaging Report - CDA Implementation Guide v1.0 [NEHTA-1528:2014]\n\n"]
[]
["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","TEST RESULT","TESTER COMMENTS","CALC.","MANDATORY AND N/A"]
["TS-DIRDoc","START:  TS-DIRDoc (Diagnostic Imaging Report clinical document)"]
["TS-DIRDoc","TC-DIRDoc-01","023435 [NEHTA-1978:2015]\nA CDA document sent to the My Health Record system SHALL conform to the requirements of one, and only one, of the following conformance levels: either 3A or 3B as defined in the Clinical Documents - Common Conformance Profile [NEHTA-1850:2015].","M",1,"Pass the test where:\n1) conformance to Level 3A or 3B is claimed, and\n2) the clinical document passes the test cases for feature sets FS-Doc, FS-Narr and FS-Types in the Conformance Test Specification for Authoring Systems  [NEHTA-2209:2016].\nElse, Fail the test.\n","1) A clinical document to be sent to the My Health Record system meets the requirements for conformance level 3A or 3B as defined in the Common Conformance Profile for Clinical Documents [NEHTA-1850:2015].\n\n2) The clinical document passes the test cases for feature sets FS-Doc, FS-Narr and FS-Types in the Conformance Test Specification for Authoring Systems [NEHTA-2209:2016].","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":0}]
["TS-DIRDoc","TC-DIRDoc-02","023473 [NEHTA-1978:2015]\nA CDA document SHALL reference one, and only one, attachment that is the original diagnostic report. The report SHALL be a PDF packaged attachment.\n\nNote: The intent of the requirement is that the original diagnostic report must be attached, it must be in PDF format and no other format, and it must be in the CDA Package as a packaged attachment. Other packaged attachments are also allowed, such as a reference to a diagnostic image.\n","M",1,"Pass the test where the clinical document contains one and only one reference to a PDF attachment which is claimed as the original diagnostic imaging report.\nElse Fail the test.\n\nNOTE TO TESTER: \nAn attachment is a document referenced from the root document by a\"reference\" element within a data element of the Encapsulated Data (ED) data type. \n","The original diagnostic imaging  report is a PDF document referenced only once.","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":0}]
["TS-DIRDoc",null,null,null,2,"Pass the test where the clinical document conforms to the test sets \"Common Conformance Profile - Attachment limitations\" and \"Package Attachments\" from the the Clinical Documents - Conformance Test Specification for CDA Packaging v1.5 [NEHTA-2065:2015].\nElse Fail the test.\n\nNOTE TO TESTER: \nA packaged attachment is an attachment whose\"reference\" value is a relative reference to a document which is contained within the package.\n","The clinical document conforms to the test sets \"Common Conformance Profile - Attachment limitations\",  \"Package Attachments\" from the the Clinical Documents - Conformance Test Specification for CDA@ Packaging v1.5 [NEHTA-2065:2015].","TBD",null,0,{"$f":"IF(AND(BGCol(D11)=48,H11=\"N/A\"),1,0)","v":0}]
["TS-DIRDoc","TC-DIRDoc-03","023651 [NEHTA-1978:2015]\nThe values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.","M",1,"Fail the test where the value of the data elements in the clinical document are not consistent with the value of the data element in the PDF document.\nElse, Pass the test.\n","The value of the data element in the clinical document is consistent with the value of the data element in the PDF document.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D12)=48,H12=\"N/A\"),1,0)","v":0}]
["TS-DIRDoc","TC-DIRDoc-04","025075 [NEHTA-1978:2015]\nThe value of the following data elements SHALL NOT be a nullFlavor:\n\n• Document Author > Participant > Person or Organisation or Device > Person > Employment Detail > Employer Organisation > Organisation > Organisation Name \n• Order Details > Accession Number\n• Order Details > Requester > Participant > Person or Organisation of Device > Person > Person Name > Family Name\n• Diagnostic Imaging > Imaging Examination Result > Examination Procedure\n• Diagnostic Imaging > Imaging Examination Result > Examination Details > Image Details > Image DateTime\n• Diagnostic Imaging > Imaging Examination Result > Modality\n• Diagnostic Imaging > Related Document > Document Details > Report Status","M",1,"For any Diagnostic Imaging Report clinical document under test:\n\nFail the test where any following data elements have the attribute with name \"nullflavor\":\n• Document Author > Participant > Person or Organisation or Device > Person > Employment Detail > Employer Organisation > Organisation > Organisation Name   (XPATH=/ClinicalDocument/author/assignedAuthor/assignedPerson/ext:asEmployment/ext:employerOrganization/asOrganizationPartOf/wholeOrganization/name)\n\n• Order Details > Accession Number\n(XPATH=/ClinicalDocument/inFulfillmentOf/order/id/@extension)\n\n• Order Details > Requester > Participant > Person or Organisation of Device > Person > Person Name > Family Name\n(XPATH=/ClinicalDocument/participant/associatedEntity/associatedPerson/name/family)\n\n• Diagnostic Imaging > Imaging Examination Result > Examination Procedure\n(XPATH=/ClinicalDocument/component/structuredBody/component[diag_inv]/section/component[img_exam]/section/entryRelationship[exam_proc]/act/text:ST)\n\n• Diagnostic Imaging > Imaging Examination Result > Examination Details > Image Details > Image DateTime\n(XPATH=/ClinicalDocument/component/structuredBody/component[diag_inv]/section/component[img_exam]/section/entry[img_exam_res]/observation/entryRelationship[exam_req]/act/entryRelationship[img_det]/observation/effectiveTime)\n\n• Diagnostic Imaging > Imaging Examination Result > Modality\n(XPATH=/ClinicalDocument/component/structuredBody/component[diag_inv]/section/component[img_exam]/section/entry[img_exam_res]/observation/methodCode)\n\n• Diagnostic Imaging > Related Document > Document Details > Report Status\n(XPATH= /ClinicalDocument/component/structuredBody/component[diag_inv]/section/entry[doc_detail]/act/entryRelationship[status]/observation/value:CD)\n\nElse, Pass the test.\n","The following data elements are populated with values and do not contain the attribute with name \"nullflavor\".\n\n• Document Author > Participant > Person or Organisation or Device > Person > Employment Detail > Employer Organisation > Organisation > Organisation Name \n\n• Order Details > Accession Number\n\n• Order Details > Requester > Participant > Person or Organisation of Device > Person > Person Name > Family Name\n\n• Diagnostic Imaging > Imaging Examination Result > Examination Procedure\n\n• Diagnostic Imaging > Imaging Examination Result > Examination Details > Image Details > Image DateTime\n\n• Diagnostic Imaging > Imaging Examination Result > Modality\n\n• Diagnostic Imaging > Related Document > Document Details > Report Status","TBD",null,0,{"$f":"IF(AND(BGCol(D13)=48,H13=\"N/A\"),1,0)","v":0}]
["TS-DIRDoc","TC-DIRDoc-05","025157 [NEHTA-1978:2015]\nIf the software includes a SNOMED CT-AU code to identify the anatomical location name and provides laterality information then the software SHALL include a SNOMED CT-AU code for the laterality and SHALL NOT use a nullFlavor.","C",1,"CONDITION: For any Diagnostic Imaging Report clinical document where SNOMED CT-AU codes are used to identify the anatomical location name and Diagnostic Imaging Report clinical document has laterality information.\n\nPass the test where there exists \"Name of Location (Anatomical Location Name)\" data component:\n1) the document contains SNOMED CT-AU codes for the laterality, and \n2) the \"nullflavor\" attribute has not been coded within the laterality element. \n\nElse, Fail the test.\n\nNOTE TO TESTER:  The XPath for coded laterality information is: /ClinicalDocument/component/structuredBody/component[diag_inv]/section/component[img_exam]/section/entry[img_exam_res]/observation/targetSiteCode/qualifier/value:CD\n","a) The document contains SNOMED CT-AU codes for the laterality.\n \nb) The \"nullflavor\" attribute has not been coded within the laterality element. ","TBD",null,0,{"$f":"IF(AND(BGCol(D14)=48,H14=\"N/A\"),1,0)","v":0}]
["TS-DIRDoc","TC-DIRDoc-06","024798 [NEHTA-1978:2015]\nThe diagnostic report provider software SHOULD sort the test result details in the CDA document in the same order as displayed in the report PDF document.\n","O",1,"Pass the test where the test result details in the clinical document <entry> elements and in the narrative/s are in the same order as displayed in the report PDF document. \nElse, mark the test as N/A.\n\n","The test result details in the clinical document narrative are in the same order as displayed in the diagnostic imaging report PDF document.","TBD",null,0,{"$f":"IF(AND(BGCol(D15)=48,H15=\"N/A\"),1,0)","v":0}]
["TS-DIRDoc","TC-DIRDoc-20","026616 [NEHTA-1978:2015]\nIf a narrative is not included in an Imaging Examination Result section then the section title SHALL NOT be included.","C",1,"CONDITION: An Imaging Examination Result section does not contain a narrative block.\n\nPass the test where there is no section title.\nElse, Fail the test.\n","There is no section title for every section with no narrative block.","TBD",null,0,{"$f":"IF(AND(BGCol(D16)=48,H16=\"N/A\"),1,0)","v":0}]
["TS-DIRDoc","TC-DIRDoc-07","025065 [NEHTA-1978:2015]\nThe following values SHALL be used for mandatory Document Author data elements when it is not possible to name one person as the Document Author:\n\n• Document Author > Role SHALL have the value nullFlavor=“NI”\n• Document Author > Participant > Entity Identifier SHALL be a local identifier with the value “NI” for the extension attribute\n• Document Author > Participant > Person or Organisation or Device > Person > Person Name > Family Name SHALL have the value nullFlavor=“NI”.\n","C",1,"CONDITION: It is NOT possible to name one person as the Document Author.\n\nPass the test where:\n1) the data element \"Document Author > Role\" has the value nullFlavor= “NI”, and \n2) the data element \"Document Author > Participant > Entity Identifier\" identifies a value that is a local identifier, and \n3) the data element \"Document Author > Participant > Entity Identifier\" passes the test cases TC-Types-29 & TC-Types-30 in the Conformance Test Specification for Authoring Systems  [NEHTA-2209:2016] and has the attribute with name \"extension\" whose value is “NI”, and\nd) the data element \"Document Author > Participant > Person or Organisation or Device > Person > Person Name > Family Name\" has the value nullFlavor=“NI”. \nElse, Fail the test.\n\nNOTE TO TESTER: A person is listed as the Document Author if there is a name included in the \"ClinicalDocument/author/assignedAuthor/assignedPerson/name/family'\"element.\n","1) The data element \"Document Author > Role\" has the value nullFlavor= “NI”; and\n\n2) the data element \"Document Author > Participant > Entity Identifier\" identifies a value that is a local identifier; and \n\n3) the data element \"Document Author > Participant > Entity Identifier\" passes test cases TC-Types-29 & TC-Types-30 in the Conformance Test Specification for Authoring Systems  [NEHTA-2209:2016] and has the attribute with name \"extension\" whose value is “NI”; and\n\n4) the data element \"Document Author > Participant > Person or Organisation or Device > Person > Person Name > Family Name\" has the value nullFlavor=“NI”. \n","TBD",null,0,{"$f":"IF(AND(BGCol(D17)=48,H17=\"N/A\"),1,0)","v":0}]
["TS-DIRDoc","TC-DIRDoc-08","025076 [NEHTA-1978:2015]\nThe following values SHALL be used for mandatory Reporting Radiologist data elements when it is not possible to name one person as the Reporting Radiologist:\n\n• Reporting Radiologist > Role SHALL have the value nullFlavor=“NI”.\n• Reporting Radiologist > Participant > Entity Identifier SHALL be a local identifier with the value “NI” for the extension attribute.\n• Reporting Radiologist > Participant > Person or Organisation or Device > Person > Person Name > Family Name SHALL have the value nullFlavor=“NI”.\n","C",1,"CONDITION: It is NOT possible to name one person as the Reporting Radiologist.\n\nPass the test where the data element \"Reporting Radiologist > Role\" conforms to all the following conditions:\n1) the data element \"Reporting Radiologist > Role\" has the value nullFlavor=“NI”.\n2) the data element \"Reporting Radiologist > Participant > Entity Identifier\" identifies a value that is a local identifier.\n3) the data element \"Reporting Radiologist > Participant > Entity Identifier\" passes the test cases TC-Types-29 & TC-Types-30 in the Conformance Test Specification for Authoring Systems  [NEHTA-2209:2016] and has the attribute with name \"extension\" whose value is “NI”.\nd) the data element \"Reporting Radiologist > Participant > Person or Organisation or Device > Person > Person Name > Family Name\" has the value nullFlavor=“NI”.\nElse, Fail the test.\n\nNOTE TO TESTER: A person is listed as the Reporting Radiologist if there is a name included in the \"ClinicalDocument/component/structuredBody/component[diag_inv]/section/author/assignedAuthor/assignedPerson/name/family\" element.\n","a) The data element \"Reporting Radiologist > Role\" has the value nullFlavor=“NI”.\n\nb) The data element \"Reporting Radiologist > Participant > Entity Identifier\" identifies a value that is a local identifier, and \n\nc) The data element \"Reporting Radiologist > Participant > Entity Identifier\" passes test cases TC-Types-29 & TC-Types-30 in the Conformance Test Specification for Authoring Systems  [NEHTA-2209:2016] and has the attribute with name \"extension\" whose value is “NI”.\n\nd) The data element \"Reporting Radiologist > Participant > Person or Organisation or Device > Person > Person Name > Family Name\" has the value nullFlavor=“NI”.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D18)=48,H18=\"N/A\"),1,0)","v":0}]
["TS-DIRDoc","TC-DIRDoc-09","024732 [NEHTA-1978:2015]\nA diagnostic report, including the attached PDF file, MAY reference an object outside of the CDA package (e.g. an external atomic attachment or a website).\n\nNote: This requirement has the effect of overriding CDA Rendering Specification [NEHTA-1199-2012] requirements CDA-RS 53(g) and CDA-R5 53(j), which apply to clinical document authoring systems and disallows references to items on a network. \n","O",1,"CONDITION: The diagnostic report references an object outside of the CDA package.\n\nIf the condition is not met, then mark the test N/A.\nFail the test where the diagnostic report references an object outside of the CDA package, and the referenced object is broken after the CDA document is created.\nElse, Pass the test.\n\nNOTE TO TESTER: \n1. A referenced object is broken when the referenced object is NOT accessible to the healthcare individual or any participant healthcare provider, who is downloading the CDA package from the My Health Record system.\n","The diagnostic report, that includes an attached PDF file, references an available object that is outside the CDA package.","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":0}]
["TS-DIRDoc","TC-DIRDoc-10","024988 [NEHTA-1978:2015]\nA reference to an object outside of the CDA package SHALL be represented as an ED element according to CDA Package [NEHTA-1229-2011] requirements M 15, M 17 and M 18.\n\n025077 [NEHTA-1978:2015]\nThe media type and filename extension requirements M 21 (CDA Package, [NEHTA-1229-2011]) 023741, 024629, 024630 and 023742 (Common Conformance Profile for Clinical Documents [NEHTA-1850:2015]) SHALL apply to an external atomic attachment.\n\n024989 [NEHTA-1978:2015]\nAn integrity check SHOULD be included when the CDA document references an external atomic attachment.\n\n024990 [NEHTA-1978:2015]\nIf the software includes an integrity check for an external atomic attachment, it SHALL conform to CDA Package [NEHTA-1978:2015] requirements M 16 and M 20.\n","M",1,"Pass the test where the CDA package conforms to the requirements in the CDA Package [NEHTA-1229-2011] specification.\nElse Fail the test.\n\nNOTE TO TESTER:\n1. Tests for the requirements in CDA Package [NEHTA-1229-2011] specification are defined in the Clinical Documents - Conformance Test Specification for CDA@ Packaging v1.5 [NEHTA-2065:2015].\n\n\n","All mandatory and relevant conditional tests in the CDA Package [NEHTA-1229-2011] specification.","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":0}]
["TS-DIRDoc","TC-DIRDoc-11","023436 [NEHTA-1978:2015]\nThe value of at least one Document Author > Participant > Entity Identifier SHALL be an HPI-I if one is present or can be obtained from the Healthcare Identifiers Service; otherwise at least one document author identifier SHALL have a value that uniquely identifies the document author, and the value SHALL NOT be a nullFlavor.\nThe relaxation of the mandatory requirement to include an HPI-I is only available to specific healthcare provider organisations, at the discretion of the My Health Record System Operator.\n\nNote: Where permission has been granted to relax the condition for the provision of an HPI-I, this requirement does not need to be met.\n","C",1,"CONDITION: Where permission has been granted to relax the condition for the provision of a HPI-I, this test does not apply.\n\nPass the test where one \"Document Author > Participant > Entity Identifier\" element contains an HPI-I.\nElse Fail the test.\n\nNOTE TO TESTER: \n1. The data element \"Document Author > Participant > Entity Identifier\" has the XPATH /ClinicalDocument/author/assignedAuthor/assignedPerson/<Entity Identifier>.\n\n","The value of the Document Author > Participant > Entity Identifier is an HPI-I, or a value that identifies the document author.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D21)=48,H21=\"N/A\"),1,0)","v":0}]
["TS-DIRDoc",null,null,null,2,"1) If the software is able to obtain an HPI-I then: \nPass the test if \"Document Author > Participant > Entity Identifier\" element contains the HPI-I.\nElse Fail the test.\n2) If the software is unable to obtain an HPI-I then: \nPass the test if \"Document Author > Participant > Entity Identifier\" element contains a local identifier and no nullFlavor.\nElse Fail the test.","The value of the Document Author > Participant > Entity Identifier is a value that identifies the document author.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D22)=48,H22=\"N/A\"),1,0)","v":0}]
["TS-DIRDoc","TC-DIRDoc-12","023553 [NEHTA-1978:2015]\nThe value of at least one Reporting Radiologist > Participant > Entity Identifier SHALL be an HPI-I if one is present or can be obtained from the Healthcare Identifiers Service; otherwise at least one Reporting Radiologist identifier SHALL have a value that identifies the reporting radiologist and the value SHALL NOT be a nullFlavor.\n\nThis requirement does not impact any relaxation to the mandatory requirement to include an HPI-I that is available to specific healthcare provider organisations, at the discretion of the My Health Record System Operator.\n\nNote: Where permission has been granted to relax the condition for the provision of a HPI-I, this requirement does not need to be met.","C",1,"Pass the test where one \"Reporting Radiologist > Participant > Entity Identifier\" element contains an HPI-I.\nElse Fail the test.\n\nNOTE TO TESTER: \n1. The data element \"Reporting Radiologist > Participant > Entity Identifier\" has the XPATH /ClinicalDocument/component/structuredBody/component[diag_inv]/section/author/assignedAuthor/assignedPerson/<Entity Identifier>.\n\n\n","The value of the Reporting Radiologist > Participant > Entity Identifier is an HPI-I.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D23)=48,H23=\"N/A\"),1,0)","v":0}]
["TS-DIRDoc",null,null,null,2,"1) If the software is able to obtain an HPI-I then: \nPass the test if \"Reporting Radiologist > Participant > Entity Identifier\" element contains the HPI-I.\nElse Fail the test.\n2) If the software is unable to obtain an HPI-I then: \nPass the test if  \"Reporting Radiologist > Participant > Entity Identifier\" element contains a local identifier and no nullFlavor.\nElse Fail the test.\n","The value of the Reporting Radiologist > Participant > Entity Identifier is a value that identifies the document author.\n","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":0}]
["TS-DIRDoc","TC-DIRDoc-13","2.26 Report DateTime (Effective Period) [NEHTA-1527:2014]\nDefinition: The period of time during which the document of interest is deemed to have clinical utility.\nThe Report DateTime SHALL be recorded as the low date of the interval.\n\nData type: TimeInterval [NEHTA-0794:2011]\nXPath: ClinicalDocument/component/structuredBody/component[diag_inv]/section/entry[doc_detail]/act/effectiveTime/low\n","M",1,"Pass the test where the Report DateTime element passes test case TC-Types-102 (Test set TS-IVL (Interval)).\nElse, Fail the test.\n\nNOTE TO TESTER:  \nThe XPath for Report DateTime is:  /ClinicalDocument/component/structuredBody/component[diag_inv]/section/entry[doc_detail]/act/effectiveTime/low.\n","The Report DateTime data element meets the requirements for the DateTime data type in the test set TC-Types-102 (Test set TS-IVL (Interval)).","TBD",null,0,{"$f":"IF(AND(BGCol(D25)=48,H25=\"N/A\"),1,0)","v":0}]
["TS-DIRDoc","TC-DIRDoc-14","3.7 Anatomical Location [NEHTA-1527:2014] [NEHTA-1528:2014]\nEach instance of this data group SHALL contain exactly one SPECIFIC LOCATION or exactly one Description (Anatomical Location Description).\n\nThis data group SHALL NOT contain both an instance of SPECIFIC LOCATION and an instance of Description (Anatomical Location Description).\n","M",1,"Pass the test where IMAGING EXAMINATION RESULT data group contains exactly one Description (Anatomical Location Description) and does not contain any Specific Location.\nElse, Pass the test where IMAGING EXAMINATION RESULT data group contains exactly one Specific Location and does not contain any Description (Anatomical Location Description).\nElse Fail the test.\n\nNOTE TO TESTER:  \nThe XPath for Description (Anatomical Location Description) is: /ClinicalDocument/component/structuredBody/component[diag_inv]/section/component[img_exam]/section/entry[img_exam_res]/observation/targetSiteCode/originalText\n\nThe XPath for Specific Location is ClinicalDocument/component/structuredBody/component[diag_inv]/section/component[img_exam]/section/entry[img_exam_res]/observation/targetSiteCode\n","Either the Specific Location or the Description (Anatomical Location Description) are present, but not both.","TBD",null,0,{"$f":"IF(AND(BGCol(D26)=48,H26=\"N/A\"),1,0)","v":0}]
["TS-DIRDoc","TC-DIRDoc-15","3.14 Anatomical Region [NEHTA-1527:2014]\nThe value of this element SHALL subsume all of the anatomical locations identified in Anatomical Site (ANATOMICAL LOCATION) (targetSiteCode and targetSiteCode/originalText).\n\nIf the anatomical region is known but the exact anatomical locations are not, the region SHALL be recorded in both Anatomical Region and Name of Location (Anatomical Location Name). [NEHTA-1528:2014]\n\nAnatomical Region and Name of Location (Anatomical Location Name) use different code systems so an implementation SHOULD use an equivalent code to the region value in Name of Location (Anatomical Location Name).[NEHTA-1528:2014]\n","M",1,"Pass the test where all the following conditions conforms to all the following conditions:\n1) The value of the Anatomical Region data element either subsumes or is equivalent to the value of the Name of Location (Anatomical Location Name) data element.\n2) Record the Anatomical Region in both the Anatomical Region and Name of Location (Anatomical Location Name) data elements, where anatomical region is known but the exact anatomical locations are not known.\n3) Anatomical Region data element and Name of Location data element (Anatomical Location Name) use different code systems.\n4) The code used for the Name of Location data element is equivalent to the code used for the Anatomical Region data element. \nElse, Fail the test.\n\nNOTE TO TESTER:  a)The XPath for Anatomical Region is: \n/ClinicalDocument/component/structuredBody/component[diag_inv]/section/component[img_exam]/section/entry[img_exam_res]/observation/entryRelationship[region]/observation/value:CD\nb)The XPath for Name of Location (Anatomical Location Name) is:\n/ClinicalDocument/component/structuredBody/component[diag_inv]/section/component[img_exam]/section/entry[img_exam_res]/observation/targetSiteCode\n","1) The value of Anatomical Region data element either subsumes or is equivalent to the value of the Name of Location (Anatomical Location Name) data element.\n\n2) The value of the Anatomical Region is recorded in both the Anatomical Region and Name of Location (Anatomical Location Name) data elements, where anatomical region is known but the exact anatomical locations are not known. \n\n3) Anatomical Region and Name of Location (Anatomical Location Name) shall use different code systems.\n\n4) The code used for the Name of Location data element is equivalent to the code used for the Anatomical Region data element.","TBD",null,0,{"$f":"IF(AND(BGCol(D27)=48,H27=\"N/A\"),1,0)","v":0}]
["TS-DIRDoc","TC-DIRDoc-16","3.20 Image DateTime [NEHTA-1527:2014]\nDefinition: Date, and optionally time, the imaging examination was performed.\n\nData type: DateTime [NEHTA-0794:2011]\nXPath:  ClinicalDocument/component/structuredBody/component[diag_inv]/section/component[img_exam]/section/entry[img_exam_res]/observation/entryRelationship[exam_req]/act/entryRelationship[img_det]/observation/effectiveTime\n","M",1,"Pass the test where the Image DateTime data element passes test case TC Types-18 in the Conformance Test Specification for Authoring Systems.  \nElse, Fail the test.\n","The Image DateTime data element meets the requirements for the DateTime data type in the test set TS-TS (Time stamp) (i.e., the test cases TC-Types-99,TC-Types-100 and TC-Types-101).","TBD",null,0,{"$f":"IF(AND(BGCol(D28)=48,H28=\"N/A\"),1,0)","v":0}]
["TS-DIRDoc","TC-DIRDoc-17","3.22 Observation DateTime [NEHTA-1527:2014]  \nDefinition: Date, and optionally time, when an observation is clinically significant to the condition of the subject of the observation.\n\nThis element SHALL hold the same value as EXAMINATION REQUEST DETAILS > IMAGE DETAILS > Image DateTime. [NEHTA-1528:2014]\n\nData Type: DateTime [NEHTA-0794:2011]\nXPath:  ClinicalDocument/component/structuredBody/component[diag_inv]/section/component[img_exam]/section/entry[img_exam_res]/observation/entryRelationship[res_date]/observation/effectiveTime\n","M",1,"Pass the test where Observation Date Time data element conforms to all the following conditions:\n1) The Observation DateTime data element passes test case TC Types-18 in the Conformance Test Specification for Authoring Systems. \n2)The Observation DateTime data element holds the same value as EXAMINATION REQUEST DETAILS > IMAGE DETAILS > Image DateTime.\n\nElse, Fail the test.\n","1) The Observation DateTime data element meets the requirements for the DateTime data type in the test set TS-TS (Time stamp) (i.e., the test cases TC-Types-99,TC-Types-100 and TC-Types-101).\n\n2) The Observation DateTime data element holds the same value as EXAMINATION REQUEST DETAILS > IMAGE DETAILS > Image DateTime.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D29)=48,H29=\"N/A\"),1,0)","v":0}]
["TS-DIRDoc","TC-DIRDoc-18","3.27 Image Location (Target) [NEHTA-1527:2014]  [NEHTA-1528:2014]\nIf a URL is referenced, then the link SHALL also be present in the corresponding CDA narrative inside a <linkHtml> element.\n\nNote: Image Location (Target) is modelled as an External Act, so the requirements in HL7 Clinical Document Architecture, Release 2 [HL7CDAR2] for external objects apply.\n","C",1,"CONDITION: The Image Location (Target) data element is present and the value of the Image Location (Target) data element contains a URL.\n\nPass the test where Image Location (Target) data element conforms to all the following conditions::\n\n1) The Image Location (Target) data element passes test case TC-Narr-92.\n2) URL referenced in the Image Location (Target) data element is present in the corresponding CDA narrative inside a <linkHtml> element.\n\nElse, Fail the test.\n\nNOTE TO TESTER:  The XPath for Image Location (Target) is: \nClinicalDocument/component/structuredBody/component[diag_inv]/section/component[img_exam]/section/entry[img_exam_res]/observation/entryRelationship[img_loc]/act/reference[img]/externalAct/text\n","1). The Image Location (Target) data element passes test case TC-Narr-92.\n\n2) URL referenced in the Image Location (Target) data element is present in the corresponding CDA narrative inside a <linkHtml> element.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D30)=48,H30=\"N/A\"),1,0)","v":0}]
["TS-DIRDoc","TC-DIRDoc-19","2.21 Document Target [NEHTA-1527:2014] [NEHTA-1528:2014]\nThe link SHALL also be present in the corresponding CDA Narrative in a <linkHtml> element.\n\nNote: Document Target is modelled as an External Document, so the requirements in HL7 Clinical Document Architecture, Release 2 [HL7CDAR2] for external objects apply.\n","M",1,"Pass the test where the Document Target data element passes test step 1 of the test case TC-Narr-92.\nElse, Fail the test.\n\nNOTE TO TESTER:  The XPath for Document Target is: \nClinicalDocument/component/structuredBody/component[diag_inv]/section/entry[doc_detail]/act/reference[document]/externalDocument/text:ED\n","The Document Target data element passes test step 1 of the test case TC-Narr-92.","TBD",null,0,{"$f":"IF(AND(BGCol(D31)=48,H31=\"N/A\"),1,0)","v":0}]
["TS-DIRDoc","END:  TS-DIRDoc (Diagnostic Imaging Report clinical document)"]
[null,null,null,null,null,null,null,"TBD","Total Steps",{"$f":"SUM(J34:J35)","v":23}]
[null,null,null,null,null,null,null,"Fail","Tests Not Started, Failed or TBD",{"$f":"COUNTIF(J8:J31,\"0\")","v":23}]
[null,null,null,null,null,null,null,"N/A","Tests Passed or N/A",{"$f":"COUNTIF(J8:J31,\"1\")","v":0}]
[null,null,null,null,null,null,null,"Pass","%Passed or N/A",{"$f":"SUM(J35/J33)","v":0}]

{"sheet":"FS-DIRProc","index":8,"n_rows":40,"n_cols":11,"rows_kept":40,"cut":false,"hidden":false,"merged":[[0,0,0,1],[1,0,1,1],[2,0,2,1],[3,0,3,1],[0,2,0,5],[1,2,1,5],[2,2,2,5],[3,2,3,5]]}
["Feature set identifier:",null,"FS-DIRProc (Business processes for the authoring system)"]
["Objective:",null,"To assess the conformance to the process requirements for a software system that creates Diagnostic Imaging Reports. These are requirements for creating, superseding and removing Diagnostic Imaging Reports, consent management and record keeping. These requirements are additional to the requirements that apply to the Diagnostic Imaging Reports created by a software system.\n"]
["Strategy:",null,"The eHealth Diagnostic Imaging Report - PCEHR Conformance Profile [NEHTA-1978:2015] includes requirements for the behaviour of the document authoring system. The conformance of the software system to these requirements is assessed by accessing the software system and applying the test cases defined here. In addition, the Clinical Documents - Common Conformance Profile [NEHTA-1850:2015] contains requirements for the behaviour of the software system that apply regardless of the type of document being authored. Test cases for those requirements are listed in the Conformance Test Specification for Authoring Systems  [NEHTA-2209:2016].\n\nTest cases that verify the conformance of Diagnostic Image Reports created by the authoring system are included separately, within this document, in the 'FS-DIRDoc' feature set worksheet. \n\nNote: The terms \"software system\", \"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 as are \"healthcare consumer\" and \"healthcare individual\"."]
["Traceability:",null,"eHealth Diagnostic Imaging Report - PCEHR Conformance Profile [NEHTA-1978:2015]\nClinical Documents - Common Conformance Profile [NEHTA-1850:2015]\n"]
[]
["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-GDIR","START:  TS-GDIR (General diagnostic imaging report)"]
["TS-GDIR","TC-DIRProc-01","023456 [NEHTA-1978:2015]\nA producer SHALL NOT be a:\n• registered consumer portal; or\n• registered provider portal.\n","M",1,"Fail the test where the producer of a clinical document is a registered consumer portal or a registered provider portal.\nElse, Pass the test.","The software system is neither a registered consumer or provider portal.","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":0}]
["TS-GDIR","TC-DIRProc-02","023706 [NEHTA-1850:2015] \nA clinical document producer 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","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: Conformance to other aspects of this requirement is assessed by other test cases in the FS-Doc and FS-Narr feature sets in the Authoring Systems Conformance Test Specification [NEHTA-2209:2016].","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(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":0}]
["TS-GDIR","TC-DIRProc-03","024885 [NEHTA-1978:2015]\nIf the software has no access to the Healthcare Identifiers Service, the software MAY use a healthcare identifier received via an electronic request without needing to revalidate the healthcare identifier.\n",null,null,"No test case is defined for this requirement.\n"]
["TS-GDIR","TC-DIRProc-04","024972 [NEHTA-1978:2015]\nThe software MAY have no access to the Healthcare Identifiers Service if the software only uses healthcare identifiers received via electronic requests.\n\n",null,null,"No test case is defined for this requirement.\n"]
["TS-GDIR","END:  TS-GDIR (General diagnostic imaging report)"]
["TS-Cons","START:  TS-Cons (Consent management)"]
["TS-Cons","TC-DIRProc-05","026757 [NEHTA-1978:2015]\nThe software SHALL store a \"withdrawn consent\" indicator against a request, report, or healthcare encounter if the healthcare individual’s consent to upload reports to their digital health record has been withdrawn. In the absence of any instruction or indication, the software SHALL indicate that consent was not withdrawn.\n","M",null,"Pass the test where:\nIf the healthcare individual’s consent to upload reports to their digital health record has been withdrawn, then the software system records a \"withdrawn consent\" indicator against a request, report, or healthcare encounter, otherwise, the software system records a \"No withdrawn consent\" indicator against a request, report, or healthcare encounter.\n\nElse, Fail the test.\n","If the healthcare individual’s consent to upload reports to their digital health record has been withdrawn, then the software system records a \"withdrawn consent\" indicator against a request, report, or healthcare encounter, otherwise, the software system records a \"No withdrawn consent\" indicator against a request, report, or healthcare encounter.\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":0}]
["TS-Cons","TC-DIRProc-06","026760 [NEHTA-1978:2015]\nThe software SHALL store a \"document uploaded\" indicator for each report to indicate documents that have been uploaded to the digital health record.","M",1,"Pass the test where:\n1) If the diagnostic imaging report is uploaded to their digital health record,  then the software system records the \"document uploaded\" indicator against the report. \nor\n2) If the diagnostic imaging report is created and not uploaded to their digital health record, then the software system does not record the \"document uploaded\" indicator against the report. \n\nElse, Fail the test.\n","1) The software system records a \"document uploaded\" indicator against the DIR report that was uploaded. \n\n2) The software system does not record the \"document uploaded\" indicator against the diagnostic imaging report that is created and not uploaded to their digital health record.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D16)=48,H16=\"N/A\"),1,0)","v":0}]
["TS-Cons","TC-DIRProc-07","026761 [NEHTA-1978:2015]\nPreventing uploading when consent is withdrawn\nThe software SHALL prevent a report from being uploaded where \"Withdrawn consent\" is indicated on the request, report, or the healthcare encounter.\n","M",1,"Pass the test where the software system prevents the diagnostic imaging report from being uploaded to the digital health record, when the \"Withdrawn consent\" indicator is set to \"Withdrawn consent\".\nElse, Fail the test.","The software system prevents the diagnostic imaging report from being uploaded to the digital health record.","TBD",null,0,{"$f":"IF(AND(BGCol(D17)=48,H17=\"N/A\"),1,0)","v":0}]
["TS-Cons","TC-DIRProc-08","026762 [NEHTA-1978:2015]\nThe software SHALL permit a report to be uploaded where:\n• there is no indication of withdrawn consent for the request, report, or encounter; and \n• it is known that the healthcare individual has a digital health record.  \n","M",1,"CONDITION: \n1) There is no indication of withdrawn consent for the request, report, or encounter; and  \n2) It is known that the healthcare individual has a digital health record.\n\nPass the test where the software system permits the diagnostic imaging report to be uploaded to the My Health Record System. Else, Fail the test.\n\n","The software system permits the Diagnostic Imaging Report to be uploaded to the My Health Record System.","TBD",null,0,{"$f":"IF(AND(BGCol(D18)=48,H18=\"N/A\"),1,0)","v":0}]
["TS-Cons","TC-DIRProc-09","026763 [NEHTA-1978:2015]\nThe software SHOULD have the capability to determine the existence and visibility of an individual’s digital health record via a doesPCEHRexist web service call.","O",1,"Pass the test where:\n1) The software system can send a web service request to the My Health Record system via a doesPCEHRexist web service call.\nand \n2) The software system can receive a web service response from the My Health Record system via a doesPCEHRexist web service call.\nElse, mark the test as N/A.","The software system sends and receives a web service request to the My Health Record System via a doesPCEHRexist web service call.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D19)=48,H19=\"N/A\"),1,0)","v":0}]
["TS-Cons","TC-DIRProc-10","026766 [NEHTA-1978:2015]\nThe software SHALL permit the \"Withdrawn consent\" indicator to be updated to reflect new knowledge provided to the diagnostic service provider that the individual has withdrawn consent prior to the upload of the document.\n","M",1,"Pass the test where the software system can change the \"Withdrawn consent\" indicator from \"No withdrawn consent\" to \"Withdrawn consent\" prior to the upload of the document.\n\nElse, Fail the test.","The software system changes the consent setting from \"No withdrawn consent\" to \"Withdrawn consent\" prior to the upload of the document..","TBD",null,0,{"$f":"IF(AND(BGCol(D20)=48,H20=\"N/A\"),1,0)","v":0}]
["TS-Cons","END:  TS-Cons (Consent management)"]
["TS-Record","START:  TS-Record (Record keeping)"]
["TS-Record","TC-DIRProc-11","025072 [NEHTA-1978:2015]\nThe software SHALL record a failure to upload a diagnostic report to the My Health Record system. The information recorded SHALL include the report or document identifier, the error code returned by the My Health Record system, and the date and time. The information recorded SHOULD include the requester’s order identifier and the accession number.","M",1,"Pass the test where:\n1) the software system records a failure to upload a diagnostic imaging report to the My Health Record system.\n2) records the report or document identifier, the error code returned by the My Health Record system and the date and time (with the time zone representing the software system's time zone). \nElse, Fail the test.","The software system records a failure to upload a diagnostic imaging report to the My Health Record system, where it records the accession number, the error code returned by the  My Health Record system and the date and time. \n","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":0}]
["TS-Record",null,null,"O",2,"CONDITION: Software system has the capability to record the requester's order identifier.\n\nPass the test where the requester’s order identifier and the accession number is included in the record. \nElse, mark the test as N/A.\n","The software system records requester's order identifier and the accession number.","TBD",null,0,{"$f":"IF(AND(BGCol(D24)=48,H24=\"N/A\"),1,0)","v":0}]
["TS-Record","TC-DIRProc-12","025073 [NEHTA-1978:2015]\nIf the software uses the Healthcare Identifiers Service to obtain or ensure the validity of an IHI or other healthcare identifier, the software SHALL record a failure to create a diagnostic report when the reason for the failure is an inability to obtain or validate one or more healthcare identifiers. \nThe information recorded SHALL include the report or document identifier, the error code returned by Healthcare Identifiers Service, and the date and time of the error. \nThe information recorded SHOULD include the requester’s order identifier and accession number. \n","C",1,"CONDITION: Software system has the capability to obtain or validate an IHI or other healthcare identifier using HI Service.\n\nPass the test where the software system:\n1) records a failure to create a diagnostic report when the reason for the failure is an inability to obtain or validate one or more healthcare identifiers; and\n2) records the report or document identifier, the error code returned by Healthcare Identifiers Service, and the date and time of the error (with the time zone representing the software system's time zone). \nElse, Fail the test.\n","The software system records a failure to create a diagnostic report when the reason for the failure is an inability to obtain or validate one or more healthcare identifiers.  \nThe software system records the report or document identifier, the error code returned by Healthcare Identifiers Service, and the date and time of the error (with the time zone representing the software system's time zone). \n","TBD",null,0,{"$f":"IF(AND(BGCol(D25)=48,H25=\"N/A\"),1,0)","v":0}]
[null,null,null,"O",2,"CONDITION: Software system has the capability to obtain or validate an IHI or other healthcare identifier using HI Service.\n\nPass the test where the requester's order identifier and accession number are included in the record. \nElse, mark the test as N/A.\n","The software system records requester's order identifier and the accession number.","TBD",null,0,{"$f":"IF(AND(BGCol(D26)=48,H26=\"N/A\"),1,0)","v":0}]
["TS-Record","TC-DIRProc-13","025074 [NEHTA-1978:2015]\nThe software SHALL record a decision to not upload a diagnostic report. \nThe information recorded SHALL include the report or document identifier, the reason for not uploading the report to the My Health Record System, and the date and time of the decision. \nThe information recorded SHOULD include the requester’s order identifier and accession number.\n","M",1,"Pass the test where:\n1) the software system records the decision not to upload the diagnostic imaging report to the My Health Record system, and\n2) records the report or document identifier, the reason for not uploading the report to the My Health Record system, and the date and time of the decision (with the time zone representing the software System's time zone). \nElse, Fail the test.\n","The software system records a decision not to upload a diagnostic imaging report to the My Health Record system, where it records the accession number, and the date and time of the decision. ","TBD",null,0,{"$f":"IF(AND(BGCol(D27)=48,H27=\"N/A\"),1,0)","v":0}]
[null,null,null,"O",2,"CONDITION: Software system has the capability to record the requester's order identifier.\n\nPass the test where the requester’s order identifier and accession number are included in the record. \nElse, mark the test as N/A.\n","The software system records the requester's order identifier and accession number.","TBD",null,0,{"$f":"IF(AND(BGCol(D28)=48,H28=\"N/A\"),1,0)","v":0}]
["TS-Record","TC-DIRProc-14","025155 [NEHTA-1978:2015]\nThe software SHOULD record the reversal of a decision by a diagnostic service provider to not upload a diagnostic report. The information recorded SHOULD include the report or document identifier, the requester’s order identifier, the accession number, and the date and time of the reversal of the decision. ","O",1,"CONDITION: Software system is reversing a decision not to upload a diagnostic report.\n\nPass the test where the software system keeps a record of the reversal of the decision by the healthcare provider not to upload the diagnostic report to the My Health Record System.\nElse, mark the test as N/A.\n","The software system records the reversal of a decision not to upload a diagnostic report to the My Health Record system.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D29)=48,H29=\"N/A\"),1,0)","v":0}]
[null,null,null,"O",2,"CONDITION: Software system has the capability to record the requester's order identifier.\n\nPass the test where the report or document identifier, requester's order identifier, the accession number, and the date and time of the reversal of the decision  (with the time zone representing the software system's time zone) are included in the record. \nElse, mark the test as N/A.\n","The software system records the report or document identifier, requester's order identifier, the accession number and the date and time of the reversal of the decision.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D30)=48,H30=\"N/A\"),1,0)","v":0}]
["TS-Record","TC-DIRProc-15.1","025156 [NEHTA-1978:2015]\nThe software SHOULD record the original withdrawal of consent indicator values associated with a request, report, or healthcare encounter for diagnostic services. The software SHOULD also record any change to the withdrawal of consent indicator. \nThe information recorded SHOULD include the report or document identifier, the accession number, the requester’s order identifier, the original and updated value of the withdrawal of consent indicator and the date and time the change of consent was captured. \n","O",1,"Pass the test where the software System records the healthcare individual's original withdrawal of consent indicator values  associated with a request, report, or healthcare encounter for diagnostic services.\nElse, mark the test as N/A.","The software system records the healthcare individual's original consent setting.","TBD",null,0,{"$f":"IF(AND(BGCol(D31)=48,H31=\"N/A\"),1,0)","v":0}]
[null,null,null,"O",2,"Pass the test where the report or document identifier, the accession number, the requester’s order identifier, the original value of the withdrawal of consent indicator, and the date and time the change of consent was captured are included in the record. \nElse, mark the test as N/A.\n","The software system records the healthcare individual's original consent setting.","TBD",null,0,{"$f":"IF(AND(BGCol(D32)=48,H32=\"N/A\"),1,0)","v":0}]
["TS-Record","TC-DIRProc-15.2","025156 [NEHTA-1978:2015]\nThe software SHOULD record the original withdrawal of consent indicator values associated with a request, report, or healthcare encounter for diagnostic services. The software SHOULD also record any change to the withdrawal of consent indicator. \nThe information recorded SHOULD include the report or document identifier, the accession number, the requester’s order identifier, the original and updated value of the withdrawal of consent indicator, and the date and time the change of consent was captured. \n","O",1,"Pass the test where the software system records the changes made to the healthcare individual's original (if available) withdrawal of consent indicator values associated with a request, report, or healthcare encounter for diagnostic services.\nElse, mark the test as N/A.\n","The software system records the report or document identifier, the accession number, the requester’s order identifier, the original (if available) and updated value of the withdrawal of consent indicator, and the date and time of the change of consent.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D33)=48,H33=\"N/A\"),1,0)","v":0}]
[null,null,null,"O",2,"CONDITION: Software system has the capability to record the requester's order identifier.\n\nPass the test where the report or document identifier, the accession number, the requester’s order identifier, the original and updated value of the withdrawal of consent indicator, and the change of consent date and time captured are included in the record. \nElse, mark the test as N/A.\n","The software system records the report or document identifier, the accession number, the requester’s order identifier, the original and updated value of the withdrawal of consent indicator, and the date and time of the change of consent.","TBD",null,0,{"$f":"IF(AND(BGCol(D34)=48,H34=\"N/A\"),1,0)","v":0}]
["TS-Record","TC-DIRProc-16","025083 [NEHTA-1978:2015]\nThe software SHOULD have the capability to retrieve and display the records of:\n• a failure to create or upload a diagnostic report;  \n• a decision, and reversal of a decision, to not upload a diagnostic report; and \n• the original and changed withdrawal of consent indicator values. \n","O",1,"Pass the test where the software system can retrieve and display records of a failure to create or upload a diagnostic report; a decision, and reversal of a decision, to not upload a diagnostic report; and the original and changed withdrawal of consent indicator values.\nElse, mark the test as N/A.\n","The software retrieves and displays information from its records.","TBD",null,0,{"$f":"IF(AND(BGCol(D35)=48,H35=\"N/A\"),1,0)","v":0}]
["TS-Record","END:  TS-Record (Record keeping)"]
[null,null,null,null,null,null,null,"TBD","Total Steps",{"$f":"SUM(J38:J39)","v":21}]
[null,null,null,null,null,null,null,"Fail","Tests Not Started, Failed or TBD",{"$f":"COUNTIF(J8:J35,\"0\")","v":21}]
[null,null,null,null,null,null,null,"N/A","Tests Passed or N/A",{"$f":"COUNTIF(J8:J35,\"1\")","v":0}]
[null,null,null,null,null,null,null,"Pass","%Passed or N/A",{"$f":"SUM(J39/J37)","v":0}]

{"sheet":"Process models","index":9,"n_rows":202,"n_cols":6,"rows_kept":202,"cut":false,"hidden":false,"merged":[[8,1,8,5],[9,2,9,5],[2,1,2,5],[3,2,3,4],[4,1,4,5],[5,1,5,4],[6,2,6,4],[7,1,7,5]]}
[]
[null,"Process models for Diagnostic Imaging Report"]
[null,"The process models used in this DIR CTS are to aid in the structure of testing and are not indicative of a workflow that should be followed by the user's authoring system.\n\nThe tables in this worksheet list process requirements, which are conformance requirements related to the following business processes:"]
[null,null,"• Author a new Diagnostic Imaging Report\n• Store or upload to the My Health Record system\n• Change consent setting\n• Supersede a Diagnostic Imaging Report\n• Remove a Diagnostic Imaging Report\n• Retrieve records\n"]
[null,"Conformance requirements that are solely related to the content of a Diagnostic Imaging Report, and are unrelated to the process, are not listed here. "]
[null,"The requirements specifications referenced here are:"]
[null,null,"1. Clinical Documents - Common Conformance Profile v1.6 [NEHTA-1850:2015]\n2. eHealth Diagnostic Imaging Report - My Health Record Conformance Profile v1.1 [NEHTA-2215:2016]\n3. PCEHR Connecting Systems - Conformance Requirements v1.5 [NEHTA-1297:2012]"]
[null,"In addition, generic process models for PCEHR Connecting Systems are listed in PCEHR Connecting Systems - Use Cases v1.1 [NEHTA-1298:2012]."]
[null,"The test cases applying to each of the process tasks are also listed below.  Test cases with an identifier commencing with:"]
[null,null,"1. \"TC-DIRProc\" are listed in the FS-DIRProc feature set within this conformance test specification.\n2. \"TC-DIRDoc\" are listed in the FS-DIRDoc feature set within this conformance test specification.\n3. \"UC.CIS\" relate to business processes for PCEHR connecting systems and are listed in the PCEHR Connecting Systems - Conformance Test Specification [NEHTA-1299:2012].\n"]
["THIS HEADER CAN BE COLLAPSED BY CLICKING THE \"-\" SYMBOL ON THE LEFT."]
[null,"A. Author a new Diagnostic Imaging Report (business process)"]
[null,"The process commences when a request for diagnostic services is received."]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[null,"#","PROCESS ITEM (AND TYPE)","DESCRIPTION","PROCESS REQUIREMENTS","TEST CASES"]
[null,"A9","Enter the Request details (task)","Information in the request for diagnostic services is entered into the software system.\n","No testable process requirements.","No testable test cases."]
[null,"A1","Consent information present? (decision)","The request for diagnostic services may include an explicit indication of consent, an explicit withdrawl of consent, or may not contain any information about consent.\n","No testable process requirements.","No testable test cases."]
[null,"A2","Record \"No Withdrawn consent\" (task)","If the healthcare individual has a record in the My Health record system and if the request for diagnostic services explicitly states that the healthcare individual has consented to their Diagnostic Imaging Reports being uploaded to the My Health Record system then the software records \"No Withdrawn consent\".\n\nIf the request for diagnostic services had no indication of consent but it is found that the My Health Record system indicates the healthcare individual has a health record in the My Health Record system (using a doesPCEHRexists web service call) then the software records \"No Withdrawn consent\".\n","eHealth Diagnostic Imaging Report - MyHealthRecord Conformance Profile: \n026757 - \"Withdrawn consent\" indicator\n025156 - Record the original and changed withdrawal of consent indicator values\n026763 - Invoke doesPCEHRexist web service","\n\nTC-DIRProc-05 (026757), \nTC-DIRProc-15.1 (025156)"]
[null,"A3","Record \"Withdrawn consent\" (task)","If the healthcare individual has a record in the My Health record system and if the request for diagnostic services explicitly states that the healthcare individual has withdrawn consent to their Diagnostic Imaging Reports being uploaded to the My Health Record system then the software records \"Withdrawn consent\".\n","eHealth Diagnostic Imaging Report - MyHealthRecord Conformance Profile: \n026757 - \"Withdrawn consent\" indicator\n025156 - Record the original and changed withdrawal of consent indicator values\n","\n\nTC-DIRProc-05 (026757), \nTC-DIRProc-15.1 (025156)"]
[null,"A4","A4. UC.CIS.001 Check if an advertised\ndigital health record exists via doesPCEHRexist web\nservice call (subprocess)","Use case documented in PCEHR Connecting Systems - Conformance Test Specification v1.6, is applied if the request for diagnostic services did not contain any consent information.\n\nIf no indication of consent is present in the request received, then the doesPCEHRexists web service call is made to determine the existence of a health record for the healthcare individual in the My Health Record system.\n","eHealth Diagnostic Imaging Report - MyHealthRecord Conformance Profile: \n026763 - Invoke doesPCEHRexist web service\nUse case UC.CIS.001 - Check if an advertised PCEHR exists\n","\n\nTC-DIRProc-09 (026763).\n Test cases for UC.CIS.001, noting that requirement 024885 overrides PCEHR connecting systems requirement 019100."]
[null,"A5","Record \"digital health record does not exist\" (task)","If the software has recorded the consent as either \"No Withdrawn consent\" or \"Withdrawn consent\" then the health record in the My Health Record system for the healthcare individual exists and the software records \"digital health record exists\". \n\nIf there is no indication of consent in the request received, then the doesPCEHRexists web service call is made. If the doesPCEHRexists returns true, then the software records \"digital health record exists\" and if the doesPCEHRexists returns false or returns an error, then the software records \"digital health record does not exist\".\n\nNote: If the My Health Record system states there is no health record, then it is possible that the healthcare individual has a health record in the My Health Record system that is hidden due to access controls.","eHealth Diagnostic Imaging Report - MyHealthRecord Conformance Profile: \n026757 - \"Withdrawn consent\" indicator\n026763 - Invoke doesPCEHRexist web service\n025156 - Record the original and changed withdrawal of consent indicator values\n","\n\nTC-DIRProc-05 (026757),\nTC-DIRProc-09 (026763),\nTC-DIRProc-15.1 (025156) \n"]
[null,"A6","Perform diagnostic tests (task)","The radiology tests are performed. The looping symbol indicates a number of diagnostic tests may be performed. The remainder of the process flow may be repeated for every diagnostic test result resulting in multiple Diagnostic Imaging Reports; otherwise one Diagnostic Imaging Report may be used to record the results of a number of diagnostic tests.\n","No testable process requirements.","No testable test cases."]
[null,"A7","Author a Diagnostic Imaging Report (task)","The Diagnostic Imaging Report is authored and is available for sending to the requester. Depending on the software design, the clinical document may also be authored as part of this task. \n","No testable process requirements.","No testable test cases."]
[null,"A8","Record \"digital health record exists\" (task)","If the healthcare individual has a record in the My Health record system and if the request for diagnostic services explicitly states the indication/withdrawl of consent for Diagnostic Imaging Reports to be uploaded to the My Health Record system, then the software records \"No Withdrawn consent\" or \"Withdrawn consent\" respectively. In this case, the software records \"digital health record exists\".  \n\nIf the healthcare individual has a record in the My Health record system and if the request for diagnostic services had no indication of consent but it is found that the healthcare individual has a health record in the My Health Record system (using doesPCEHRexists web service call) then the software records \"digital health record exists\".          ","026763 - Invoke doesPCEHRexist web service","TC-DIRProc-09 (026763)"]
[null,"A10","digital health record exists? (decision)","If the request received by the software system has a consent with a value  \"No Withdrawn consent\" or \"Withdrawn consent\" and the health record in the My Health Record system for the healthcare individual exists, then the decision is true. \n\nIf the request received by the software system has no indication of consent, then the doesPCEHRexists web service call is made. If the doesPCEHRexists returns true, then the decision (A10) is true, otherwise the decision (A10) is false.\n","026763 - Invoke doesPCEHRexist web service","TC-DIRProc-09 (026763)"]
[null,"B","Store or upload to the My Health Record system (subprocess)\n","Storing and uploading a Diagnostic Imaging Report is documented as process B.","Requirements are listed in the process requirements of the subprocess.","No testable test cases."]
[]
[]
[null,"B. Store or upload to the My Health Record system (subprocess)"]
[" ","                                    "]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[null,"#","PROCESS ITEM (AND TYPE)","DESCRIPTION","PROCESS REQUIREMENTS","TEST CASES"]
[null,"B1","Consent for upload? (decision)","If the software has recorded the consent setting as \"No Withdrawn consent\" then the healthcare individual has consented to the upload of the Diagnostic Imaging Report to the My Health Record system, otherwise the consent setting is \"Withdrawn consent\" and the Diagnostic Imaging Report cannot be uploaded the My Health Record system until the consent setting is revised.\n","No testable process requirements.","No testable test cases."]
[null,"B2","Store a Diagnostic Imaging Report document for a future upload (task)","If the software has recorded the consent setting as \"Withdrawn consent\" then the Diagnostic Imaging Report is stored for future use, in the event that the consent setting is revised.\n","eHealth Diagnostic Imaging Report - MyHealthRecord Conformance Profile: \n026761 - Preventing uploading when consent is withdrawn","\n\nTC-DIRProc-07 (026761)"]
[null,"B3","Prepare for upload (task)","The software prepares the Diagnostic Imaging Report for upload to the My Health Record system. This includes creating the clinical document, creating an eSignature and CDA package and obtaining or validating healthcare identifiers, if they were not obtained prior to this task.\n\n","eHealth Diagnostic Imaging Report - MyHealthRecord Conformance Profile: \n025065 - When the document author is not one person\n025076 - Multiple reporting radiologists\n023436 - Identifier for document author\n023553 - Identifier for reporting radiologist\n\nClinical Documents - Common Conformance Profile: \n023731 - The value of the personId if approver is not recorded in the eSignature\n023732 - Authenticate the person identified as the approver recorded in the eSignature\n023733 - Record approver's approval of the contents of the clinical document","\n\nTC-DIRDoc-07(025065), \nTC-DIRDoc-08(025076), \nTC-DIRDoc-11 (023436), \nTC-DIRDoc-12(023553) \n"]
[null,"B11","Ready to upload? (decision)","If the software has successfully created a CDA package containing the Diagnostic Imaging Report and has obtained a valid set of healthcare identifiers, then the Diagnostic Imaging Report is ready to be uploaded to the My Health Record system.\n","No testable process requirements.","No testable test cases."]
[null,"B4","New or replacement Diagnostic Imaging Report? (decision)","Different tasks are performed depending on whether the Diagnostic Imaging Report is a new report or a revision of a report that was previously uploaded to the My Health Record system.\n","No testable process requirements.","No testable test cases."]
[null,"B5","UC.CIS.201 Upload a clinical document (subprocess)","Use case documented in PCEHR Connecting Systems - Conformance Test Specification v1.6 is applied for uploading the Diagnostic Imaging Report to the My Health Record system.\n\nThe possible outcomes are that the Diagnostic Imaging Report upload to the My Health Record system:\na) is successful, or \nb) was attempted but failed, or \nc) the healthcare provider withheld the report from being uploaded.\n\nThe software prevents a Diagnostic Imaging report from being uploaded to the My Health Record system, where \"Withdrawn consent\" is indicated on the request.\n \nThis subprocess is documented in the Section 4.1 - Figure 3: UC.CIS.201 - Upload a clinical document of NEHTA-1298:2012 PCEHR Connecting Systems - Use Cases v1.1[NEHTA-1298:2012].","eHealth Diagnostic Imaging Report - MyHealthRecord Conformance Profile:\n026762 - Uploading when a digital health record exists\nUC.CIS.201 - Upload a Clinical Document","\n\nTC-DIRProc-08 (026762), \nTest cases for UC.CIS.201."]
[null,"B6","Record upload failure (task)","If the Diagnostic Imaging Report could not be uploaded to the My Health Record system, then the upload failure is recorded.","eHealth Diagnostic Imaging Report - MyHealthRecord Conformance Profile: \n025072 - Record upload failure\n","\n\nTC-DIRProc-11 (025072)"]
[null,"B7","Withhold the document (task)","The Diagnostic Imaging Report document is withheld from being uploaded to the My Health Record system, due to a decision by a healthcare provider. ","eHealth Diagnostic Imaging Report - MyHealthRecord Conformance Profile: \n025074 - Record a decision to not upload a diagnostic report\n","\n\nTC-DIRProc-13 (025074)"]
[null,"B8","Reverse a withhold decision (task)","An event occurs that results in the healthcare provider’s reversal of a previous decision to not upload a Diagnostic Imaging Report.","eHealth Diagnostic Imaging Report - MyHealthRecord Conformance Profile: \n025155 - Record the reversal of a diagnostic service provider's decision to not upload a diagnostic report\n","\n\nTC-DIRProc-14(025155)"]
[null,"B9","UC.CIS.202 Supersede a clinical document (subprocess)","Use case documented in  PCEHR Connecting Systems - Conformance Test Specification v1.6, is applied for superseding the existing Diagnostic Imaging Report in the My Health Record system.\n\nThe possible outcomes are that the replacement Diagnostic Imaging Report is:\na) successfully uploaded to the My Health Record system, or \nb) the upload was attempted but failed, or \nc) that the healthcare provider withheld the report from being uploaded.\n\nThis subprocess is documented in the Section 4.2 - Figure 5: UC.CIS.202 – Supersede a clinical document of NEHTA-1298:2012 PCEHR Connecting Systems - Use Cases v1.1[NEHTA-1298:2012].","eHealth Diagnostic Imaging Report - MyHealthRecord Conformance Profile: \nUC.CIS.202 - Supersede a clinical document\n","\n\nTest cases for UC.CIS.202 (note that requirement 024885 overrides PCEHR connecting systems requirement 019100)"]
[null,"B10","Record any healthcare identifier failure (task)","If a Diagnostic Imaging Report cannot be uploaded to the My Health Record system due to a failure to obtain a valid healthcare identifier then this failure is recorded.","eHealth Diagnostic Imaging Report - MyHealthRecord Conformance Profile: \n025073 - Record information on validity of healthcare identifiers","\n\nTC-DIRProc-12 (025073)"]
[null,"B12","Record \"Document uploaded\" (task)","If a Diagnostic Imaging Report is uploaded to the My Health Record system, then the software records \"Document uploaded\".","eHealth Diagnostic Imaging Report - MyHealthRecord Conformance Profile: \n026760 - \"Document uploaded\" indicator\n","\n\nTC-DIRProc-06 (026760)"]
[null,"B13","Record \"Document not uploaded\" (task)","If a Diagnostic Imaging Report cannot be uploaded to the My Health Record system, then the software records \"Document not uploaded\".","eHealth Diagnostic Imaging Report - MyHealthRecord Conformance Profile: \n026760 - \"Document uploaded\" indicator\n","\n\nTC-DIRProc-06 (026760)"]
[null,"B14","Upload sucessful? (Decision)","Different tasks are performed depending on outcome of the attempt made to upload the Diagnostic Imaging Report document to the My Health Record system.\n\nThe possible outcomes from this decision are.\n1. Upload of the Diagnostic Imaging Report document to the My Health Record system succeeds.\n2. Upload of the Diagnostic Imaging Report document to the My Health Record system fails.\n3. The healthcare provider has withheld the Diagnostic Imaging Report document from being uploaded to the My Health Record system.","No testable process requirements.","No testable test cases."]
[]
[null,"D. Change consent setting (business process)"]
[null,"The process commences when an indication of consent is received some time after a request for diagnostic services is received."]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[null,"#","PROCESS ITEM (AND TYPE)","DESCRIPTION","PROCESS REQUIREMENTS","TEST CASES"]
[null,"D7","Enter the indication of consent (task)","The indication of consent may be in any form, including paper, electronic or verbal. Information from the indication of consent is entered into the software system.\n","No testable process requirements.","No testable test cases."]
[null,"D1","Revise the consent setting? (decision)","If the indication of consent states that the healthcare individual has consented to Diagnostic Imaging Reports being uploaded to the My Health Record system then the software examines the previously recorded consent settings and determines if needs to be revised.\nIf the recorded consent setting is \"No Withdrawn consent\" then the decision is ‘no’. \nIf the recorded consent setting is \"Withdrawn consent\" then the decision is ‘yes’.","eHealth Diagnostic Imaging Report - MyHealthRecord Conformance Profile: \n026766 - Changing \"Withdrawn consent\" indicator","\n\nTC-DIRProc-10 (026766)"]
[null,"D2","Record \"No Withdrawn consent\" (task)","The consent setting recorded by the software is changed to \"No Withdrawn consent\".\n","eHealth Diagnostic Imaging Report - MyHealthRecord Conformance Profile: \n026757 - \"Withdrawn consent\" indicator\n026762 - software system permits the report to be uploaded to the My Health Record system\n025156 - Record the original and changed withdrawal of consent indicator values\n\n","\n\nTC-DIRProc-05 (026757), \nTC-DIRProc-08 (026762), \n\nTC-DIRProc-15.2 (025156)"]
[null,"D3","Any stored diagnostic records? (decision)","The software determines if there are any previously stored diagnostic records (for upload) awaiting a change of consent. Read this task in relation to the task B2.\n","No testable process requirements.","No testable test cases."]
[null,"D4","Select the latest version of the Diagnostic Imaging Report (task)","If there are any previously stored Diagnostic Imaging Reports then it is possible that the store includes more than one version of a report (see the Supersede a Diagnostic Imaging Report process). The most recent version of a Diagnostic Imaging report is selected for uploading to the My Health Record system (i.e., older versions are not selected for upload).\n","No testable process requirements.","No testable test cases."]
[null,"B","Store or Upload a Diagnostic Imaging Report (subprocess)","Storing and uploading a Diagnostic Imaging Report is documented as process B.\n","No testable process requirements.","No testable test cases."]
[" ","D5","May consent be withdrawn? (decision)","Consent cannot be withdrawn if any Diagnostic Imaging Reports resulting from the diagnostic services request have been uploaded to the My Health Record system, otherwise consent can be withdrawn.\n","No testable process requirements.","No testable test cases."]
[null,"D6","Record \"Withdrawn consent\" (task)","If the request to withdraw consent can be acted upon, then the software records the consent setting as \"Withdrawn consent\". \n","eHealth Diagnostic Imaging Report - MyHealthRecord Conformance Profile: \n026757 - \"Withdrawn consent\" indicator\n025156 - Record the original and changed withdrawal of consent indicator values.  \n","\n\nTC-DIRProc-05 (026757), \nTC-DIRProc-15.2 (025156)."]
[null,"D8","Consent provided? (Decision)","If the indication of consent states that the healthcare individual has consented to Diagnostic Imaging Reports being uploaded to the My Health Record system, then the decision is set to \"Consent provided\". \n\nIf the indication of consent states that the healthcare individual has withdrawn consent to upload Diagnostic Imaging Reports to the My Health Record system, then the decision is set to \"Consent withdrawn\".","No testable process requirements.","No testable test cases."]
[]
[]
[null,"E. Supersede a Diagnostic Imaging Report (business process)"]
[]
[null,"The process commences whenever the diagnostic service provider needs to supersede a previously authored Diagnostic Imaging report with a replacement report."]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[null,"#","PROCESS ITEM (AND TYPE)","DESCRIPTION","PROCESS REQUIREMENTS","TEST CASES"]
[null,"E1","Create a replacement Diagnostic Imaging Report (task)","A Diagnostic Imaging Report is created to replace a previously authored Diagnostic Imaging Report. Depending on the software design, the replacement clinical document may also be created as part of this task. In this model, it is assumed the replacement clinical document is created during this task. The replacement Diagnostic Imaging Report is authored even if the consent setting is \"Withdrawn consent\" as the healthcare individual may change their consent to \"No Withdrawn consent\".\n\nNote: The previously authored Diagnostic Imaging Report may have been uploaded to the My Health Record system or may be in storage for upload at a future date.\n","eHealth Diagnostic Imaging Report - MyHealthRecord Conformance Profile: \n025065 - Mandatory Document Author Values used\n025076 - Multiple reporting radiologists\n023436 - Identifier for document author\n023553 - Identifier for reporting radiologist\n\n\nClinical Documents - Common Conformance Profile: \n023731 - The value of the personId if approver is not recorded in the eSignature\n023732 - Authenticate the person identified as the approver recorded in the eSignature\n023733 - Record approver's approval of the contents of the clinical document\n","\n\nTC-DIRDoc-07 (025065), \nTC-DIRDoc-08 (025076), \nTC-DIRDoc-11 (023436), \nTC-DIRDoc-12 (023553) \n"]
[null,"E2","Digital health record exists? (decision)","If the request received by the software system has a consent with a value  \"No Withdrawn consent\" or \"Withdrawn consent\" then the health record in the My Health Record system for the healthcare individual exists and the decision is true. \n\nIf the request received by the software system has no indication of consent, then the doesPCEHRexists web service call is made. If the doesPCEHRexists returns true, then the decision (E2) is true otherwise the decision (E2) is false.\n","No testable process requirements.","No testable test cases."]
[null,"B","Store or upload to the My Health Record system (subprocess)","Storing and uploading a Diagnostic Imaging Report is documented as process B.\n","No testable process requirements.","No testable test cases."]
[]
[]
[null,"F. Remove a Diagnostic Imaging Report (business process)"]
[]
[null,"The process commences whenever the diagnostic service provider needs to remove a previously authored Diagnostic Imaging report that is already uploaded to the My Health Record system."]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[null,"#","PROCESS ITEM (AND TYPE)","DESCRIPTION","PROCESS REQUIREMENTS","TEST CASES"]
[null,"F3","Select a document to remove (task)","The Diagnostic Imaging Report to be removed is selected.\n","No testable process requirements.","No testable test cases."]
[null,"F1","Obtain/validate healthcare identifiers (task)","Healthcare identifiers may be obtained from a) manual input, b) the HI Service, or c) the diagnostic service request, and are validated using the HI service.  \nIf a healthcare identifier is found to be invalid, then a failure is recorded.\n","No testable process requirements.","No testable test cases."]
[null,"F2","UC.CIS.203 Remove a clinical document (subprocess)","Use case documented in PCEHR Connecting Systems - Conformance Test Specification v1.6, is applied for removing the Diagnostic Imaging Report that is already uploaded to the My Health Record system.\n","eHealth Diagnostic Imaging Report - MyHealthRecord Conformance Profile: \nUC.CIS.203 - Remove a Clinical Document\n","\n\nTest cases for UC.CIS.203 (note that requirement 024885 overrides PCEHR connecting systems requirement 019100)"]
[]
[]
[null,"G. Retrieve records (business process)"]
[]
[]
[]
[]
[]
[]
[]
[]
[null,"#","PROCESS ITEM (AND TYPE)","DESCRIPTION","PROCESS REQUIREMENTS","TEST CASES"]
[null,"G1","Retrieve recorded information (task)","Retrieve information related to a request for diagnostic services, e.g. to determine why a Diagnostic Imaging Report was not uploaded to the My Health Record system.","eHealth Diagnostic Imaging Report - MyHealthRecord Conformance Profile: \n025083 - Retrievable records\n","\n\nTC-DIRProc-16 (025083)"]

{"sheet":"TSR","index":10,"n_rows":29,"n_cols":7,"rows_kept":29,"cut":false,"hidden":false,"merged":[]}
[null,"Australian Digital Health Agency"]
[null,null,null,"TEST SUMMARY REPORT\n"]
[]
[null,null,"Software developer organisation:","Please complete"]
[null,null,"Software name:","Please complete"]
[null,null,"Software version:","Please complete"]
[null,null,"Software description:","Please complete"]
[null,null,"Testing location address:","Please complete"]
[null,null,"Date(s) of testing:","Please complete"]
[null,null,"Name of person(s) conducting tests:","Please complete"]
[null,null,"Operating System/Environment Configuration (name and version)","Optional."]
[null,null,"Additional software tools and versions used which are not subject to testing (e.g. web browser)","Optional."]
[]
[]
[]
[]
[null,null,null,"THIS SECTION DOES NOT NEED TO BE MANUALLY FILLED IN - IT WILL BE AUTOMATICALLY CALCULATED."]
[null,null,"Scenario worksheet"," Total % Tests Passed or N/A","Number of Scenarios","Scenarios Complete"]
[null,1,"TP-NewDoc",{"$f":"'TP-NewDoc'!$F456","v":0},{"$f":"'TP-NewDoc'!C466","v":9},{"$f":"'TP-NewDoc'!C464","v":0}," "]
[null,2,"TP-Consent",{"$f":"'TP-Consent'!F150","v":0},{"$f":"'TP-Consent'!C155","v":4},{"$f":"'TP-Consent'!C153","v":0}]
[null,3,"TP-Supersede",{"$f":"'TP-Supersede'!$F150","v":0},{"$f":"'TP-Supersede'!C154","v":3},{"$f":"'TP-Supersede'!C152","v":0}]
[null,4,"TP-Remove",{"$f":"'TP-Remove'!$F29","v":0},{"$f":"'TP-Remove'!C31","v":1},{"$f":"'TP-Remove'!C29","v":0}]
[null,5,"TP-DIR",{"$f":"'TP-DIR'!$F$194","v":0},{"$f":"'TP-DIR'!$C$199","v":4},{"$f":"'TP-DIR'!$C$197","v":0}]
[]
[null,null,"THIS SECTION DOES NOT NEED TO BE MANUALLY FILLED IN - IT WILL BE AUTOMATICALLY CALCULATED USING A MACRO. PRESS <F9> IF YOU HAVE MACROS DISABLED."]
[null,null,"Test Case worksheet ","Test % Success Rate","Number of Tests","Number of \"N/A\" test results for mandatory tests"]
[null,null,"FS-DIRDoc",{"$f":"'FS-DIRDoc '!$J36","v":0},{"$f":"'FS-DIRDoc '!$J33","v":23},{"$f":"SUM('FS-DIRDoc '!K:K)","v":0}]
[null,null,"FS-DIRProc",{"$f":"'FS-DIRProc'!$J40","v":0},{"$f":"'FS-DIRProc'!$J37","v":21},{"$f":"SUM('FS-DIRProc'!K:K)","v":0}]
[null,{"$f":"IF(OR(ISERROR(F27),ISERROR(F28)),\"WARNING: You must enable macros for this workbook.\",IF(SUM(F27:F28)>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":""}]

{"sheet":"Traceability","index":11,"n_rows":61,"n_cols":35,"rows_kept":61,"cut":false,"hidden":false,"merged":[[2,2,14,2],[15,2,21,2],[24,2,38,2],[39,2,59,2]]}
[]
[null,"Traceability Reference","Related Specification","Conformance Requirement","Test Cases","Feature Set & Test Case Reference","Test Case Exists?","Priority","Test Steps","TP-Dir-01.1 ","TP-Dir-01.2 ","TP-Dir-02.1","TP-Dir-02.2","TP-Dir-03","TP-Dir-04","TP-NewDoc-01","TP-NewDoc-02","TP-NewDoc-03","TP-NewDoc-04","TP-NewDoc-05","TP-NewDoc-06","TP-NewDoc-07","TP-NewDoc-08","TP-NewDoc-09","TP-Consent-01","TP-Consent-02","TP-Consent-03","TP-Consent-04","TP-Supersede-01","TP-Supersede-02","TP-Supersede-03","TP-Remove-01","Notes"]
[null,"TR-DIRCTS-001","NEHTA-1978:2015","023435 - Conform to the requirements for one, and only one, of the following conformance levels: 3A or 3B as defined in the Common Conformance Profile for Clinical Documents.","TC-DIRDoc-01","FS-DIRDoc","P","M",1,"P",null,null,null,null,"P","P","P","P","P","P",null,null,null,"P",null,null,"P",null,"P","P"]
[null,"TR-DIRCTS-002",null,"023473 - Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TC-DIRDoc-02","FS-DIRDoc","P","M",2,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-DIRCTS-003",null,"023651 - The values of diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.","TC-DIRDoc-03","FS-DIRDoc","P","M",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-DIRCTS-004",null,"025075 - Various Diagnostic Imaging Report Results and Documents not nullflavor.","TC-DIRDoc-04","FS-DIRDoc","P","M",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-DIRCTS-005",null,"025157 - SNOMED-CT-AU not nullFlavor.","TC-DIRDoc-05","FS-DIRDoc","P","C",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-DIRCTS-006",null,"024798 - Sort test results.","TC-DIRDoc-06","FS-DIRDoc","P","O",1,"P","P","P","P","P",null,"P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-DIRCTS-007",null,"026616 - Check the narrative and section title.","TC-DIRDoc-20","FS-DIRDoc","P","C",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-DIRCTS-008",null,"025065 - Mandatory Document Author Values used.","TC-DIRDoc-07","FS-DIRDoc","P","C",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-DIRCTS-009",null,"025076 - Mandatory Reporting Radiologist Values used.","TC-DIRDoc-08","FS-DIRDoc","P","C",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-DIRCTS-010",null,"024732 - References in CDA Package.","TC-DIRDoc-09","FS-DIRDoc","O","-",0,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-DIRCTS-011",null,"024988  - References in CDA Package.","TC-DIRDoc-10","FS-DIRDoc","O","-",0,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-DIRCTS-012",null,"023436 - Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TC-DIRDoc-11","FS-DIRDoc","P","C",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-DIRCTS-013",null,"023553 - Reporting Radiologist > Participant > Entity Identifier value SHALL be an HPI-I.","TC-DIRDoc-12","FS-DIRDoc","P","M",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-DIRCTS-014","NEHTA-1527:2014","2.26 Report DateTime (Effective Period).","TC-DIRDoc-13","FS-DIRDoc","P","M",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-DIRCTS-015",null,"3.7 Anatomical Location.","TC-DIRDoc-14","FS-DIRDoc","P","M",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-DIRCTS-016",null,"3.14 Anatomical Region.","TC-DIRDoc-15","FS-DIRDoc","P","M",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P",null,null,null," "]
[null,"TR-DIRCTS-017",null,"3.20 Image DateTime.","TC-DIRDoc-16","FS-DIRDoc","P","M",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-DIRCTS-018",null,"3.22 Observation DateTime.","TC-DIRDoc-17","FS-DIRDoc","P","M",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-DIRCTS-019",null,"3.27 Image Location.","TC-DIRDoc-18","FS-DIRDoc","P","C",1,null,"P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-DIRCTS-020",null,"2.21 Document Target.","TC-DIRDoc-19","FS-DIRDoc","P","C",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-DIRCTS-021","NEHTA-1978:2015","023456 - Clinical document producer SHALL NOT be a  registered consumer portal or registered provider portal.","TC-DIRProc-01","FS-DIRProc","P","M",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P"]
[null,"TR-DIRCTS-022","NEHTA-1850:2015","023706 - Clinical document producer 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. ","TC-DIRProc-02","FS-DIRProc","P","M",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P"]
[null,"TR-DIRCTS-023","NEHTA-1978:2015","024885 - Healthcare software access to the Healthcare Identifiers Service.","TC-DIRProc-03","FS-DIRProc","O","-",0]
[null,"TR-DIRCTS-024",null,"024972 - Healthcare software access to the Healthcare Identifiers Service.","TC-DIRProc-04","FS-DIRProc","O","-",0]
[null,"TR-DIRCTS-025",null,"026757 - \"Withdrawn consent\" indicator is recorded.","TC-DIRProc-05","FS-DIRProc","P","M",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P"]
[null,"TR-DIRCTS-027",null,"026760 - \"Document uploaded\" indicator is recorded.","TC-DIRProc-06","FS-DIRProc","P","M",1,null,null,null,null,null,"P","P","P","P","P","P","P",null,null,"P",null,null,"P",null,"P","P","P"]
[null,"TR-DIRCTS-029",null,"025061 - The Diagnostic Imaging Report is not uploaded to My Health Record system. A copy of the Diagnostic Imaging Report is saved to Authoring System.","TC-DIRProc-07","FS-DIRProc","P","M",1,null,null,null,null,null,"P",null,null,null,null,null,"P",null,null,null,null,null,null,null,null,null,"P"]
[null,"TR-DIRCTS-030",null,"026762  - Authoring system permits the report to be uploaded to the My Health Record system.","TC-DIRProc-08","FS-DIRProc","P","M",1,null,null,null,null,null,"P",null,"P"]
[null,"TR-DIRCTS-032",null,"026763 - Invoke doesPCEHRexist web service.","TC-DIRProc-09","FS-DIRProc","P","M",2,null,null,null,null,null,"P",null,"P",null,null,null,null,"P","P"]
[null,"TR-DIRCTS-033",null,"026766  - Changing \"Withdrawn consent\" indicator.","TC-DIRProc-10","FS-DIRProc","P","M",2,null,null,null,null,null,"P",null,null,null,null,null,null,null,null,null,"P",null,"P","P"]
[null,"TR-DIRCTS-034",null,"025072 - Record upload failure.","TC-DIRProc-11","FS-DIRProc","P","M",2,null,null,null,null,null,"P",null,null,"P"]
[null,"TR-DIRCTS-035",null,"025073 - Record information on validity of healthcare identifiers.","TC-DIRProc-12","FS-DIRProc","P","M",2,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P"]
[null,"TR-DIRCTS-036",null,"025074 - Record a decision to not upload a diagnostic report.","TC-DIRProc-13","FS-DIRProc","P","M",2,null,null,null,null,null,"P",null,null,null,"P",null,null,null,null,null,null,null,null,null,null,"P"]
[null,"TR-DIRCTS-037",null,"025155 - Record the reversal of a decision by a diagnostic service provider to not upload a diagnostic report.","TC-DIRProc-14","FS-DIRProc","P","M",2,null,null,null,null,null,null,null,null,null,"P",null,null,null,null,null,null,null,null,null,null,"P"]
[null,"TR-DIRCTS-038",null,"025156 - Record the original and changed withdrawal of consent indicator values.","TC-DIRProc-15.1","FS-DIRProc","P","M",2,null,null,null,null,null,null,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P"]
[null,"TR-DIRCTS-039",null,"025156 - Record the original and changed withdrawal of consent indicator values.","TC-DIRProc-15.2","FS-DIRProc","P","M",2,null,null,null,null,null,null,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P"]
[null,"TR-DIRCTS-040",null,"025083 - Retrievable records.","TC-DIRProc-16","FS-DIRProc","P","M",1,null,null,null,null,null,null,null,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P"]
[null,"TR-DIRCTS-067","NEHTA-1299:2012","019100 (UC.CIS.001) -  CIS uses IHI.","PCEHR_CIS_019100","UC.CIS.001","-","-","-",null,null,null,null,null,null,"P","P","P","P","P","P","P","P","P","P","P","P","P",null,"","","P"]
[null,"TR-DIRCTS-068",null,"019378 (UC.CIS.001) - CIS Audit.","PCEHR_CIS_019378","UC.CIS.001","-","-","-",null,null,null,null,null,null,"P","P","P","P","P","P","P","P","P","P","P","P","P",null,"","","P"]
[null,"TR-DIRCTS-069",null,"019100 (UC.CIS.201) - CIS uses IHI.","PCEHR_CIS_019100","UC.CIS.201","-","-","-",null,null,null,null,null,null,"P","P","P","P","P","P","P","P","P","","","","",null,"","","P"]
[null,"TR-DIRCTS-070",null,"019429 (UC.CIS.201) - CIS uses HPI-I.","PCEHR_CIS_019429","UC.CIS.201","-","-","-",null,null,null,null,null,null,"P","P","P","P","P","P","P","P","P",null,null,null,null,null,"",""]
[null,"TR-DIRCTS-071",null,"019042 (UC.CIS.201) - Withdraw Consent.","PCEHR_CIS_019042","UC.CIS.201","-","-","-",null,null,null,null,null,null,"P","P","P","P","P","P","P","P","P",null,null,null,null,"","",""]
[null,"TR-DIRCTS-072",null,"017842a (UC.CIS.201) - CIS Identifies Uploads.","PCEHR_CIS_017842a","UC.CIS.201","-","-","-",null,null,null,null,null,null,"P","P",null,"P",null,null,null,null,"P",null,null,"P",null,"",""]
[null,"TR-DIRCTS-073",null,"017841a (UC.CIS.201) - CIS Retains Clinical info.","PCEHR_CIS_017841a","UC.CIS.201","-","-","-",null,null,null,null,null,null,"P","P","P","P",null,null,null,null,"P",null,null,"P",null,"","",""]
[null,"TR-DIRCTS-074",null,"017839 (UC.CIS.201) - Clinical Document explicit command.","PCEHR_CIS_017839","UC.CIS.201","-","-","-",null,null,null,null,null,null,"P","P","P","P",null,null,null,null,"P",null,null,"P",null,"","",""]
[null,"TR-DIRCTS-075",null,"019378 (UC.CIS.201) - CIS Audit.","PCEHR_CIS_019378","UC.CIS.201","-","-","-",null,null,null,null,null,null,"P","P","P","P","P","P","P","P","P","","","","","","","",""]
[null,"TR-DIRCTS-076",null,"019100 (UC.CIS.202) - CIS uses IHI.","PCEHR_CIS_019100","UC.CIS.202","-","-","-",null,null,null,null,null,null,null,null,"","","","","","","","","","","","P","P","P",""]
[null,"TR-DIRCTS-077",null,"019429 (UC.CIS.202) - CIS uses HPI-I.","PCEHR_CIS_019429","UC.CIS.202","-","-","-",null,null,null,null,null,null,null,null,"","","","","","","",null,null,null,null,"P","P","P"]
[null,"TR-DIRCTS-078",null,"019042 (UC.CIS.202) - Withdraw Consent.","PCEHR_CIS_019042","UC.CIS.202","-","-","-",null,null,null,null,null,null,null,null,"","","","","","","",null,null,null,null,"P","P","P"]
[null,"TR-DIRCTS-079",null,"017842b (UC.CIS.202)  - CIS Identifies Uploads.","PCEHR_CIS_017842b","UC.CIS.202","-","-","-",null,null,null,null,null,null,null,null,null,"",null,null,null,null,"",null,null,"",null,"P","P"]
[null,"TR-DIRCTS-080",null,"017841b (UC.CIS.202)  - CIS Retains Clinical info.","PCEHR_CIS_017841b","UC.CIS.202","-","-","-",null,null,null,null,null,null,null,null,"","",null,null,null,null,"",null,null,"",null,"P","P","P"]
[null,"TR-DIRCTS-081",null,"017839 (UC.CIS.202)  - CIS Clinical Document Check.","PCEHR_CIS_017839","UC.CIS.202","-","-","-",null,null,null,null,null,null,null,null,"","",null,null,null,null,"",null,null,"",null,"P","P","P"]
[null,"TR-DIRCTS-082",null,"019378 (UC.CIS.202) - CIS Audit.","PCEHR_CIS_019378","UC.CIS.202","-","-","-",null,null,null,null,null,null,null,"","","","","","","","","","","","","P","P","P",""]
[null,"TR-DIRCTS-083",null,"018338 (UC.CIS.202) - CIS Supersede.","PCEHR_CIS_018338","UC.CIS.202","-","-","-",null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,"P","P","P"]
[null,"TR-DIRCTS-083",null,"019100 (UC.CIS.203)  - CIS uses IHI.","PCEHR_CIS_019100","UC.CIS.203","-","-","-",null,null,null,null,null,null,null,null,"","","","","","","","","","","","","","",""]
[null,"TR-DIRCTS-084",null,"017887 (UC.CIS.203) - Identify remove documents.","PCEHR_CIS_017887","UC.CIS.203","-","-","-",null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,"P"]
[null,"TR-DIRCTS-085",null,"019377 (UC.CIS.203)- Remove documents.","PCEHR_CIS_019377","UC.CIS.203","-","-","-",null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,"P"]
[null,"TR-DIRCTS-086",null,"019378 (UC.CIS.203) - CIS Audit.","PCEHR_CIS_019378","UC.CIS.203","-","-","-",null,null,null,null,null,null,null,"","","","","","","","","","","","","","",""]
[null,"TR-DIRCTS-087","NEHTA-2029:2016","All the mandatory and applicable conditional tests in Conformance Test Specification for Authoring Systems.","All the mandatory and applicable conditional tests","FS-Doc, FS-Narr, Fs-Types, FS-Auth"]

{"sheet":"References","index":12,"n_rows":18,"n_cols":5,"rows_kept":18,"cut":false,"hidden":false,"merged":[]}
[null,null,"Australian Digital Health Agency"]
[]
[null,null,"References and Related Documents"]
[null,null,"Identifier","Date","Name"]
[null,null,"HL7CDAR2","2004-12-21","HL7CDAR2 - HL7 Clinical Document Architecture, Release 2"]
[null,null,"NEHTA-0794:2011","2011-07-20","NEHTA-0794:2011 Participation Data Specification - Data Specification v3.2"]
[null,null,"NEHTA-1199:2012","2012-03-07","NEHTA-1199:2012 Clinical Documents - CDA Rendering Specification v1.0"]
[null,null,"NEHTA-1229:2011","2011-11-29","NEHTA-1229:2011 Clinical Documents - CDA Package v1.0"]
[null,null,"NEHTA-1297:2012","2012-09-06","NEHTA-1297:2012 PCEHR Connecting Systems - Conformance Requirements v1.5"]
[null,null,"NEHTA-1298:2012","2012-09-06","NEHTA-1298:2012 PCEHR Connecting Systems - Use Cases v1.1"]
[null,null,"NEHTA-1299:2012","2012-09-27","NEHTA-1299:2012 PCEHR Connecting Systems - Conformance Test Specification v1.6"]
[null,null,"NEHTA-1528:2014","2014-12-31","NEHTA-1528:2014 Diagnostic Imaging Report - CDA Implementation Guide v1.0"]
[null,null,"NEHTA-1527:2014","2014-12-31","NEHTA-1527:2014 Diagnostic Imaging Report - Structured Content Specification v1.0"]
[null,null,"NEHTA-1850:2015","2015-04-10","NEHTA-1850:2015 Clinical Documents - Common Conformance Profile v1.6"]
[null,null,"NEHTA-2215:2016","2016-03-10","NEHTA-2215:2016 eHealth Diagnostic Imaging Report - My Health Record Conformance Profile v1.1"]
[null,null,"NEHTA-2065:2015","2015-07-15","NEHTA-2065:2015 Clinical Documents - Conformance Test Specification for CDA Packaging v1.5"]
[null,null,"DH-2209:2016","NOT YET PUBLISHED","DH-2209:2016 Conformance Test Specification for Authoring systems v1.0"]
[null,null,"NEHTA-1978:2015","2015-07-31","NEHTA-1978:2015 eHealth Diagnostic Imaging Report - PCEHR Conformance Profile v1.0.1\n"]