Technical Specification
Track updates
iconCreated with Sketch.

ATS 4888.3-2013

[Current]

Electronic transfer of prescriptions, Part 3: Platform implementation specific e-prescription HL7 Clinical Document Architecture implementation guide

A CDA Implementation Guide that provides requirements for implementing, as an HL7 Clinical Document Architecture Release 2 (CDA) XML document, the logical model of an e-prescription detailed in ATS 4888.1, Electronic transfer of prescriptions, Part 1: Platform independent (logical) information model to support electronic transfer of prescriptions. One of three CDA Implementation Guides in the series of six Technical Specifications that collectively define a method for the electronic transfer of prescriptions in Australia.
Published: 20/05/2013
Pages: 218
Table of contents
Cited references
Content history
Table of contents
Header
About this publication
Preface
Foreword
1 Scope and general
1.1 Scope
1.2 Intended audience
1.3 Normative references
1.4 Terms, definitions and acronyms
1.4.1 Terms and definitions
1.4.2 E-prescription
1.4.3 Acronyms
1.5 Keyword interpretations
1.5.1 Interpretation of normative language
1.5.2 Cardinality obligations legend
1.6 Conformance
1.7 Lifecycle and document management
2 Guide for use
2.1 General
2.2 Clinical Document Architecture Release 2
2.3 Mapping interpretation
2.3.1 General
2.3.2 CDA R-MIM representation
2.3.3 CDA mapping (normative)
2.3.3.1 Mapping requirements
2.3.3.2 Example mapping table
2.3.3.3 Interpretation of example mapping
2.3.4 Example XML fragment
2.4 CDA extensions
2.5 W3C XML Schema
2.6 Schematron
2.7 Implementation strategies
3 E-prescription context data hierarchy
4 E-prescription content data hierarchy
5 Administrative Observations
5.1 General
5.2 CDA R-MIM representation
5.2.1 General
5.2.2 CDA mapping
5.2.3 CDA mapping for Administrative Observations
5.2.4 Example Administrative Observations XML fragment
6 CDA Header
6.1 General
6.2 ClinicalDocument
6.2.1 Identification
6.2.2 Relationships
6.2.3 CDA R-MIM representation
6.2.4 CDA mapping
6.2.5 Example ClinicalDocument body XML fragment
6.3 LegalAuthenticator
6.3.1 Identification
6.3.2 Relationships
6.3.3 CDA R-MIM representation
6.3.4 CDA mapping
6.3.5 Example LegalAuthenticator XML fragment
6.4 Custodian
6.4.1 Identification
6.4.2 Relationships
6.4.3 CDA R-MIM representation
6.4.4 CDA mapping
6.4.5 Example Custodian XML fragment
6.5 EncompassingEncounter
6.5.1 Identification
6.5.2 Relationships
6.5.3 CDA R-MIM representation
6.5.4 CDA mapping
6.5.5 Example EncompassingEncounter XML fragment
7 Context data specification—CDA mapping
7.1 E-prescription
7.1.1 Identification
7.1.2 Relationships
7.1.3 CDA R-MIM representation
7.1.4 CDA mapping
7.1.5 Example E-prescription content XML fragment
7.2 Subject of Care
7.2.1 Identification
7.2.2 Relationships
7.2.3 CDA R-MIM representation
7.2.4 CDA mapping
7.2.5 Example Subject of Care XML fragment
7.3 Prescriber
7.3.1 Identification
7.3.2 Relationships
7.3.3 CDA R-MIM representation
7.3.4 CDA mapping
7.3.5 Example prescriber XML fragment
7.4 Prescriber Organization
7.4.1 Identification
7.4.2 Relationships
7.4.3 CDA R-MIM representation
7.4.4 CDA mapping
7.4.5 Example prescriber organization XML fragment
8 Content data specification—CDA mapping
8.1 E-prescription
8.1.1 Identification
8.1.2 Relationships
8.1.3 CDA R-MIM representation
8.1.4 CDA mapping
8.1.5 Example E-prescription body XML fragment
8.2 Prescription Item
8.2.1 Identification
8.2.2 Relationships
8.2.3 CDA R-MIM representation
8.2.4 CDA mapping
8.2.5 Example Prescription Item XML fragment
8.3 Observations
8.3.1 Identification
8.3.2 Relationships
8.3.3 CDA R-MIM representation
8.3.4 CDA mapping
8.3.5 Example Observations XML fragment
8.4 Body Weight
8.4.1 Identification
8.4.2 Relationships
8.4.3 CDA R-MIM representation
8.4.4 CDA mapping
8.4.5 Example Observation body weight XML fragment
8.5 Body Height
8.5.1 Identification
8.5.2 Relationships
8.5.3 CDA R-MIM representation
8.5.4 CDA mapping
8.5.5 Example Body Height XML fragment
8.6 Prescription Note Detail
8.6.1 Identification
8.6.2 Relationships
8.6.3 CDA R-MIM representation
8.6.4 CDA mapping
8.6.5 Example Prescription Note detail XML fragment
Appendix A
A1 Code
A1.1 General
A1.2 Example code
A2 ID
A2.1 General
A2.2 Example id
A3 Time
A3.1 General
A3.2 Example Simple Timestamp
A3.3 Example Low time
A3.4 Example Interval Timestamp 1
A3.5 Example Interval Timestamp 2
A3.6 Example Width time
A4 Entity Identifier
A4.1 CDA mapping
A4.2 Example Entity Identifier XML fragment
A5 Person Name
A5.1 CDA mapping
A5.2 Example Person Name XML fragment
A6 Address
A6.1 CDA mapping
A6.2 Example Address XML fragment
A7 Electronic Communication Detail
A7.1 CDA mapping
A7.2 Example Electronic communication detail XML fragment
A8 Employment
A8.1 CDA mapping
A8.2 Example Employment XML fragment
Appendix B
B1 General
B2 EntityIdentifier
B3 Multiple Birth
B4 Administrative Gender Code
B5 Birth Time
B6 Employment
B7 Qualifications
B8 Entitlement
B9 Policy
B10 Coverage
B11 Brand Substitute Not Allowed
B12 Method Code
B13 Ingredient
B14 ControlAct
Appendix C
C1 General
C1.1 Context
C1.2 Example All Values
C1.3 Example One Value
C2 HL7 V3: TelecommunicationAddressUse value set
C3 Health Care Client Sex value set
C4 Health Care Client Name Usage value set
C5 Health Care Provider Organization Name Usage value set
C6 Health Care Client Identifier Address Purpose value set
C7 Health Care Client Identifier Geographic Area value set
C8 Health Care Client Electronic Communication Medium value set
C9 Health Care Client Electronic Communication Usage Code
C10 Australian State/Territory Identifier—Postal value set
C11 Health Care Client Identifier Date Accuracy Indicator value set
C12 NCTIS: Admin Codes — Section/Entries
C13 NCTIS: Admin Codes—Concurrent Supply Grounds
C14 NCTIS: Admin Codes—Medical Benefit Category Type
C15 NCTIS: Admin Codes—Entitlement Type
C16 HL7 V3 CDA: ActMood code
C17 OIDs
C18 Medicare: PBS Prescription Type Values
C19 NCTIS: External Concepts
C20 METeOR 291036: Indigenous Status
Appendix D
Bibliography
Cited references in this standard
[Current]
Electronic transfer of prescriptions, Part 4: Platform implementation specific dispense record HL7 Clinical Document Architecture implementation guide
[Current]
Electronic transfer of prescriptions, Part 5: Platform implementation specific prescription request HL7 Clinical Document Architecture implementation guide
[Current]
Electronic transfer of prescriptions, Part 1: Platform independent (logical) information model to support electronic transfer of prescriptions
[Current]
Electronic transfer of prescriptions, Part 2: Platform independent (logical) services model to support electronic transfer of prescriptions
[Current]
Electronic transfer of prescriptions, Part 6: Platform implementation specific web service
Content history
DR ATS 4888.3

One-time Purchase

Access via web browser on any device
One-time purchase
Single publication
Offline access via PDF^

$262.48 AUD

Inclusive of GST
Format *
iconCreated with Sketch.
Web Reader
Licenses *
iconCreated with Sketch.
1 user
Total$262.48 AUD
Add to Cart
IMPORTANT