{"text_format":"1","workbook":"xlsx","n_sheets":13,"sheets":["Cover","Intro","TP-NewDoc","TP-Consent","TP-Supersede","TP-Remove","TP-Path","FS-PathDoc ","FS-PathProc","Process models","TSR","Traceability","References"],"not_rendered":{"charts":0,"images":8,"macros":1,"external_links":5,"defined_names":37,"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":[[23,1,23,3],[4,1,4,4],[16,3,16,4],[20,1,20,3],[21,1,21,3],[22,1,22,3],[24,1,24,3],[25,1,25,3],[26,1,26,3],[27,1,27,3],[28,1,28,3]]}
[]
[]
[null,null,null," "]
[]
[null,"Pathology Report "]
[null,"Conformance Test Specification"]
[]
[null,"Version 1.0"]
[null,"2017-06-16"]
[]
[null,"Approved for external use"]
[null,"Document ID: DH-2525:2017"]
[]
[]
[null,"Product version history"]
[null,"Version","Date","Comments"]
[null,1,"2017-06-16","Approved for release"]
[]
[]
[]
[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."]
[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 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. Australian Digital Health 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,null,null,null,null,null," "]
[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 © 2017 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 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":[[2,1,2,2],[103,1,103,2],[84,1,84,2],[12,1,12,2],[14,1,14,2],[15,1,15,2],[16,1,16,2],[26,1,26,2],[31,1,31,2],[32,1,32,2],[33,1,33,2],[46,1,46,2],[64,1,64,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 Pathology Report, based on the type of \"user\" you are; and\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: 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 materials 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 materials do I need?","`"]
[null,"USER 1:  I want to test the Pathology Reports created by my Authoring System (Producers of the Pathology Report clinical document)."]
[null,"In this scenario, you have developed a software system that can create Pathology Reports, and you want to test the conformance of  the Pathology Reports produced by the system against the eHealth requirements."]
[null,"Tests applicable to the Pathology Report Authoring system:"]
[null,null,"From the Pathology Report Conformance Test Specification (this specification):"]
[null,null,"TP-NewDoc"]
[null,null,"TP-Consent"]
[null,null,"TP-Supersede"]
[null,null,"TP-Remove"]
[]
[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 applicable to the Pathology Report document:"]
[null,null,"From the Pathology Report Conformance Test Specification (this specification):"]
[null,null,"TP-Path"]
[]
[]
[null,"USER 2:  I want to test Pathology Report clinical documents that were downloaded from My Health Record system."]
[null,"In this scenario  you have a Pathology Report document; but no knowledge of the software system that produced it, and you want to test the document’s conformance against the eHealth requirements.   "]
[null,"Tests applicable to the Pathology Report document:"]
[null,null,"From the Pathology Report Conformance Test Specification (this specification):"]
[null,null,"FS-PathDoc"]
[]
[null,null,"From the  Clinical Documents - Conformance Test Specification for Authoring Systems [NEHTA-2209:2016]:"]
[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","PURPOSE"]
[null,"TP-NewDoc","Full name: Author a new Pathology Report function\nObjective: To assess the conformance of a Pathology Report authoring system to the requirements that apply to the process of creating a new Pathology Report.\n"]
[null,"TP-Consent","Full name: Change consent setting function\nObjective: To assess the conformance of a Pathology Report authoring system to the requirements that apply to the receipt of an indication of consent.\n"]
[null,"TP-Supersede","Full name: Supersede a Pathology Report function\nObjective: To assess the conformance of a Pathology Report authoring system to the requirements that apply to the process of superseding a Pathology Report that was uploaded to the My Health Record system."]
[null,"TP-Remove","Full name: Remove a Pathology Report function\nObjective: To assess the conformance of a Pathology Report authoring system to the requirements that apply to the process of removing a Pathology Report from the My Health Record system.\n"]
[null,"TP-Path","Full name: Pathology Report information content\nObjective: To assess the ability of a Pathology Report authoring system to create Pathology Reports with a variety of information content that may be used for a specific type of clinical document.\n"]
[null,"FS-PathDoc","Full name: Pathology Report clinical document\nObjective: To assess the conformance of a Pathology Report clinical document to the requirements for documents of that type.\n"]
[null,"FS-PathProc","Full name: Business processes for the authoring system\nObjective: To assess the conformance to the process requirements of an Authoring System that creates Pathology Reports. These are requirements for creating, superseding and removing Pathology Reports, consent management and record keeping. These requirements are additional to the requirements that apply to the Pathology Reports created by an Authoring System.\n"]
[null,"Process models","Full name: Process models for Pathology Report\nObjective: Lists process requirements, that are conformance requirements related to the following business processes:\n• Author a new Pathology Report\n• Store or upload to the My Health Record system\n• Change consent setting\n• Supersede a Pathology Report\n• Remove a Pathology Report\n• Retrieve records"]
[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","Full name: Traceability\nObjective: This worksheet contains a list of requirements and specifications that shows requirements coverage over the feature sets.\n"]
[null,"References","Full name: References and Related Documents\nObjective: 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 first 5 Test Procedures:  TP-NewDoc, TP-Consent, TP-Supersed, TP-Removeand TP-Path. \nFeature sets FS-PathDoc and FS-PathProc 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 of 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 (i.e. the test may be for an optional requirement that is not implemented in the software, or the test is conditional and the condition is not present).\nTBD:   To be determined - the test result is still to be determined."]
[null,"TESTER COMMENTS","Comments in support of the test result.\n"]
[null,"Scenario result","Result status of the scenario exercised by this test procedure. Automatically populated, either \"Complete\" or \"Incomplete\"."]
[null,"Return to top"]
[]
[]
[4,"Worksheet structure for Feature Sets"]
[null,"Table 4 below describes the final 2 feature set worksheets:  FS-PathDoc and FS-PathProc.\n"]
[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.\n"]
[null,"Objective","Briefly describes the focus or objective for the feature set.\n"]
[null,"Strategy","Specifies the implementation of the strategy for this feature set.\n"]
[null,"Traceability","Lists reference(s) to the associated features in the test basis.\n"]
[null,"TEST SET ID","Unique identifier that distinguishes each test case from within the entire set of test specifications.\n"]
[null,"TEST CASE ID","A unique value to identify the test case.\n"]
[null,"CONFORMANCE REQUIREMENT","Displays the requirement to be met by the software being tested.\n"]
[null,"PRIORITY","Specifies whether a test is mandatory, conditional or optional.  This is done with the abbreviation:\nM for Mandatory \nC for Conditional\nO for Optional\n"]
[null,"STEP NO.","The individual test step number within a test case that has multiple steps\n"]
[null,"TEST STEP","The evaluation required for applying the test case.\n"]
[null,"EXPECTED RESULT","The expected outcome of the Test Step.\n"]
[null,"TEST RESULT","Result of the test (Pass, Fail, N/A or TBD)\n\nPass:  The software passed the test.\nFail:    The software failed the test.\nN/A:   Not applicable - the test is not applicable for the software being tested (i.e. the test may be for an optional requirement that is not implemented in the software, or the test is conditional and the condition is not present).\nTBD:   To be determined - the test result is still to be determined."]
[null,"TESTER COMMENTS","Comments in support of the test result\n"]
[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","Individual Healthcare Identifier"]
[null,"NEHTA","National E-Health Transition Authority"]
[null,"PCEHR","Personally Controlled Electronic Health Record (replaced by My Health Record sysytem)"]
[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":420,"n_cols":9,"rows_kept":420,"cut":false,"hidden":false,"merged":[[195,2,195,6],[238,2,238,6],[239,2,239,6],[278,2,278,6],[279,2,279,6],[196,2,196,6],[197,2,197,6],[198,2,198,6],[236,2,236,6],[237,2,237,6],[52,2,52,6],[53,2,53,6],[145,2,145,6],[146,2,146,6],[147,2,147,6],[98,2,98,6],[99,2,99,6],[100,2,100,6],[101,2,101,6],[144,2,144,6],[7,2,7,6],[0,2,0,6],[50,2,50,6],[51,2,51,6],[1,2,1,6],[2,2,2,6],[4,2,4,6],[5,2,5,6],[6,2,6,6],[361,2,361,6],[280,2,280,6],[281,2,281,6],[318,2,318,6],[319,2,319,6],[320,2,320,6],[321,2,321,6],[358,2,358,6],[359,2,359,6],[360,2,360,6]]}
[null,"Test procedure:","TP-NewDoc: Author a new Pathology Report function"]
[null,"Overview:","To assess the conformance of a Pathology Report software system to the requirements that apply to the process of creating a new Pathology Report.\n\nThe business process of authoring a new Pathology Report is initiated when a request for diagnostic services is received, includes requirements for managing consent and record keeping, as well as creating the report and CDApackage 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 are 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\"."]
[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 authoring system has the functionality required to support the test. For the \"conditional\" test scenario, if the authoring 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-PathProc\" are listed in the FS-PathProc feature set within this conformance test specification.\n2. \"TC-PathDoc\" are listed in the FS-PathDoc 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 authoring 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 authoring system can be declared conformant. "]
[]
[null,"Scenario:","TP-NewDoc-01 - New Report Uploaded to My Health Record  (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: \nUsing the Authoring System, author a new Pathology Report that includes one Pathology Test Result . The author of the Pathology Report performs an action to upload the report to the My Health Record system. The Pathology 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. Upload the Pathology  Report to the My Health Record system.\n3. Create a conformant Pathology 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 includes sufficient demographic information within the request to successfully obtain their IHI from the HI Service.\n4. The software system has been set up to successfully upload the Pathology 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,"TP-NewDoc-01","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,null,"(A2: Record \"No withdrawn consent\")","TC-PathProc-05","\"Withdrawn consent\" indicator is recorded","TBD",null,0]
[null,null,null,"TC-PathProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,"(A8: Record \"PCEHR 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 Pathology Report","-",null,"TBD",null,0]
[null,null,"(B3: Prepare for upload)","TC-PathDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-08","Mandatory Reporting Pathologist Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-12","Reporting Pathologist  > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,"(B5: UC.CIS.201 Upload a clinical document)",null,"Pathology 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-PathProc-06","\"Document uploaded\" indicator is recorded","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-PathProc-16","The record shows that the original consent setting is \"No withdrawn consent\".","TBD",null,0]
[null,null,"Assess the conformance of the Pathology Report to the mandatory and relevant conditional requirements.","TC-PathDoc-01","Conform to the requirements for conformance levels 3A or 3B.","TBD",null,0]
[null,null,"Assess the conformance of the listed Pathology Report & CIS requirements","TC-PathDoc-02","A CDA document SHALL reference one, and only one, attachment that is the original diagnostic report. The report SHALL be a PDF packaged attachment.","TBD",null,0]
[null,null,null,"TC-PathDoc-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-PathDoc-04","Check for elements that cannot be a \"nullFlavor\".","TBD",null,0]
[null,null,null,"TC-PathDoc-05","Narrative and section title.","TBD",null,0]
[null,null,null,"TC-PathDoc-06","Sort test results","TBD",null,0]
[null,null,null,"TC-PathDoc-09","References in CDA Package","TBD",null,0]
[null,null,null,"TC-PathDoc-10","Report Date Time","TBD",null,0]
[null,null,null,"TC-PathDoc-13","Collection Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-14","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-15","Document target.","TBD",null,0]
[null,null,null,"TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-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-PathProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-PathProc-15.2","Record the original 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(I49=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H10:H48) / (COUNT(H10:H48))","v":0}]
[]
[null,"Scenario:","TP-NewDoc-02 -  New Report Uploaded to My Health Record System (Consent Found by Web Service Call)"]
[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 Pathology Report that includes one Pathology Examination Result. The My Health Record system reports that the healthcare individual has a digital health record (see pre-requisites). The author of the Pathology Report performs an action to upload the report to the My Health Record system. The Pathology 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. Upload the Pathology 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\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 contains no information about consent.\n3. The request for the diagnostic services states the healthcare individual's name, and includes sufficient demographic information within the request to successfully obtain their IHI from the HI Service.\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 Pathology Reports to the digital health record."]
[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-NewDoc-02","A9: Enter the request details","-",null,"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,"(A4. UC.CIS.001 Check if an advertised digital health record exists)","TC-PathProc-09,Test cases for UC.CIS.001 \n(note: requirement 024885 overrides PCEHR connecting systems requirement 019100)","Invoke doesPCEHRexist web service.\nUpload the clinical document.","TBD",null,0]
[null,null,"(A2: Record \"No withdrawn consent\")",null,null,"TBD",null,0]
[null,null,null,"TC-PathProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"TC-PathProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,"(A8: Record \"PCEHR 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 Pathology Report","-",null,"TBD",null,0]
[null,null,"(B3: Prepare for upload)","TC-PathDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-08","Mandatory Reporting Pathologist Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-12","Reporting Pathologist  > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-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-PathProc-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-PathProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-PathProc-16","The record shows that the consent setting is \"No withdrawn consent\".","TBD",null,0]
[null,null,"Assess the conformance of the listed Pathology Report & CIS requirements","TC-PathDoc-02","A CDA document SHALL reference one, and only one, attachment that is the original diagnostic report. The report SHALL be a PDF packaged attachment.","TBD",null,0]
[null,null,null,"TC-PathDoc-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-PathDoc-04","Check for elements that cannot be a \"nullFlavor\".","TBD",null,0]
[null,null,null,"TC-PathDoc-05","Narrative and section title.","TBD",null,0]
[null,null,null,"TC-PathDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-PathDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-PathDoc-10","Report Date Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-13","Collection Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-14","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-15","Document target.","TBD",null,0]
[null,null,null,"TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-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-PathProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-PathProc-15.2","Record the original 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(I97=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H56:H96) / (COUNT(H56:H96))","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 Pathology Report that includes one Pathology Examination Result. The author of the Pathology Report performs an action to upload the report to the My Health Record system.  The software system fails to upload the Pathology 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 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 ->  A2 -> A8 -> A6 -> A7 -> B3 -> B5  -> B6 -> B13 -> 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 digital health record.\n3. The request for the diagnostic services states the healthcare individual's name, and includes sufficient demographic information within the request to successfully obtain their IHI from the HI Service.\n4. The software system has been set up so that an attempt to upload a Pathology Report to the My Health Record system results in an error."]
[null,"SCENARIO","STEP","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-NewDoc-03","A9: Enter the request details","-",null,"TBD",null,{"$f":"IF(F104=\"\",\"0\",IF(F104=\"Pass\",1,IF(F104=\"Fail\",0,IF(F104=\"TBD\",0,IF(F104=\"N/A\",1)))))","v":0}]
[null,null,"(A2: Record \"No withdrawn consent\")","TC-PathProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-PathProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,"(A8: Record \"PCEHR 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 Pathology Report","-",null,"TBD",null,0]
[null,null,"(B3: Prepare for upload)","TC-PathDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-08","Mandatory Reporting Pathologist Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-12","Reporting Pathologist  > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-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,"Pathology 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-PathProc-11","Record upload failure.","TBD",null,0]
[null,null,"(B13: Record \"Document not uploaded\")","TC-PathProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-PathProc-16","The record has information about the failure to upload the report.","TBD",null,0]
[null,null,"Assess the conformance of the listed Pathology Report & CIS requirements","TC-PathDoc-02","A CDA document SHALL reference one, and only one, attachment that is the original diagnostic report. The report SHALL be a PDF packaged attachment.","TBD",null,0]
[null,null,null,"TC-PathDoc-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-PathDoc-04","Check for elements that cannot be a \"nullFlavor\".","TBD",null,0]
[null,null,null,"TC-PathDoc-05","Narrative and section title.","TBD",null,0]
[null,null,null,"TC-PathDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-PathDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-PathDoc-10","Report Date Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-13","Collection Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-14","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-15","Document target.","TBD",null,0]
[null,null,null,"TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-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-PathProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-PathProc-15.2","Record the original 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(I143=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H104:H142) / (COUNT(H104:H142))","v":0}]
[]
[null,"Scenario:","TP-NewDoc-04 - New Report Upload to My Health Record System (Initially Withheld & Not Uploaded, then Reversed & 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 Pathology Report that includes one Pathology  Examination Result. The author of the Pathology 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 Pathology 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 Pathology 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 Pathology 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 Pathology 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"]
[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 includes sufficient demographic information within the request to successfully obtain their IHI from the HI Service.\n4. The software system has been set up to successfully upload the Pathology Reports to the My Health Record system."]
[null,"SCENARIO","STEP","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-NewDoc-04","A9: Enter the request details","-",null,"TBD",null,{"$f":"IF(F150=\"\",\"0\",IF(F150=\"Pass\",1,IF(F150=\"Fail\",0,IF(F150=\"TBD\",0,IF(F150=\"N/A\",1)))))","v":0}]
[null,null,"(A2: Record \"No withdrawn consent\")","TC-PathProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-PathProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,"(A8: Record \"PCEHR 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 Pathology Report","-",null,"TBD",null,0]
[null,null,"(B3: Prepare for upload)","TC-PathDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-08","Mandatory Reporting Pathologist Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-12","Reporting Pathologist  > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-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-PathProc-13","Record a decision to not upload a Pathology Report.","TBD",null,0]
[null,null,null,null,"Record the reversal of a decision by a diagnostic service provider to not upload a Pathology Report.","TBD",null,0]
[null,null,"(B8. Reverse a withhold decision)","TC-PathProc-14","Record the reversal of a decision by a diagnostic service provider to not upload a Pathology Report.","TBD",null,0]
[null,null,"(B13: Record \"Document not uploaded\")","TC-PathProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"(B5: UC.CIS.201 Upload a clinical document)",null,"Document Identification, Revisions, and Addenda.","TBD",null,0]
[null,null,null,"Test cases for UC.CIS.201 \n(note that requirement 024885 overrides PCEHR connecting systems requirement 019100)","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,"(B12: Record \"Document uploaded\")","TC-PathProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-PathProc-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 Pathology Report & CIS requirements","TC-PathDoc-02","A CDA document SHALL reference one, and only one, attachment that is the original diagnostic report. The report SHALL be a PDF packaged attachment.","TBD",null,0]
[null,null,null,"TC-PathDoc-03","Use a healthcare identifier received via an electronic request without needing to revalidate the healthcare identifier.","TBD",null,0]
[null,null,null,"TC-PathDoc-04","Check for elements that cannot be a \"nullFlavor\".","TBD",null,0]
[null,null,null,"TC-PathDoc-05","Narrative and section title.","TBD",null,0]
[null,null,null,"TC-PathDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-PathDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-PathDoc-10","Report Date Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-13","Collection Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-14","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-15","Document target.","TBD",null,0]
[null,null,null,"TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-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-PathProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-PathProc-15.2","Record the original 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(I194=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H151:H193) / (COUNT(H151:H193))","v":0}]
[]
[null,"Scenario:","TP-NewDoc-05 - New 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 Pathology Report that includes one Pathology Test Result. The author of the Pathology 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 Pathology Report and prevent the Pathology 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 services is mandatory if the request is paper-based and if the Authoring Systems 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 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 Pathology Reports to the My Health Record system.\n\n\n"]
[null,"SCENARIO","STEP","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-NewDoc-05","A9: Enter the request details","-",null,"TBD",null,{"$f":"IF(F201=\"\",\"0\",IF(F201=\"Pass\",1,IF(F201=\"Fail\",0,IF(F201=\"TBD\",0,IF(F201=\"N/A\",1)))))","v":0}]
[null,null,"(A2: Record \"No withdrawn consent\")","TC-PathProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-PathProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,"(A8: Record \"PCEHR 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 Pathology Report","-",null,"TBD",null,0]
[null,null,"(B3: Prepare for upload)","TC-PathDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-08","Mandatory Reporting Pathologist Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-12","Reporting Pathologist  > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-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-PathProc-12","Record failure to upload due to invalid healthcare identifiers.","TBD",null,0]
[null,null,"(B13: Record \"Document not uploaded\")","TC-PathProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-PathProc-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 Pathology Report & CIS requirements","TC-PathDoc-02","A CDA document SHALL reference one, and only one, attachment that is the original diagnostic report. The report SHALL be a PDF packaged attachment.","TBD",null,0]
[null,null,null,"TC-PathDoc-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-PathDoc-04","Check for elements that cannot be a \"nullFlavor\".","TBD",null,0]
[null,null,null,"TC-PathDoc-05","Narrative and section title.","TBD",null,0]
[null,null,null,"TC-PathDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-PathDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-PathDoc-10","Report Date Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-13","Collection Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-14","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-15","Document target.","TBD",null,0]
[null,null,null,"TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-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-PathProc-15.2","Record the original 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(I235=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H201:H234) / (COUNT(H201:H234))","v":0}]
[]
[null,"Scenario:","TP-NewDoc-06 - New 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 Pathology Report that includes one Pathology Test Result. \n\nDemonstrate that the software system has the ability to:\n1. Record the consent setting as \"Withdrawn consent\". \n2. Save a copy of the Pathology Report in the software system.\n3. Verify the original consent information is recorded 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 includes sufficient demographic information within the request to successfully obtain their IHI from the HI Service.\n4. The software system has been set up to successfully upload the Pathology Reports to the My Health Record system."]
[null,"SCENARIO","STEP","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-NewDoc-06","A9: Enter the request details","-",null,"TBD",null,{"$f":"IF(F242=\"\",\"0\",IF(F242=\"Pass\",1,IF(F242=\"Fail\",0,IF(F242=\"TBD\",0,IF(F242=\"N/A\",1)))))","v":0}]
[null,null,"(A3: Record \"Withdrawn consent\")","TC-PathProc-06","Paper/Electronic Withdrawn consent.","TBD",null,0]
[null,null,null,"TC-PathProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"TC-PathProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,"(A8: Record \"PCEHR exists\")",null,null,"TBD",null,0]
[null,null,"A6: Perform diagnostic tests ","-",null,"TBD",null,0]
[null,null,"A7: Author a Pathology  Report","-",null,"TBD",null,0]
[null,null,"(B2. Store a Pathology Report for a future upload)","TC-PathProc-07","The Pathology Report is not uploaded to the My Health Record system. \nA copy of the Pathology Report is saved to the Authoring System.","TBD",null,0]
[null,null,"(B13: Record \"Document not uploaded\")",null,"\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-PathProc-16","The record shows that the original consent setting is \"Withdrawn consent\".","TBD",null,0]
[null,null,"Assess the conformance of the listed Pathology Report & CIS requirements","TC-PathDoc-02","A  CDA document SHALL reference one, and only one, attachment that is the original diagnostic report. The report SHALL be a PDF packaged attachment.","TBD",null,0]
[null,null,null,"TC-PathDoc-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-PathDoc-04","Check for elements that cannot be a \"nullFlavor\".","TBD",null,0]
[null,null,null,"TC-PathDoc-05","Narrative and section title.","TBD",null,0]
[null,null,null,"TC-PathDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-PathDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-08","Mandatory Reporting Pathologist Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-PathDoc-10","Report Date Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-12","Reporting Pathologist  > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-13","Collection Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-14","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-15","Document target.","TBD",null,0]
[null,null,null,"TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-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-PathProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-PathProc-15.2","Record the original 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(I277=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H242:H276) / (COUNT(H242:H276))","v":0}]
[]
[null,"Scenario:","TP-NewDoc-07 - New Report Not Uploaded to My Health Record System (No Consent - Digital Health Record Not Found)"]
[null,"Objective:","Using the software system, create a new Pathology 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," "]
[null,"SCENARIO","STEP","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-NewDoc-07","A9: Enter the request details","-",null,"TBD",null,{"$f":"IF(F284=\"\",\"0\",IF(F284=\"Pass\",1,IF(F284=\"Fail\",0,IF(F284=\"TBD\",0,IF(F284=\"N/A\",1)))))","v":0}]
[null,null,"(A4. UC.CIS.001 Check if an advertised digital health record exists via doesPCEHRexist web service call)","TC-PathProc-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\").","TC-PathProc-07","Changing No withdrawn consent Settings.","TBD",null,0]
[null,null,null,"TC-PathProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-PathProc-16","The record shows that the original consent setting is \"Withdrawn consent\".","TBD",null,0]
[null,null,null,"TC-PathProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,"A6: Perform diagnostic tests ","-",null,"TBD",null,0]
[null,null,"A7: Author a Pathology Report","-","Pathology Report is not uploaded to the My Health Record system.","TBD",null,0]
[null,null,"Assess the conformance of the listed Pathology Report & CIS requirements","TC-PathDoc-02","A  CDA document SHALL reference one, and only one, attachment that is the original diagnostic report. The report SHALL be a PDF packaged attachment.","TBD",null,0]
[null,null,null,"TC-PathDoc-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-PathDoc-04","Check for elements that cannot be a \"nullFlavor\".","TBD",null,0]
[null,null,null,"TC-PathDoc-05","Narrative and section title.","TBD",null,0]
[null,null,null,"TC-PathDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-PathDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-08","Mandatory Reporting Pathologist Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-PathDoc-10","Report Date Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-12","Reporting Pathologist  > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-13","Collection Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-14","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-15","Document target.","TBD",null,0]
[null,null,null,"TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-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-PathProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-PathProc-15.2","Record the original 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."]
[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(I317=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H284:H316) / (COUNT(H284:H316))","v":0}]
[]
[null,"Scenario:","TP-NewDoc-08  - New 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 Pathology Report for a recipient of healthcare services who has not provided any information of their 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 the request made to the software system and the search for the Healthcare Individual digital 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.  \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 digital health record is searched for in the My Health Record system.\n"]
[null,"SCENARIO","STEP","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-NewDoc-08","A9: Enter the request details","-",null,"TBD",null,{"$f":"IF(F324=\"\",\"0\",IF(F324=\"Pass\",1,IF(F324=\"Fail\",0,IF(F324=\"TBD\",0,IF(F324=\"N/A\",1)))))","v":0}]
[null,null,"(A4. UC.CIS.001 Check if an advertised digital health record exists via doesPCEHRexist web service call)","TC-PathProc-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-PathProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-PathProc-16","The record shows that the original consent setting is \"Withdrawn consent\".","TBD",null,0]
[null,null,null,"TC-PathProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,"A6: Perform diagnostic tests ","-",null,"TBD",null,0]
[null,null,"A7: Author a Pathology Report","-","Pathology Report is not uploaded to the My Health Record system.","TBD",null,0]
[null,null,"Assess the conformance of the listed Pathology Report & CIS requirements","TC-PathDoc-02","A  CDA document SHALL reference one, and only one, attachment that is the original diagnostic report. The report SHALL be a PDF packaged attachment.","TBD",null,0]
[null,null,null,"TC-PathDoc-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-PathDoc-04","Check for elements that cannot be a \"nullFlavor\".","TBD",null,0]
[null,null,null,"TC-PathDoc-05","Narrative and section title.","TBD",null,0]
[null,null,null,"TC-PathDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-PathDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-08","Mandatory Reporting Pathologist Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-PathDoc-10","Report Date Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-12","Reporting Pathologist  > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-13","Collection Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-14","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-15","Document target.","TBD",null,0]
[null,null,null,"TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-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-PathProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-PathProc-15.2","Record the original 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(I357=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H324:H356) / (COUNT(H324:H356))","v":0}]
[]
[null,"Scenario:","TP-NewDoc-09 - New Report Uploaded to My Health Record  (Consent Provided) - 2 Exam Results"]
[null,"Objective:","Using the software system, create a new Pathology Report containing two Pathology Test 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 Pathology Report performs an action to upload the report to the My Health Record system. The Pathology Report is uploaded to the My Health Record system successfully.\n\nDemonstrate that the software system has the ability to:\n1. Create a conformant Pathology Report that has two Pathology Test results.\n2. Store the Pathology Report (refer objective 1) on the software system.\n3. Upload the Pathology Report (refer objective 1) 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"]
[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 includes sufficient demographic information within the request to successfully obtain their IHI from the HI Service.\n4. The software system has been set up to successfully upload the Pathology Reports to the My Health Record system.\n\n"]
[null,"SCENARIO","STEP","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-NewDoc-09","A9: Enter the request details","-",null,"TBD",null,{"$f":"IF(F364=\"\",\"0\",IF(F364=\"Pass\",1,IF(F364=\"Fail\",0,IF(F364=\"TBD\",0,IF(F364=\"N/A\",1)))))","v":0}]
[null,null,"(A2: Record \"No withdrawn consent\")","TC-PathProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-PathProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,"(A8: Record \"PCEHR 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 Pathology Report","-",null,"TBD",null,0]
[null,null,"(B3: Prepare for upload)","TC-PathDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-08","Mandatory Reporting Pathologist Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-12","Reporting Pathologist  > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-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. Pathology Report has two Pathology Test results. \n2. Pathology 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-PathProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-PathProc-16","The record shows that the original consent setting is \"No withdrawn consent\".","TBD",null,0]
[null,null,"Assess the conformance of the listed Pathology Report & CIS requirements","TC-PathDoc-02","A  CDA document SHALL reference one, and only one, attachment that is the original diagnostic report. The report SHALL be a PDF packaged attachment.","TBD",null,0]
[null,null,null,"TC-PathDoc-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-PathDoc-04","Check for elements that cannot be a \"nullFlavor\".","TBD",null,0]
[null,null,null,"TC-PathDoc-05","Narrative and section title.","TBD",null,0]
[null,null,null,"TC-PathDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-PathDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-PathDoc-10","Report Date Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-13","Collection Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-14","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-15","Document target.","TBD",null,0]
[null,null,null,"TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-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-PathProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-PathProc-15.2","Record the original 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(I403=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H363:H402) / (COUNT(H363:H402))","v":0}]
[]
[]
[null,"Scenario","Percentage complete","Scenario status",null,{"$f":"COUNTIF($H$10:$H403,\"0\")","v":336},"Test Cases Failed or TBD","Fail"]
[null,"TP-NewDoc-01",{"$f":"I49","v":0},{"$f":"C49","v":"Incomplete"},null,{"$f":"COUNTIF($H$10:$H403,\"1\")","v":0},"Test cases Passed or N/A","Pass"]
[null,"TP-NewDoc-02",{"$f":"I97","v":0},{"$f":"C97","v":"Incomplete"},null,{"$f":"COUNTIF(H10:H403,\">=0\")","v":336},"Total Test cases","N/A"]
[null,"TP-NewDoc-03",{"$f":"I143","v":0},{"$f":"C143","v":"Incomplete"},null,{"$f":"SUM($F407/$F408)","v":0},"Test case % Passed or N/A","TBD"]
[null,"TP-NewDoc-04",{"$f":"I194","v":0},{"$f":"C194","v":"Incomplete"}]
[null,"TP-NewDoc-05",{"$f":"I235","v":0},{"$f":"C235","v":"Incomplete"}]
[null,"TP-NewDoc-06",{"$f":"I277","v":0},{"$f":"C277","v":"Incomplete"}]
[null,"TP-NewDoc-07",{"$f":"I317","v":0},{"$f":"C317","v":"Incomplete"}]
[null,"TP-NewDoc-08",{"$f":"I357","v":0},{"$f":"C357","v":"Incomplete"}]
[null,"TP-NewDoc-09",{"$f":"I403","v":0},{"$f":"C403","v":"Incomplete"}]
[]
[null,null,{"$f":"COUNTIF(D407:D415,\"Complete\")","v":0},"Scenarios Complete"]
[null,null,{"$f":"COUNTIF(D407:D415,\"Incomplete\")","v":9},"Scenarios Not Complete"]
[null,null,{"$f":"SUM($C$417:$C$418)","v":9},"Total Scenarios"]
[null,null,{"$f":"SUM($C$417)/($C$419)","v":0},"Scenarios Completed  (percentage)"]

{"sheet":"TP-Consent","index":3,"n_rows":147,"n_cols":9,"rows_kept":147,"cut":false,"hidden":false,"merged":[[4,2,4,6],[5,2,5,6],[6,2,6,6],[7,2,7,6],[0,0,2,0],[0,2,0,6],[1,2,1,6],[2,2,2,6],[117,2,117,6],[116,2,116,6],[118,2,118,6],[25,2,25,6],[26,2,26,6],[27,2,27,6],[28,2,28,6],[61,2,61,6],[62,2,62,6],[63,2,63,6],[64,2,64,6],[115,2,115,6]]}
[null,"Test procedure:","TP-Consent: Change consent setting function"]
[null,"Overview:","To assess the conformance of a Pathology Report software system to the requirements that apply with the receipt of an indication of consent.\n\nThe business process is initiated upon the receipt of an indication of consent related to a previously received request for diagnostic services. The business process includes requirements for managing consent, record keeping and uploading of stored Pathology 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 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\"."]
[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 authoring system has the functionality required to support the test. If it does not, then the test result to be recorded is \"N/A\" (not applicable). \nThe 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-PathProc\" are listed in the FS-PathProc feature set within this conformance test specification.\n2. \"TC-PathDoc\" are listed in the FS-PathDoc 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 \"(D7: Enter an Indication of Consent)\", are assumed to be automatically performed by the authoring 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 authoring system can be declared conformant. "]
[]
[null,"Scenario:","TP-Consent-01 - Change Consent setting from No Withdrawn Consent to Withdrawn Consent."]
[null,"Objective:","Within the context of a single diagnostic services request, where no Pathology Reports resulting from the diagnostic services request 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 Pathology Reports present on the My Health Record system.\n\nBusiness process models D & G Path: Start -> D7 -> D6 -> G1 -> End\n\n"]
[null,"Priority:","Mandatory"]
[null,"Pre-conditions:","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 Pathology 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-PathProc-15.2","Software system records the change to the healthcare individual's consent setting.","TBD",null,0]
[null,null,null,"TC-PathProc-15.1","Appropriate Additional Consent Information Recorded.","TBD",null,0]
[null,null,null,"TC-PathProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-PathProc-16","The record has information about the change of consent.","TBD",null,0]
[null,null,null,"TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-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-PathProc-10","Changing \"Withdrawn consent\" indicator.","TBD",null,0]
[null,null,null,"TC-PathProc-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(H9:H23) / (COUNT(H9:H23))","v":0}]
[]
[null,"Scenario:","TP-Consent-02 - Change Consent setting from No Withdrawn Consent to Withdrawn Consent - Restrictions & Fully Recorded Information. "]
[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 Pathology Report 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 Pathology Reports resulting from the diagnostic services request that have been previously uploaded to the My Health Record system.\n\nBusiness process model D & G.\nPath: Start -> D7 ->  G1 -> End\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 \"No withdrawn consent\".\n3. The healthcare individual has one or more Pathology 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\"","TC-PathProc-10","Changing \"Withdrawn consent\" indicator.","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","-","Consent setting remains as \"No withdrawn consent\".","TBD",null,0]
[null,null,"Verify that the setting is \"No withdrawn consent\"","-","Consent setting remains as \"No withdrawn consent\".","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-PathProc-16","The record has no information about a change of consent.","TBD",null,0]
[null,null,null,"TC-PathDoc-02","A  CDA document SHALL reference one, and only one, attachment that is the original diagnostic report. The report SHALL be a PDF packaged attachment.","TBD",null,0]
[null,null,null,"TC-PathDoc-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-PathDoc-04","Check for elements that cannot be a \"nullFlavor\".","TBD",null,0]
[null,null,null,"TC-PathDoc-05","Narrative and section title.","TBD",null,0]
[null,null,null,"TC-PathDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-PathDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-08","Mandatory Reporting Pathologist Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-PathDoc-10","Report Date Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-12","Reporting Pathologist  > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-13","Collection Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-14","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-15","Document target.","TBD",null,0]
[null,null,null,"TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-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-PathProc-05","Store \"Withdrawn consent\" indicator.","TBD",null,0]
[null,null,null,"TC-PathProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-PathProc-15.1","Appropriate Additional Consent Information Recorded.","TBD",null,0]
[null,null,null,"TC-PathProc-15.2","Record the original 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(I60=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H31:H59) / (COUNT(H31:H59))","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 Pathology 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 Pathology Report to the My Health Record system from the second diagnostic service request.\n\nin the first diagnostic service request, create a new  Pathology 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  Pathology 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  Pathology Report (Document B) and not the first  Pathology Report (Document A). \n\nBusiness process model D, B & G. Path: Start -> D7 -> D2 -> D4 -> B3 -> B5 -> B12 -> G1 -> End\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\"."]
[null,"SCENARIO","TASK","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(F67=\"\",\"0\",IF(F67=\"Pass\",1,IF(F67=\"Fail\",0,IF(F67=\"TBD\",0,IF(F67=\"N/A\",1)))))","v":0}]
[null,"TP-Consent-03","D7: Enter the indication of consent (as  \"Withdrawn consent\")","-",null,"TBD",null,{"$f":"IF(F68=\"\",\"0\",IF(F68=\"Pass\",1,IF(F68=\"Fail\",0,IF(F68=\"TBD\",0,IF(F68=\"N/A\",1)))))","v":0}]
[null,null,"Receive an indication of consent as \"No withdrawn consent\"","TC-PathProc-10","Changing \"Withdrawn consent\" indicator.\n","TBD",null,0]
[null,null,"(D2: Record \"Withdrawn consent\")",null,null,"TBD",null,0]
[null,null,null,"TC-PathProc-15.2","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"TC-PathProc-05","\"Withdrawn consent\" indicator is recorded.","TBD"]
[null,null,null,"TC-PathProc-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,0]
[null,null,"A7: Author a Pathology Report\n(Call it as Document A)","-",null,"TBD",null,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 Pathology Report\n(Call it as Document B)","TC-PathProc-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,0]
[null,null,"Receive an indication of consent as \"No withdrawn consent\"","TC-PathProc-10","Changing \"Withdrawn consent\" indicator.\n","TBD",null,0]
[null,null,"(D2: Record \"No withdrawn consent\")","-",null,"TBD",null,0]
[null,null,null,"TC-PathProc-15.2","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"TC-PathProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-PathProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,"(D4: Select the latest version of the Pathology Report (task))","-","Pathology Report (Document B) from the second diagnostic service request is selected for the upload.","TBD",null,0]
[null,null,"(B3: Prepare for upload)","TC-PathDoc-07","Mandatory Document Author Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-08","Mandatory Reporting Pathologist Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-12","Reporting Pathologist > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-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 Pathology 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-PathProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-PathProc-16","The record has information about the change of consent.","TBD",null,0]
[null,null,"Assess the conformance of the listed Pathology Report & CIS requirements","TC-PathDoc-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-PathDoc-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,null,null,"TC-PathDoc-04","Check for elements that cannot be a \"nullFlavor\".","TBD"]
[null,null,null,"TC-PathDoc-05","Narrative and section title.","TBD"]
[null,null,null,"TC-PathDoc-06","Sort test results.","TBD"]
[null,null,null,"TC-PathDoc-09","References in CDA Package.","TBD"]
[null,null,null,"TC-PathDoc-10","Report Date Time.","TBD"]
[null,null,null,"TC-PathDoc-13","Collection DateTime.","TBD"]
[null,null,null,"TC-PathDoc-14","Observation DateTime.","TBD"]
[null,null,null,"TC-PathDoc-15"," Document Target.","TBD"]
[null,null,null,"TC-PathProc-01","Clinical document producer SHALL NOT be a  registered consumer portal or registered provider portal.","TBD"]
[null,null,null,"TC-PathProc-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,null,null,"TC-DPathProc-12","Record information on validity of healthcare identifiers.","TBD"]
[null,null,null,"PCEHR_CIS_019100 (UC.CIS.001)","CIS uses IHI.","TBD"]
[null,null,null,"PCEHR_CIS_019378 (UC.CIS.001)","CIS Audit.","TBD"]
[null,null,null,"PCEHR_CIS_017842a (UC.CIS.201)","CIS Identifies Uploads.","TBD"]
[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(I114=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H67:H113) / (COUNT(H67:H113))","v":0}]
[]
[null,"Scenario:","TP-Consent - 04  Change \"Withdrawn consent\" indicator value from \"Withdrawn consent\" to \"No withdrawn consent\" when no Pathology 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 Pathology Reports resulting from the diagnostic services request have been stored on the software system.\nBusiness process models D & G.\nPath: Start -> D7 -> D2 -> G1 -> End\n\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 Pathology Reports stored on the Authoring System.\n\n"]
[null,"SCENARIO","TASK","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(F121=\"\",\"0\",IF(F121=\"Pass\",1,IF(F121=\"Fail\",0,IF(F121=\"TBD\",0,IF(F121=\"N/A\",1)))))","v":0}]
[null,"TP-Consent-04","Receive an indication of consent as \"No withdrawn consent\"","TC-PathProc-10","Changing \"Withdrawn consent\" indicator.","TBD",null,0]
[null,null,"(D2: Record \"No withdrawn consent\")",null,null,"TBD",null,0]
[null,null,null,"TC-PathProc-15.2","Software system records the change to the healthcare individual's consent setting.","TBD",null,0]
[null,null,null,"TC-PathProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-PathProc-15.1","Appropriate Additional Consent Information Recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-PathProc-16","The record has information about the change of consent.","TBD",null,0]
[null,null,null,"TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-02","Clinical document producer SHALL 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-PathProc-10","Changing \"Withdrawn consent\" indicator.","TBD",null,0]
[null,null,null,"TC-PathProc-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(I135=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H121:H134) / (COUNT(H121:H134))","v":0}]
[]
[]
[null,"Scenario","Tests","Overall",null,{"$f":"COUNTIF($H$10:$H135,\"0\")","v":88},"Test Cases Failed or TBD","Fail"]
[null,"TP-Consent-01",{"$f":"I24","v":0},{"$f":"C24","v":"Incomplete"},null,{"$f":"COUNTIF($H$10:$H135,\"1\")","v":0},"Test cases Passed or N/A","Pass"]
[null,"TP-Consent-02",{"$f":"I60","v":0},{"$f":"C60","v":"Incomplete"},null,{"$f":"COUNTIF($H$10:$H135,\">=0\")","v":88},"Total Test cases","N/A"]
[null,"TP-Consent-03",{"$f":"I114","v":0},{"$f":"C114","v":"Incomplete"},null,{"$f":"SUM($F139/$F140)","v":0},"Test case % Passed or N/A","TBD"]
[null,"TP-Consent-04",{"$f":"I135","v":0},{"$f":"C135","v":"Incomplete"}]
[]
[null,null,{"$f":"COUNTIF($D$139:$D$142,\"Complete\")","v":0},"Scenarios Complete"]
[null,null,{"$f":"COUNTIF($D$139:$D$142,\"Incomplete\")","v":4},"Scenarios Not Complete"]
[null,null,{"$f":"SUM($C$144:$C$145)","v":4},"Total Scenarios"]
[null,null,{"$f":"SUM($C$144)/($C$146)","v":0},"Scenarios Completed (percentage)"]

{"sheet":"TP-Supersede","index":4,"n_rows":138,"n_cols":9,"rows_kept":138,"cut":false,"hidden":false,"merged":[[0,2,0,6],[1,2,1,6],[95,2,95,6],[93,2,93,6],[2,2,2,6],[4,2,4,6],[5,2,5,6],[94,2,94,6],[6,2,6,6],[7,2,7,6],[45,2,45,6],[46,2,46,6],[47,2,47,6],[48,2,48,6],[92,2,92,6]]}
[null,"Test procedure:","TP-Supersede: Supersede a Pathology Report function"]
[null,"Overview:","To assess the conformance of a Pathology Report authoring system to the requirements that apply to the process of superseding a Pathology Report that was uploaded to the My Health Record system.\n\nThe business process of superseding a Pathology Report is initiated when an author of a previously created Pathology 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 Pathology Report and CDApackage 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 by default, but when applied in the context of the test scenario they are mandatory. Therefore the only possible outcomes of each test case are \"Pass\" or \"Fail\". Each test scenario is passed when all the specified test cases have a status of \"Pass\".\n\n"]
[null,"Instructions:","A test scenario with the priority of \"mandatory\" must be applied and passed by the Authoring System before it may be declared conformant to the requirements. Any \"conditional\" test scenario is to be applied if the authoring system has the functionality required to support the test. If it does not, 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-PathProc\" are listed in the FS-PathProc feature set within this conformance test specification.\n2. \"TC-PathDoc\" are listed in the FS-PathDoc 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 \"(F1. Obtain/validate healthcare identifiers)\", are assumed to be automatically performed by the authoring 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 authoring system can be declared conformant. \n"]
[]
[null,"Scenario:","TP-Supersede-01 - Create a replacement Pathology Report - Store the report  on the software system and upload it to the My Health Record system."]
[null,"Objective:","To demonstrate that the software system has the ability to\n1. Create a replacement Pathology Report to supersede an existing Pathology Report that was previously uploaded to the My Health Record system.\n2. Store the replacement Pathology Report on the software system.\n3. Upload the replacement Pathology Report to the My Health Record system.\n\nUsing the software system, for a healthcare individual, create a replacement Pathology Report to supersede an existing Pathology 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 Pathology 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 Pathology 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 includes sufficient demographic information within the request to successfully obtain their IHI from the HI Service.\n4. The request for the diagnostic services states the healthcare individual has at least one previously uploaded Pathology Report in My Health Record system.\n5 The software system has been set up to successfully upload the Pathology 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,"E1: Create a replacement Pathology Report","TC-PathDoc-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,"TP-Supersede-01","(B3: Prepare for upload)","TC-PathDoc-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-PathDoc-08","Mandatory Reporting Pathologist Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-12","Reporting Pathologist  > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-01","Conform to the requirements for conformance levels 3A or 3B.","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-PathProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-PathProc-16","The record shows that the original consent setting is \"No withdrawn consent\".","TBD",null,0]
[null,null,"Assess the conformance of the listed Pathology Report & CIS requirements","TC-PathDoc-02","A  CDA document SHALL reference one, and only one, attachment that is the original diagnostic report. The report SHALL be a PDF packaged attachment.","TBD",null,0]
[null,null,null,"TC-PathDoc-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-PathDoc-04","Check for elements that cannot be a \"nullFlavor\".","TBD",null,0]
[null,null,null,"TC-PathDoc-05","Narrative and section title.","TBD",null,0]
[null,null,null,"TC-PathDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-PathDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-PathDoc-10","Report Date Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-13","Collection Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-14","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-15","Document target.","TBD",null,0]
[null,null,null,"TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-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-PathProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-PathProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-PathProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"TC-PathProc-15.2","Record the original 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(I44=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H10:H43) / (COUNT(H10:H43))","v":0}]
[]
[null,"Scenario:","TP-Supersede-02 - Create a replacement Pathology Report - Upload to the My Health Record System (Initially Withheld & Not Uploaded, then Reversed Withhold decision & Uploaded to the My Health Record system)"]
[null,"Objective:","To demonstrate that the software system has the ability to:\n1. Create a replacement Pathology Report to supersede an existing Pathology Report that was previously uploaded to the My Health Record system.\n2. Allow the author to withhold the Pathology Report from uploading to the My Health Record system.\n3. Allow the author to reverse the withhold decision.\n4. Upload the replacement Pathology Report to the My Health Record system.\n\nUsing the software system, for a healthcare individual,  create a replacement Pathology Report to supersede an existing Pathology 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 Pathology Report from uploading to the My Health Record system. The replacement Pathology 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\n"]
[null,"Priority:","  Mandatory"]
[null,"Pre-requisites:","To apply this test scenario, a Pathology 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 includes sufficient demographic information within the request to successfully obtain their IHI from the HI Service.\n4. The request for the diagnostic services states the healthcare individual has at least one previously uploaded Pathology Report in My Health Record system.\n5 The software system has been set up to successfully upload the Pathology Reports to the My Health Record system.\n"]
[null,"SCENARIO","TASK","TEST SETS/TEST CASES","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,"TP-Supersede-02","E1: Create a replacement Pathology Report","TC-PathDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,{"$f":"IF(F51=\"\",\"0\",IF(F51=\"Pass\",1,IF(F51=\"Fail\",0,IF(F51=\"TBD\",0,IF(F51=\"N/A\",1)))))","v":0}]
[null,null,"(B3: Prepare for upload)","TC-PathDoc-07","Mandatory Document Author Values used.","TBD",null,{"$f":"IF(F52=\"\",\"0\",IF(F52=\"Pass\",1,IF(F52=\"Fail\",0,IF(F52=\"TBD\",0,IF(F52=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-PathDoc-08","Mandatory Reporting Pathologist Values used.","TBD",null,0]
[null,null,null,"TC-PathDoc-12","Reporting Pathologist  > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-01","Conform to the requirements for conformance levels 3A or 3B.","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,{"$f":"IF(F58=\"\",\"0\",IF(F58=\"Pass\",1,IF(F58=\"Fail\",0,IF(F58=\"TBD\",0,IF(F58=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-PathProc-13","Record a decision to not upload a Pathology Report.","TBD",null,0]
[null,null,"B8. Reverse a withhold decision","TC-PathProc-14","Record the reversal of a decision by a Pathologist service provider to not upload a Pathology Report.","TBD",null,0]
[null,null,"(B13: Record \"Document not uploaded\")",null,null,"TBD",null,0]
[null,null,"B9: UC.CIS.202 Supersede a clinical document",null,"1. Pathology Report upload decision withheld.\n2. Pathology Report upload withheld decision is reversed.\n3. Pathology 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-PathProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-PathProc-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,null,"TC-PathDoc-02","A  CDA document SHALL reference one, and only one, attachment that is the original diagnostic report. The report SHALL be a PDF packaged attachment.","TBD",null,0]
[null,null,null,"TC-PathDoc-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-PathDoc-04","Check for elements that cannot be a \"nullFlavor\".","TBD",null,0]
[null,null,null,"TC-PathDoc-05","Narrative and section title.","TBD",null,0]
[null,null,null,"TC-PathDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-PathDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-PathDoc-10","Report Date Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-13","Collection Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-14","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-15","Document target.","TBD",null,0]
[null,null,null,"TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-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-PathProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-PathProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-PathProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"TC-PathProc-15.2","Record the original 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(I91=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H51:H90) / (COUNT(H51:H90))","v":0}]
[]
[null,"Scenario:","TP-Supersede-03 - Replace a previously stored Pathology Report and store the replacement Pathology Report on the Authoring system."]
[null,"Objective:","To demonstrate that the software system has the ability to:\n1. Find a previously stored Pathology Report.\n2. Create a replacement Pathology Report to supersede a Pathology Report stored by the software system.\n3. Store the replacement Pathology Report.\n\nUsing the software system, for a healthcare individual, create a replacement Pathology Report to supersede an existing Pathology Report that is stored by the software system. The healthcare individual has indicated their withdrawal of consent to upload clinical documents to the My Health Record system. The replacement Pathology 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-conditions:","To apply this test scenario a Pathology 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 includes sufficient demographic information within the request to successfully obtain their IHI from the HI Service.\n4. The request for the diagnostic services states the healthcare individual has at least one previously uploaded Pathology Report in My Health Record system.\n5. The software system has been set up to successfully upload the Pathology Reports to the My Health Record system.\n"]
[null,"SCENARIO","TASK","TEST SETS/TEST CASES","TEST STEP/CASE DESCRIPTION","ACTUAL TEST RESULT","TESTER COMMENTS","CALC."]
[null,"TP-Supersede-03","E1: Create a replacement Pathology Report","TC-PathDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,{"$f":"IF(F98=\"\",\"0\",IF(F98=\"Pass\",1,IF(F98=\"Fail\",0,IF(F98=\"TBD\",0,IF(F98=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-PathDoc-08","Mandatory Reporting Pathologist Values used.","TBD",null,0]
[null,null,"(B2: Store a Pathology Report for a future upload)","TC-PathProc-07","The Pathology Report is not uploaded to My Health Record system. Pathology Report is saved for future upload.","TBD",null,0]
[null,null,"(B13: Record \"Document not uploaded\")","TC-PathProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,"G1: Retrieve recorded information","TC-PathProc-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,null,"TC-PathDoc-02","A  CDA document SHALL reference one, and only one, attachment that is the original diagnostic report. The report SHALL be a PDF packaged attachment.","TBD",null,0]
[null,null,null,"TC-PathDoc-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-PathDoc-04","Check for elements that cannot be a \"nullFlavor\".","TBD",null,0]
[null,null,null,"TC-PathDoc-05","Narrative and section title.","TBD",null,0]
[null,null,null,"TC-PathDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-PathDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-PathDoc-10","Report Date Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-12","Reporting Pathologist  > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-13","Collection Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-14","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-15","Document target.","TBD",null,0]
[null,null,null,"TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-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-PathProc-05","\"Withdrawn consent\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-PathProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-PathProc-15.1","Record the original and changed withdrawal of consent indicator values.","TBD",null,0]
[null,null,null,"TC-PathProc-15.2","Record the original 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(I128=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H98:H127) / (COUNT(H98:H127))","v":0}]
[]
[null,"Scenario","Percentage complete","Scenario status",null,{"$f":"COUNTIF($H$10:$H127,\"0\")","v":104},"   Test Cases Failed or TBD","Fail"]
[null,"TP-Supersede-01",{"$f":"I44","v":0},{"$f":"C44","v":"Incomplete"},null,{"$f":"COUNTIF($H$10:$H127,\"1\")","v":0},"Test cases Passed or N/A","Pass"]
[null,"TP-Supersede-02",{"$f":"I91","v":0},{"$f":"C91","v":"Incomplete"},null,{"$f":"COUNTIF($H$10:$H127,\">=0\")","v":104},"Total Test cases","N/A"]
[null,"TP-Supersede-03",{"$f":"I128","v":0},{"$f":"C128","v":"Incomplete"},null,{"$f":"SUM($F131/$F132)","v":0},"Test case % Passed or N/A","TBD"]
[]
[null,null,{"$f":"COUNTIF(D131:D133,\"Complete\")","v":0},"Scenarios Complete"]
[null,null,{"$f":"COUNTIF(D131:D133,\"Incomplete\")","v":3},"Scenarios Not Complete"]
[null,null,{"$f":"SUM(C135:C136)","v":3},"Total Scenarios"]
[null,null,{"$f":"SUM(C135) / (C137)","v":0},"Scenarios Completed (percentage)"]

{"sheet":"TP-Remove","index":5,"n_rows":31,"n_cols":9,"rows_kept":31,"cut":false,"hidden":false,"merged":[[1,2,1,6],[0,2,0,6],[7,2,7,6],[2,2,2,6],[4,2,4,6],[5,2,5,6],[6,2,6,6]]}
[null,"Test procedure:","TP-Remove: Remove a Pathology Report function"]
[null,"Overview:","To assess the conformance of a Pathology Report authoring system to the requirements that apply to the process of removing a Pathology Report from the My Health Record system.\n\nThe business process of removing a Pathology Report is initiated by the report author, the requester for diagnostic  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 by default, but when applied in the context of the test scenario they are mandatory. Therefore the only possible outcomes of each test case are \"Pass\" or \"Fail\". Each test scenario is passed when all the specified test cases have a status of \"Pass\"."]
[null,"Instructions:","A test scenario with the priority of \"mandatory\" must be applied and passed by the Authoring System  before it may be declared conformant to the requirements. Any \"conditional\" test scenario is to be applied if the authoring system has the functionality required to support the test. If it does not, 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-PathProc\" are listed in the FS-PathProc feature set within this conformance test specification.\n2. \"PCEHR_CIS\" are listed in the PCEHR Connecting Systems - Conformance Test Specification v1.6 [NEHTA-1299:2012].\n\nTasks surrounded by brackets, for example \"(F1. Obtain/validate healthcare identifiers)\", are assumed to be automatically performed by the authoring 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 authoring system can be declared conformant. \n\n"]
[]
[null,"Scenario:","TP-Remove-01 - Remove an existing Pathology 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 Pathology Report that was previously uploaded to the My Health Record system.\n\nSelect a Pathology Report that was uploaded to the My Health Record system, then use the software system to remove the Pathology 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 Pathology 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 includes sufficient demographic information within the request to successfully obtain their IHI from the HI Service.\n4. The request for the diagnostic services states the healthcare individual has at least one previously uploaded Pathology Report in My Health Record system.\n5.  The software system has been set up to successfully remove the pathology  reports from the My Health Record system.\n"]
[null,"SCENARIO","PERFORM THIS TASK","TEST SETS/TEST CASES","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)","Pathology Report is removed successfully. ","TBD",null,{"$f":"IF(F12=\"\",\"0\",IF(F12=\"Pass\",1,IF(F12=\"Fail\",0,IF(F12=\"TBD\",0,IF(F12=\"N/A\",1)))))","v":0}]
[null,null,"G1: Retrieve recorded information",null,null,"TBD",null,0]
[null,null,"Assess the conformance of the listed Pathology Report & CIS requirements","TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-05","Store \"Withdrawn consent\" indicator.","TBD",null,0]
[null,null,null,"TC-PathProc-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(H6:H22) / (COUNT(H6:H22))","v":0}]
[]
[null,"Scenario","Percentage complete","Scenario status",null,{"$f":"COUNTIF($H$7:$H22,\"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:$H22,\"1\")","v":0},"Test cases Passed or N/A","Pass"]
[null,null,null,null,null,{"$f":"COUNTIF($H$7:$H22,\">=0\")","v":13},"Total Test cases","N/A"]
[null,null,{"$f":"COUNTIF(D26:D27,\"Complete\")","v":0},"Scenarios Complete",null,{"$f":"SUM($F26/$F27)","v":0},"Test case % Passed or N/A","TBD"]
[null,null,{"$f":"COUNTIF(D26:D27,\"Incomplete\")","v":1},"Scenarios Not Complete"]
[null,null,{"$f":"SUM($C28:$C29)","v":1},"Total Scenarios"]
[null,null,{"$f":"SUM(C28) / (C30)","v":0},"Scenarios Completed (percentage)"]

{"sheet":"TP-Path","index":6,"n_rows":152,"n_cols":9,"rows_kept":152,"cut":false,"hidden":false,"merged":[[108,2,108,6],[109,2,109,6],[111,2,137,2],[111,1,137,1],[84,1,103,1],[106,2,106,6],[107,2,107,6],[84,2,103,2],[4,2,4,6],[5,2,5,6],[6,2,6,6],[7,2,7,6],[0,2,0,6],[1,2,1,6],[2,2,2,6],[82,2,82,3],[35,2,35,6],[37,2,56,2],[81,2,81,6],[9,1,28,1],[34,2,34,6],[32,2,32,6],[33,2,33,6],[9,2,28,2],[37,1,56,1],[57,2,76,2],[57,1,76,1],[79,2,79,6],[80,2,80,6]]}
[null,"Test procedure:","TP-Path: Pathology Report information content"]
[null,"Overview:","To assess the ability of a Pathology Report authoring system to create Pathology 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 Pathology Reports with specific types of content.  \nThe conformance of the Pathology Reports can then be assessed using selected test cases. \n\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 Pathology Report authoring system."]
[null,"Instructions:","Test scenarios with the priority of \"Mandatory\" must be applied and passed by the authoring system  before it may be declared conformant to the requirements. Any \"Conditional\" test scenarios are to be applied if the authoring system has the functionality required to support the test. If the authoring 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 as well as other specifications.  Test Cases commencing with the identifier:\n1. \"TC-PathDoc\" are listed in the FS-PathDoc feature set within this conformance test specification.\n2. \"TC-PathProc\" are listed in the FS-PathProc feature set within this conformance test specification.\n",null," "]
[]
[null,"Scenario:","TP-PATH-01 - Create one Pathology Report where the Pathology Test Result contains a reference to a website.                       "]
[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 who has indicated their consent to upload clinical documents to the My Health Record system,  using the software system author a Pathology Report that contains a reference to a website. \n1. Demonstrate the use of the software system to create a Pathology Report where the Pathology Test Result contains a reference to a website."]
[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-Path-01.1","Create a Pathology Report where the Pathology Test Result contains a reference to a website.","Indicate if this scenario is applicable to your software system in the \nACTUAL TEST RESULT","A Pathology Report has been created with Pathology Test 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-PathDoc-02","A  CDA document SHALL reference one, and only one, attachment that is the original diagnostic report. The report SHALL be a PDF packaged attachment.","TBD",null,0]
[null,null,null,"TC-PathDoc-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-PathDoc-04","Check for elements that cannot be a \"nullFlavor\".","TBD",null,0]
[null,null,null,"TC-PathDoc-05","Narrative and Section title.","TBD",null,0]
[null,null,null,"TC-PathDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-PathDoc-07","Document Author data elements.","TBD",null,0]
[null,null,null,"TC-PathDoc-08","Reporting Pathologist data elements.","TBD",null,0]
[null,null,null,"TC-PathDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-PathDoc-10","Report Date Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-12","Reporting Pathologist  > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-13","Collection Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-14","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-15","Verify the URL of the Document Target is also present in a <linkHtml> element in the narrative block.","TBD",null,0]
[null,null,null,"TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-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-PathProc-05","Store \"Withdrawn consent\" indicator.","TBD",null,0]
[null,null,null,"TC-PathProc-12","Record information on validity of healthcare identifiers.","TBD",null,{"$f":"IF(F28=\"\",\"0\",IF(F28=\"Pass\",1,IF(F28=\"Fail\",0,IF(F28=\"TBD\",0,IF(F28=\"N/A\",1)))))","v":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(I30=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H10:I29) / (COUNT(H10:I29))","v":0}]
[]
[]
[null,"Scenario:","TP-PATH-02 - Create one Pathology Report with multiple Pathology Test Results reported by a single Reporting Pathologist.\n                         Create one Pathology Report with multiple Pathology Test Results reported by different Reporting Pathologists.  "]
[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 who has indicated their consent to upload clinical documents to the My Health Record system, using the software system author a Pathology Report that has multiple Pathology Test Results reported by a single Reporting Pathologist. For the same recipient, author a Pathology Report that has multiple Pathology Test Results reported by a different Reporting Pathologist.\n1. Demonstrate that the software system is capable of creating a Pathology Report that has multiple Pathology Test Results reported by a single Reporting Pathologist.\n2. Demonstrate that the software system is capable of creating a Pathology Report that has multiple Pathology Test Results reported by  different Reporting Pathologists."]
[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-Path-02.1","Create a Pathology Report  that has multiple Pathology Test Results where all the Pathology Test Results are reported by single Reporting Pathologist.","Indicate if this scenario is applicable to your software system in the \nACTUAL TEST RESULT","Pathology Report has been created with multiple Pathology Test Results where all the results are reported by one Reporting Pathologist.","TBD",null,{"$f":"IF(F38=\"\",\"0\",IF(F38=\"Pass\",1,IF(F38=\"Fail\",0,IF(F38=\"TBD\",0,IF(F38=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-PathDoc-02","A  CDA document SHALL reference one, and only one, attachment that is the original diagnostic report. The report SHALL be a PDF packaged attachment.","TBD",null,0]
[null,null,null,"TC-PathDoc-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-PathDoc-04","Check for elements that cannot be a \"nullFlavor\".","TBD",null,0]
[null,null,null,"TC-PathDoc-05","Narrative and Section title.","TBD",null,0]
[null,null,null,"TC-PathDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-PathDoc-07","Document Author data elements.","TBD",null,0]
[null,null,null,"TC-PathDoc-08","Reporting Pathologist data elements.","TBD",null,0]
[null,null,null,"TC-PathDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-PathDoc-10","Report Date Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-12","Reporting Pathologist  > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-13","Collection Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-14","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-15","Document Target: URL Referenced - Link in corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-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-PathProc-05","Store \"Withdrawn consent\" indicator.","TBD",null,0]
[null,null,null,"TC-PathProc-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-Path-02.2","Demonstrate that the software system is capable of creating a Pathology Report with multiple Pathology Test Results reported by different Reporting Pathologists.","Indicate if this scenario is applicable to your software system in the \nACTUAL TEST RESULT","Pathology Report has been created with multiple Pathology Test Results where each result is reported by  different Reporting Pathologists.","TBD",null,0]
[null,null,null,"TC-PathDoc-02","A  CDA document SHALL reference one, and only one, attachment that is the original diagnostic report. The report SHALL be a PDF packaged attachment.","TBD",null,0]
[null,null,null,"TC-PathDoc-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-PathDoc-04","Check for elements that cannot be a \"nullFlavor\".","TBD",null,0]
[null,null,null,"TC-PathDoc-05","Narrative and Section title.","TBD",null,0]
[null,null,null,"TC-PathDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-PathDoc-07","Document Author data elements.","TBD",null,0]
[null,null,null,"TC-PathDoc-08","Reporting Pathologist data elements.","TBD",null,0]
[null,null,null,"TC-PathDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-PathDoc-10","Report Date Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-12","Reporting Pathologist  > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-13","Collection Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-14","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-15","Document Target: URL Referenced - Link in corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-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-PathProc-05","Store \"Withdrawn consent\" indicator.","TBD",null,0]
[null,null,null,"TC-PathProc-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(I78=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H38:H77) / (COUNT(H38:H77))","v":0}]
[]
[null,"Scenario:","TP-PATH-03 - Create a Pathology Report with the Requestor's entity identifier, address & contact details, and the Requestor's employer entity identifier. "]
[null,"Objective:","Demonstrate the authoring system's ability to create a Pathology Report with:\n1. The Requestor's entity identifier, address and contact details\n2. The Requestor's employer entity identifier."]
[null,"Priority:","  Mandatory."]
[null,"Pre-conditions:","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-Path-03.1","Create a Pathology Report with the Requester's entity identifier, address and contact details.\n\n","-","Pathology Report has been created with Requester's entity identifier, address and contact details.","TBD",null,{"$f":"IF(F85=\"\",\"0\",IF(F85=\"Pass\",1,IF(F85=\"Fail\",0,IF(F85=\"TBD\",0,IF(F85=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-PathDoc-02","A  CDA document SHALL reference one, and only one, attachment that is the original diagnostic report. The report SHALL be a PDF packaged attachment.","TBD",null,0]
[null,null,null,"TC-PathDoc-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-PathDoc-04","Check for elements that cannot be a \"nullFlavor\".","TBD",null,0]
[null,null,null,"TC-PathDoc-05","Narrative and Section title.","TBD",null,0]
[null,null,null,"TC-PathDoc-06","Sort test results.","TBD",null,0]
[null,null,null,"TC-PathDoc-07","Document Author data elements.","TBD",null,0]
[null,null,null,"TC-PathDoc-08","Reporting Pathologist data elements.","TBD",null,0]
[null,null,null,"TC-PathDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-PathDoc-10","Report Date Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-12","Reporting Pathologist  > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-13","Collection Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-14","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-15","Document Target: URL Referenced - Link in corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-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-PathProc-05","Store \"Withdrawn consent\" indicator.","TBD",null,0]
[null,null,null,"TC-PathProc-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(I105=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H85:H104) / (COUNT(H85:H104))","v":0}]
[]
[null,"Scenario:","TP-PATH-04 - Create a Pathology Report to test all the mandatory requirements and the applicable conditional requirements defined in the Pathology Report Conformance Profile."]
[null,"Objective:","Demonstrate the software system conforms to all the mandatory requirements and the applicable conditional requirements defined in the Pathology Report Conformance Profile."]
[null,"Priority:","  Mandatory."]
[null,"Pre-conditions:","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-Path-04.1","Create one or more Pathology Reports that satisfy the criteria that all the mandatory requirements and the applicable conditional requirements defined in the Pathology Report Conformance Profile can be verified.\n\n","-","One or more Pathology Reports have been created. ","TBD",null,{"$f":"IF(F112=\"\",\"0\",IF(F112=\"Pass\",1,IF(F112=\"Fail\",0,IF(F112=\"TBD\",0,IF(F112=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-PathDoc-01","Conform to the requirements for conformance levels 3A or 3B.","TBD",null,0]
[null,null,null,"TC-PathDoc-02","A  CDA document SHALL reference one, and only one, attachment that is the original diagnostic report. The report SHALL be a PDF packaged attachment.","TBD",null,0]
[null,null,null,"TC-PathDoc-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-PathDoc-04","Check for elements that cannot be a \"nullFlavor\".","TBD",null,0]
[null,null,null,"TC-PathDoc-05","Narrative and Section title.","TBD",null,0]
[null,null,null,"TC-PathDoc-07","Document Author data elements.","TBD",null,0]
[null,null,null,"TC-PathDoc-08","Reporting Pathologist data elements.","TBD",null,0]
[null,null,null,"TC-PathDoc-09","References in CDA Package.","TBD",null,0]
[null,null,null,"TC-PathDoc-10","Report Date Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-11","Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-12","Reporting Pathologist  > Participant > Entity Identifier SHALL be an HPI-I.","TBD",null,0]
[null,null,null,"TC-PathDoc-13","Collection Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-14","Appropriate Observation Date & Time.","TBD",null,0]
[null,null,null,"TC-PathDoc-15","Document Target: URL Referenced - Link in corresponding CDA Narrative.","TBD",null,0]
[null,null,null,"TC-PathProc-01","Clinical document producer is neither a registered consumer portal nor registered provider portal.","TBD",null,0]
[null,null,null,"TC-PathProc-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-PathProc-05","Store \"Withdrawn consent\" indicator.","TBD",null,0]
[null,null,null,"TC-PathProc-06","\"Document uploaded\" indicator is recorded.","TBD",null,0]
[null,null,null,"TC-PathProc-07","The Pathology Report is not uploaded to My Health Record system. \nA copy of the Pathology Report is saved to Authoring System.","TBD",null,0]
[null,null,null,"TC-PathProc-08","Software system permits the report to be uploaded to the My Health Record system.","TBD",null,0]
[null,null,null,"TC-PathProc-09","Invoke doesPCEHRexist web service. Upload the clinical document.","TBD",null,0]
[null,null,null,"TC-PathProc-10","Changing \"Withdrawn consent\" indicator.\n","TBD",null,0]
[null,null,null,"TC-PathProc-11","Record upload failure.","TBD",null,0]
[null,null,null,"TC-PathProc-12","Record information on validity of healthcare identifiers.","TBD",null,0]
[null,null,null,"TC-PathProc-13","Healthcare Provider decision not to upload.","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(I139=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H112:I138) / (COUNT(H112:H138))","v":0}]
[]
[]
[]
[null," Scenario","Percentage complete","Scenario status",null,{"$f":"COUNTIF(H10:H139,\"0\")","v":107},"Test Cases Failed or TBD","Fail"]
[null,"TP-Path-01",{"$f":"I30","v":0},{"$f":"C30","v":"Incomplete"},null,{"$f":"COUNTIF(H10:H140,\"1\")","v":0},"Test cases Passed or N/A","Pass"]
[null,"TP-Path-02",{"$f":"I78","v":0},{"$f":"C78","v":"Incomplete"},null,{"$f":"COUNTIF(H10:H139,\">=0\")","v":107},"Total Test cases","N/A"]
[null,"TP-Path-03",{"$f":"I105","v":0},{"$f":"C105","v":"Incomplete"},null,{"$f":"SUM(F144/F145)","v":0},"Test case % Passed or N/A","TBD"]
[null,"TP-Path-04",{"$f":"I139","v":0},{"$f":"C139","v":"Incomplete"}]
[]
[null,null,{"$f":"COUNTIF($D$144:$D$147,\"Complete\")","v":0},"Scenarios Complete"]
[null,null,{"$f":"COUNTIF($D$144:$D$147,\"Incomplete\")","v":4},"Scenarios Not Complete"]
[null,null,{"$f":"SUM($C$149:$C$150)","v":4},"Total Scenarios"]
[null,null,{"$f":"SUM($C$149)/($C$151)","v":0},"Scenarios Completed (percentage)"]

{"sheet":"FS-PathDoc ","index":7,"n_rows":31,"n_cols":11,"rows_kept":31,"cut":false,"hidden":false,"merged":[[21,2,22,2],[0,0,0,1],[0,2,0,5],[1,2,1,5],[2,2,2,5],[3,2,3,5],[1,0,1,1],[2,0,2,1],[3,0,3,1],[19,1,20,1],[19,2,20,2]]}
["Feature set identifier:",null,"FS-Paths (Pathology Report clinical document)"]
["Objective:",null,"To assess the conformance of a Pathology Report clinical document to the requirements specified in the Common Conformance Profile and the requirements specified in Pathology Report Conformance Profile."]
["Strategy:",null,"A Pathology Report clinical document to be tested may be obtained from any source, such as a 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 wherever practical.  The test cases listed here are to be used in conjunction with the test cases in the Clinical Documents - 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 Pathology 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. In general the priority of the corresponding test case is \"optional\" to indicate that, it need only be applied if the developer of the software system claims to have implemented the recommended requirement.\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,"1. eHealth Pathology Report - My Health Record Conformance Profile v1.1 [NEHTA-2214:2016]\n2. Clinical Documents - Common Conformance Profile [NEHTA-1850:2015]\n3. Pathology Report - Structured Content Specification v1.0 [NEHTA-1413:2014] "]
[]
["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-PathDoc","START:  TS-PathDoc (Pathology Report clinical document)"]
["TS-PathDoc","TC-PathDoc-01","023435 [NEHTA-2214:2016]\nA CDA document sent to the My Health Record system SHALL 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 [NEHTA-1850:2015].\n","M",1,"Pass the test where:\na) conformance to Level 3A or 3B is claimed, and\nb) the clinical document passes the test cases for feature sets FS-Doc, FS-Narr and FS-Types in the Clinical Documents - Conformance Test Specification for Authoring systems [NEHTA-2209:2016].\nElse, Fail the test.\n","a) 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\nb) 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].\n\n","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-PathDoc","TC-PathDoc-02","023473 [NEHTA-2214:2016]\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 that is claimed as the original Pathology 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 Pathology 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-PathDoc",null,null,null,2,"Pass the test where 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].\nElse Fail the test. \n\nNOTE TO TESTER: \nA packaged attachment is an attachment whose \"reference\" value is a relative reference to a document that 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,{"$f":"IF(H11=\"\",\"0\",IF(H11=\"Pass\",1,IF(H11=\"Fail\",0,IF(H11=\"TBD\",0,IF(H11=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D11)=48,H11=\"N/A\"),1,0)","v":0}]
["TS-PathDoc","TC-PathDoc-03","023651 [NEHTA-2214:2016]\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-PathDoc","TC-PathDoc-04","024692  [NEHTA-2214:2016]\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 > Requester > Participant > Person or Organisation of Device > Person > Person Name > Family Name\n• Pathology > Pathology Test Result > Test Result Name\n• Pathology > Pathology Test Result > Test Specimen Detail > Handling and Processing > Collection DateTime\n• Pathology > Pathology Test Result > Diagnostic Service\n• Pathology > Pathology Test Result > Overall Test Result Status\n• Pathology > Related Document > Document Details > Report Identifier\n• Pathology > Related Document > Document Details > Report DateTime","M",1,"For any Pathology Report clinical document under test:\n\nFail the test where any following data elements have the XML attribute \"nullFlavor\":\n\n• Document Author > Participant > Person or Organisation or Device > Person > Employment Detail > Employer Organisation > Organisation > Organisation Name\n(XPATH - /ClinicalDocument/author/assignedAuthor/assignedPerson/ext:asEmployment/ext:employerOrganization/asOrganizationPartOf/wholeOrganization/name)\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• Pathology > Pathology Test Result > Test Result Name\n(XPATH - ClinicalDocument/component/structuredBody/component[pathology]/section/component[path_test]/section/entry[path_test_res]/observation)\n\n• Pathology > Pathology Test Result > Test Specimen Detail > Handling and Processing > Collection DateTime\n(XPATH - /ClinicalDocument/component/structuredBody/component[pathology]/section/component[path_test]/section/entry[path_test_res]/observation/entryRelationship[specimen]/observation/effectiveTime)\n\n• Pathology > Pathology Test Result > Diagnostic Service\n(XPath=/ClinicalDocument/component/structuredBody/component[pathology]/section/component[path_test]/section/entry[path_test_res]/observation/entryRelationship[specimen]/observation/effectiveTime)\n\n• Pathology > Pathology Test Result > Overall Test Result Status\n(XPATH - /ClinicalDocument/component/structuredBody/component[pathology]/section/component[path_test]/section/entry[path_test_res]/observation/entryRelationship[res_stat]/observation/value:CD)\n\n• Pathology > Related Document > Document Details > Report Identifier\n(XPATH - /ClinicalDocument/component/structuredBody/component[pathology]/section/entry[doc_detail]/act/reference[document]/externalDocument/id)\n\n• Pathology > Related Document > Document Details > Report DateTime\n(XPATH - /ClinicalDocument/component/structuredBody/component[pathology]/section/entry[doc_detail]/act/effectiveTime/low@value)\n\nElse, Pass the test.","The following data elements are populated with values and do not contain the \"nullFlavor\" attribute.\n\n• Document Author > Participant > Person or Organisation or Device > Person > Employment Detail > Employer Organisation > Organisation > Organisation Name\n\n• Order Details > Requester > Participant > Person or Organisation of Device > Person > Person Name > Family Name\n\n• Pathology > Pathology Test Result > Test Result Name\n\n• Pathology > Pathology Test Result > Test Specimen Detail > Handling and Processing > Collection DateTime\n\n• Pathology > Pathology Test Result > Diagnostic Service\n\n• Pathology > Pathology Test Result > Overall Test Result Status\n\n• Pathology > Related Document > Document Details > Report Identifier\n\n• Pathology > Related Document > Document Details > Report DateTime","TBD",null,0,{"$f":"IF(AND(BGCol(D13)=48,H13=\"N/A\"),1,0)","v":0}]
["TS-PathDoc","TC-PathDoc-05","026615 [NEHTA-2214:2016]\nIf a narrative is not included in a Pathology Test Result section then the section title SHALL NOT be included.","C",1,"CONDITION: Pathology Test Result section does not contain a narrative block.\n\nPass the test where:\na) there is no section title for every section with no narrative block \nElse, Fail the test.\n","There is no section title for every section with no narrative block.","TBD",null,0,{"$f":"IF(AND(BGCol(D14)=48,H14=\"N/A\"),1,0)","v":0}]
["TS-PathDoc","TC-PathDoc-06","024798 [NEHTA-2214:2016]\nThe diagnostic report provider software SHOULD order 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 Pathology Report PDF document.","TBD",null,0,{"$f":"IF(AND(BGCol(D15)=48,H15=\"N/A\"),1,0)","v":0}]
["TS-PathDoc","TC-PathDoc-07","025065 [NEHTA-2214:2016]\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:\na) the data element \"Document Author > Role\" has the value nullFlavor= “NI”, and \nb) the data element \"Document Author > Participant > Entity Identifier\" passes test cases TC-Types-34, TC-Types-37 & TC-Types-32 in the Clinical Documents - Conformance Test Specification for Authoring Systems [NEHTA-2209:2016] and has the attribute with name \"extension\" whose value is “NI”, and\nc) 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","a) The data element \"Document Author > Role\" has the value nullFlavor= “NI”. \nb) The data element \"Document Author > Participant > Entity Identifier\" passes test cases TC-Types-34, TC-Types-37 & TC-Types-32 in the Clinical Documents - Conformance Test Specification for Authoring Systems [NEHTA-2209:2016] and has the attribute with name \"extension\" whose value is “NI”.\nc) The data element \"Document Author > Participant > Person or Organisation or Device > Person > Person Name > Family Name\" has the value nullFlavor=“NI”. ","TBD",null,0,{"$f":"IF(AND(BGCol(D16)=48,H16=\"N/A\"),1,0)","v":0}]
["TS-PathDoc","TC-PathDoc-08","025066 [NEHTA-2214:2016]\nThe following values SHALL be used for mandatory Reporting Pathologist data elements when it is not possible to name one person as the Reporting Pathologist:\n\n• Reporting Pathologist > Role SHALL have the value nullFlavor=“NI”.\n\n• Reporting Pathologist > Participant > Entity Identifier SHALL be a local identifier with the value “NI” for the extension attribute.\n\n• Reporting Pathologist > Participant > Person or Organisation or Device > Person > Person Name > Family Name SHALL have the value nullFlavor=“NI”.\n\n\n\n","C",1,"CONDITION: It is NOT possible to name one person as the Reporting Pathologist.\n\nElse, Pass the test where:\na) the data element \"Reporting Pathologist > Role\" has the value nullFlavor=“NI”, and  \nb) the data element \"Reporting Pathologist > Participant > Entity Identifies a value that is a local identifier, and \nc) the data element \"Reporting Pathologist > 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 \"Reporting Pathologist > Participant > Person or Organisation or Device > Person > Person Name > Family Name\" has the value nullFlavor=“NI”.\nOtherwise, Fail the test.\n\nNOTE TO TESTER: \na) Mark the test N/A where one person is listed as the Reporting Pathologist.\nb) A person is listed as the Reporting Pathologist. if there is a name included in the \"/ClinicalDocument/component/structuredBody/component[pathology]/section/author/assignedAuthor/assignedPerson/name/family\" element.\n","a) The data element \"Reporting Pathologist > Role\" has the value nullFlavor=“NI”, and\n\nb) the data element \"Reporting Pathologist > Participant > Entity Identifies value that is a local identifier, and \n\nc) the data element \"Reporting Pathologist > 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\nd) the data element \"Reporting Pathologist > Participant > Person or Organisation or Device > Person > Person Name > Family Name\" has the value nullFlavor=“NI”.\n","N/A",null,1,{"$f":"IF(AND(BGCol(D17)=48,H17=\"N/A\"),1,0)","v":0}]
["TS-PathDoc","TC-PathDoc-09","024732 [NEHTA-2214:2016]\nA Pathology 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-2064-2016] 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.\n","N/A",null,1,{"$f":"IF(AND(BGCol(D18)=48,H18=\"N/A\"),1,0)","v":0}]
["TS-PathDoc","TC-PathDoc-10","2.25 Report DateTime (Effective Period) [NEHTA-1413:2014]\nThe period of time during which the document of interest is deemed to have clinical utility. The start of Effective Period SHALL be the date and time of the report (Report DateTime). Report DateTime SHALL include a date and a time component.\n\n\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: \nData type: TimeInterval \nXPath: ClinicalDocument/component/structuredBody/component[pathology]/section/entry[doc_detail]/act/effectiveTime/low@value\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(D19)=48,H19=\"N/A\"),1,0)","v":0}]
["TS-PathDoc","TC-PathDoc-11","023436 [NEHTA-2214:2016]\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.\n\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: The structured content specifications and CDA implementation guides require the inclusion of an HPI-I for every document author. This requirement overrides those specifications. The Clinical Documents - Common Conformance Profile [NEHTA-1850:2015] provides requirements for the local identifiers of the type that are managed by a healthcare provider. Examples of other types of local identifiers are provided by the Healthcare Identifier HL7 Implementation Guide [SA2012].\n","C",1,"CONDITION: Permission has not been granted to relax the need to provide a HPI-I. \n\nPass the test where one \"Document Author > Participant > Entity Identifier\" element contains an HPI-I.\nElse Fail the test.\n\n\nNOTE TO TESTER: 1. The data element \"Document Author > Participant > Entity Identifier\" has the XPATH /ClinicalDocument/author/assignedAuthor/assignedPerson/<Entity Identifier>.\n\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(D20)=48,H20=\"N/A\"),1,0)","v":0}]
["TS-PathDoc",null,null,"C",2,"CONDITION: Permission has been granted to relax the need to provide a HPI-I. \n\na) 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.\n\nb)  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.\n\nNOTE TO TESTER: \na) The data element \"Document Author > Participant > Entity Identifier\" has the XPATH /ClinicalDocument/author/assignedAuthor/assignedPerson/<Entity Identifier>.\n\nb) A local identifier is one that conforms to the requirement  \"Requirement 023876 Healthcare consumer's local identifier managed by a healthcare provider organisation\" (Test case ID TC-Types-29 )  specified in the Clinical Documents - Conformance Test Specification for Authoring Systems [NEHTA-2209:2016].","The value of the Document Author > Participant > Entity Identifier is an HPI-I, or a value that identifies the document author.\n","TBD"]
["TS-PathDoc","TC-PathDoc-12","023648 [NEHTA-2214:2016]\nThe value of at least one reporting pathologist 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 pathologist identifier SHALL have a value that identifies the reporting pathologist 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: Reporting pathologists may be stored in:\nPathology Report > Pathology > Reporting Pathologist\nThe eHealth Pathology Report structured content specification and CDA implementation guide require the inclusion of an HPI-I for every reporting pathologist. This requirement overrides those specifications\nThe Clinical Documents - Common Conformance Profile [NEHTA-1850:2015] provides requirements for the local identifiers of the type that are managed by a healthcare provider. Examples of other types of local identifiers are provided by the Healthcare Identifier HL7 Implementation Guide [SA2012].\n","C",1,"CONDITION: Permission has not been granted to relax the need to provide a HPI-I.\n\nPass the test where one \"Document Author > Participant > Entity Identifier\" element contains an HPI-I.\nElse Fail the test.\n\nNOTE TO TESTER: The data element \"Pathology Report > Pathology > Reporting Pathologist\" has the XPATH /ClinicalDocument/component/structuredBody/component[pathology]/section/author/assignedAuthor/assignedPerson/<Entity Identifier>.\n","The value of the Pathology Report > Pathology > Reporting Pathologist is an HPI-I.","TBD",null,0,{"$f":"IF(AND(BGCol(D22)=48,H22=\"N/A\"),1,0)","v":0}]
["TS-PathDoc",null,null,null,2,"CONDITION: Permission has been granted to relax the need to provide a HPI-I. \n\na) 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.\n\nb)  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.\n\n","The value of the Pathology Report > Pathology > Reporting Pathologist is a value that identifies the document author.","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-PathDoc","TC-PathDoc-13","3.11 Collection DateTime [NEHTA-1413:2014]\nDefinition: Date, and optionally time, of collection.\n\n\n\n\n","M",1,"Pass the test where the Collection DateTime data element passes test case TC Types-18 in the Conformance Test Specification for Authoring Systems [NEHTA-2209:2016].  \nElse, Fail the test.\n\nData type: DateTime [NEHTA-0794:2011]\nXPath:  ClinicalDocument/component/structuredBody/component[pathology]/section/component[path_test]/section/entry[path_test_res]/observation/entryRelationship[specimen]/observation/effectiveTime\n","The Collection 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,{"$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-PathDoc","TC-PathDoc-14","3.14 Observation DateTime [NEHTA-1413:2014]  \nDefinition: Date, and optionally time, when an observation is clinically significant to the condition of the subject of the observation.\n\nThis element will hold the same value as Test SpecimenDetail (SPECIMEN)> HANDLING AND PROCESSING > Collection DateTime (entryRelationship[specimen]/observation/effectiveTime) [NEHTA-1412:2014]\n","M",1,"Pass the test where the Observation DateTime data element passes test case TC Types-18 in the Conformance Test Specification for Authoring Systems [NEHTA-2209:2016] and has the same value as Test Specimen Detail (SPECIMEN)> HANDLING AND PROCESSING > Collection DateTime.\nElse, Fail the test.\n\nData Type: DateTime [NEHTA-0794:2011]\nXPath: \nClinicalDocument/component/structuredBody/component[pathology]/section/component[path_test]/section/entry[path_test_res]/observation/entryRelationship[tst_date]/observation/effectiveTime\n","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).","TBD",null,0,{"$f":"IF(AND(BGCol(D25)=48,H25=\"N/A\"),1,0)","v":0}]
["TS-PathDoc","TC-PathDoc-15","2.20 Document Target [NEHTA-1413:2014] \nThe link SHALL also be present in the corresponding CDA Narrative in a <linkHtml> element.\n\n\n","M",1,"Pass the test where the Document Target data element passes test case TC-Narr-92.\nElse, Fail the test.\n\nNOTE TO TESTER: Document Target is modelled as an External Document, so the requirements in HL7 Clinical Document Architecture, Release 2 [HL7CDAR2] for external objects apply.\n\nThe XPath for Document Target is: \nClinicalDocument/component/structuredBody/component[pathology]/section/entry[doc_detail]/act/reference[document]/externalDocument/text:ED","The URL in a Document Target data element is also present in a <linkHtml> element in the narrative block, and is not present in a <renderMultiMedia> element.","TBD",null,0,{"$f":"IF(AND(BGCol(D26)=48,H26=\"N/A\"),1,0)","v":0}]
["TS-PathDoc","END:  TS-PathDoc (Pathology Report clinical document)"]
[null,null,null,null,null,null,null,"TBD","Total Steps",{"$f":"SUM(J29:J30)","v":17}]
[null,null,null,null,null,null,null,"Fail","Tests Not Started, Failed or TBD",{"$f":"COUNTIF(J2:J26,\"0\")","v":15}]
[null,null,null,null,null,null,null,"N/A","Tests Passed or N/A",{"$f":"COUNTIF(J2:J26,\"1\")","v":2}]
[null,null,null,null,null,null,null,"Pass","%Passed or N/A",{"$f":"SUM(J30/J28)","v":0.11764705882352941}]

{"sheet":"FS-PathProc","index":8,"n_rows":40,"n_cols":11,"rows_kept":40,"cut":false,"hidden":false,"merged":[[32,2,33,2],[30,2,31,2],[22,2,23,2],[24,2,25,2],[26,2,27,2],[28,2,29,2],[0,0,0,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],[1,0,1,1]]}
["Feature set identifier:",null,"FS-PathProc (business processes for the authoring system)"]
["Objective:",null,"To assess the conformance to the process requirements for an software system that creates Pathology Reports. These are requirements for creating, superseding and removing Pathology Reports, consent management and record keeping. These requirements are additional to the requirements that apply to the Pathology Reports created by an software system.\n"]
["Strategy:",null,"The eHealth Pathology Report - My Health Record Conformance Profile v1.1 [NEHTA-2214:2016] include requirements for the behaviour of the document authoring system. The conformance of an authoring system to these requirements is assessed by accessing the authoring 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 an authoring system that apply regardless of the type of document being authored. Test cases for those requirements are listed in the Clinical Documents - Conformance Test Specification for Authoring Systems [NEHTA-2209:2016].\n\nTest cases that verify the conformance of Pathology Reports created by the authoring system are included separately, within this document, in the \"FS-PathDoc\" 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,"1. eHealth Pathology Report - My Health Record Conformance Profile v1.1 [NEHTA-2214:2016]\n2. Clinical 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-GPATH","START:  TS-GPATH (General pathology  report))"]
["TS-GPATH","TC-PathProc-01","023456 [NEHTA-2214:2016]\nA producer SHALL NOT be a:\n• registered consumer portal; or a\n• registered provider portal.\n","M",1,"Determine whether the producer of a clinical document is a registered consumer portal or is a registered provider portal.\n\nFail the test where the producer of a clinical document is a registered consumer portal or a registered provider portal.\nElse, Pass the test.\n","The software system is neither a registered consumer or provider portal.\n","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-GPATH","TC-PathProc-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,"Apply the test cases in the FS-Auth (Authoring systems) feature set in the Clinical Documents - Conformance Test Specification for Authoring Systems [NEHTA-2209:2016].\n\nPass the test where the test cases in the software system passes the test cases in the FS-Auth feature set;\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-GPATH","TC-PathProc-03","024885 [NEHTA-2214:2016]\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-GPATH","TC-PathProc-04","024972 [NEHTA-2214:2016]\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-GPATH","END:  TS-GPATH (General pathology  report))"]
["TS-Cons","START:  TS-Cons (Consent management)"]
["TS-Cons","TC-PathProc-05","026757 [NEHTA-2214:2016]\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.\nIn the absence of any instruction or indication, the software SHALL indicate that consent was not withdrawn.\n                                                       ","M",1,"Pass the test where:\na) 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; or\nb) The healthcare individual’s consent to upload reports to their digital health record  has not been withdrawn, then the software system records a \"No withdrawn consent\" indicator against a request, report, or healthcare encounter; or \nc) The healthcare individual’s consent to upload reports to their digital health record  has not been specified, then the software system records a \"No withdrawn consent\" indicator against a request, report, or healthcare encounter. \n\nElse, Fail the test.\n","a) The software system records a \"Withdrawn consent\" indicator against a request, report, or healthcare encounter if the healthcare individual’s consent to upload reports to their My Health Record system has been withdrawn.\n\nb) The software system records a \"No withdrawn consent\" indicator against a request, report, or healthcare encounter if the healthcare individual’s consent to upload reports to their My Health Record system has not been withdrawn.\n\nc) The software system records a \"No withdrawn consent\" indicator against a request, report, or healthcare encounter if the healthcare individual’s consent to upload reports to their My Health Record system has not been specified.\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-PathProc-06","026760 [NEHTA-2214:2016]\nThe software SHALL store a \"document uploaded\" indicator for each report and will indicate documents that have been uploaded to the My Health Record system.\n","M",1,"Pass the test where:\na) If the Pathology Report is uploaded to the My Health Record system,  then the software system records a \"document uploaded\" indicator against the report. \nor\nb)  If the Pathology Report is created and not uploaded to the My Health Record system, then the software system does not indicate \"document uploaded\" against the report.\n\nElse, Fail the test.","a) When the Pathology Report is uploaded to the My Health Record system,  then the software system records a \"document uploaded\" indicator against the report. \n\nb) When the Pathology Report is created and not uploaded to the My Health Record system, then the software system does not indicate \"document uploaded\" against the report. ","TBD",null,0,{"$f":"IF(AND(BGCol(D16)=48,H16=\"N/A\"),1,0)","v":0}]
["TS-Cons","TC-PathProc-07","026761 [NEHTA-2214:2016]\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 Pathology report from being uploaded to the My Health Record System when the indicator against the request, report or healthcare encounter is set to \"Withdrawn consent\".\nElse, Fail the test.\n\n","When the indicator against the request, report or healthcare encounter is set to \"Withdrawn consent\", then the software system prevents the Pathology Report from being uploaded to the My Health Record system. ","TBD",null,0,{"$f":"IF(AND(BGCol(D17)=48,H17=\"N/A\"),1,0)","v":0}]
["TS-Cons","TC-PathProc-08","026762 [NEHTA-2214:2016]\nUploading when digital health record exists.\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 Pathology Report to be uploaded to the My Health Record System. Else, Fail the test.\n\n","Where there is no indication of withdrawal of consent for the request, report, or encounter; or it is known that the healthcare individual has a digital health record, then the software system permits the Pathology 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-PathProc-09","026763 [NEHTA-2214:2016]\nInvoking doesPCEHRexist web service.\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.\n","O",1,"Pass the test where the software system can send and receive a web service response from the My Health Record System via a doesPCEHRexist web service call.\nElse, mark the test as N/A.\n","The software system sends and receives a web service request to the My Health Record System via a doesPCEHRexist web service call.","TBD",null,0,{"$f":"IF(AND(BGCol(D19)=48,H19=\"N/A\"),1,0)","v":0}]
["TS-Cons","TC-PathProc-10","026766 [NEHTA-2214:2016]\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-PathProc-11","026625 [NEHTA-2214:2016]\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.","M",1,"Pass the test where the software system:\na) records a failure to upload a Pathology Report to the My Health Record system, and\nb) 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 Pathology Report to the My Health Record system, where it records the error code returned by the My Health Record system and the date and time when the information was recorded. \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,"Pass the test where the requester’s order identifier is included in the record. \nElse, mark the test as N/A.\n","Requester's order identifier is recorded by the My Health Record system (with all other information), when there is a failure to upload a Pathology Report. ","TBD",null,0,{"$f":"IF(AND(BGCol(D24)=48,H24=\"N/A\"),1,0)","v":0}]
["TS-Record","TC-PathProc-12","026626 [NEHTA-2214:2016]\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 the Healthcare Identifiers Service and the date and time the error occurred. \nThe information recorded SHOULD include the requester’s order identifier.\n","M",1,"Pass the test where:\na) the software system records a failure to obtain or validate one or more healthcare identifier, and\nb) records the report or document identifier, the error code returned by Healthcare Identifiers Service, and the date and time the error occurred (with the time zone representing the software system's time zone). \nElse, Fail the test.\n","The software system records a failure obtain or validate a healthcare identifier, where it records the error code returned by the My Health Record system and the ate and time of the decision. \n","N/A",null,1,{"$f":"IF(AND(BGCol(D25)=48,H25=\"N/A\"),1,0)","v":1}]
["TS-Record",null,null,"O",2,"Pass the test where the requester's order identifier included in the record. \nElse, mark the test as N/A.","The software system records requester's order identifier.","TBD",null,0,{"$f":"IF(AND(BGCol(D26)=48,H26=\"N/A\"),1,0)","v":0}]
["TS-Record","TC-PathProc-13","026627 [NEHTA-2214:2016]\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.\n","M",1,"Pass the test where:\na) the software system records the decision not to upload the Pathology Report to the My Health Record system, and\nb) 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 Pathology Report to the My Health Record system, where it records the ate and time of the decision.","TBD",null,0,{"$f":"IF(AND(BGCol(D27)=48,H27=\"N/A\"),1,0)","v":0}]
["TS-Record",null,null,"O",2,"Pass the test where the requester’s order identifier included in the record. \nElse, mark the test as N/A.\n","The software system records the requester's order identifier.","TBD",null,0,{"$f":"IF(AND(BGCol(D28)=48,H28=\"N/A\"),1,0)","v":0}]
["TS-Record","TC-PathProc-14","026628 [NEHTA-2214:2016]\nThe software SHOULD record the reversal of a decision by a diagnostic service provider to not upload a diagnostic report. \nThe information recorded SHOULD include the report or document identifier, the requester's order identifier and the date and time of the reversal of the decision.\n","O",1,"Pass 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.","TBD",null,0,{"$f":"IF(AND(BGCol(D29)=48,H29=\"N/A\"),1,0)","v":0}]
["TS-Record",null,null,"O",2,"Pass the test where the report or document identifier, requester's order identifier 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 report or document identifier, requester's order identifier 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-PathProc-15.1","026629 [NEHTA-2214:2016]\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 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}]
["TS-Record",null,null,"O",2,"Pass the test where the report or document identifier, 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-PathProc-15.2","026629 [NEHTA-2214:2016]\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 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\n","The software system records the report or document identifier, the requester’s order identifier, the original (if available) and updated value of the withdrawal of consent indicator and the date and time the change of consent.\n","TBD",null,0,{"$f":"IF(AND(BGCol(D33)=48,H33=\"N/A\"),1,0)","v":0}]
["TS-Record",null,null,"O",2,"Pass the test where the report or document identifier, 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 are included in the record. \nElse, mark the test as N/A.\n","The software system records the report or document identifier, 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.","TBD",null,0,{"$f":"IF(AND(BGCol(D34)=48,H34=\"N/A\"),1,0)","v":0}]
["TS-Record","TC-PathProc-16","025083 [NEHTA-2214:2016]\nThe software SHOULD have the capability to retrieve and display the 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.\n","O",1,"Pass the test where the software system can retrieve and display records of:\na) a failure to create or upload a diagnostic report; and\nb) a decision, and reversal of a decision, to not upload a diagnostic report; and\nc) 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":20}]
[null,null,null,null,null,null,null,"N/A","Tests Passed or N/A",{"$f":"COUNTIF(J8:J35,\"1\")","v":1}]
[null,null,null,null,null,null,null,"Pass","%Passed or N/A",{"$f":"SUM(J39/J37)","v":4.7619047619047616E-2}]

{"sheet":"Process models","index":9,"n_rows":201,"n_cols":6,"rows_kept":201,"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 Pathology Report"]
[null,"The process models used in this Path 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.\nThe tables in this worksheet list process requirements, that are conformance requirements, related to the following business processes:\n"]
[null,null,"• Author a new Pathology Report\n• Store or upload to the My Health Record system\n• Change consent setting\n• Supersede a Pathology Report\n• Remove a Pathology Report\n• Retrieve records\n"]
[null,"Conformance requirements that are solely related to the content of a Pathology 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 [NEHTA-1850:2015]\n2. eHealth Pathology Report - My Health Record Conformance Profile v1.1 [NEHTA-2214:2016]\n3. PCEHR Connecting Systems - Conformance Requirements [NEHTA-1297:2012]\n"]
[null,"In addition, generic process models for PCEHR Connecting Systems are listed in PCEHR Connecting Systems - Use Cases [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-PathProc\" are listed in the FS-PathProc feature set within this conformance test specification.\n2.  \"TC-PathDoc\" are listed in the FS-PathDoc 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]."]
["THIS HEADER CAN BE COLLAPSED BY CLICKING THE \"-\" SYMBOL ON THE LEFT."]
[null,"A. Author a new Pathology 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)","The information for the request of the 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 withdrawal 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 request explicitly states that the healthcare individual has consented to their Pathology Reports being uploaded to the My Health Record system then the software records \"No withdrawn consent\".\n\nIf the request had no indication of consent but it is found that the My Health Record system indicates the healthcare individual has a My Health Record system (using a doesPCEHRexists web service call) then the software records \"No withdrawn consent\".                                                                                                                                ","eHealth Pathology Report - My Health Record Conformance Profile [NEHTA-2214:2016]:\n026757-\"Withdrawn consent\" indicator\n026629-Record the original and changed withdrawal of consent indicator values\n026763 - Invoke doesPCEHRexist web service\n","TC-PathProc-05 (026757)\nTC-PathProc-15.1 (026629)\nTC-PathProc-09 (026763)"]
[null,"A3","Record \"Withdrawn consent\" (task)","If the request explicitly states that the healthcare individual has withdrawn their consent to their Pathology Reports being uploaded to the My Health Record system then the software records \"Withdrawn consent\".\n\n","eHealth Pathology Report - My Health Record Conformance Profile [NEHTA-2214:2016]:\n026757-\"Withdrawn consent\" indicator.\n026629-Record the original and changed withdrawal of consent indicator values","TC-PathProc-05 (026757)\nTC-PathProc-15.1 (026629)"]
[null,"A4","UC.CIS.001 Check if an advertised digital health record system 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 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. If 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.","eHealth Pathology Report - My Health Record Conformance Profile [NEHTA-2214:2016]:\n024885 (varies 019100) Healthcare identifier received via electronic request does not require revalidation\n024972 Access to the Healthcare Identifiers Service\n026763 Invoking doesPCEHRexist web service\n\nAlso see the requirements for PCEHR connecting systems for UC.CIS.001. Check if an advertised PCEHR exists.\n","TC-PathProc-03 (024885)\nTC-PathProc-04 (024972)\nTC-PathProc-09 (026763)\n\nTest 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\" and a health record in the My Health Record system for the healthcare individual exists, then the software records \"digital health record exists\". If 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.\n","eHealth Pathology Report - My Health Record Conformance Profile [NEHTA-2214:2016]:\n026757 - Store '\"Withdrawn consent\" indicator\n026763 - Invoke doesPCEHRexist web service\n026629 Record the original and changed withdrawal of consent indicator values","TC-PathProc-05 (026757)\nTC-PathProc-09 (026763)\nTC-PathProc-15.1 (026629)"]
[null,"A6","Perform diagnostic tests (task)","The pathology 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 Pathology Reports; otherwise one Pathology 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 Pathology Report (task)","The Pathology 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, the software records \"digital health record exists\".\n\nAdditionally, if the request for diagnostic services explicitly states the indication/withdrawal of consent for Pathology Reports to be uploaded to the My Health Record system, then the software also records either \"No withdrawn consent\" or \"Withdrawn consent\" respectively.  \n\nHowever, if the request for diagnostic services had no indication of consent, then the software only records \"digital health record exists\".  \n","026763 - Invoke doesPCEHRexist web service","TC-PathProc-09 (026763)"]
[null,"A10","digital health record exists? (decision)","If the request received by the Authoring 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 Authoring system has no indication of consent, then the doesPCEHRexists web service call is made. If the doesPCEHRexists returns \"true\", then decision (A10) is \"true\", otherwise decision (A10) is \"false\".","026763 - Invoke doesPCEHRexist web service","TC-PathProc-09 (026763)"]
[null,"B","Store or upload to the My Health Record system (subprocess)\n","Storing and uploading a Pathology Report is documented as process B.","Requirements are listed in the process requirements of the subprocess\n","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 Pathology Report to the My Health Record system, otherwise the consent setting is \"Withdrawn consent\" and the Pathology 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 Pathology Report for a future upload (task)","If the software has recorded the consent setting as \"Withdrawn consent\" then the Pathology Report  is stored for future use, in the event that the consent setting is revised.\n","eHealth Pathology Report - My Health Record Conformance Profile [NEHTA-2214:2016]: \n026761 Preventing uploading when consent is withdrawn","TC-PathProc-07 (026761)"]
[null,"B3","Prepare for upload (task)","The software prepares the Pathology 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 Pathology Report - My Health Record Conformance Profile [NEHTA-2214:2016]:\n025065 When the document author is not one person\n025066 Multiple reporting pathologists\n023436 Identifier for document author\n023648 Identifier for reporting pathologist\n\nClinical Documents - Common Conformance Profile [NEHTA-1850:2015]:\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","TC-PathDoc-07 (025065)\nTC-PathDoc-08 (025066)\nTC-PathDoc-11 (023436)\nTC-PathDoc-12 (023648)"]
[null,"B11","Ready to upload? (decision)","If the software has successfully created a CDA package containing the Pathology Report and has obtained a valid set of healthcare identifiers then the Pathology Report is ready to be uploaded to the My Health Record system.","No testable process requirements.","No testable test cases."]
[null,"B4","New or replacement Pathology Report? (decision)","Different tasks are performed depending on whether the Pathology 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 [NEHTA-1299:2012], is applied for uploading the Pathology Report to the My Health Record system.\n\nThe possible outcomes are that the Pathology 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 Pathology 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 PCEHR Connecting Systems - Use Cases v1.1[NEHTA-1298:2012].\n\n","eHealth Pathology Report - My Health Record Conformance Profile [NEHTA-2214:2016]:\n026762 Uploading when a digital health record exists\nUC.CIS.201 Upload a Clinical Document\n","TC-PathProc-03 (024885)  \nTC-PathProc-04 (024972)\nTC-PathProc-08 (026762)\nTest cases for UC.CIS.201"]
[null,"B6","Record upload failure (task)","If the Pathology Report could not be uploaded to the My Health Record system, then the upload failure is recorded.\n","eHealth Pathology Report - My Health Record Conformance Profile [NEHTA-2214:2016]:\n026625 Record a failure to upload a diagnostic report\n","TC-PathProc-11 (026625)"]
[null,"B7","Withhold the report (task)","The Pathology Report document is withheld from being uploaded to the My Health Record system, due to a decision by a healthcare provider. \n","eHealth Pathology Report - My Health Record Conformance Profile [NEHTA-2214:2016]:\n026627 Record upload failure\n","TC-PathProc-13 (026627)"]
[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 Pathology Report.\n","eHealth Pathology Report - My Health Record Conformance Profile [NEHTA-2214:2016]:\n026628 Record the reversal of a diagnostic service provider's decision to not upload a diagnostic report\n","TC-PathProc-14 (026628)"]
[null,"B9","UC.CIS.202 Supersede a clinical document (subprocess)","Use case documented in  PCEHR Connecting Systems - Conformance Test Specification v1.6 [NEHTA-1299:2012], is applied for superseding the existing Pathology Report in the My Health Record system.\n\nThe possible outcomes are that the replacement Pathology 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 PCEHR Connecting Systems - Use Cases v1.1[NEHTA-1298:2012].\n\n\n","eHealth Pathology Report - My Health Record Conformance Profile [NEHTA-2214:2016]: \nUC.CIS.202 - Supersede a clinical document","Test 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 Pathology Report cannot be uploaded to a My Health Record system due to a failure to obtain a valid healthcare identifier then this failure is recorded.\n","eHealth Pathology Report - My Health Record Conformance Profile [NEHTA-2214:2016]:\n026626  Record information on validity of healthcare identifiers\n","TC-PathProc-12 (026626)"]
[null,"B12","Record \"Document uploaded\" (task)","If a Pathology Report is uploaded to the My Health Record system, then the software records \"Document uploaded\".\n","eHealth Pathology Report - My Health Record Conformance Profile [NEHTA-2214:2016]:\n026760  \"Document uploaded\" indicator.\n\n","TC-PathProc-06 (026760)\n\n"]
[null,"B13","Record \"Document not uploaded\" (task)","If a Pathology Report cannot be uploaded to a My Health Record system, then the software records \"Document not uploaded\".","eHealth Pathology Report - My Health Record Conformance Profile [NEHTA-2214:2016]:\n026760 \"Document uploaded\" indicator\n","TC-PathProc-06 (026760)\n\n"]
[null,"B14","Upload sucessful? (Decision)","Different tasks are performed depending on outcome of the attempt made to upload the Pathology Report document to the My Health Record system.\n\nThe possible outcomes from this decision are:\n1. The upload of the Pathology Report document to the My Health Record system is successful .\n2. The upload of the Pathology Report document to the My Health Record system has resulted in a failure.\n3. The healthcare provider has withheld the Pathology Report document from being uploading 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 Pathology Reports being uploaded to the My Health Record system, then the software examines the previously recorded consent settings and determines if it 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\".\n","eHealth Pathology Report - My Health Record Conformance Profile [NEHTA-2214:2016]: \n026766 Changing \"Withdrawn consent\" indicator","TC-PathProc-10 (026766)"]
[null,"D2","Record \"No withdrawn consent\" (task)","The consent setting recorded by the software is changed to \"No withdrawn consent\".\n\n","eHealth Pathology Report - My Health Record Conformance Profile [NEHTA-2214:2016]: \n026757 - Store '\"Withdrawn consent\" indicator.\n026762 - Uploading when digital health record exists.\n026629 Record the original and changed withdrawal of consent indicator values\n","\nTC-PathProc-05 (026757)\nTC-PathProc-08 (026762) \nTC-PathProc-15.2 (026629)"]
[null,"D3","Any stored Pathology Reports? (decision)","The software determines if there are any previously stored Pathology Reports (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 Pathology Report (task)","If there are any previously stored Pathology Reports then it is possible that the store includes more than one version of a report (see the Supersede a Pathology Report process). The most recent version of a Pathology Report is selected for uploading to the My Health Record system (i.e. any older versions are not selected for upload).\n","No testable process requirements.","No testable test cases."]
[" ","B","Store or Upload a Pathology Report (subprocess)","Storing and uploading a Pathology Report is documented as process B.","No testable process requirements.","No testable test cases."]
[null,"D5","May consent be withdrawn? (decision)","Consent cannot be withdrawn if any Pathology 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 \"Withdrawn consent\". \n","eHealth Pathology Report - My Health Record Conformance Profile [NEHTA-2214:2016]: \n026766 Changing \"Withdrawn consent\" indicator.\n026629 Record the original and changed withdrawal of consent indicator values, \n","TC-PathProc-05 (026757)\n TC-PathProc-15.2 (026629)"]
[null,"D8","Consent provided? (Decision)","If the indication of consent states that the healthcare individual has consented to Pathology 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 Pathology Reports to the My Health Record system, then the decision is set to \"Consent withdrawn\".\n","No testable process requirements.","No testable test cases."]
[]
[]
[null,"E. Supersede a Pathology Report (business process)"]
[null,"The process commences whenever the diagnostic service provider needs to supersede a previously authored report with a replacement report."]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[null,"#","PROCESS ITEM (AND TYPE)","DESCRIPTION","PROCESS REQUIREMENTS","TEST CASES"]
[null,"E1","Create a replacement Pathology Report (task)","A Pathology Report is created to replace a previously authored Pathology 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 Pathology 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 Pathology Report may have been uploaded to the My Health Record system or may be in storage for upload at a future date.","eHealth Pathology Report - My Health Record Conformance Profile [NEHTA-2214:2016]: \n025065 When the document author is not one person\n025066 Multiple reporting pathologists\n023436 Identifier for document author\n023648 Identifier for reporting pathologist\n\n\nClinical Documents - Common Conformance Profile [NEHTA-1850:2015]: \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","TC-PathDoc-07 (025065)\nTC-PathDoc-08 (025066)\nTC-PathDoc-11 (023436)\nTC-PathDoc-12 (023648)"]
[null,"E2","Digital health record exists? (decision)","If the software has recorded the consent as either \"No withdrawn consent\" or \"Withdrawn consent\", that indicates that the healthcare individual's digital health record exists in the My Health Record system, and the decision is \"true\". \n\nIf there is no indication of consent in the request received by the Authoring system, then the doesPCEHRexists web service call is made, and if it returns \"true\", then decision (E2) is \"true\",  otherwise 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)","The Pathology Report is reviewed and a decision is made to upload or not to upload the report to the My Health Record system. This is documented as process B.\n","See the requirements listed in the description of the subprocess.","No testable test cases."]
[]
[]
[null,"F. Remove a Pathology Report (business process)"]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[null,"#","PROCESS ITEM (AND TYPE)","DESCRIPTION","PROCESS REQUIREMENTS","TEST CASES"]
[null,"F3","Select a document to remove (task)","The Pathology Report to be removed is selected.","No testable process requirements.","No testable test cases."]
[null,"F1","Obtain/validate healthcare identifiers (task)","Healthcare identifiers may be obtained from:\na) manual input, or\nb) the HI Service, or \nc) the diagnostic service request\nThey 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)","The Pathology Report to remove is selected.","eHealth Pathology Report - My Health Record Conformance Profile [NEHTA-2214:2016]: \n024885 (varies PCEHR connecting systems requirement 019100) Healthcare identifier received via electronic request does not require revalidation\n024972 Access to the Healthcare Identifiers Service\nUC.CIS.203 Remove a Clinical Document\n","TC-PathProc-03 (024885)\nTC-PathProc-04 (024972)\nTest cases for UC.CIS.203 (note that requirement 024885 overrides PCEHR connecting systems requirement 019100)\n"]
[]
[]
[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 Pathology Report was not uploaded to the My Health Record system.\n","eHealth Pathology Report - My Health Record Conformance Profile [NEHTA-2214:2016]: \n025083 Retrievable records","TC-PathProc-16 (025083)"]

{"sheet":"TSR","index":10,"n_rows":30,"n_cols":10,"rows_kept":30,"cut":false,"hidden":false,"merged":[[24,1,24,5],[7,1,7,2],[1,2,1,3],[3,1,3,2],[4,1,4,2],[5,1,5,2],[6,1,6,2],[8,1,8,2],[9,1,9,2],[10,1,10,2],[11,1,11,2],[16,1,16,5]]}
[null,"Australian Digital Health Agency"]
[null,null,"TEST SUMMARY REPORT\n"]
[]
[null,"Software developer organisation:",null,"Please complete"]
[null,"Software name:",null,"Please complete"]
[null,"Software version:",null,"Please complete"]
[null,"Software description:",null,"Please complete"]
[null,"Testing location address:",null,"Please complete"]
[null,"Date(s) of testing:",null,"Please complete"]
[null,"Name of person(s) conducting tests:",null,"Please complete"]
[null,"Operating System/Environment Configuration (name and version)",null,"Optional."]
[null,"Additional software tools and versions used which are not subject to testing  (e.g. web browser)",null,"Optional."]
[null,null,null,null,null,null,null,null," "]
[]
[]
[]
[null,"THIS SECTION DOES NOT NEED TO BE FILLED IN - IT WILL BE AUTOMATICALLY CALCULATED."]
[null,null,"Scenario Worksheet","  Total % Tests Passed or N/A","Number of Scenarios","Scenarios Complete"]
[null,1,"TP-NewDoc",{"$f":"'TP-NewDoc'!F409","v":0},{"$f":"'TP-NewDoc'!C419","v":9},{"$f":"'TP-NewDoc'!C417","v":0},null,null,null," "]
[null,2,"TP-Consent",{"$f":"'TP-Consent'!F141","v":0},{"$f":"'TP-Consent'!C146","v":4},{"$f":"'TP-Consent'!C144","v":0}]
[null,3,"TP-Supersede",{"$f":"'TP-Supersede'!F133","v":0},{"$f":"'TP-Supersede'!C137","v":3},{"$f":"'TP-Supersede'!C135","v":0}]
[null,4,"TP-Remove",{"$f":"'TP-Remove'!F28","v":0},{"$f":"'TP-Remove'!C30","v":1},{"$f":"'TP-Remove'!C28","v":0}]
[null,5,"TP-Path",{"$f":"'TP-Path'!F146","v":0},{"$f":"'TP-Path'!C151","v":4},{"$f":"'TP-Path'!C149","v":0}]
[]
[null,"THIS SECTION DOES NOT NEED TO BE FILLED IN - IT WILL BE AUTOMATICALLY CALCULATED USING A MACRO. PRESS <F9> IF YOU HAVE MACROS DISABLED."]
[null,null,"Test Case Worksheet ","% Success Rate","Number of Tests","Number of \"N/A\" test results for mandatory tests"]
[null,1,"FS-PathDoc",{"$f":"'FS-PathDoc '!J31","v":0.11764705882352941},{"$f":"'FS-PathDoc '!$J28","v":17},{"$f":"SUM('FS-PathDoc '!K:K)","v":0}]
[null,2,"FS-PathProc",{"$f":"'FS-PathProc'!J40","v":4.7619047619047616E-2},{"$f":"'FS-PathProc'!J37","v":21},{"$f":"SUM('FS-PathProc'!K:K)","v":1}]
[]
[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":"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."}]

{"sheet":"Traceability","index":11,"n_rows":56,"n_cols":32,"rows_kept":56,"cut":false,"hidden":false,"merged":[[2,2,10,2],[12,2,13,2],[14,2,16,2],[19,2,33,2],[34,2,54,2]]}
[]
[null,"Traceability Reference","Related Specification","Conformance Requirement","Test Cases","Feature Set & Test Case Reference","Test Case Exists?","Priority","Test Steps","TP-Path-01.1","TP-Path-02.1","TP-Path-02.2","TP-Path-03.1","TP-Path-04.1","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","TS-Consent-04","TP-Supersede-01","TP-Supersede-02","TP-Supersede-03","TP-Remove-01","Notes"]
[null,"TR-PATH-01","NEHTA-2214:2016 eHealth Pathology Report - My Health Record Conformance Profile v1.1","23435 - 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-PathDoc-01","FSPathDoc","P","M",1,null,null,null,null,"P","P","P","P","P","P",null,null,null,"P",null,null,"P",null,"P","P"]
[null,"TR-PATH-02",null,"23473 - Check CDA document has a reference to only one PDF attachment that is the original diagnostic report.","TC-PathDoc-02","FSPathDoc","P","M",2,"P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-PATH03",null,"23651 - The values of the diagnostic report data elements that are present in both the CDA document and the PDF document SHALL be consistent.","TC-PathDoc-03","FSPathDoc","P","M",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-PATH-04",null,"24692 - Various Pathology Report Results and Documents not nullFlavor.","TC-PathDoc-04","FSPathDoc","P","M",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-PATH-05",null,"26615 - Narrative and section title.","TC-PathDoc-05","FSPathDoc","P","C",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-PATH-06",null,"24798 - Sort test results.","TC-PathDoc-06","FSPathDoc","P","O",1,"P","P","P","P",null,"P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-PATH-07",null,"25065 - Mandatory Document Author Values used.","TC-PathDoc-07","FSPathDoc","P","C",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-PATH-08",null,"25066 - Mandatory Reporting Pathologist Values used.","TC-PathDoc-08","FSPathDoc","P","C",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-PATH-09",null,"24732 - References in CDA Package.","TC-PathDoc-09","FSPathDoc","P","O",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-PATH-10","NEHTA-1413:2014 Pathology Report - Structured Content Specification v1.0","2.25 - Report Date Time (Effective Period)","TC-PathDoc-10","FSPathDoc","P","M",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-PATH-11","NEHTA-2214:2016 eHealth Pathology Report - My Health Record Conformance Profile v1.1","23436 - Document Author > Participant > Entity Identifier value SHALL be an HPI-I.","TC-PathDoc-11","FSPathDoc","P","C",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-PATH-12",null,"23648 - Reporting Pathologist  > Participant > Entity Identifier SHALL be an HPI-I.","TC-PathDoc-12","FSPathDoc","P","C",2,"P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-PATH-13","NEHTA-1413:2014 Pathology Report - Structured Content Specification v1.0","3.11 - Collection DateTime","TC-PathDoc-13","FSPathDoc","P","M",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-PATH-14",null,"3.14 - Observation DateTime","TC-PathDoc-14","FSPathDoc","P","M",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-PATH-15",null,"2.20 - Document Target","TC-PathDoc-15","FSPathDoc","P","C",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P",null,"P","P",null,"P","P","P"]
[null,"TR-PATH-16","NEHTA-2214:2016 eHealth Pathology Report - My Health Record Conformance Profile v1.1","23456 - Clinical document producer is neither a registered consumer portal nor registered provider portal.","TC-PathProc-01","FS PathProc","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-PATH-17","NEHTA-1850:2015 Clinical Documents - Common Conformance Profile v1.6","23706 - 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-PathProc-02","FS PathProc","P","M",1,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P"]
[null,"TR-PATH-18","NEHTA-2214:2016 eHealth Pathology Report - My Health Record Conformance Profile v1.1","24885 - Healthcare software access to the Healthcare Identifiers Service","TC-PathProc-03","FS PathProc","O","-",0]
[null,"TR-PATH-19",null,"24972 - Healthcare software access to the Healthcare Identifiers Service","TC-PathProc-04","FS PathProc","O","-",0]
[null,"TR-PATH-20",null,"26757 - \"Withdrawn consent\" indicator is recorded","TC-PathProc-05","FS PathProc","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-PATH-21",null,"26760 - \"Document uploaded\" indicator is recorded","TC-PathProc-06","FS PathProc","P","M",1,null,null,null,null,"P","P","P","P","P","P","P",null,null,"P",null,null,"P",null,"P","P","P"]
[null,"TR-PATH-22",null,"26761 - The Pathology Report is not uploaded to the My Health Record system. A copy of the Pathology Report is saved to the Authoring System.","TC-PathProc-07","FS PathProc","P","M",1,null,null,null,null,"P",null,null,null,null,null,"P","P",null,null,null,null,null,null,null,null,"P"]
[null,"TR-PATH-23",null,"26762 - The Authoring system permits the report to be uploaded to the My Health Record system","TC-PathProc-08","FS PathProc","P","M",1,null,null,null,null,"P",null,"P"]
[null,"TR-PATH-24",null,"226763 - Invoke doesPCEHRexist web service","TC-PathProc-09","FS PathProc","P","M",1,null,null,null,null,null,null,"P",null,null,null,null,"P","P"]
[null,"TR-PATH-25",null,"26766 - Changing \"Withdrawn consent\" indicator","TC-PathProc-10","FS PathProc","P","M",1,null,null,null,null,"P",null,null,null,null,null,null,null,null,null,"P",null,"P","P"]
[null,"TR-PATH-26",null,"26625 - Record upload failure.","TC-PathProc-11","FS PathProc","P","M",2,null,null,null,null,"P",null,null,"P"]
[null,"TR-PATH-27",null,"26626 - Record information on the validity of the healthcare identifiers.","TC-PathProc-12","FS PathProc","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"]
[null,"TR-PATH-28",null,"26627 - Record a decision to not upload a Pathology Report.","TC-PathProc-13","FS PathProc","P","M",2,null,null,null,null,"P",null,null,null,"P",null,null,null,null,null,null,null,null,null,null,"P"]
[null,"TR-PATH-29",null,"26628 - Record the reversal of a decision by a diagnostic service provider to not upload a Pathology Report","TC-PathProc-14","FS PathProc","P","C",2,null,null,null,null,null,null,null,null,"P",null,null,null,null,null,null,null,null,null,null,"P"]
[null,"TR-PATH-30",null,"26629 - Record the original and changed withdrawal of consent indicator values","TC-PathProc-15.1","FS PathProc","P","C",2,null,null,null,null,null,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P"]
[null,"TR-PATH-31",null,"26629 - Record the original withdrawal of consent indicator values ","TC-PathProc-15.2","FS PathProc","P","C",2,null,null,null,null,null,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P"]
[null,"TR-PATH-32",null,"25083 - Retrievable records","TC-PathProc-16","FS PathProc","P","O",1,null,null,null,null,null,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P"]
[null,"TR-PATH-33","NEHTA-1299:2012 PCEHR Connecting Systems - Conformance Test Specification v1.6","019100 (UC.CIS.001) -  CIS uses IHI","PCEHR_CIS_019100","UC.CIS.001","-","-","-",null,null,null,null,null,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P"]
[null,"TR-PATH-34",null,"019378 (UC.CIS.001) - CIS Audit","PCEHR_CIS_019378","UC.CIS.001","-","-","-",null,null,null,null,null,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P"]
[null,"TR-PATH-35",null,"019100 (UC.CIS.201) - CIS uses IHI","PCEHR_CIS_019100","UC.CIS.201","-","-","-",null,null,null,null,null,"P","P","P","P","P","P","P","P","P",null,null,null,null,null,null,null,"P"]
[null,"TR-PATH-36",null,"019429 (UC.CIS.201) - CIS uses HPI-I","PCEHR_CIS_019429","UC.CIS.201","-","-","-",null,null,null,null,null,"P","P","P","P","P","P","P","P","P"]
[null,"TR-PATH-37",null,"019042 (UC.CIS.201) - Withdraw Consent","PCEHR_CIS_019042","UC.CIS.201","-","-","-",null,null,null,null,null,"P","P","P","P","P","P","P","P","P"]
[null,"TR-PATH-38",null,"017842a (UC.CIS.201) - CIS Identifies Uploads","PCEHR_CIS_017842a","UC.CIS.201","-","-","-",null,null,null,null,null,"P","P",null,"P",null,null,null,null,"P",null,null,"P"]
[null,"TR-PATH-39",null,"017841a (UC.CIS.201) - CIS Retains Clinical info","PCEHR_CIS_017841a","UC.CIS.201","-","-","-",null,null,null,null,null,"P","P","P","P",null,null,null,null,"P",null,null,"P"]
[null,"TR-PATH-40",null,"017839 (UC.CIS.201) - Clinical Document explicit command","PCEHR_CIS_017839","UC.CIS.201","-","-","-",null,null,null,null,null,"P","P","P","P",null,null,null,null,"P",null,null,"P"]
[null,"TR-PATH-41",null,"019378 (UC.CIS.201) - CIS Audit","PCEHR_CIS_019378","UC.CIS.201","-","-","-",null,null,null,null,null,"P","P","P","P","P","P","P","P","P"]
[null,"TR-PATH-42",null,"019100 (UC.CIS.202) - CIS uses IHI","PCEHR_CIS_019100","UC.CIS.202","-","-","-"]
[null,"TR-PATH-43",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,null,null,null,null,null,null,"P","P","P"]
[null,"TR-PATH-44",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,null,null,null,null,null,null,null,null,null,"P","P","P"]
[null,"TR-PATH-45",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,"P",null,null,null,null,"P","P"]
[null,"TR-PATH-46",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,"P",null,null,null,null,"P","P","P"]
[null,"TR-PATH-47",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,"P",null,null,null,null,"P","P","P"]
[null,"TR-PATH-48",null,"019378 (UC.CIS.202) - CIS Audit","PCEHR_CIS_019378","UC.CIS.202","-","-","-",null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,"P","P","P"]
[null,"TR-PATH-49",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,"P","P","P"]
[null,"TR-PATH-50",null,"019100 (UC.CIS.203)  - CIS uses IHI","PCEHR_CIS_019100","UC.CIS.203","-","-","-",null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,"P"]
[null,"TR-PATH-51",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,"P"]
[null,"TR-PATH-52",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,"P"]
[null,"TR-PATH-53",null,"019378 (UC.CIS.203) - CIS Audit","PCEHR_CIS_019378","UC.CIS.203","-","-","-"]
[null,"TR-PATH-54","DH-2209:2016 Conformance Test Specification for Authoring systems v1.0","Perform all the mandatory and applicable conditional tests in the Conformance Test Specification for Authoring Systems.","All the mandatory and applicable conditional tests","FS-Doc, FS-Narr, Fs-Types, FS-Auth","-","-","-","P","P",null,"P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P","P"]

{"sheet":"References","index":12,"n_rows":16,"n_cols":5,"rows_kept":16,"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-12","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-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-1412:2014","2014-12-31","NEHTA-1412:2014 Pathology Report - CDA Implementation Guide v1.0"]
[null,null,"NEHTA-1413:2014","2014-12-31","NEHTA-1413:2014 Pathology Report - Structured Content Specification v1.0"]
[null,null,"NEHTA-1732:2014","2014-10-31","NEHTA-1732:2014 Use of HIs in Health Software Systems - Conformance Requirements v3.1"]
[null,null,"NEHTA-1850:2015","2015-04-10","NEHTA-1850:2015 Clinical Documents - Common Conformance Profile v1.6"]
[null,null,"NEHTA-2214:2016","2016-03-10","NEHTA-2214:2016 eHealth Pathology 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"]