AU Provider Directory Implementation Guide
2.1.0-ci-build - Draft Australia flag

AU Provider Directory Implementation Guide, published by HL7 Australia. This guide is not an authorized publication; it is the continuous build for version 2.1.0-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7au/au-fhir-pd/ and changes regularly. See the Directory of published versions

Resource Profile: AUPDHealthcareService - Mappings

Page standards status: Draft Maturity Level: 0

Mappings for the au-pd-healthcareservice resource profile.

Mappings to Structures in this Implementation Guide

No Mappings Found

Mappings to other Structures

No Mappings Found

Other Mappings

NameRIM MappingFiveWs Pattern Mappingdoco
.. HealthcareService
act[classCode=ACT][moodCode=DEF]
... id
... meta
.... id
n/a
.... extension
n/a
.... versionId
.... lastUpdated
.... source
.... profile
.... security
.... tag
... implicitRules
... language
... text
Act.text?
... contained
N/A
... extension
N/A
... modifierExtension
N/A
... Slices for identifier
II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
.... identifier:All Slices
..... id
n/a
..... Slices for extension
...... extension:routability
...... extension:assigningAuthority
..... use
Role.code or implied by context
..... type
Role.code or implied by context
..... system
II.root or Role.id.root
..... value
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
..... period
Role.effectiveTime or implied by context
..... assigner
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
.... identifier:hpio
II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
.... identifier:auvdi
II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
... active
.statusCode
FiveWs.status
... providedBy
.scopingRole.Organization
... category
.code
FiveWs.class
... type
.actrelationship[typeCode=COMP.act[classCode=ACT][moodCode=DEF].code
... specialty
.actrelationship[typeCode=COMP.act[classCode=ACT][moodCode=DEF].code
... location
.location.role[classCode=SDLOC]
FiveWs.where[x]
... name
.name
... comment
.location.role[classCode=SDLOC].desc
... extraDetails
.actrelationship[typeCode=COMP.act[classCode=ACT][moodCode=DEF].text
... photo
.actrelationship[typeCode=SBJ].observation.value
... telecom
.telecom
... coverageArea
.location.role[classCode=SDLOC].subjectOf.A_SpatialCoordinate
... serviceProvisionCode
.actrelationship[typeCode=PRCN].observation[moodCode=EVN.CRT]
... eligibility
.... id
n/a
.... extension
n/a
.... modifierExtension
N/A
.... code
.actrelationship[typeCode=PRCN].observation[moodCode=EVN.CRT]
.... comment
.actrelationship[typeCode=PRCN].observation[moodCode=EVN.CRT].text
... program
.actrelationship[typeCode=PERT].observation
... characteristic
.actrelationship[typeCode=PERT].observation
... communication
... referralMethod
.actrelationship[typeCode=PERT].observation
... appointmentRequired
.actrelationship[typeCode=PERT].observation
... availableTime
.effectiveTime
.... id
n/a
.... extension
n/a
.... modifierExtension
N/A
.... daysOfWeek
.effectiveTime
.... allDay
.effectiveTime
.... availableStartTime
.effectiveTime
..... id
..... Slices for extension
...... extension:timeZone
..... value
.... availableEndTime
.effectiveTime
..... id
..... Slices for extension
...... extension:timeZone
..... value
... notAvailable
.effectiveTime
.... id
n/a
.... extension
n/a
.... modifierExtension
N/A
.... description
n/a
.... during
.effectiveTime
... availabilityExceptions
.effectiveTime
... endpoint
n/a

doco Documentation for this format