AU eRequesting Implementation Guide
0.1.0-ballot - Ballot
This page is part of the AU eRequesting (v0.1.0-ballot: AU eRequesting R1 Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. . For a full list of available versions, see the Directory of published versions
Official URL: http://hl7.org.au/fhir/ereq/CapabilityStatement/au-erequesting-patientaccess | Version: 0.1.0-ballot | |||
Standards status: Draft | Maturity Level: 0 | Computable Name: AUeRequestingPatientAccessCapabilityStatement | ||
Copyright/Legal: Used by permission of HL7 International, all rights reserved Creative Commons License. HL7 Australia© 2024+; Licensed Under Creative Commons No Rights Reserved. |
This CapabilityStatement describes the basic rules for the AU eRequesting Patient Access actor that is the digital interface that allows patients or their representatives to view and manage requests for diagnostic services. The complete list of FHIR profiles, RESTful operations, and search parameters supported by AU eRequesting patient access clients are defined in this CapabilityStatement.
The table below identifies where a Profile has a Must Support reference to other profiles or resources (i.e., Target Profiles). This list is provided to clarify where additional profiles or resources may need to be supported if a patient access client supports a particular resource.
Resource Type | Profile | Supported Target Reference |
---|---|---|
Coverage | AU Base Coverage | - |
Condition | AU Core Condition | AU Core Patient |
DocumentReference | DocumentReference | - |
Encounter | AU Core Encounter | AU Core Condition, AU Core Location, Observation, AU Core Organization, AU Core Patient, AU Core Practitioner, AU Core PractitionerRole, AU Core Procedure, AU Base Related Person |
Location | AU Core Location | AU Core Organization |
Organization | AU Core Organization | - |
Observation | Observation | - |
Patient | AU Core Patient | - |
Practitioner | AU Core Practitioner | - |
PractitionerRole | AU Core PractitionerRole | AU Core Organization, AU Core Practitioner |
Procedure | AU Core Procedure | AU Core Condition, DocumentReference, AU Core Encounter, Observation, AU Core Patient, AU Core Procedure |
RelatedPerson | AU Base Related Person | - |
ServiceRequest | AU eRequesting ServiceRequest, AU eRequesting Imaging Request, AU eRequesting Pathology Request | AU Base Coverage, AU Core Encounter, AU Core Patient, AU Core PractitionerRole |
Raw OpenAPI-Swagger Definition file | Download
Generated Narrative: CapabilityStatement au-erequesting-patientaccess
json
, MAY support xml
application/json-patch+json
Note to Implementers: FHIR Capabilities
Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.
client
The AU eRequesting Patient Access SHALL:
None defined.
The summary table lists the resources that are part of this configuration, and for each resource it lists:
_include
_revinclude
Resource Type | Profile | R | S | U | C | Searches | _include | _revinclude | Operations |
---|---|---|---|---|---|---|---|---|---|
ServiceRequest | Supported Profiles AU eRequesting ServiceRequest AU eRequesting Pathology Request AU eRequesting Imaging Request | y | _id, requisition | ||||||
Coverage | Supported Profiles AU Base Coverage | ||||||||
Encounter | Supported Profiles AU Core Encounter | ||||||||
Organization | Supported Profiles AU Core Organization | ||||||||
Patient | Supported Profiles AU Core Patient | ||||||||
Practitioner | Supported Profiles AU Core Practitioner | ||||||||
PractitionerRole | Supported Profiles AU Core PractitionerRole | ||||||||
Condition | Supported Profiles AU Core Condition | ||||||||
DocumentReference | Supported Profiles DocumentReference | ||||||||
Location | Supported Profiles AU Core Location | ||||||||
Observation | Supported Profiles Observation | ||||||||
Procedure | Supported Profiles AU Core Procedure | ||||||||
RelatedPerson | Supported Profiles AU Base Related Person |
Patient Accesss SHALL support the ServiceRequest resource, at least one AU eRequesting ServiceRequest profile, and the conformance expectations for the ServiceRequest resource.
Conformance | Parameter | Type | Documentation |
---|---|---|---|
SHALL | _id | token | |
SHALL | requisition | token |
Patient Accesss clients SHOULD support the Coverage resource, the AU Base profile, and the conformance expectations for the Coverage resource.
http://hl7.org.au/fhir/core/StructureDefinition/au-core-encounter
Patient Accesss clients SHOULD support the Encounter resource, the AU Core profile, and the conformance expectations for the Encounter resource.
http://hl7.org.au/fhir/core/StructureDefinition/au-core-organization
Patient Accesss clients SHOULD support the Organization resource, the AU Core profile, and the conformance expectations for the Organization resource.
http://hl7.org.au/fhir/core/StructureDefinition/au-core-patient
Patient Accesss clients SHOULD support the Patient resource, the AU Core profile, and the conformance expectations for the Patient resource.
http://hl7.org.au/fhir/core/StructureDefinition/au-core-practitioner
Patient Accesss clients SHOULD support the Practitioner resource, the AU Core profile, and the conformance expectations for the Practitioner resource.
http://hl7.org.au/fhir/core/StructureDefinition/au-core-practitionerrole
Patient Accesss clients SHOULD support the PractitionerRole resource, the AU Core profile, and the conformance expectations for the PractitionerRole resource.
http://hl7.org.au/fhir/core/StructureDefinition/au-core-condition
Patient Accesss MAY support the Condition resource, the AU Core profile, and the conformance expectations for the Condition resource.
Patient Accesss MAY support the DocumentReference resource.
http://hl7.org.au/fhir/core/StructureDefinition/au-core-location
Patient Accesss MAY support the Location resource, the AU Core profile, and the conformance expectations for the Location resource.
Patient Accesss MAY support the Observation resource.
http://hl7.org.au/fhir/core/StructureDefinition/au-core-procedure
Patient Accesss MAY support the Procedure resource, the AU Core profile, and the conformance expectations for the Procedure resource.
Patient Accesss MAY support the RelatedPerson resource, the AU Base profile, and the conformance expectations for the RelatedPerson resource.