Bed Management

Standards and specifications

General requirements

Cyber security

The software must demonstrate adherence to the ‘Essential 8’ cyber security principles.

Core requirements

Standards for identification

The software must:

• support the use of Healthcare Identifiers in accordance with the Healthcare Identifiers Act 2010
• support adherence to Patient Identification best practices as outlined by the Australian Commission on Safety and Quality in Health Care
• be able to discover and validate Individual Healthcare Identifiers (IHI) via the Healthcare Identifier (HI) Service Business-2-Business web services.

Standards for data sharing

The software should be capable of using:

• HL7 FHIR-compliant API when sending clinical information.
• HL7 FHIR-compliant API when receiving clinical information.

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 system must support adherence to:

• all relevant NSQHS Standards in accordance with the intended scope of the system being procured. These may include, but not limited to the following standards:
  • Partnering with Consumers Standard
  • Communicating for Safety Standard
  • Comprehensive Care Standard
• Clinical Governance Standard
• all relevant Clinical Care Standards.

Other Standards

National

The system should support:

• Access IHE Patient Care Coordination Technical Framework Supplement - Bed Management (BED) - Rev 1.2 - Trial implementation.

Connections to National Systems

Healthcare Identifiers Service (HI Service)

If the software is expected to deal with healthcare identifiers (e.g. in a hospital environment) then it 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 discovery 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).

Conformance

HI service

The software should:

• have production access to the Health Identifiers Service.

Healthcare Information Provider Services (HIPS)

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

• conform with the HIPS conformance profile V1.

State and territory requirements

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