Technical Specification
Track updates
ATS 4888.2-2013
[Current]Electronic transfer of prescriptions, Part 2: Platform independent (logical) services model to support electronic transfer of prescriptions
Specifies an Electronic Transfer of Prescriptions (ETP) solution for the generation and transfer of electronic prescriptions and associated dispensing records between participating Prescribers and Dispensers; contains the clinical information that is communicated between participants using ETP services. The second in a series of six Technical Specifications that collectively define a method for ETP in Australia; to be read in conjunction with ATS 4888.1, Electronic transfer of prescriptions, Part 1: Platform independent (logical) information model to support electronic transfer of prescriptions.
Published: 20/05/2013
Pages: 102
Table of contents
Cited references
Content history
Table of contents
Header
About this publication
Preface
1 Scope and general
1.1 Scope and application
1.2 Scope exclusions
1.3 Implementation
1.4 Intended audience
1.5 Normative references
1.6 Terms, definitions and acronyms
1.6.1 Terms and definitions
1.6.2 Definitions
1.6.3 Acronyms
1.7 Keyword interpretation
2 Business context for ETP
2.1 Introduction
2.2 Phased implementation
2.2.1 Introduction
2.2.2 ETP Level 1—Electronic copies of paper prescriptions
2.2.3 ETP Level 2—Electronic prescriptions
2.2.4 ETP Level 3—Electronic prescription notifications for individuals
2.2.4.1 Introduction
2.2.4.2 Relationship to paper prescriptions and prescribing software
2.3 National infrastructure services
3 ETP business services
3.1 Introduction
3.2 Roles and participants
3.3 ETP business services
4 ETP processes
4.1 Scope
4.2 Electronic prescribing and dispensing
4.3 Facility managed supply
4.4 Dispensing on prescriber’s instructions
4.5 Cancelling an electronic prescription
4.6 Reversing a dispense process
4.7 Abandoning a dispense process
4.8 Service resilience
5 Computational viewpoint
5.1 Introduction
5.2 Technical services architecture overview
5.2.1 Participants
5.2.2 Service contracts
5.2.3 Service interfaces
5.3 Security overview
5.3.1 Introduction
5.3.2 Service participation management
5.3.3 Authentication
5.3.4 Authorization
5.3.4.1 Introduction
5.3.4.2 Identity credentials
5.3.4.3 Retrieval Key
5.3.4.4 DAK
5.3.5 Confidentiality of data in transit
5.3.6 Confidentiality of data at rest
5.3.7 DAK
5.3.8 Audit
5.3.9 Document attestation
5.4 State management overview
5.4.1 Architectural approach
5.4.2 Dispensing state
5.4.3 Prescription Exchange Service (PES) Events
6 Information viewpoint
6.1 Introduction
6.2 Common data types
6.2.1 Introduction
6.2.2 Document Access Key
6.2.2.1 DAK data type
6.2.2.2 Keys derived from a DAK
6.2.3 Qualified Retrieval Key (RK)
6.2.4 Current Interest
6.3 Clinical documents
6.4 PES Event data types
6.4.1 Introduction
6.4.2 Data types used to signal PES Events
6.4.3 Data types used to acknowledge PES Events
6.4.4 Specialized PES Events
6.4.4.1 Introduction
6.4.4.2 Prescription Available Event occurrence
6.4.4.3 Prescription Available Event PES acknowledgement
6.4.4.4 Prescription Cancelled PES Event occurrence
6.4.4.5 Prescription Cancelled PES Event acknowledgement
6.4.4.6 Dispense Initiated PES Event occurrence
6.4.4.7 Dispense Initiated Event acknowledgement
6.4.4.8 Dispense Finalised PES Event occurrence
6.4.4.9 Dispense Finalised PES Event acknowledgement
6.4.4.10 Dispense Terminated PES Event occurrence
6.4.4.11 Dispense Terminated PES Event acknowledgement
6.4.4.12 Dispense Reversed PES Event occurrence
6.4.4.13 Dispense Reversed PES Event acknowledgement
6.5 Retrieval request data types
6.5.1 Introduction
6.5.2 Retrieval Requests
6.5.3 Retrieval Response
6.5.4 Specialized Retrieval Requests
6.5.4.1 Introduction
6.5.4.2 Prescription Retrieval Request
6.5.4.3 Prescription Retrieval Response
6.6 ETP Notification data types
6.6.1 Introduction
6.6.2 ETP Notification
6.6.3 ETP Delivery Notification Acknowledgement
6.6.4 Specialized ETP Notifications
6.6.4.1 Prescription Required Notification
6.6.4.2 Required Prescription Notification
6.6.4.3 Prescription Available Notification
6.6.4.4 Electronic Prescription Notification
6.6.4.5 Last Supply Notification
7 Conformance specifications
7.1 Introduction
7.2 Identity credentials and PKI conformance points
7.3 Common fault types
7.3.1 Introduction
7.3.2 Reliable communications conformance points
7.3.3 Data security conformance points
7.4 Endpoint location
7.5 Prescription Exchange acting as prescription manager
7.5.1 Introduction
7.5.2 State managed by a Prescription Exchange
7.5.3 Interfaces conformance points
7.5.4 Authentication and authorization conformance points
7.5.5 Common processing of PES Events
7.5.6 State changes as a result of PES Events conformance points
7.5.7 Other operations provided
7.5.7.1 Introduction
7.5.7.2 E-prescribing::retrievePrescription and E-dispensing::retrievePrescription conformance points
7.6 Prescription Exchange acting as intermediary
7.7 Electronic Prescribing System
7.7.1 Introduction
7.7.2 Digital Prescriber Signatures conformance points
7.7.3 Interfaces conformance points
7.7.4 Authentication and Authorization conformance points
7.7.5 E-prescribing Service
7.7.5.1 Introduction
7.7.5.2 E-prescribing::prescribe (invoker) conformance points
7.7.5.3 E-prescribing::retrievePrescription (invoker) conformance points
7.7.5.4 E-prescribing:cancelPrescription (invoker) conformance points
7.7.6 Prescription Requesting Service
7.7.6.1 Introduction
7.7.6.2 Prescription Requesting:deliverNotification (provider) conformance points
7.7.6.3 Prescription Receiving::deliverNotification (invoker) conformance points
7.7.7 Facility Managed Supply Service (optional)
7.7.7.1 Introduction
7.7.7.2 Facility Managed Supply:deliverNotification (invoker) conformance points
7.8 Electronic Dispensing System
7.8.1 Introduction
7.8.2 Interfaces conformance points
7.8.3 Authentication and Authorization conformance points
7.8.4 Prescription Requesting Service
7.8.4.1 Introduction
7.8.4.2 Prescription Receiving::deliverNotification (provider) conformance points
7.8.4.3 Prescription Required::deliverNotification (invoker) conformance points
7.8.5 E-dispensing Service
7.8.5.1 Introduction
7.8.5.2 E-dispensing::initiateDispense (invoker) conformance points
7.8.5.3 E-dispensing::finaliseDispense (invoker) conformance points
7.8.5.4 E-dispensing::terminateDispense (invoker) conformance points
7.8.5.5 E-dispensing::reverseDispense (invoker) conformance points
7.8.5.6 E-dispensing::cancelPrescription (invoker) conformance points
7.8.5.7 E-dispensing::retrievePrescription (invoker) conformance points
7.8.6 Contract Dispensing Service (optional)
7.8.6.1 Introduction
7.8.6.2 Contract Dispensing::deliverNotification (provider) conformance points
7.8.7 Last Supply Notification Service (optional)
7.8.7.1 Introduction
7.8.7.2 Last Supply Notification::deliverNotification (invoker) conformance points
7.9 Facility Based Supply Manager
7.9.1 Introduction
7.9.2 Interfaces conformance points
7.9.3 Authentication and Authorization conformance points
7.9.4 Facility Managed Supply Service
7.9.4.1 Introduction
7.9.4.2 Facility Managed Supply::deliverNotification (provider) conformance points
7.9.5 Contract Dispensing Service
7.9.5.1 Introduction
7.9.5.2 Contract Dispensing::deliverNotification (invoker) conformance points
7.10 Last Supply Notification Agent
7.10.1 Introduction
7.10.2 Interfaces conformance points
7.10.3 Authentication and Authorization conformance points
7.10.4 Last Supply Notification Service
7.10.4.1 Introduction
7.10.4.2 Last Supply Notification::deliverNotification (provider) conformance points
8 Authorization policies
8.1 Introduction
8.2 Prescription Exchange
8.3 Electronic Prescribing System
8.4 Electronic Dispensing System
8.5 Facility Based Supply Manager
8.6 Last Supply Notification Agent
Appendix A
Bibliography
Cited references in this standard
[Current]
Electronic transfer of prescriptions, Part 1: Platform independent (logical) information model to support electronic transfer of prescriptions
[Current]
Electronic transfer of prescriptions, Part 6: Platform implementation specific web service
[Current]
Electronic transfer of prescriptions, Part 5: Platform implementation specific prescription request HL7 Clinical Document Architecture implementation guide
[Current]
Electronic transfer of prescriptions, Part 4: Platform implementation specific dispense record HL7 Clinical Document Architecture implementation guide
[Current]
Electronic transfer of prescriptions, Part 3: Platform implementation specific e-prescription HL7 Clinical Document Architecture implementation guide
Content history
One-time Purchase
Access via web browser on any device
One-time purchase
Single publication
Offline access via PDF^
$203.34 AUD
Inclusive of GSTFormat *
Web Reader
Licenses *
1 user
Total$203.34 AUD
IMPORTANT