Medical Triage Service

 

Standards and specifications

General requirements

Cyber security

The service must demonstrate ability to effectively achieve mitigation strategies in line with ‘Essential 8’.

Privacy

The service must demonstrate adherence to relevant federal, state or territory privacy legislation for example, the Privacy Act 1988 (Federal) or Health Records and Information Privacy Act 2002 (NSW).

The applicable federal legislation is the Privacy Act 1988.

Details of the relevant state and territory legislations are contained under the State and territory requirements section below.

Core requirements

Standards for identification

The service must:

• support the use of Healthcare Identifiers in accordance with the Healthcare Identifiers Act 2010  
• support data capture and storage of unique device identification of medical devices as defined within AS ISO/IEC 15459.4:2023 Information technology — Automatic identification and data capture techniques — Unique identification, Part 4: Individual products and product packages.

The service should:  

• be able to discover and validate Individual Healthcare Identifiers (IHI) via the Healthcare Identifier (HI) Service Business-2-Business web services
• utilise Individual Healthcare Identifiers (IHIs) to integrate and link records into the local patient record
• support adherence to Patient Identification best practices as outlined by the Australia Commission on Safety and Quality in Health Care.

Australian Core Data for Interoperability (AUCDI)

The service should support the use of AUCDI Release 1.

Note: The focus of the AUCDI Release 1 is the representation of the clinical content necessary for each of the data groups identified within the Release 1 scope.

Development is continuing to enhance AUCDI.

Standards for data sharing

The service should:  

• support the consumption of clinical documents in Fast Healthcare Interoperability Resources (FHIR®) formats
• be capable of using HL7 FHIR-compliant API when sending clinical information.
• be capable of using HL7 FHIR-compliant API when receiving clinical information.

If the service stores, transmits, retrieves, prints, processes or displays medical imaging, it must:

• support the DICOM standard.

Standards for terminology, code sets and classifications  

Where appropriate the service must:

• support Systematised Nomenclature of Medicine-Clinical Terms AU (SNOMED CT-AU)
• support the use of Australian Medicines Terminology (AMT) for the storage of patients’ current medicines
• support the use of MBS item numbers as defined on MBS online
• support Standardised Pathology Informatics in Australia (SPIA)
• support Logical Observation Identifiers Names and Codes (LOINC®)
• support Australian Medicines Terminology (AMT)
• be capable of using METEOR for recording clinical information with data specifications
• be capable of using Nutrition Care Process Terminology (NCPT)
• support the National Clinical Terminology Service (NCTS)
• support the inclusion of medicines listed on the Australian Register of Therapeutic Goods (ARTG).

The service should support:

• person and provider identification in healthcare National Best Practice Data Set
• the use of content from the National Health Services Directory.

National Safety and Quality Health Service (NSQHS) Standards

Implementation of NSQHS is mandated in all hospitals, day procedure services and public dental services across Australia.

The service must:  

• support adherence to best practices related to Informed Consent  
• support adherence to all relevant National Safety and Quality Health Service Standards in accordance with the intended scope of the service being procured. These may include, but not limited to the following standards:  
  • Partnering with Consumers Standard
  • Communicating for Safety Standard
  • Comprehensive Care Standard
  • Blood Management Standard
  • Medication Safety Standard
  • Clinical Governance Standard.
• support adherence to all relevant Clinical Care Standards.

Other Standards

International

Where appropriate, the service should comply with:

• ISO/TR 11147:2023 Health informatics — Personalised digital health — Digital therapeutics health software systems
• ISO 10781:2023 Health informatics — HL7 Electronic Health Record-System Functional Model, Release 2.1 (EHR FM)
• ISO 13606-1:2019 Health informatics — Electronic health record communication — Part 1: Reference model.

National

The service must comply with:  

• AS2828.2: Digitised health records where digitisation of paper records is required  
• AS ISO 18308:2022 Health informatics — Requirements for an electronic health record architecture
• ATS ISO 14265-2013 Health informatics – Classification of purposes for processing personal health information.

Connections to National Systems

Healthcare Identifiers Service (HI Service)

The software should either:

• be able to discover and validate Individual Healthcare Identifiers (IHI) via the Healthcare Identifier (HI) Service, or

Where the enterprise utilises an enterprise-wide system for discover and validation of Individual Healthcare Identifiers (IHI) the software should:  

• be able to manage and interface with this middleware in order to enable discovery and validation of Individual Healthcare Identifiers (IHI).

My Health Record  

The software must:  

• be able to respect patient instruction not to upload at a patient and document level when contributing clinical information to the My Health Record system
• be able to access record information from the My Health Record as required
• be able to upload an Event Summary to the My Health Record system, if required
• support patient instruction not to upload.

API Gateway or Government Provider Management System (GPMS)

For aged care patients, the software should:

• be capable of sharing relevant data and reports to the GPMS.

National Authentication Service for Health (NASH)

If the service is connecting to My Health Record, the software must:

• have a valid NASH Certificate.

Conformance

HI service

The software should:

• have production access to the Health Identifiers Service.

Healthcare Information Provider Services (HIPS)

If the service connects to the Healthcare Information Provider Service (HIPS) middleware product, it must:

• conform with the HIPS conformance profile V1.

My Health Record

The software should:

• conform with the My Health Record Conformance Assessment Scheme.

eReferral

The software should:

• have the ability to send and receive ADHA conformant eReferral.

Provider Connect

The software should:

• conform with the Provider Connect Australia service.

State and territory requirements  

The following state and territory requirements must be upheld based on location.