{"text_format":"1","workbook":"xlsx","n_sheets":12,"sheets":["Title","Data values","Intro","TP-NewDoc","TP-Supersede","TP-Remove","FS-PSMLProc","FS-PSMLDoc","Process models","TSR","Traceability","References"],"not_rendered":{"charts":0,"images":6,"macros":1,"external_links":4,"defined_names":13,"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":"Title","index":0,"n_rows":27,"n_cols":4,"rows_kept":27,"cut":false,"hidden":false,"merged":[[23,1,23,3],[24,1,24,3],[25,1,25,3],[26,1,26,3],[3,1,3,3],[19,1,19,3],[20,1,20,3],[21,1,21,3],[22,1,22,3]]}
[null," "]
[]
[]
[null,"Pharmacist Shared Medicines List"]
[null,"Conformance Test Specification"]
[]
[null,"Version 1.1.1"]
[null,"2020-03-31"]
[null,"OFFICIAL"]
[null,"Approved for external use"]
[null,"Document ID: DH-3018:2020"]
[]
[]
[null,"Product version history"]
[null,"Version","Date","Comments"]
[null,1,"2018-09-28","Initial release."]
[null,"1.1","2018-12-31","Named changed to PSML."]
[null,"1.2","2020-03-31","HPI-I relaxation updated."]
[]
[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,"Disclaimer"]
[null,"The Australian Digital Health Agency (“the Agency”) makes the information and other material (“Information”) in this document available in good faith but without any representation or warranty as to its accuracy or completeness. The Agency cannot accept any responsibility for the consequences of any use of the Information. As the Information is of a general nature only, it is up to any person using or relying on the Information to ensure that it is accurate, complete and suitable for the circumstances of its use."]
[null,"Document control"]
[null,"This document is maintained in electronic form and is uncontrolled in printed form. It is the responsibility of the user to verify that this copy is the latest revision."]
[null,"Copyright © 2020 Australian Digital Health Agency"]
[null,"This document contains information which is protected by copyright. All Rights Reserved. No part of this work may be reproduced or used in any form or by any means—graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systems—without the permission of the Australian Digital Health Agency. All copies of this document must include the copyright and other information contained on this page."]

{"sheet":"Data values","index":1,"n_rows":22,"n_cols":4,"rows_kept":22,"cut":false,"hidden":true,"merged":[]}
["Document status values",null,"Draft versions","Protective marking"]
["Draft for internal review",null,null,"Select protective marking"]
["Draft for external review",null,"Draft version 001","OFFICIAL"]
["Awaiting approval for external use",null,"Draft version 002","OFFICIAL: Sensitive"]
["Approved for limited external trial use",null,"Draft version 003"]
["Approved for external use",null,"Draft version 004"]
[null,null,"Draft version 005"]
[null,null,"Draft version 006"]
[null,null,"Draft version 007"]
[null,null,"Draft version 008"]
[null,null,"Draft version 009"]
[null,null,"Draft version 010"]
[null,null,"Draft version 011"]
[null,null,"Draft version 012"]
[null,null,"Draft version 013"]
[null,null,"Draft version 014"]
[null,null,"Draft version 015"]
[null,null,"Draft version 016"]
[null,null,"Draft version 017"]
[null,null,"Draft version 018"]
[null,null,"Draft version 019"]
[null,null,"Draft version 020"]

{"sheet":"Intro","index":2,"n_rows":118,"n_cols":5,"rows_kept":118,"cut":false,"hidden":false,"merged":[[2,1,2,2],[12,1,12,2],[14,1,14,2],[15,1,15,2],[16,1,16,2],[26,1,26,2],[77,1,77,2],[95,1,95,2],[27,1,27,2],[57,1,57,2],[28,1,28,2],[41,1,41,2]]}
[null,null,null,"Document information"]
[null,"Introduction",null,"Owner:","Head of Product Delivery"]
[null,"The information in this section will:\na.  help you determine the test materials needed to apply for Pharmacist Shared Medicines List - this will be based on the user category you fall into.\nb.  give you an overview of the individual worksheets and their structure i.e. what the columns mean and how to record the Test Results (i.e. Pass, Fail etc.).\n\nThis conformance test specification uses software testing concepts and terminology defined in these standards:\nISO/IEC/IEEE 29119-1 Software and systems engineering – Software testing – Part 1: Concepts and definitions\nISO/IEC/IEEE 29119-3 Software and systems engineering – Software testing – Part 3: Test documentation\n",null,"Contact for enquiries:","Australian Digital Health Agency Help Centre\nt:  1300 901 001\ne:  help@digitalhealth.gov.au"]
[]
[null,"Table of contents"]
[1,"What test material do I need?"]
[2,"Worksheet Names"]
[3,"Worksheet Structure for Test Procedures"]
[4,"Worksheet structure for Feature Sets"]
[5,"Acronyms"]
[]
[1,"What test material do I need?"]
[null,"The type of user you are will determine which tests you need to apply.  This section defines the two possible target audiences of this test material, and gives instructions on which tests cases need to be applied. "]
[null,"Table 1: What test material do I need?","`"]
[null,"USER 1:  I want to test the Pharmacist Shared Medicines List's created by my Software System."]
[null,"In this scenario, you have developed an Software System which creates Pharmacist Shared Medicines Lists, and you want to test the conformance of the Pharmacist Shared Medicines Lists produced by the system against the eHealth requirements.\n"]
[null,"Tests to apply to the Pharmacist Shared Medicines List Software System:"]
[null,null,"From the Pharmacist Shared Medicines List Conformance Test Specification (this specification):"]
[null,null,"TP-NewDoc"]
[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,null,"Test cases commencing with the identifier  'PKG'  are from the Clinical Documents - Conformance Test Specification for CDA® Packaging v1.5 [NEHTA-2065:2015]:"]
[]
[]
[null,"USER 2:  I want to test Pharmacist Shared Medicines List clinical documents created by another Software System."]
[null,"In this scenario, you have a Pharmacist Shared Medicines List document; but no knowledge of the Software System which produced it and you want to test the document’s conformance against the eHealth requirements. "]
[null,"Tests to apply to the Pharmacist Shared Medicines Lists clinical documents:"]
[null,null,"From the Pharmacist Shared Medicines List Conformance Test Specification(this specification):"]
[null,null,"FS-PCMLDoc"]
[]
[null,null,"From the Authoring Systems Conformance Test Specification [DH-2209:2017]:"]
[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: Worsheet Names","`"]
[null,"WORKSHEET NAME","FEATURE SET and PURPOSE"]
[null,"TP-NewDoc","Full name: Author a new Pharmacist Shared Medicines List function\nObjective: To assess the conformance of a Pharmacist Shared Medicines List Software System to the requirements that apply to the process of creating a new Pharmacist Shared Medicines List.\n"]
[null,"TP-Supersede","Full name: Supersede a Pharmacist Shared Medicines List function\nObjective: To assess the conformance of a Pharmacist Shared Medicines List authoring system to the requirements that apply to the process of superseding a Pharmacist Shared Medicines List that was uploaded to the My Health Record system.\n"]
[null,"TP-Remove","Full name: Remove a Pharmacist Shared Medicines List function\nObjective: To assess the conformance of a Pharmacist Shared Medicines List Software System to the requirements that apply to the process of removing a Pharmacist Shared Medicines List from the My Health Record system."]
[null,"FS-PCMLProc","Full name: business processes for the Software System\nObjective: To assess the conformance to the process requirements for an Software System that creates Pharmacist Shared Medicines Lists. These are requirements for creating a Pharmacist Shared Medicines Lists clinical document.\n"]
[null,"FS-PCMLDoc","Full name: Pharmacist Shared Medicines List clinical document\nObjective: To assess the conformance of a Pharmacist Shared Medicines List clinical document to the requirements for documents of that type.\n"]
[null,"Process models","Lists process requirements, which are conformance requirements related to the following business processes:\n• Author a new Pharmacist Shared Medicines List\n• Remove a Pharmacist Shared Medicines List\n\n"]
[null,"TSR","Full name: Test Summary Report\nObjective: This worksheet has 2 parts:\nPart 1 is the area where you record details about the developer organisation and the software being tested.\nPart 2 is the area where the results of the testing will be automatically calculated using a Macro.  If you currently have Macros disabled, press <F9> to enable. \n\nIf the tester selects a TEST RESULT of N/A for one or more mandatory test cases - a warning will be displayed on the TSR page, because the only appropriate results for a mandatory test case are Pass or Fail."]
[null,"Traceability","This worksheet contains a list of requirements and specifications which shows requirements coverage over the feature sets.\n"]
[null,"References","This worksheet contains a list of documents that are referenced directly from this document and other documents that are related to this document.\n"]
[null,"Return to top"]
[]
[]
[3,"Worksheet Structure for Test Procedures"]
[null,"Table 3 below describes the three Test procedures:  TP-NewDoc, TP-Remove and TP-Supersede.  \nFeature sets FS-PCMLDoc and FS-PCMLProc are described in section 4 below."]
[null,"Table 3: Worksheet Structure - Test procedure"]
[null,"LABEL NAME","DESCRIPTION"]
[null,"Test procedure","A logical grouping of test cases to be executed for a given Software System scenario.\n"]
[null,"Overview","Briefly describes the focus or objective for these test procedures, and includes the implementation of the conformance strategy.\n"]
[null,"Instructions","Explains important data elements used in the test scenarios and contains information on how to apply."]
[null,"Scenario ","Provides an individual identifier and a short description of the test scenario."]
[null,"Objective","Identifies and briefly describes the special focus or objective for the each scenario."]
[null,"Priority","Specifies whether the scenario exercised by this test procedure is mandatory or conditional."]
[null,"Pre-requisites","Describes the actions necessary to prepare for the execution of the scenario."]
[null,"PERFORM THIS TASK","Specific scenario description."]
[null,"RUN THESE TEST SETS/TEST CASES","A list of the test cases to be executed for this scenario."]
[null,"TEST STEP / CASE DESCRIPTION","A brief test case description."]
[null,"ACTUAL TEST RESULT","Result of the test (Pass, Fail, N/A or TBD pick list). \n\nPass:  The software passed the test.\nFail:    The software failed the test.\nN/A:   Not applicable - the test is not applicable for the software being tested \ni.e. the test may be for an optional requirement that is not implemented in the software, or \nthe test is conditional and the condition is not present.\nTBD:   To be determined - the test result is still to be determined.\n"]
[null,"TESTER COMMENTS","Comments in support of the test result\n"]
[null,"Scenario result","Result status of the scenario exercised by this test procedure. Automatically populated, either 'Incomplete' or' Complete'.\n"]
[null,"Return to top"]
[]
[]
[4,"Worksheet structure for Feature Sets"]
[null,"Table 4 below describes the final 2 feature set worksheets:  FS-PCMLDoc and FS-PCMLProc."]
[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 Software 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 which distinguishes each test case from within the entire set of test specifications\n"]
[null,"CONFORMANCE REQUIREMENT","Displays the requirement to be met by the software being tested.\n"]
[null,"PRIORITY","Specifies whether a test is mandatory, conditional or optional.  This is done with the abbreviation:\nM for Mandatory \nC for Conditional\nO for Optional\n"]
[null,"STEP NO.","The individual test step number within a test case which has multiple steps\n"]
[null,"TEST STEP","The evaluation required for applying the test case.\n"]
[null,"EXPECTED RESULT","The expected outcome of the Test Step\n"]
[null,"TEST RESULT","Result of the test (Pass, Fail, N/A or TBD)\n\nPass:  The software passed the test.\nFail:    The software failed the test.\nN/A:   Not applicable - the test is not applicable for the software being tested \ni.e. the test may be for an optional requirement that is not implemented in the software, or \nthe test is conditional and the condition is not present.\nTBD:   To be determined - the test result is still to be determined.\n"]
[null,"TESTER COMMENTS","Comments in support of the test result\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","IHI – Individual Healthcare Identifier"]
[null,"NEHTA","National E-Health Transition Authority"]
[null,"OID","Object Identifier"]
[null,"PCEHR","Personally Controlled Electronic Health Record"]
[null,"PDF","Portable Document Format"]
[null,"SNOMED CT","Systemised Nomenclature of Medicine - Clinical Terminology"]
[null,"SNOMED CT-AU","Systemised Nomenclature of Medicine - Clinical Terminology (Australia)"]
[null,"PCML","Pharmacist Curated Medicines List"]
[null,"PSML","Pharmacist Shared Medicines List"]
[null,"DAA","Dose Administration Aids"]
[null,"IG","Implementation Guide"]
[null,"TC","Test Case"]
[null,"TS","Test Set"]
[null,"Return to top"]

{"sheet":"TP-NewDoc","index":3,"n_rows":82,"n_cols":9,"rows_kept":82,"cut":false,"hidden":false,"merged":[[6,2,6,6],[7,2,7,6],[0,2,0,6],[1,2,1,6],[2,2,2,6],[4,2,4,6],[5,2,5,6],[40,2,40,6],[41,2,41,6],[43,1,68,1],[43,2,68,2],[9,1,32,1],[9,2,34,2],[39,2,39,6],[38,2,38,6]]}
[null,"Test procedure:","TP-NewDoc: Author a new Pharmacist Shared Medicines List"]
[null,"Overview:","To assess the conformance of a  Pharmacist Shared Medicines List software system to the requirements that apply to the process of creating a new  Pharmacist Shared Medicines List.\n\nThe business process of Uploading a new  Pharmacist Shared Medicines List includes requirements for managing consent and the CDA package to be sent to the My Health Record system. \n\nConformance to the requirements associated with the business process is assessed through a set of test scenarios, where each scenario corresponds to a path through the model documented in the 'Process models' worksheet. Test scenarios have been selected to achieve complete coverage of every sequence flow in the model, while reducing the duplication of tests.\n\nA test procedure has been developed for each scenario, where the procedure involved a set of activities and the application of selected test cases. Some test cases used in the scenarios have a 'conditional' priority. Should the condition apply in the context of the test scenario they should be considered mandatory and be marked as Pass or Fail and not N/A.  Each test scenario is passed when all the specified test cases have a status of 'Pass'.\n\nNote: The terms \"software system\", \"authoring system\", \"CIS producer\" and \"clinical document producers\" are all used in the conformance requirements and have the same meaning.  Similarly, \"CDA document\" and \"clinical document\" are used interchangeably as are \"healthcare consumer\" and \"healthcare individual\".\n"]
[null,"Instructions:","A test scenario with the priority of 'mandatory' must be applied and passed by the Software System before it may be declared conformant to the requirements. Any 'conditional' test scenario is to be applied if the Software System has the functionality required to support the test. For the 'conditional' test scenario, if the Software System does not have the required functionality then the test result to be recorded is \"N/A\" (not applicable). The overall test result is calculated from the result of each test scenario.\n\nIt is assumed that some tasks will be automatically performed by the Software System without requiring any action by the tester. \n\nThe test scenarios are made up of test cases, Test cases commencing with the identifier:\n\n1. \"TC-PSMLProc\" are listed in the FS-PSMLProc feature set within this conformance test specification.\n2. \"TC-PSMLDoc\" are listed in the FS-PSMLDoc 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].\n4. Clinical Documents - Common Conformance Profile_v1.7 [DH-2481:2017].\n\n"]
[]
[null,"Scenario:","TP-NewDoc-01 - New  Pharmacist Shared Medicines List - Uploaded to My Health Record System"]
[null,"Objective:","Request a  Pharmacist Shared Medicines List, to upload to My Health Record system.\n\nAuthor and upload a new  Pharmacist Shared Medicines List into My Health Record system."]
[null,"Priority:","Mandatory."]
[null,"Pre-requisites:","1. The healthcare individual has a valid IHI, valid Medicare card number and a current digital health record.\n2. The Software System has been setup to successfully upload  Pharmacist Shared Medicines List to the My Health Record system.\n\n\n"]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST CASE DESCRIPTION","TEST RESULT","TESTER COMMENTS","CALC."]
[null," \nTP-NewDoc-01","\nA1: Author a  clinical document.","TC-PSMLProc-01"," Pharmacist Shared Medicines List clinical documents MAY be produced by Clinical information systems (CIS) or Contracted service provider (CSP) systems.","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-PSMLProc-02"," Pharmacist Shared Medicines List clinical documents SHALL NOT be produced by registered consumer portals or registered provider portals or registered repositories.","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-PSMLProc-03","Dose Administration Aids.","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,null,"TC-PSMLProc-04","Inclusion of optional elements in clinical document.","TBD",null,{"$f":"IF(F13=\"\",\"0\",IF(F13=\"Pass\",1,IF(F13=\"Fail\",0,IF(F13=\"TBD\",0,IF(F13=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-PSMLDoc-01"," 'Document type' representing the code \"56445-0\".","TBD",null,0]
[null,null,null,"TC-PSMLDoc-02","Clinical document represented with template identifier “1.2.36.1.2001.1001.100.1002.237” and code \"1.0\".","TBD",null,0]
[null,null,null,"TC-PSMLDoc-03"," 'Subject of Care' entity identifier representing the patient is an IHI.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-04"," 'Subject of care' address representing the patient is an Australian residential address.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-05","The 'Document author' is represented as a Person.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-06","The 'Document author' entity identifier representing the personal identifier is an HPI-I  or a value that identifies the document author.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-09","The 'document author' address purpose is included as business.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-10","The 'document author' employment detail and organisation name is included.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-11","The 'document author' employer organisation entity identifier representing the organisations HPI-O.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-12","The clinical document can contain at most one primary healthcare provider.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-13","The primary healthcare provider represented has not been coded with an abnormal value.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-14","The 'primary healthcare provider as a person' entity identifier representing the personal identifier and that identifier is a HPI-I.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-15","The 'primary healthcare provider as a person' employment detail and organisation name is included.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-16","The primary healthcare provider organisation identifier contain a HPI-O as an organisation identifier.","TBD",null,{"$f":"IF(F27=\"\",\"0\",IF(F27=\"Pass\",1,IF(F27=\"Fail\",0,IF(F27=\"TBD\",0,IF(F27=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-PSMLDoc-17","The 'primary healthcare provider organisation' contain only one value of Australian workplace address.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-18","Inclusion of ENCAPSULATED DATA.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-19","Inclusion of PDF attachment.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-20","Referencing PCML PDF attachment.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-21","PDF attachment MIME type.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-22","Levels of conformance.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-23","Content of PCML.","TBD",null,{"$f":"IF(F34=\"\",\"0\",IF(F34=\"Pass\",1,IF(F34=\"Fail\",0,IF(F34=\"TBD\",0,IF(F34=\"N/A\",1)))))","v":0}]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA® Authoring.",null,"TBD",null,0]
[null,null,"A2:  UC.CIS.201 Upload a clinical document","\nTest cases for UC.CIS.201","Pharmacist Shared Medicines List is uploaded successfully to My Health Record system.\n","TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I37=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H10:H37) / (COUNT(H10:H37))","v":0}]
[]
[null,"Scenario:","TP-NewDoc-02 - New  Pharmacist Shared Medicines List - NOT Uploaded to My Health Record System"]
[null,"Objective:","1. Demonstrate the Software System's inclusion of entitlement information in clinical document. \n    (e.g. Medicare card number and Department of Veterans' Affairs (DVA) file number)\n2. Demonstrate the Software System has the ability to cancel or not approve the clinical document.\n"]
[null,"Priority:","Mandatory."]
[null,"Pre-requisites:","1. The healthcare individual has a valid IHI, valid Medicare card number and a current digital health record.\n2. The Software System has been setup to successfully upload  Pharmacist Shared Medicines List to the My Health Record system.\n\n\n"]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST CASE DESCRIPTION","TEST RESULT","TESTER COMMENTS","CALC."]
[null," \nTP-NewDoc-02","\nA1: Author a  clinical document.","TC-PSMLProc-01"," Pharmacist Shared Medicines List clinical documents MAY be produced by Clinical information systems (CIS) or Contracted service provider (CSP) systems.","TBD",null,{"$f":"IF(F44=\"\",\"0\",IF(F44=\"Pass\",1,IF(F44=\"Fail\",0,IF(F44=\"TBD\",0,IF(F44=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-PSMLProc-02"," Pharmacist Shared Medicines List clinical documents SHALL NOT be produced by registered consumer portals or registered provider portals or registered repositories.","TBD",null,{"$f":"IF(F45=\"\",\"0\",IF(F45=\"Pass\",1,IF(F45=\"Fail\",0,IF(F45=\"TBD\",0,IF(F45=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-PSMLProc-03","Dose Administration Aids.","TBD",null,{"$f":"IF(F46=\"\",\"0\",IF(F46=\"Pass\",1,IF(F46=\"Fail\",0,IF(F46=\"TBD\",0,IF(F46=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-PSMLProc-04","Inclusion of optional elements in clinical document.","TBD",null,{"$f":"IF(F47=\"\",\"0\",IF(F47=\"Pass\",1,IF(F47=\"Fail\",0,IF(F47=\"TBD\",0,IF(F47=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-PSMLDoc-01","Document type' representing the code \"56445-0\".","TBD",null,0]
[null,null,null,"TC-PSMLDoc-02","Clinical document represented with template identifier “1.2.36.1.2001.1001.100.1002.237” and code \"1.0\".","TBD",null,0]
[null,null,null,"TC-PSMLDoc-03"," 'Subject of Care' entity identifier representing the patient is an IHI.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-04"," 'Subject of care' address representing the patient is an Australian residential address.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-05","The 'Document author' is represented as a Person.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-06","The 'Document author' entity identifier representing the personal identifier is an HPI-I  or a value that identifies the document author.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-09","The 'document author' address purpose is included as business.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-10","The 'document author' employment detail and organisation name is included.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-11","The 'document author' employer organisation entity identifier representing the organisations HPI-O.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-12","The clinical document can contain at most one primary healthcare provider.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-13","The primary healthcare provider represented has not been coded with an abnormal value.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-14","The 'primary healthcare provider as a person' entity identifier representing the personal identifier and that identifier is a HPI-I","TBD",null,0]
[null,null,null,"TC-PSMLDoc-15","The 'primary healthcare provider as a person' employment detail and organisation name is included.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-16","The primary healthcare provider organisation identifier contain a HPI-O as an organisation identifier.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-17","The 'primary healthcare provider organisation' contain only one value of Australian workplace address.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-18","Inclusion of ENCAPSULATED DATA.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-19","Inclusion of PDF attachment.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-20","Referencing PCML PDF attachment.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-21","PDF attachment MIME type.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-22","Levels of conformance.","TBD",null,0]
[null,null,null,"TC-PSMLDoc-23","Content of PCML.","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,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA® Authoring.",null,"TBD",null,0]
[null,null,"A2:  UC.CIS.201 Upload a clinical document","PCEHR_CIS_019042 (UC.CIS.201)","Ability to support the withdrawal of consent to upload a clinical document to the My Health Record system.","TBD",null,0]
[null,"Scenario result:",{"$f":"IF($I71=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H44:H71) / (COUNT(H44:H71))","v":0}]
[]
[]
[]
[null,"Scenario","Percentage complete","Status",null,{"$f":"COUNTIF(H10:H72,\">=0\")","v":54},"Total Tests","TBD"]
[null,"TP-NewDoc-01",{"$f":"I37","v":0},{"$f":"C37","v":"Incomplete"},null,{"$f":"COUNTIF(H10:H72,\"0\")","v":54},"Tests Failed or TBD","Fail"]
[null,"TP-NewDoc-02",{"$f":"I71","v":0},{"$f":"C71","v":"Incomplete"},null,{"$f":"COUNTIF(H10:H72,\"1\")","v":0},"Tests Passed or N/A","Pass"]
[null,null,null,null,null,{"$f":"SUM(F77/F75)","v":0},"% Passed or N/A","N/A"]
[null,null,{"$f":"SUM(C80:C81)","v":2},"Total Scenarios"]
[null,null,{"$f":"COUNTIF(D76:D77,\"Complete\")","v":0},"Scenarios Complete"]
[null,null,{"$f":"COUNTIF(D76:D77,\"Incomplete\")","v":2},"Scenarios Not Complete"]
[null,null,{"$f":"SUM(C80) / (C79)","v":0},"Scenarios percentage Complete"]

{"sheet":"TP-Supersede","index":4,"n_rows":49,"n_cols":9,"rows_kept":49,"cut":false,"hidden":false,"merged":[[7,2,7,6],[9,1,32,1],[9,2,34,2],[6,2,6,6],[0,2,0,6],[1,2,1,6],[2,2,2,6],[4,2,4,6],[5,2,5,6]]}
[null,"Test procedure:","TP-Supersede: Supersede a Pharmacist Shared Medicines List"]
[null,"Overview:","To assess the conformance of a Pharmacist Shared Medicines List authoring system to the requirements that apply to the process of superseding a Pharmacist Shared Medicines List that was uploaded to the My Health Record system.\n\nThe business process of superseding a Pharmacist Shared Medicines List is initiated when an author of a previously created  Pharmacist Shared Medicines List 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 Pharmacist Shared Medicines List and CDA package to be sent to the My Health Record system. \n\nConformance to the requirements associated with the business process is assessed through a set of test scenarios, where each scenario corresponds to a path through the model documented in the \"Process models\" worksheet. Test scenarios have been selected to achieve complete coverage of every sequence flow in the model, while reducing the duplication of tests. \n\nA test procedure has been developed for each scenario, where the procedure involved a set of activities and the application of selected test cases. Some test cases used in the scenarios have a \"conditional\" priority.  Should the condition apply in the context of the test scenario they should be considered mandatory and be marked as Pass or Fail and not N/A.  Each test scenario is passed when all the specified test cases have a status of \"Pass\".\n\nNote: The terms \"software system\", \"authoring system\", \"CIS producer\" and \"clinical document producers\" are all used in the conformance requirements and have the same meaning.  Similarly, \"CDA document\" and \"clinical document\" are used interchangeably as are \"healthcare consumer\" and \"healthcare individual\".\n\n"]
[null,"Instructions:","A test scenario with the priority of 'mandatory' must be applied and passed by the Software System before it may be declared conformant to the requirements. Any 'conditional' test scenario is to be applied if the Software System has the functionality required to support the test. For the 'conditional' test scenario, if the Software System does not have the required functionality then the test result to be recorded is \"N/A\" (not applicable). The overall test result is calculated from the result of each test scenario.\n\nIt is assumed that some tasks will be automatically performed by the Software System without requiring any action by the tester. \n\nThe test scenarios are made up of test cases, Test cases commencing with the identifier:\n\n1. \"TC-PCMLProc\" are listed in the FS-PCMLProc feature set within this conformance test specification.\n2. \"TC-PCMLDoc\" are listed in the FS-PCMLDoc 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].\n4. Clinical Documents - Common Conformance Profile_v1.7 [DH-2481:2017].\n"]
[]
[null,"Scenario:","TP-Supersede-01 - Create a replacement Pharmacist Shared Medicines List - Upload to My Health Record System."]
[null,"Objective:","To demonstrate that the software system has the ability to:\n1. Create a replacement Pharmacist Shared Medicines List to supersede an existing Pharmacist Shared Medicines List that was previously uploaded to the My Health Record system.\n2. Upload the replacement Pharmacist Shared Medicines List to the My Health Record system.\n\nUsing the software system, for a healthcare individual, create a replacement Pharmacist Shared Medicines List to supersede an existing Pharmacist Shared Medicines List 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 Pharmacist Shared Medicines List to the My Health Record system. \n"]
[null,"Priority:","Mandatory."]
[null,"Pre-requisites:","To apply this test scenario, a Pharmacist Shared Medicines List 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. Healthcare individual has indicated consent to upload to the My Health Record system.\n3. Healthcare individual's name and sufficient demographic information is present in the request, as is needed to successfully search the HI Service to obtain their IHI.\n4. Healthcare individual has at least one previously uploaded Pharmacist Shared Medicines List in the My Health Record system.\n5 The software system has been set up to successfully upload the Pharmacist Shared Medicines List 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 CASE DESCRIPTION","TEST RESULT","TESTER COMMENTS","CALC."]
[null," \nTP-Supersede-01 ","\nA1: Author a  clinical document.","TC-PCMLProc-01"," Pharmacist Shared Medicines List clinical documents MAY be produced by Clinical information systems (CIS) or Contracted service provider (CSP) systems.","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-PCMLProc-02"," Pharmacist Shared Medicines List clinical documents SHALL NOT be produced by registered consumer portals or registered provider portals or registered repositories.","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-PCMLProc-03","Dose Administration Aids.","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,null,"TC-PCMLProc-04","Inclusion of optional elements in clinical document.","TBD",null,{"$f":"IF(F13=\"\",\"0\",IF(F13=\"Pass\",1,IF(F13=\"Fail\",0,IF(F13=\"TBD\",0,IF(F13=\"N/A\",1)))))","v":0}]
[null,null,null,"TC-PCMLDoc-01","Document type' representing the code \"56445-0\".","TBD",null,0]
[null,null,null,"TC-PCMLDoc-02","Clinical document represented with template identifier “1.2.36.1.2001.1001.100.1002.237” and code \"1.0\".","TBD",null,0]
[null,null,null,"TC-PCMLDoc-03"," 'Subject of Care' entity identifier representing the patient is an IHI.","TBD",null,0]
[null,null,null,"TC-PCMLDoc-04"," 'Subject of care' address representing the patient is an Australian residential address.","TBD",null,0]
[null,null,null,"TC-PCMLDoc-05","The 'Document author' is represented as a Person.","TBD",null,0]
[null,null,null,"TC-PCMLDoc-06","The 'Document author' entity identifier representing the personal identifier is an HPI-I  or a value that identifies the document author.","TBD",null,0]
[null,null,null,"TC-PCMLDoc-09","The 'document author' address purpose is included as business.","TBD",null,0]
[null,null,null,"TC-PCMLDoc-10","The 'document author' employment detail and organisation name is included.","TBD",null,0]
[null,null,null,"TC-PCMLDoc-11","The 'document author' employer organisation entity identifier representing the organisations HPI-O.","TBD",null,0]
[null,null,null,"TC-PCMLDoc-12","The clinical document can contain at most one primary healthcare provider.","TBD",null,0]
[null,null,null,"TC-PCMLDoc-13","The primary healthcare provider represented has not been coded with an abnormal value.","TBD",null,0]
[null,null,null,"TC-PCMLDoc-14","The 'primary healthcare provider as a person' entity identifier representing the personal identifier and that identifier is a HPI-I","TBD",null,0]
[null,null,null,"TC-PCMLDoc-15","The 'primary healthcare provider as a person' employment detail and organisation name is included.","TBD",null,0]
[null,null,null,"TC-PCMLDoc-16","The primary healthcare provider organisation identifier contain a HPI-O as an organisation identifier.","TBD",null,0]
[null,null,null,"TC-PCMLDoc-17","The 'primary healthcare provider organisation' contain only one value of Australian workplace address.","TBD",null,0]
[null,null,null,"TC-PCMLDoc-18","Inclusion of ENCAPSULATED DATA.","TBD",null,0]
[null,null,null,"TC-PCMLDoc-19","Inclusion of PDF attachment.","TBD",null,0]
[null,null,null,"TC-PCMLDoc-20","Referencing PCML PDF attachment.","TBD",null,0]
[null,null,null,"TC-PCMLDoc-21","PDF attachment MIME type.","TBD",null,0]
[null,null,null,"TC-PCMLDoc-22","Levels of conformance.","TBD",null,0]
[null,null,null,"TC-PCMLDoc-23","Content of PCML.","TBD",null,{"$f":"IF(F34=\"\",\"0\",IF(F34=\"Pass\",1,IF(F34=\"Fail\",0,IF(F34=\"TBD\",0,IF(F34=\"N/A\",1)))))","v":0}]
[null,null,null,"All the mandatory and applicable conditional tests in Conformance Test Specification for CDA® Authoring.",null,"TBD",null,0]
[null,null,"C2:  UC.CIS.202 Supersede a clinical document","\nTest cases for UC.CIS.202","Replacement Pharmacist Shared Medicines List is uploaded successfully to My Health Record system.\n","TBD",null,0]
[null,"Scenario result:",{"$f":"IF(I37=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H10:H37) / (COUNT(H10:H37))","v":0}]
[]
[]
[]
[]
[null,"Scenario","Percentage complete","Status",null,{"$f":"COUNTIF(H10:H39,\">=0\")","v":27},"Total Tests","TBD"]
[null,"TP-NewDoc-01",{"$f":"I37","v":0},{"$f":"C37","v":"Incomplete"},null,{"$f":"COUNTIF(H10:H39,\"0\")","v":27},"Tests Failed or TBD","Fail"]
[null,null,null,null,null,{"$f":"COUNTIF(H10:H39,\"1\")","v":0},"Tests Passed or N/A","Pass"]
[null,null,null,null,null,{"$f":"SUM(F44/F42)","v":0},"% Passed or N/A","N/A"]
[null,null,{"$f":"SUM(C47:C48)","v":1},"Total Scenarios"]
[null,null,{"$f":"COUNTIF(D43:D44,\"Complete\")","v":0},"Scenarios Complete"]
[null,null,{"$f":"COUNTIF(D43:D44,\"Incomplete\")","v":1},"Scenarios Not Complete"]
[null,null,{"$f":"SUM(C47) / (C46)","v":0},"Scenarios percentage Complete"]

{"sheet":"TP-Remove","index":5,"n_rows":24,"n_cols":9,"rows_kept":24,"cut":false,"hidden":false,"merged":[[7,2,7,6],[6,2,6,6],[0,2,0,6],[1,2,1,6],[2,2,2,6],[4,2,4,6],[5,2,5,6]]}
[null,"Test procedure:","TP-Remove: Remove a  Pharmacist Shared Medicines List"]
[null,"Overview:","To assess the conformance of a  Pharmacist Shared Medicines List (PSML) Software System to the requirements that apply to the process of removing a  Pharmacist Shared Medicines List from the My Health Record System.\n\nThe business process of removing a  Pharmacist Shared Medicines List is initiated by the report author 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 involved a set of activities and the application of selected test cases. Some test cases used in the scenarios have a 'conditional' priority. Should the condition apply in the context of the test scenario they should be considered mandatory and be marked as Pass or Fail and not N/A.  Each test scenario is passed when all the specified test cases have a status of 'Pass'."]
[null,"Instructions:","A test scenario with the priority of 'mandatory' must be applied and passed by the Software System before it may be declared conformant to the requirements. Any 'conditional' test scenario is to be applied if the Software System has the functionality required to support the test. For the 'conditional' test scenario, if the Software System does not have the required functionality then the test result to be recorded is \"N/A\" (not applicable). The overall test result is calculated from the result of each test scenario.\n\nThe test scenarios are made up of test cases, Test cases commencing with the identifier:\n\n1.\"PCEHR_CIS\" are listed in the PCEHR Connecting Systems - Conformance Test Specification v1.6 [NEHTA-1299:2012].\n\n"]
[]
[null,"Scenario:","TP-Remove-01"]
[null,"Objective:","To demonstrate that the Software System has the ability to remove an existing  Pharmacist Shared Medicines List that was previously uploaded to the My Health Record system.\n\nSelect a  Pharmacist Shared Medicines List that was uploaded to the My Health Record system, then use the Software System to remove the  Pharmacist Shared Medicines List from the My Health Record system.\n"]
[null,"Priority:","Mandatory."]
[null,"Pre-requisites:","To apply this test scenario a  Pharmacist Shared Medicines List 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 digital health record.\n2. The Software System has been setup to successfully remove the  Pharmacist Curated Medicines List from My Health Record system.\n"]
[null,"SCENARIO","PERFORM THIS TASK","RUN THESE TEST SETS/TEST CASES\nALL MUST PASS FOR SCENARIO TO PASS","TEST CASE DESCRIPTION","TEST RESULT","TESTER COMMENTS","CALC."]
[null," TP-Remove-01","B1: Select a  Pharmacist Shared Medicines List to Remove.","-","There are no requirements for this task.","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,"B2: UC.CIS.203 Remove a clinical document.","Test cases for UC.CIS.203"," Pharmacist Shared Medicines List is removed successfully from the My Health Record system.","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,"Scenario result:",{"$f":"IF(I12=100%, \"Complete\", \"Incomplete\")","v":"Incomplete"},null,null,null,null,null,{"$f":"SUM(H10:H12) / (COUNT(H10:H12))","v":0}]
[]
[]
[]
[]
[null,"Scenario","Percentage complete","Status",null,{"$f":"COUNT(H10:H14)","v":2},"Total Tests","TBD"]
[null,"TP-Remove-01",{"$f":"I12","v":0},{"$f":"C12","v":"Incomplete"},null,{"$f":"COUNTIF(H10:H14,\"0\")","v":2},"Tests Failed or TBD","Fail"]
[null,null,null,null,null,{"$f":"COUNTIF(H10:H14,\"1\")","v":0},"Tests Passed or N/A","Pass"]
[null,null,null,null,null,{"$f":"SUM(F19/F17)","v":0},"% Passed or N/A","N/A"]
[null,null,{"$f":"SUM(C22:C23)","v":1},"Total Scenarios"]
[null,null,{"$f":"COUNTIF(D18:D19,\"Complete\")","v":0},"Scenarios Complete"]
[null,null,{"$f":"COUNTIF(D18:D19,\"Incomplete\")","v":1},"Scenarios Not Complete"]
[null,null,{"$f":"SUM(C22) / (C21)","v":0},"Scenarios percentage Complete"]

{"sheet":"FS-PSMLProc","index":6,"n_rows":17,"n_cols":11,"rows_kept":17,"cut":false,"hidden":false,"merged":[[1,2,1,5],[2,2,2,5],[3,2,3,5],[0,2,0,5],[0,0,0,1],[1,0,1,1],[2,0,2,1],[3,0,3,1]]}
["Feature set identifier:",null,"FS-PSMLProc (Pharmacist Shared Medicines List clinical document)",null,null,null,null,"Software tested:\n"]
["Objective:",null,"To assess a Software System’s conformance against the process requirements for a Software System that creates Pharmacist Shared Medicines List. These requirements are in addition to the requirements that apply to the Pharmacist Shared Medicines List created by a Software System.\n",null,null,null,null,"Software version:"]
["Strategy:",null,"The  Pharmacist Shared Medicines List - MHR Conformance Profile V1.0 [DH-2637:2018]  includes requirements for the behaviour of the document Software System. The conformance of a Software System to these requirements is assessed by evaluating the Software System and applying the test cases defined here. In addition, the Clinical Documents - Common Conformance Profile v1.7 [DH-2481:2017] contains requirements for the behaviour of a Software system that apply regardless of the type of document being authored. Test cases for those requirements are listed in the Conformance Test Specification for CDA Authoring v1.5 [DH-2209:2017].\n\nNote: The terms 'Software System', 'CIS producer' and 'clinical document producers' are all used in the conformance requirements and have the same meaning. Similarly, 'CDA document' and 'clinical document' are used interchangeably as are 'healthcare consumer' and 'healthcare individual'.",null,null,null,null,"Software supplier:"]
["Traceability:",null,"1. Pharmacist Shared Medicines List - Conformance Profile v1.0 [DH-2637:2018] \n2. Clinical Documents - Common Conformance Profile_v1.7 [DH-2481:2017]",null,null,null,null,"Tester:",null,null," "]
[null,null,null,null,null,null,null,"Test date:"]
["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-Gen","START: TS-Gen (General)"]
["TS-Gen","TC-PSMLProc-01","028153 [DH-2637:2018]\n\nAllowable types of conformance\nPSML clinical documents MAY be produced by:\n• clinical information systems (CIS); and\n• contracted service provider (CSP) systems.\n","O ",1,"Pass this test where the system under test produces Pharmacist Shared Medicines List (PSML) clinical documents and is either:\na) Clinical information systems (CIS), or\nb) Contracted service provider (CSP) systems.\nElse, record N/A.\n\nNOTE TO TESTER: Although this test is Optional, a Pharmacy Shared Medicines List can only be created by a clinical information system (CIS) or a contracted service provider (CSP) system.\n","The system producing the Pharmacist Shared Medicines List clinical documents is either:\n 1. a Clinical Information System (CIS), or\n 2. a Contracted Service Provider (CSP) system.","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-Gen","TC-PSMLProc-02","024569 [DH-2637:2018]\n\nDisallowed types of producers \nA producer SHALL NOT be a:\n• registered consumer portal;\n• registered repository;\nor\n• registered provider portal.\n\nAdditional Notes\nThe risk profile for these types of producers has not been assessed. it is not appropriate for these producers to upload PSML documents until that risk profile is understood.","M",1,"Pass this test, where the system under test that produces Pharmacist Shared Medicines List clinical documents is NOT a:\na) Registered consumer portal, or\nb) Registered provider portal, or\nc) Registered repository.\nElse, Fail the test.\n","Pharmacist Shared Medicines List clinical documents producing system is not a:\n 1. Registered consumer portals; or\n 2. Registered provider portals; or\n 3. Registered repositories.","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-Gen","TC-PSMLProc-03","028154 [DH-2637:2018]\n\nDose Administration Aids\nSoftware for Dose Administration Aids SHALL have the capability to include all packed and non-packed medicines the patient record states an individual is known to be taking.\n\nAdditional Notes\nIt is important for the PSML to be as complete as possible.\n","C",1,"CONDITION: If the Pharmacist Shared Medicines List clinical document is created by Dose Administration Aids (DAA) software.\n\nPass the test where the Dose Administration Aids software has the capability to include both packed and non-packed medicines.\nElse, Fail the test.\n\nNOTE TO TESTER:\na) Non-packaged medicines include non-prescribed medicines purchased over-the-counter, complimentary medicines and supplements (such as vitamins, herbal remedies, etc).\"\nb) Examples of Dose Administration Aids software are Webstercare, Practicare,Telstra Health etc.\n ","Dose Administration Aids software records both packaged and non-packaged (over-the-counter) medicines.","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-Gen","TC-PSMLProc-04","027732  [DH-2481:2017]\n\nInclusion of optional elements in clinical document\nIf the software has information in a form that may be used to populate an optional data component then the software SHALL allow the inclusion of that data component in a clinical document.\n\nAdditional Notes\nThe data component may be omitted from a clinical document if at least one of the following conditions is true:\n• The software does not have information for an optional data component;\n• The information is not in a form that may be used for the data component;\n• There is a clinical reason why supplying the data would be unsafe, misleading, or otherwise clinically inappropriate.\n","C",1,"CONDITION: The software system has information in a form that may be used to populate an optional data component and there is no clinical reason why the data should not be supplied.\n\nPass the test, where all information within the local system, which may be used to populate an optional data component, has been included in that data component in the PSML clinical document.\nElse, Fail the test.\n","All information within the local system, which may be used to populate an optional data component, has been included in that data component in the PSML clinical document.","TBD",null,{"$f":"IF(H12=\"\",\"0\",IF(H12=\"Pass\",1,IF(H12=\"Fail\",0,IF(H12=\"TBD\",0,IF(H12=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D12)=48,H12=\"N/A\"),1,0)","v":0}]
["TS-Gen","END: TS-Gen (General)"]
[null,null,null,null,null,null,null,"TBD","Total Steps",{"$f":"SUM(J15:J16)","v":4}]
[null,null,null,null,null,null,null,"Fail","Tests Not Started, Failed or TBD",{"$f":"COUNTIF(J9:J13,\"0\")","v":4}]
[null,null,null,null,null,null,null,"N/A","Tests Passed or N/A",{"$f":"COUNTIF(J9:J13,\"1\")","v":0}]
[null,null,null,null,null,null,null,"Pass","%Passed or N/A",{"$f":"SUM(J16/J14)","v":0}]

{"sheet":"FS-PSMLDoc","index":7,"n_rows":44,"n_cols":11,"rows_kept":44,"cut":false,"hidden":false,"merged":[[36,1,36,2],[11,1,11,2],[30,1,30,2],[0,0,0,1],[1,0,1,1],[2,0,2,1],[3,0,3,1],[0,2,0,5],[1,2,1,5],[2,2,2,5],[3,2,3,5],[22,1,22,2],[29,1,29,2]]}
["Feature set identifier:",null,"FS-PSMLDoc ( Pharmacist Shared Medicines List clinical document)",null,null,null,null,"Software tested:\n"]
["Objective:",null,"To assess the conformance of a  Pharmacist Shared Medicines List clinical document against the requirements for that document type.",null,null,null,null,"Software version:"]
["Strategy:",null,"A Pharmacist Shared Medicines List clinical document to be tested, can only be obtained by passing FS-PSML Proc. 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 Conformance Test Specification for CDA Authoring v1.5 [DH-2209:2017], 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  Core Level One clinical document structured content specification it is assumed that, the Template Packages will assess conformance to these requirements.\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",null,null,null,null,"Software supplier:"]
["Traceability:",null,"1. Pharmacist Shared Medicines List - MHR Conformance Profile v1.1.1 [DH-2926:2019]\n2. Clinical Documents - Common Conformance Profile_v1.7 [DH-2481:2017]\n3. Conformance Test Specification for Authoring Systems_v1.0 [DH-2209:2017]\n4. Core Level One Clinical Document - Structured Content Specification v1.1 [DH-2579:2018]\n",null,null,null,null,"Tester:",null,null," "]
[null,null,null,null,null,null,null,"Test date:"]
["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-PSML ID","START: TS-PSML ID (Pharmacist Shared Medicines List Identifier)"]
["TS-PSML ID","TC-PSMLDoc-01","027999  [DH-2926:2019]\n\nDocument type\nWhen instantiating the document type, the software SHALL use:\n•  the code “56445-0” in the code attribute of the code element of the clinical document;\n • the OID in the codeSystem attribute of the code element of the clinical document SHALL be “2.16.840.1.113883.6.1”; and\n • the title element value of the clinical document SHALL be “Pharmacist Shared Medicines List”.\n","M",1,"Pass the test where:\na) The Pharmacist Shared Medicines List clinical document authoring system generates the correct code header element attribute values as defined in the corresponding Conformance Profile, and\nb) the title element value of the clinical document is “Pharmacist Shared Medicines List”.\nElse, Fail the test.","Authoring system generates the clinical document header element with code =\"56445-0\", root=\"2.16.840.1.113883.6.1\" and the title=\"Pharmacist Shared Medicines List\".","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-PSML ID","TC-PSMLDoc-02","028000 [DH-2926:2019]  \n\nClinical document template identifier\nWhen instantiating the templateid the software SHALL ensure that one instance of the clinical document:\n• the root attribute of the templateId element SHALL be “1.2.36.1.2001.1001.100.1002.237”; and\n•The extension attribute of the templateId element SHALL be “1.0”.\n\nAdditional Notes \nThis is in addition to the template ID specified in the Core Level One Clinical Document CDA Implementation Guide.\n","M",1,"Pass the test where:\nThe Pharmacist Shared Medicines List clinical document contains one instance of a <templateId> header element with root=\"1.2.36.1.2001.1001.100.1002.237\" Object Identifier (OID)  and extension=\"1.0\".\nElse, Fail the test.","Pharmacist Shared Medicines List clinical document includes one instance of a <templateId> header element with root=\"1.2.36.1.2001.1001.100.1002.237\" Object Identifier (OID)  and extension=\"1.0\".","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-PSML ID","END: TS-PSML ID (Pharmacist Shared Medicines List Identifier)"]
["TS-Subj Care & Doc Auth","START: TS-Subj Care & Doc Auth (Subject of Care and Document Author)"]
["TS-Subj Care & Doc Auth","TC-PSMLDoc-03","027988 [DH-2926:2019]  \n\nSubject of Care identifier \nWhen instantiating the subject of care, the document SHALL contain one and only one personal identifier and that identifier SHALL be an Individual Healthcare Identifier (IHI).","M",1,"Pass the test, where the document contains only one value for 'Subject of Care' entity identifier representing the patient, and that identifier is a valid IHI (Individual Healthcare Identifier).\nElse, Fail the test. \n\nNOTE TO TESTER: The data element 'SUBJECT OF CARE > Participant >Entity Identifier' has the XPATH:\nClinicalDocument/recordTarget/patientRole/patient/<Entity Identifier>\n","The subject of care has one and only one personal identifier, and that identifier is an Individual Healthcare Identifier (IHI).","TBD",null,{"$f":"IF(H13=\"\",\"0\",IF(H13=\"Pass\",1,IF(H13=\"Fail\",0,IF(H13=\"TBD\",0,IF(H13=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D13)=48,H13=\"N/A\"),1,0)","v":0}]
["TS-Subj Care & Doc Auth","TC-PSMLDoc-04","027991 [DH-2926:2019]  \n\nSubject of care address\nWhen instantiating the subject of care, the document SHALL contain:\n• an address (of any type)\nOR\n• a nullFlavor (of any type).\nor both \nBUT NOT\n• an address (of any type) AND a MSK nullFlavor;\n\nAdditional Notes\nThe document author is permitted to suppress or not include the individual's residential address through the use of nullflavor. If the address is known, but not included in the document, then it is preferred the “MSK” nullflavor is used. The masking of the address may be used when there are patient privacy or safety concerns.\nIt is prohibited to include a MSK nullflavor AND an address because a masked address should not be available in the CDA/XML document.\nOther nullflavors are also permitted.","M",1,"Pass the test where the 'Subject of Care' address contains either:\na) an address (of any type) or a nullFlavor (of any type), or\nb) an address and a nullFlavor of any value except the value \"MSK\"\nElse, Fail the test.\n\nNOTE TO TESTER: \na) The nullFlavor codes and names are from ISO standard ISO21090. \nnullFlavor=\"PINF\", display name = \"positive infinity\"\nnullFlavor=\"NINF\", display name = \"negative infinity\"\nnullFlavor=\"ASKU\", display name = \"asked but unknown\"\nnullFlavor=\"NAV\", display name = \"temporarily unavailable\"\nnullFlavor=\"NASK\", display name = \"not asked\"\nnullFlavor=\"QS\", display name = \"sufficient quantity\"\nnullFlavor=\"TRC\", display name = \"trace\"\nnullFlavor=\"MSK\", display name = \"masked\"\nnullFlavor=\"NA\", display name = \"not applicable\"\nnullFlavor=\"NI\", display name = \"no information\"\nnullFlavor=\"INV\", display name = \"invalid\"\nnullFlavor=\"OTH\", display name = \"other\"\nnullFlavor=\"UNC\", display name = \"unencoded\"\nnullFlavor=\"DER\", display name = \"derived\"\nnullFlavor=\"UNK\", display name = \"unknown\"\nb)  Software system should allow document author to suppress or not include the individual's residential address through the use of nullFlavor.\nc) The data element 'SUBJECT OF CARE > Participant >Address' has the XPATH:\nClinicalDocument/recordTarget/patientRole/<Address>\n","The 'Subject of Care' has an 'address' and/or a 'nullFlavor'.\nWhere both an 'address' and a 'nullFlavor' are provided, the 'nullFlavor' is not \"MSK\".","TBD",null,{"$f":"IF(H14=\"\",\"0\",IF(H14=\"Pass\",1,IF(H14=\"Fail\",0,IF(H14=\"TBD\",0,IF(H14=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D14)=48,H14=\"N/A\"),1,0)","v":0}]
["TS-Subj Care & Doc Auth","TC-PSMLDoc-05","027989 [DH-2926:2019]  \n\nDocument Author\nWhen instantiating the document author, the document SHALL instantiate the document author as a person.\n\nAdditional Notes\nThe document author must be instantiated as a person and must not be an organisation or device.\n","M",1,"Pass the test where the 'Document Author' is represented as a Person.\nElse, Fail the test.\n\nNOTE TO TESTER: The data element DOCUMENT AUTHOR has the XPATH:\nClinicalDocument/author/assignedPerson\n","Document author is represented as a Person.","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-Subj Care & Doc Auth","TC-PSMLDoc-06","028630 [DH-2926:2019]\n\nDocument Author Entity Identifier value\nWhen instantiating the document author, the document SHALL contain one and only one personal identifier that is a Healthcare Provider Identifier for Individual (HPI-I), otherwise it SHALL have a value that identifies the document author, and that value SHALL NOT be a nullflavor.\n\nAdditional Notes\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","M",1,"Pass the test where the document contains one and only one value for 'Document Author' personal entity identifier and that identifier is a HPI-I (Healthcare Provider Identifier – Individual) or a value that identifies the document author and that value is not a nullflavor.\nElse, Fail the test.  \n\nNOTE TO TESTER:\nThe data element 'Document Author > Participant >Entity Identifier' Represented via the following XPATH:\n/ClinicalDocument/author/assignedAuthor/assignedPerson/<Entity Identifier>\n \n","The entity Identifier included in the 'Document Author' personal identifier has only one identifier and that identifier is a HPI-I or a value that identifies the document author.","TBD",null,{"$f":"IF(H16=\"\",\"0\",IF(H16=\"Pass\",1,IF(H16=\"Fail\",0,IF(H16=\"TBD\",0,IF(H16=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D16)=48,H16=\"N/A\"),1,0)","v":0}]
["TS-Subj Care & Doc Auth","TC-PSMLDoc-07","024980  [DH-2926:2019]  \n\nConfirm individual electronic communication details to be included\nSoftware SHALL allow document authors to confirm which (if any) of their individual electronic communication details (e.g. email address, phone number or fax number) may be automatically included. The default SHALL be to include no details.\n",null,null,"No test case is defined for this requirement.\n"]
["TS-Subj Care & Doc Auth","TC-PSMLDoc-08","024982  [DH-2926:2019]  \n\nConfirm individual address to be included\nSoftware SHALL allow document authors to confirm which (if any) of their individual addresses may be automatically included. The default SHALL be to include no details.\n",null,null,"No test case is defined for this requirement.\n"]
["TS-Subj Care & Doc Auth","TC-PSMLDoc-09","027993 [DH-2926:2019]  \n\nDocument author workplace address\nWhen instantiating the document author, the document SHALL contain one and only one value for healthcare provider individual’s workplace address and that address is an Australian address.\n\nAdditional Notes\nThe document MAY contain other non-workplace addresses. See requirement 024982.\n","M",1,"Pass the test where 'Document Author' contains only one workplace address and that address is an Australian address.\nElse, Fail the test.\n\nNOTE TO TESTER: \na) Document author can contain other non-workplace addresses. \nb) Address use can be identified as a workplace address by the use (purpose) as 'WP' (WorkPlace).\nc) The data element 'DOCUMENT AUTHOR > Participant > Address' has the XPATH:\nClinicalDocument/author/assignedAuthor/<Address>","The Document Author has only one workplace address, and that address is an Australian address.","TBD",null,{"$f":"IF(H19=\"\",\"0\",IF(H19=\"Pass\",1,IF(H19=\"Fail\",0,IF(H19=\"TBD\",0,IF(H19=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D19)=48,H19=\"N/A\"),1,0)","v":0}]
["TS-Subj Care & Doc Auth","TC-PSMLDoc-10","027992 [DH-2926:2019]  \n\nDocument author organisation name\nWhen instantiating the document author, the document SHALL contain one and only one organisation name represented as:\n• Document Author > Participant > Person or Organisation or Device > Person > Employment Detail > Employer Organisation > Organisation > Organisation Name\nRepresented via the following XPATH:\n•/ClinicalDocument/author/assignedAuthor/assignedPerson/ext:asEmployment/ext:employerOrganization/asOrganizationPartOf/wholeOrganization/name\n\nAdditional Notes\nImplementers should note that this requirement effectively makes the “Employment Detail” section mandatory.\n","M",1,"Pass the test where the 'Document Author' includes only one 'Organisation Name'.\nElse, Fail the test.\n\nNOTE TO TESTER:\na) This requirement mandates the Employment detail.\nb) The data element 'Document Author > Participant > Person or Organisation or Device > Person > Employment Detail > Employer Organisation > Organisation > Organisation Name' Represented via the following XPATH:\n/ClinicalDocument/author/assignedAuthor/assignedPerson/ext:asEmployment/ext:employerOrganization/asOrganizationPartOf/wholeOrganization/name\n","Document author includes only one 'employer organisation name'.","TBD",null,{"$f":"IF(H20=\"\",\"0\",IF(H20=\"Pass\",1,IF(H20=\"Fail\",0,IF(H20=\"TBD\",0,IF(H20=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D20)=48,H20=\"N/A\"),1,0)","v":0}]
["TS-Subj Care & Doc Auth","TC-PSMLDoc-11","027995 [DH-2926:2019]  \n\nDocument author organisation identifier\nWhen instantiating the document author, the document SHALL contain one and only one organisation identifier and that identifier is a Healthcare Provider Identifier for Organisation (HPI-O).\n","M",1,"Pass the test where the document contains one and only one value for 'Document Author' employer organisation entity identifier and that identifier is HPI-O (Healthcare Provider Identifier – Organisation).\nElse, Fail the test.  \n\nNOTE TO TESTER:\nThe data element 'Document Author > Participant > Person or Organisation or Device > Person > Employment Detail > Employer Organisation > Entity Identifier' Represented via the following XPATH:\n/ClinicalDocument/author/assignedAuthor/assignedPerson/ext:asEmployment/ext:employerOrganization/asOrganizationPartOf/wholeOrganization/<Entity Identifier>\n \n","The entity Identifier included in the 'Document Author' employer organisation has only one identifier and that identifier is a HPI-O.","TBD",null,{"$f":"IF(H21=\"\",\"0\",IF(H21=\"Pass\",1,IF(H21=\"Fail\",0,IF(H21=\"TBD\",0,IF(H21=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D21)=48,H21=\"N/A\"),1,0)","v":0}]
["TS-Subj Care & Doc Auth","END: TS-Subj Care & Doc Auth (Subject of Care and Document Author)"]
["TS-Part","START: TS-Part (Participant (Primary Healthcare provider as a Person or Organisation))"]
["TS-Part","TC-PSMLDoc-12","027990  [DH-2926:2019]  \n\nPrimary healthcare provider\nThe document SHALL contain at most one primary healthcare provider. The primary healthcare provider SHALL have PARTICIPANT (/ClinicalDocument/participant) instantiated with a typeCode of “PART” and a functionCode of “PCP”:\n• /ClinicalDocument/participant/@typeCode=“PART”\n• /ClinicalDocument/participant/functionCode/@code=“PCP”\n","O",1,"Mark the test N/A where the clinical document does not contain a Primary Healthcare Provider,\nElse, Pass the test where the clinical document contains only one Primary Healthcare Provider,\nElse, Fail the test.\n\nNOTE TO TESTER: \na) The primary healthcare provider is represented with a typeCode of “PART” and a functionCode of “PCP”, and has the following XPATH:\n• /ClinicalDocument/participant/@typeCode=“PART”\n• /ClinicalDocument/participant/functionCode/@code=“PCP”\nb) The primary healthcare provider is instantiated as a Person or an organisation, but not both.\n","The clinical document contains only one Primary Healthcare Provider.","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-Part","TC-PSMLDoc-13","028029  [DH-2926:2019]  \n\nPrimary healthcare provider role\nIf instantiating the primary healthcare provider (/ClinicalDocument/participant/functionCode/@code=“PCP”), the document MAY contain an absent value for the professional role. The professional role SHALL NOT be an abnormal value, represented as the following data element:\n• PARTICIPANT > Role\nRepresented in CDA using XPath notation as:\n• /ClinicalDocument/participant/associatedEntity/code.\n\nAdditional Notes\nRefer to Appendix B.4 Exceptional Values in the Core Level One Clinical Document Structured Content Specification for the permitted absent values. These absent values applies to primary healthcare provider role as a person and an organisation.\n","C",1,"CONDITION: A Primary Healthcare Provider has been provided and their Role has been identified by the use of an 'exceptional' value.\n\nPass the test where the primary healthcare provider's role has not been coded with an abnormal value. \nElse, Fail the test.\n\nNOTE TO TESTER: \na)  Exceptional values are described in Core Level One SCS 'Appendix B.4 Exceptional Values'. This describes \"Absent\" and \"Abnormal\" values, and provides a list of each.[DH-2579:2018]\nb) The primary healthcare provider is instantiated as a Person or an organisation, but not both.\n","The Primary Healthcare Provider's role does not contain a code with an abnormal value.","TBD",null,0,{"$f":"IF(AND(BGCol(D25)=48,H25=\"N/A\"),1,0)","v":0}]
["TS-Part","TC-PSMLDoc-14","028033 [DH-2926:2019]  \n\nPrimary Healthcare provider individual identifier\nIf instantiating the primary healthcare provider as a person, the document SHOULD contain a Healthcare Provider Identifier for Individual (HPI-I) as a person identifier represented as the following data element:\n• PARTICIPANT > PARTICIPANT > Entity Identifier\nRepresented in CDA using XPath notation as:\n•/ClinicalDocument/participant/associatedEntity/associatedPerson/ext:asEntityIdentifier","O",1,"Mark the test N/A if:\na) There is no primary healthcare provider as a person; or\nb) There is no entity identifier representing the personal identifier; or\nc)  The entity identifier representing the person is NOT a national identifier.\n\nPass the test where the 'primary healthcare provider as a person' entity identifier is a HPI-I (Healthcare Provider Identifier for Individual).\nElse, Fail the test.\n\nNOTE TO TESTER: The data element 'PARTICIPANT > PARTICIPANT > Entity Identifier' has the XPATH:\nClinicalDocument/participant[part_person]/associatedEntity/associatedPerson/<Entity Identifier>\n","The entity Identifier included for the 'primary healthcare provider as a person' is a valid HPI-I.","TBD",null,0,{"$f":"IF(AND(BGCol(D26)=48,H26=\"N/A\"),1,0)","v":0}]
["TS-Part","TC-PSMLDoc-15","028031  [DH-2926:2019]  \n\nPrimary healthcare provider organisation name\nIf instantiating the primary healthcare provider as a person, the document SHALL contain one and only one organisation name represented as the following data element:\n• PARTICIPANT > PARTICIPANT > PERSON OR ORGANISATION OR DEVICE > PERSON > EMPLOYMENT DETAIL > EMPLOYER ORGANISATION > ORGANISATION > Organisation Name\nRepresented in CDA using XPath notation as:\n•/ClinicalDocument/participant/associatedEntity/associatedPerson/ext:asEmployment/ext:employerOrganization/asOrganizationPartOf/wholeOrganization/name\n\nAdditional Notes\nImplementers should note that this requirement effectively makes the “Employment Detail” section mandatory.\n","C",1,"CONDITION: A Primary Healthcare Provider has been provided, and the provider is a Person.\n\nPass the test where, the 'primary healthcare provider as a person' includes only one value for 'Organisation Name'.\nElse, Fail the test.\n\nNOTE TO TESTER:\na) This requirement mandates the Employment Detail data group.\n\nb) The data element 'PARTICIPANT > PARTICIPANT > PERSON OR ORGANISATION OR DEVICE > PERSON > EMPLOYMENT DETAIL > EMPLOYER ORGANISATION > ORGANISATION > Organisation Name' has the XPATH:\n/ClinicalDocument/participant/associatedEntity/associatedPerson/ext:asEmployment/ext:employerOrganization/asOrganizationPartOf/wholeOrganization/name","The clinical document contains the Employment Detail data group, which contains one, and only one, Employer Organisation Name.","TBD",null,0,{"$f":"IF(AND(BGCol(D27)=48,H27=\"N/A\"),1,0)","v":0}]
["TS-Part","TC-PSMLDoc-16","028032  [DH-2926:2019]  \n\nPrimary healthcare provider organisation identifier\nIf instantiating the primary healthcare provider, the document SHOULD contain a Healthcare Provider Identifier for Organisation (HPI-O) as an organisation identifier.\n\nRepresented as the following data element if the primary healthcare provider is instantiated as a person:\n• PARTICIPANT > PARTICIPANT > PERSON OR ORGANISATION OR DEVICE > PERSON > EMPLOYMENT DETAIL > EMPLOYER ORGANISATION > ORGANISATION > Entity Identifier\n\nRepresented as the following data element if the primary healthcare provider is instantiated as an organisation:\n• PARTICIPANT > PARTICIPANT > Entity Identifier\n\nRepresented in CDA using XPath notation, if the primary healthcare provider is instantiated as a person, as:\n•/ClinicalDocument/participant/associatedEntity/associatedPerson/ext:asEmployment/ext:employerOrganization/asOrganizationPartOf/wholeOrganization/ext:asEntityIdentifier\n\nRepresented in CDA using XPath notation, if the primary healthcare provider is instantiated as an organisation, as:\n•/ClinicalDocument/participant/associatedEntity/scopingOrganization/asOrganizationPartOf/wholeOrganization/ext:asEntityIdentifier\n","O",1,"Mark the test N/A if:\na) There is no Primary healthcare provider.\nb) There is no Primary healthcare provider organisation identifier. \nc)  The identifier representing the organisation is NOT a national identifier.\n\nPass the test where the Primary healthcare provider organisation identifier contains a HPI-O (Healthcare Provider Identifier for Organisation).\nElse, Fail the test.\n\nNOTE TO TESTER:\na) The data element for 'primary healthcare provider as a person'\n'PARTICIPANT > PARTICIPANT > PERSON OR ORGANISATION OR DEVICE > PERSON > EMPLOYMENT DETAIL > EMPLOYER ORGANISATION > ORGANISATION > Entity Identifier' has the XPATH:\n/ClinicalDocument/participant/associatedEntity/associatedPerson/ext:asEmployment/ext:employerOrganization/asOrganizationPartOf/wholeOrganization/ext:asEntityIdentifier\n\nb) The data element for 'primary healthcare provider as an organisation'\n'PARTICIPANT > PARTICIPANT > Entity Identifier' has the XPATH:\n/ClinicalDocument/participant/associatedEntity/scopingOrganization/asOrganizationPartOf/wholeOrganization/ext:asEntityIdentifier","The Primary healthcare provider organisation identifier contains a HPI-O.","TBD",null,0,{"$f":"IF(AND(BGCol(D28)=48,H28=\"N/A\"),1,0)","v":0}]
["TS-Part","TC-PSMLDoc-17","027997 [DH-2926:2019]  \n\nPrimary healthcare provider organisation workplace address\nIf instantiating the primary healthcare provider, the document SHALL contain one and only one value for healthcare provider organisation’s workplace address and that address is an Australian address.\nRepresented as the following data element if the primary healthcare provider is instantiated as a person:\n• PARTICIPANT > PARTICIPANT > PERSON OR ORGANISATION OR DEVICE > PERSON > EMPLOYMENT DETAIL > EMPLOYER ORGANISATION > ORGANISATION > ADDRESS\nRepresented as the following data element if the primary healthcare provider is instantiated as an organisation:\n• PARTICIPANT > PARTICIPANT > ADDRESS\nRepresented in CDA using XPath notation, if the primary healthcare provider is instantiated as a person, as:\n•/ClinicalDocument/participant/associatedEntity/associatedPerson/ext:asEmployment/ext:employerOrganization/asOrganizationPartOf/wholeOrganization/addr\nRepresented in CDA using XPath notation, if the primary healthcare provider is instantiated as an organisation, as:\n• /ClinicalDocument/participant/associatedEntity/addr\n\nAdditional Notes\nImplementers should note that this requirement effectively makes the “Employment Detail” section mandatory.\n","C",1,"CONDITION: : A Primary Healthcare Provider has been provided.\nPass the test, where the document contains only one value for healthcare provider organisation’s workplace address and that address is an Australian workplace address.\nElse, Fail the test.\n\nNOTE TO TESTER:\na) The data element for 'primary healthcare provider as a person'\n'PARTICIPANT > PARTICIPANT > PERSON OR ORGANISATION OR DEVICE > PERSON > EMPLOYMENT DETAIL > EMPLOYER ORGANISATION > ORGANISATION > ADDRESS' has the XPATH:\n/ClinicalDocument/participant/associatedEntity/associatedPerson/ext:asEmployment/ext:employerOrganization/asOrganizationPartOf/wholeOrganization/addr\n\nb) The data element for 'primary healthcare provider as an organisation'\n'PARTICIPANT > PARTICIPANT > ADDRESS' has the XPATH:\n/ClinicalDocument/participant/associatedEntity/scopingOrganization/asOrganizationPartOf/wholeOrganization/addr\n\nc) This requirement mandates the Employment Detail data group.\n\nd)The primary healthcare provider is instantiated as a Person or an organisation, but not both.","The primary healthcare provider organisation has only one workplace address, and that address is an Australian address.","TBD",null,0,{"$f":"IF(AND(BGCol(D29)=48,H29=\"N/A\"),1,0)","v":0}]
["TS-Part","END: TS-Part (Participant (Primary Healthcare provider as a Person or Organisation))"]
["TS-C Doc body","START: TS-C Doc body (Clinical document body)"]
["TS-C Doc body","TC-PSMLDoc-18","028068  [DH-2926:2019]  \n\nInclusion of PDF attachment\nThe document SHALL contain one and only one PSML document that reflects the original PSML document.\nThe PSML document SHALL be a PDF packaged attachment.\n\nAdditional Notes\nUntil the PSML can be represented with structured data it should only be made available in the My Health Record system in PDF format to ensure that the presentation and rendering of the data is as expected by the authoring healthcare provider.\nThe PDF file is expected to be viewable by the healthcare individual and any healthcare provider that is a My Health Record participant. For example, the PSML document PDF files should not have any of these features:\n- Encryption\n- Password protection\n- Printing or copying restriction\n- Embedded fonts (as not all PDF viewers support them)\n","M",1,"Pass the test where there is only one attached document that reflects the original PSML and that attached document is a PDF.\nElse, Fail the test.\n\nNOTE TO TESTER: The document MAY contain other attachments (e.g. logos) that do not contain a PSML.","Only one attached document contains the original PSML, and that attachment is a PDF.","TBD",null,{"$f":"IF(H32=\"\",\"0\",IF(H32=\"Pass\",1,IF(H32=\"Fail\",0,IF(H32=\"TBD\",0,IF(H32=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D32)=48,H32=\"N/A\"),1,0)","v":0}]
[null,null,null,"M",2,"Fail the test where the PSML PDF document contains any of the following features:\n- Encryption\n- Password protection\n- Printing or copying restriction\n- Embedded fonts \nElse, Pass the test.","The PSML PDF document does not contain any of the following features:\n- Encryption\n- Password protection\n- Printing or copying restriction\n- Embedded fonts ","TBD",null,{"$f":"IF(H33=\"\",\"0\",IF(H33=\"Pass\",1,IF(H33=\"Fail\",0,IF(H33=\"TBD\",0,IF(H33=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D33)=48,H33=\"N/A\"),1,0)","v":0}]
["TS-C Doc body","TC-PSMLDoc-19","028069[DH-2926:2019]  \n\nReferencing PSML PDF attachment\nThe document SHALL contain the PDF (see requirement 028068) in ENCAPSULATED DATA with\n“templateID/@root=“1.2.36.1.2001.1001.101.102.16883”\nunder section with\n“templateID/@root=“1.2.36.1.2001.1001.101.101.16886”.\n\nAdditional Notes\nThe document may contain other attachments (e.g. logos) that do not contain a PSML or any other medicines information.\nThe requirement applies only to attachments that include PSML medicines.\n","M",1,"Pass the test where the PSML PDF attachment is contained within the 'Encapsulated Data' component with root OID (Object Identifier) 1.2.36.1.2001.1001.101.102.16883 included under the 'Section' data component with root OID 1.2.36.1.2001.1001.101.101.16886.\nElse, Fail the test. \n\nNOTE TO TESTER: The data element 'SECTION > ENCAPSULATED DATA' has the XPATH: ClinicalDocument/component/structuredBody/component[clocd]/section/entry\nThe document may contain other attachments (e.g. logos) that do not contain a PSML or any other medicines information.\n\n","The PSML PDF attachment is represented in ENCAPSULATED DATA with “templateId/@root=“1.2.36.1.2001.1001.101.102.16883” under section with “templateId/@root=“1.2.36.1.2001.1001.101.101.16886”.\n","TBD",null,{"$f":"IF(H34=\"\",\"0\",IF(H34=\"Pass\",1,IF(H34=\"Fail\",0,IF(H34=\"TBD\",0,IF(H34=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D34)=48,H34=\"N/A\"),1,0)","v":0}]
["TS-C Doc body","TC-PSMLDoc-20","027998 [DH-2926:2019]  \n\nPDF attachment MIME type\nWhen instantiating a PDF attachment, the MIME type of the attachment SHALL be of .pdf application/pdf MIME type.\n\nAdditional Notes\nThis requirement overrides Requirement 023741 in the Clinical Documents Common Conformance Profile.\n","M",1,"Pass the test where the Pharmacist Shared Medicines List clinical document contains a PDF attachment that has been represented as a .pdf application/pdf MIME type.\nElse, Fail the test.\n\nNOTE TO TESTER: The following XML is an example of the usage of .pdf application/pdf MIME type:\n\n                      <observationMedia ID=\"asthma_fact_sheet_enPDF\" classCode=\"OBS\" moodCode=\"EVN\" >\n                            <id root=\"87f37a45-76ec-4755-b755-fbede86aa8aa\" />\n                            <value mediaType=\"application/pdf\"\n                                integrityCheck=\"bWB+y8fr5emKPqKkOtjdfdyMPFg=\"\n                                integrityCheckAlgorithm=\"SHA-1\">\n                                <reference value=\"asthma_fact_sheet_en.pdf\" />\n                            </value>\n                        </observationMedia>\n","PSML clinical document contains a PDF attachment that has been represented as a .pdf application/pdf MIME type.","TBD",null,{"$f":"IF(H35=\"\",\"0\",IF(H35=\"Pass\",1,IF(H35=\"Fail\",0,IF(H35=\"TBD\",0,IF(H35=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D35)=48,H35=\"N/A\"),1,0)","v":0}]
["TS-C Doc body","END: TS-C Doc body (Clinical document body) "]
["TS-CC","START:  TS-CC (Conformance criteria)"]
["TS-CC","TC-PSMLDoc-21","027987 [DH-2926:2019]  \n\nLevels of conformance\nA PSML sent to the My Health Record system SHALL conform to the requirements for conformance level 1A as defined in the Common Conformance Profile for Clinical Documents.\n","M",1,"Pass the test, where the PSML clinical document shows conformance to level 1A by passing the test cases set out in the Conformance Test Specification for Authoring Systems  [NEHTA-2209:2017].\nElse, Fail the test.\n\nNOTE TO TESTER: \nThe requirements for conformance level 1A are defined in the Common Conformance Profile for Clinical Documents [DH-2481:2017] and are tested in the Conformance Test Specification for Authoring Systems  [NEHTA-2209:2017]. Please note that the test cases within the Conformance Test Specification for Authoring Systems  [NEHTA-2209:2017] are based on v1.6 of the Common Conformance Profile, which mandates that conformance level 1A clinical documents have a <title> element. The requirement for this element has been removed in the current Common Conformance Profile (v1.7). The Conformance Test Specification for Authoring Systems will be updated to align with the latest Common Conformance Profile, and published, at a later date.\n","The PSML clinical document to be sent to the My Health Record system meets the requirements for conformance level 1A.\n","TBD",null,{"$f":"IF(H38=\"\",\"0\",IF(H38=\"Pass\",1,IF(H38=\"Fail\",0,IF(H38=\"TBD\",0,IF(H38=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D38)=48,H38=\"N/A\"),1,0)","v":0}]
["TS-CC","TC-PSMLDoc-22","028034 [DH-2926:2019]  \n\nContent of PSML\nThe producing system SHALL have the capability to include in the document all medicines the patient record states an individual is known to be taking.\n\nAdditional Notes\nThis includes prescription medicines, non-prescription medicines and complimentary medicines.\n","M",1,"Pass the test where:\nThe Pharmacist Shared Medicines List (PSML) document contains all the medications recorded in the producing system/s patient record.\nElse, Fail the test.\n\nNOTE TO TESTER: \na) The list of medications can include prescribed medicines, non-prescribed (over-the-counter) medicines and supplements, and complimentary medicines, whether or not they were prescribed or dispensed by the reporting pharmacist.\nb) This test can only be performed by comparing the PSML document to the information contained within the local system/s (observed session).\n","All the medications recorded for the Subject of Care within the producing system/s are included in the PSML document.","TBD",null,{"$f":"IF(H39=\"\",\"0\",IF(H39=\"Pass\",1,IF(H39=\"Fail\",0,IF(H39=\"TBD\",0,IF(H39=\"N/A\",1)))))","v":0},{"$f":"IF(AND(BGCol(D39)=48,H39=\"N/A\"),1,0)","v":0}]
["TS-CC","END: TS-CC (Conformance criteria)"]
[null,null,null,null,null,null,null,"TBD","Total Steps",{"$f":"SUM(J42:J43)","v":21}]
[null,null,null,null,null,null,null,"Fail","Tests Not Started, Failed or TBD",{"$f":"COUNTIF(J8:J39,\"0\")","v":21}]
[null,null,null,null,null,null,null,"N/A","Tests Passed or N/A",{"$f":"COUNTIF(J8:J36,\"1\")","v":0}]
[null,null,null,null,null,null,null,"Pass","%Passed or N/A",{"$f":"SUM(J43/J41)","v":0}]

{"sheet":"Process models","index":8,"n_rows":80,"n_cols":6,"rows_kept":80,"cut":false,"hidden":false,"merged":[[61,2,61,4],[61,6,61,8],[10,1,10,5],[11,2,11,5],[9,1,9,5],[5,2,5,5],[4,1,4,5],[6,1,6,5],[7,1,7,4],[8,2,8,4]]}
[]
[null,"Process models for Pharmacist Shared Medicines List"]
[null,"The process models used in this PSML 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."]
[]
[null,"The tables in this document list process requirements, which are conformance requirements related to the following business processes:\n"]
[null,null,"• Author a new Pharmacist Shared Medicines List\n• Remove a Pharmacist Shared Medicines List\n\n"]
[null,"Some process requirements are also related to the content of a Pharmacist Shared Medicines List.  Conformance requirements that are solely related to the content of a Pharmacist Shared Medicines List, and are unrelated to the process, are not listed here. "]
[null,"The requirements specifications referenced here are:"]
[null,null,"1. Pharmacist Shared Medicines List - Conformance Profile v1.0 [DH-2637:2018] \n2. PCEHR Connecting Systems - Conformance Requirements v1.5 [NEHTA-1297:2012]\n3. Clinical Documents - Common Conformance Profile_v1.7 [DH-2481:2017]\n4. Clinical Documentation - CDA Rendering Specification v1.0 [NEHTA-1199:2012]\n5. Common CDA - CDA Package v1.0 [NEHTA-1229:2011]\n\n"]
[null,"In addition, generic process models for My Health Record Connecting Systems are listed in PCEHR Connecting Systems - Use Cases v1.1 [NEHTA-1298:2012]."]
[null,"The test cases applying to each of the process tasks are also listed here and include the following:"]
[null,null,"1.\"TC-PSMLProc\" are listed in the FS-PSMLProc feature set within this conformance test specification.\n2. \"TC-PSMLDoc\" are listed in the FS-PSMLDoc feature set within this conformance test specification.\n3. \"UC.CIS\" relate to business processes for PCEHR connecting systems and are listed in the PCEHR Connecting Systems - Conformance Test Specification [NEHTA-1299:2012].\n\n"]
["THIS HEADER CAN BE COLLAPSED BY CLICKING THE '-' SYMBOL ON THE LEFT."]
[null,"A. Author a new Pharmacist Shared Medicines List (business process)"]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[null,null,"A1: Author a clinical document"]
[]
[null,null," "]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[null,"#","PROCESS ITEM (AND TYPE)","DESCRIPTION","PROCESS REQUIREMENTS","Test Cases"]
[null,"A1","Author a clinical document (task)","The Pharmacist Shared Medicines List is authored by a healthcare provider. ","\nTask A1.1 - Pharmacist Shared Medicines List - Conformance Profile v1.0:\nPharmacist Shared Medicines List clinical documents MAY be produced by:\n• clinical information systems (CIS); and\n• contracted service provider (CSP) systems.\n\n Pharmacist Shared Medicines List clinical documents SHALL NOT be produced by \n• registered consumer portals or \n• registered provider portals or \n• registered repositories.\n\nDose Administration Aids\nSoftware for Dose Administration Aids SHALL have the capability to include all packed and non-packed medicines an individual is known to be taking.\n\nInclusion of optional elements in clinical document\nIf the software has information in a form that may be used to populate an optional data component then the software SHALL allow the inclusion of that data component in a clinical document.\n\nTask A1.2 - Author clinical document\n•  There are no process requirements within this task.\n\nSee the requirements in the PCEHR usability recommendations. \nNote: conformance to PCEHR usability requirements is not mandatory for software that accesses the My Health Record System.\n\nTask A1.3 - Render clinical document\nNEHTA_1199_2012_ClinicalDocumentation_CDARenderingSpecification_v1.0:\n• CDA-RS 69: Authoring Systems SHALL produce documents that render correctly to the Author when processed by a compliant Rendering System.\n","Task A1.1 - Allowed Producers\nTC-PSMLProc-01 (2.2 Objects of conformance),\nTC-PSMLProc-02 (2.2 Objects of conformance),\nTC-PSMLProc-03,\nTC-PSMLProc-04.\n\nTask A1.2 - Author clinical document\n• There are no process test cases for this task.\n\nTask A1.3 - Render clinical document\n• CDAR-RS-069"]
[null,"A2","UC.CIS.201 Upload a clinical document (sub process)","The Pharmacist Shared Medicines List is uploaded to the My Health Record system.  \n\n","Task A2.1: Pharmacist Shared Medicines List - Conformance Profile v1.0:\n • 027987 - A PCML sent to the My Health Record system SHALL conform to the requirements for conformance level 1A as defined in the Common Conformance Profile for Clinical Documents.\n\nTask A2.2: Clinical Documents - Common Conformance Profile v1.7:\n023730, 023732, 023733 - Approval of the clinical document.\n\nTask A2.3: Create CDA Package\nClinical documents_CDAPackage_v1.0:\n•  All requirements within this specification.\n\nTask A2.4: PCEHR Connecting Systems - Use Cases v1.1:\n• UC.CIS.201 - Upload a Clinical Document.","Task A2.1 - Pharmacist Shared Medicines List - Conformance level:\n • 027987\n\nTask A2.2 - Clinical documents - Common conformance profile:\n•  023730, 023732, 023733 (Tests are covered in Authoring CTS & CDA Package CTS)\n\nTask A2.3 - Create CDAPackage\n•  All requirements within this specification\n\nTask A2.4 - Upload Document\n• UC.CIS.201 \n"]
[]
[]
[null,"B. Remove a Pharmacist Shared Medicines List (business process)"]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[null,"#","PROCESS ITEM (AND TYPE)","DESCRIPTION","PROCESS REQUIREMENTS","Test Cases"]
[null,"B1","Select a clinical document to remove.\n","The Pharmacist Shared Medicines List to be removed is selected. ","There are no requirements for this task.","None"]
[null,"B2","UC.CIS.203 Remove a clinical document (sub process)\n","The Pharmacist Shared Medicines List is removed from the My Health Record system.  ","PCEHR Connecting Systems - Use Cases v1.1:\n UC.CIS.203 - Pharmacist Shared Medicines List is removed successfully from the My Health Record system.","Task B2.1- Remove Document UC.CIS.203."]
[]
[]
[null,"C. Supersede a Pharmacist Shared Medicines List (business process)"]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[]
[null,"#","PROCESS ITEM (AND TYPE)","DESCRIPTION","PROCESS REQUIREMENTS","Test Cases"]
[null,"A1","Author a clinical document (Sub-process)","The Pharmacist Shared Medicines List is authored by a healthcare provider. ","\nTask A1.1 - Pharmacist Shared Medicines List - Conformance Profile:\nPharmacist Shared Medicines List clinical documents MAY be produced by:\n• clinical information systems (CIS); and\n• contracted service provider (CSP) systems.\n\nPharmacist Shared Medicines List clinical documents SHALL NOT be produced by \n• registered consumer portals or \n• registered provider portals or \n• registered repositories.\n\nDose Administration Aids\nSoftware for Dose Administration Aids SHALL have the capability to include all packed and non-packed medicines an individual is known to be taking.\n\nInclusion of optional elements in clinical document\nIf the software has information in a form that may be used to populate an optional data component then the software SHALL allow the inclusion of that data component in a clinical document.\n\nTask A1.2 - Author clinical document\n•  There are no process requirements within this task\n\nTask A1.3 - Render clinical document\nClinicalDocumentation_CDARenderingSpecification_v1.0:\n• CDA-RS 67: Authoring Systems SHALL produce documents that render correctly to the Author when processed by a compliant Rendering System.\n\nSee the requirements in the PCEHR usability recommendations. \nNote: conformance to PCEHR usability requirements is not mandatory for software that accesses the My Health Record System.\n","Task A1.1 - Allowed Producers\nTC-PSMLProc-01 (2.2 Objects of conformance),\nTC-PSMLProc-02 (2.2 Objects of conformance),\nTC-PSMLProc-03,\nTC-PSMLProc-04.\n\nTask A1.2 - Author clinical document\n• There are no process test cases for this task\n\nTask A1.3 - Render clinical document\n• CDAR-RS-067"]
[null,"C2","Supersede a clinical document (Sub process)","The Pharmacist Shared Medicines List clinical document is superseded in the My Health Record system.  \n\n\n","Task C2.1 - Pharmacist Shared Medicines List - Conformance level:\n • 027987 - A PSML sent to the My Health Record system SHALL conform to the requirements for conformance level 1A as defined in the Common Conformance Profile for Clinical Documents.\n\nTask C2.2 - Create CDA Package\nClinical documents_CDAPackage_v1.0\n•  All requirements within this specification\n\nTask C2.3 - Supersede document\nPCEHR Connecting Systems - Use Cases v1.1:\n•  UC.CIS.202: Supersede a clinical document\n","Task C2.1 - Pharmacist Shared Medicines List - Conformance level:\n • 027987\n\nTask C2.2 - Create CDA Package\n• Test cases for CDA Packaging\n\nTask C2.3 - Supersede document\n•  Test cases for UC.CIS.202\n\n"]

{"sheet":"TSR","index":9,"n_rows":26,"n_cols":9,"rows_kept":26,"cut":false,"hidden":false,"merged":[[21,1,21,5],[14,1,14,5],[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],[7,1,7,2]]}
[]
[null,null,"TEST SUMMARY REPORT\n"]
[]
[null,"Software developer organisation:",null,"Please complete"]
[null,"Software name:",null,"Please complete"]
[null,"Software version:",null,"Please complete"]
[null,"Software description:",null,"Please complete"]
[null,"Testing location address:",null,"Please complete"]
[null,"Date(s) of testing:",null,"Please complete"]
[null,"Name of person(s) conducting tests:",null,"Please complete"]
[null,"Operating System/Environment Configuration (name and version)",null,"Optional."]
[null,"Additional software tools and versions not subject to testing used \n(e.g. web browser)",null,"Optional."]
[null,null,null,null,null,null,null,null," "]
[]
[null,"THIS SECTION DOES NOT NEED TO BE MANUALLY FILLED IN - IT WILL BE AUTOMATICALLY CALCULATED."]
[null,null,"Scenario worksheet"," Total % Tests Passed or N/A","Number of Scenarios","Scenarios Complete"]
[null,1,"TP-NewDoc",{"$f":"'TP-NewDoc'!F78","v":0},{"$f":"'TP-NewDoc'!C79","v":2},{"$f":"'TP-NewDoc'!C80","v":0}]
[null,2,"TP-Supersede",{"$f":"'TP-Supersede'!F45","v":0},{"$f":"'TP-Supersede'!C46","v":1},{"$f":"'TP-Supersede'!C47","v":0}]
[null,3,"TP-Remove",{"$f":"'TP-Remove'!F20","v":0},{"$f":"'TP-Remove'!C21","v":1},{"$f":"'TP-Remove'!C22","v":0}]
[]
[]
[null,"THIS SECTION DOES NOT NEED TO BE MANUALLY FILLED IN - IT WILL BE AUTOMATICALLY CALCULATED USING A MACRO. PRESS <F9> IF YOU HAVE MACROS DISABLED."]
[null,null,"Test Case worksheet ","Test % Success Rate","Number of Tests","Number of N/A test results for mandatory tests"]
[null,1,"FS-PSMLDoc",{"$f":"'FS-PSMLDoc'!J44","v":0},{"$f":"'FS-PSMLDoc'!J41","v":21},{"$f":"SUM('FS-PSMLDoc'!K:K)","v":0}]
[null,2,"FS-PSMLProc",{"$f":"'FS-PSMLProc'!J17","v":0},{"$f":"'FS-PSMLProc'!J14","v":4},{"$f":"SUM('FS-PSMLProc'!K:K)","v":0}]
[null,{"$f":"IF(OR(ISERROR(F24),ISERROR(F25)),\"WARNING: You must enable macros for this workbook.\",IF(SUM(F24:F25)>0,\"WARNING: A test result of N/A (not applicable) has been selected for one or more mandatory test cases. The only appropriate test results for a mandatory test are Pass or Fail. Please review and update the test results.\",\"\"))","v":""}]

{"sheet":"Traceability","index":10,"n_rows":48,"n_cols":14,"rows_kept":48,"cut":false,"hidden":false,"merged":[[28,2,46,2]]}
[]
[null,"Traceability Reference","Related Specification","Conformance Requirement","Test Cases","Feature Set & Test Case Reference","Test Case Exists?","Priority","Test Steps","TP-Newdoc-01","TP-Newdoc-02","TP-Supersede-01","TP-Remove-01","Notes"]
[null,"TR-PSMLCTS-01",null,"027999 - Document type","TC-PSMLDoc-01","FS-PSMLDoc","P","M",1,"P","P","P"]
[null,"TR-PSMLCTS-02",null,"028000 - Clinical document template identifier","TC-PSMLDoc-02","FS-PSMLDoc","P","M",1,"P","P","P"]
[null,"TR-PSMLCTS-03",null,"027988 - Subject of Care identifier ","TC-PSMLDoc-03","FS-PSMLDoc","P","M",1,"P","P","P"]
[null,"TR-PSMLCTS-04",null,"027991 - Subject of care address","TC-PSMLDoc-04","FS-PSMLDoc","P","M",1,"P","P","P"]
[null,"TR-PSMLCTS-05",null,"027989 - Document Author","TC-PSMLDoc-05","FS-PSMLDoc","P","M",1,"P","P","P"]
[null,"TR-PSMLCTS-06",null,"028630 - Document Author Entity Identifier value","TC-PSMLDoc-06","FS-PSMLDoc","P","M",1,"P","P","P"]
[null,"TR-PSMLCTS-07",null,"024980 - Confirm individual electronic communication details to be included","TC-PSMLDoc-07","FS-PSMLDoc","O","-",0,null,null,null,null,"No test case is defined for this requirement."]
[null,"TR-PSMLCTS-08",null,"024982 - Confirm individual address to be included","TC-PSMLDoc-08","FS-PSMLDoc","O","-",0,null,null,null,null,"No test case is defined for this requirement."]
[null,"TR-PSMLCTS-09",null,"027993 - Document author workplace address","TC-PSMLDoc-09","FS-PSMLDoc","P","M",1,"P","P","P"]
[null,"TR-PSMLCTS-10",null,"027992 - Document author organisation name","TC-PSMLDoc-10","FS-PSMLDoc","P","M",1,"P","P","P"]
[null,"TR-PSMLCTS-11",null,"027995 - Document author organisation identifier","TC-PSMLDoc-11","FS-PSMLDoc","P","M",1,"P","P","P"]
[null,"TR-PSMLCTS-12",null,"027990 - Primary healthcare provider","TC-PSMLDoc-12","FS-PSMLDoc","P","O",1,"P","P","P"]
[null,"TR-PSMLCTS-13","DH-2926:2019","028029 - Primary healthcare provider role","TC-PSMLDoc-13","FS-PSMLDoc","P","C",1,"P","P","P"]
[null,"TR-PSMLCTS-14",null,"028033 - Primary Healthcare provider individual identifier","TC-PSMLDoc-14","FS-PSMLDoc","P","O",1,"P","P","P"]
[null,"TR-PSMLCTS-15",null,"028031 - Primary healthcare provider organisation name","TC-PSMLDoc-15","FS-PSMLDoc","P","C",1,"P","P","P"]
[null,"TR-PSMLCTS-16",null,"028032 - Primary healthcare provider organisation identifier","TC-PSMLDoc-16","FS-PSMLDoc","P","O",1,"P","P","P"]
[null,"TR-PSMLCTS-17",null,"027997 -Primary healthcare provider organisation workplace address","TC-PSMLDoc-17","FS-PSMLDoc","P","C",1,"P","P","P"]
[null,"TR-PSMLCTS-18",null,"028068  - Inclusion of PDF attachment","TC-PSMLDoc-18","FS-PSMLDoc","P","M",2,"P","P","P"]
[null,"TR-PSMLCTS-19",null,"028069 - Referencing PSML PDF attachment","TC-PSMLDoc-19","FS-PSMLDoc","P","M",1,"P","P","P"]
[null,"TR-PSMLCTS-20",null,"027998 - PDF attachment MIME type","TC-PSMLDoc-20","FS-PSMLDoc","P","M",1,"P","P","P"]
[null,"TR-PSMLCTS-21",null,"027987 - Levels of conformance","TC-PSMLDoc-21","FS-PSMLDoc","P","M",1,"P","P","P"]
[null,"TR-PSMLCTS-22",null,"028034 - Content of PSML","TC-PSMLDoc-22","FS-PSMLDoc","P","M",1,"P","P","P"]
[null,"TR-PSMLCTS-23",null,"028153 - Allowable types of conformance","TC-PSMLProc-01","FS-PSMLProc","P","O",1,"P","P","P"]
[null,"TR-PSMLCTS-24",null,"024569 - Disallowed types of producers ","TC-PSMLProc-02","FS-PSMLProc","P","M",1,"P","P","P"]
[null,"TR-PSMLCTS-25",null,"028154 - Dose Administration Aids","TC-PSMLProc-03","FS-PSMLProc","P","C",1,"P","P","P"]
[null,"TR-PSMLCTS-26","DH-2481:2017","27732 - Inclusion of optional elements in clinical document","TC-PSMLProc-04","FS-PSMLProc","P","C",1,"P","P","P"]
[null,"TR-PSMLCTS-27","NEHTA-1299:2012","019100 (UC.CIS.201) - CIS uses IHI","PCEHR_CIS_019100","UC.CIS.201","-","-","-","P"]
[null,"TR-PSMLCTS-28",null,"019429 (UC.CIS.201) - CIS uses HPI-I","PCEHR_CIS_019429","UC.CIS.201","-","-","-","P"]
[null,"TR-PSMLCTS-29",null,"019042 (UC.CIS.201) - Withdraw Consent","PCEHR_CIS_019042","UC.CIS.201","-","-","-","P","P"]
[null,"TR-PSMLCTS-30",null,"017842a (UC.CIS.201) - CIS Identifies Uploads","PCEHR_CIS_017842a","UC.CIS.201","-","-","-","P"]
[null,"TR-PSMLCTS-31",null,"017841a (UC.CIS.201) - CIS Retains Clinical info","PCEHR_CIS_017841a","UC.CIS.201","-","-","-","P"]
[null,"TR-PSMLCTS-32",null,"017839 (UC.CIS.201) - Clinical Document explicit command","PCEHR_CIS_017839","UC.CIS.201","-","-","-","P"]
[null,"TR-PSMLCTS-33",null,"019378 (UC.CIS.201) - CIS Audit","PCEHR_CIS_019378","UC.CIS.201","-","-","-","P"]
[null,"TR-PSMLCTS-34",null,"019100 (UC.CIS.202) - CIS uses IHI.","PCEHR_CIS_019100","UC.CIS.202","-","-","-",null,null,"P"]
[null,"TR-PSMLCTS-35",null,"019429 (UC.CIS.202) - CIS uses HPI-I.","PCEHR_CIS_019429","UC.CIS.202","-","-","-",null,null,"P"]
[null,"TR-PSMLCTS-36",null,"019042 (UC.CIS.202) - Withdraw Consent.","PCEHR_CIS_019042","UC.CIS.202","-","-","-",null,null,"P"]
[null,"TR-PSMLCTS-37",null,"017842b (UC.CIS.202)  - CIS Identifies Uploads.","PCEHR_CIS_017842b","UC.CIS.202","-","-","-",null,null,"P"]
[null,"TR-PSMLCTS-38",null,"017841b (UC.CIS.202)  - CIS Retains Clinical info.","PCEHR_CIS_017841b","UC.CIS.202","-","-","-",null,null,"P"]
[null,"TR-PSMLCTS-39",null,"017839 (UC.CIS.202)  - CIS Clinical Document Check.","PCEHR_CIS_017839","UC.CIS.202","-","-","-",null,null,"P"]
[null,"TR-PSMLCTS-40",null,"019378 (UC.CIS.202) - CIS Audit.","PCEHR_CIS_019378","UC.CIS.202","-","-","-",null,null,"P"]
[null,"TR-PSMLCTS-41",null,"018338 (UC.CIS.202) - CIS Supersede.","PCEHR_CIS_018338","UC.CIS.202","-","-","-",null,null,"P"]
[null,"TR-PSMLCTS-42",null,"019100 (UC.CIS.203)  - CIS uses IHI","PCEHR_CIS_019100","UC.CIS.203","-","-","-",null,null,null,"P"]
[null,"TR-PSMLCTS-43",null,"017887 (UC.CIS.203) - Identify remove documents","PCEHR_CIS_017887","UC.CIS.203","-","-","-",null,null,null,"P"]
[null,"TR-PSMLCTS-44",null,"019377 (UC.CIS.203)- Remove documents","PCEHR_CIS_019377","UC.CIS.203","-","-","-",null,null,null,"P"]
[null,"TR-PSMLCTS-45",null,"019378 (UC.CIS.203) - CIS Audit","PCEHR_CIS_019378","UC.CIS.203","-","-","-",null,null,null,"P"]
[null,"TR-PSMLCTS-46","DH-2209:2017","All the mandatory and applicable conditional tests in Conformance Test Specification for CDA® Authoring.","All the mandatory and applicable conditional tests","FS-Doc, FS-Narr, Fs-Types, FS-Auth","-","-","-","P","P","P"]

{"sheet":"References","index":11,"n_rows":18,"n_cols":4,"rows_kept":18,"cut":false,"hidden":false,"merged":[]}
[]
[]
[null,"References and Related Documents"]
[null,"Identifier","Date","Name"]
[null,"DH-2926:2019","NOT YET PUBLISHED","Pharmacist Shared Medicines List - MHR Conformance Profile v1.1.1"]
[null,"DH-2579:2018","2019-08-26","Core Level One Clinical Document - Structured Content Specification v1.1 "]
[null,"DH-2580:2018","2019-08-26","Core Level One Clinical Document - CDA® Implementation Guide v1.1 "]
[null,"DH-2481:2017","2017-12-21","DH-2481:2017 Clinical Documents - Common Conformance Profile v1.7"]
[null,"NEHTA-1299:2012","2012-09-27","NEHTA-1299:2012 PCEHR Connecting Systems - Conformance Test Specification v1.6"]
[null,"NEHTA-1298:2012","2012-09-06","NEHTA-1298:2012 PCEHR Connecting Systems - Use Cases v1.1"]
[null,"NEHTA-1297:2012","2012-09-06","NEHTA-1297:2012 PCEHR Connecting Systems - Conformance Requirements v1.5"]
[null,"NEHTA-2065:2015","2015-07-15","NEHTA-2065:2015 Clinical Documents - Conformance Test Specification for CDA® Packaging v1.5"]
[null,"DH-2209:2017","2017-06-16","DH-2209:2017 Conformance Test Specification for Authoring systems v1.0"]
[null,"HL7CDAR2","2004-12-21","HL7CDAR2 - HL7 Clinical Document Architecture, Release 2"]
[null,"NEHTA-0794:2011","2011-07-20","NEHTA-0794:2011 Participation Data Specification - Data Specification v3.2"]
[null,"NEHTA-1199:2012","2012-03-07","NEHTA-1199:2012 Clinical Documents - CDA® Rendering Specification v1.0"]
[null,"NEHTA-1229:2011","2011-11-29","NEHTA-1229:2011 Clinical Documents - CDA® Package v1.0"]
[null,"ISO21090","2011-02-15","ISO 21090:2011 Health informatics -- Harmonized data types for information interchange - https://www.iso.org"]