{ "resourceType" : "CapabilityStatement", "id" : "au-core-server", "text" : { "status" : "extensions", "div" : "
json
, SHOULD support xml
\n application/json-patch+json
\n \n\n\n Note to Implementers: FHIR Capabilities\n
\nAny 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.
\n
server
\n The AU Core Server SHALL: \n
\nSupport the AU Core Patient resource profile.
\nSupport at least one additional resource profile from the list of AU Core Profiles.
\nImplement the RESTful behavior according to the FHIR specification.
\nReturn the following response classes:
\n(Status 400): Bad Request
\n(Status 401): Not Authorized
\n(Status 403): Forbidden
\n(Status 404): Not Found
\nSupport JSON source formats for all AU Core interactions.
\nDeclare a CapabilityStatement identifying the list of profiles, operations, and search parameters supported.
\nThe AU Core Server SHOULD: \n
\n\n\n\n\n\n\n
\n- A server MAY reject any unauthorized requests by returning an HTTP 401 "Unauthorized", HTTP 403 "Forbidden", or HTTP 404 "Not Found"
\n- For authentication and authorisation, systems MAY support any SMART App Launch and SMART Backend Service Authorization. When this is not avalable, basic authentication MAY be used.
\n
transaction
interaction.batch
interaction.search-system
interaction.history-system
interaction.The summary table lists the resources that are part of this configuration, and for each resource it lists:
\n_include
\n_revinclude
\n\nResource Type\n | \n\nProfile\n | \n\nR\n | \n\nS\n | \n\nU\n | \n\nC\n | \n\nSearches\n | \n\n\n_include\n \n | \n\n\n_revinclude\n \n | \n\nOperations\n | \n
---|---|---|---|---|---|---|---|---|---|
\nAllergyIntolerance\n | \n\nhttp://hl7.org.au/fhir/core/StructureDefinition/au-core-allergyintolerance\n | \ny | \ny | \n\n | \n | clinical-status, patient, patient.identifier, patient+clinical-status | \n\n | \nProvenance:target \n | \n\n |
\nCondition\n | \n\nhttp://hl7.org.au/fhir/core/StructureDefinition/au-core-condition\n | \ny | \ny | \n\n | \n | category, clinical-status, code, onset-date, patient, patient.identifier, patient+category, patient+category+clinical-status, patient+clinical-status, patient+code, patient+onset-date | \n\n | \nProvenance:target \n | \n\n |
\nEncounter\n | \n\nhttp://hl7.org.au/fhir/core/StructureDefinition/au-core-encounter\n | \ny | \ny | \n\n | \n | class, date, discharge-disposition, identifier, location, patient, patient.identifier, patient+class, patient+date, patient+discharge-disposition, patient+location, patient+status, patient+type, status, type | \n\n | \nProvenance:target \n | \n\n |
\nImmunization\n | \n\nhttp://hl7.org.au/fhir/core/StructureDefinition/au-core-immunization\n | \ny | \ny | \n\n | \n | date, patient, patient.identifier, patient+date, patient+status, patient+vaccine-code, status, vaccine-code | \n\n | \nProvenance:target \n | \n\n |
\nLocation\n | \n\nhttp://hl7.org.au/fhir/core/StructureDefinition/au-core-location\n | \ny | \ny | \n\n | \n | address, address-city, address-postalcode, address-state, identifier, name | \n\n | \n | \n |
\nMedication\n | \n\nhttp://hl7.org.au/fhir/core/StructureDefinition/au-core-medication\n | \ny | \n\n | \n | \n | \n | \n | \n | \n |
\nMedicationRequest\n | \n\nhttp://hl7.org.au/fhir/core/StructureDefinition/au-core-medicationrequest\n | \ny | \ny | \n\n | \n | _id, authoredon, category, identifier, intent, patient, patient.identifier, patient+intent, patient+intent+authoredon, patient+intent+status, status | \n\nMedicationRequest:medication \n | \n\nProvenance:target \n | \n\n |
\nMedicationStatement\n | \n\nhttp://hl7.org.au/fhir/core/StructureDefinition/au-core-medicationstatement\n | \ny | \ny | \n\n | \n | effective, patient, patient.identifier, patient+effective, patient+status, status | \n\nMedicationStatement:medication \n | \n\nProvenance:target \n | \n\n |
\nObservation\n | \n\nhttp://hl7.org.au/fhir/core/StructureDefinition/au-core-waistcircum,http://hl7.org.au/fhir/core/StructureDefinition/au-core-bodyweight,http://hl7.org.au/fhir/core/StructureDefinition/au-core-bodytemp,http://hl7.org.au/fhir/core/StructureDefinition/au-core-diagnosticresult,http://hl7.org.au/fhir/core/StructureDefinition/au-core-heartrate,http://hl7.org.au/fhir/core/StructureDefinition/au-core-resprate,http://hl7.org.au/fhir/core/StructureDefinition/au-core-diagnosticresult-path,http://hl7.org.au/fhir/core/StructureDefinition/au-core-smokingstatus,http://hl7.org.au/fhir/core/StructureDefinition/au-core-bloodpressure,http://hl7.org.au/fhir/core/StructureDefinition/au-core-bodyheight\n | \ny | \ny | \n\n | \n | category, code, date, patient, patient.identifier, patient+category, patient+category+date, patient+category+status, patient+code, patient+code+date, status | \n\n | \nProvenance:target \n | \n\n |
\nOrganization\n | \n\nhttp://hl7.org.au/fhir/core/StructureDefinition/au-core-organization\n | \ny | \ny | \n\n | \n | _id, address, identifier, name | \n\n | \nProvenance:target \n | \n\n |
\nPatient\n | \n\nhttp://hl7.org.au/fhir/core/StructureDefinition/au-core-patient\n | \ny | \ny | \n\n | \n | _id, birthdate, birthdate+family, birthdate+name, family, family+gender, gender, gender+name, identifier, indigenous-status, name, patient-gender-identity | \n\n | \nProvenance:target \n | \n\n |
\nPractitioner\n | \n\nhttp://hl7.org.au/fhir/core/StructureDefinition/au-core-practitioner\n | \ny | \ny | \n\n | \n | _id, identifier, name | \n\n | \nProvenance:target \n | \n\n |
\nPractitionerRole\n | \n\nhttp://hl7.org.au/fhir/core/StructureDefinition/au-core-practitionerrole\n | \ny | \ny | \n\n | \n | _id, identifier, organization, practitioner, practitioner.identifier, specialty | \n\nPractitionerRole:practitioner \n | \n\nProvenance:target \n | \n\n |
\nProcedure\n | \n\nhttp://hl7.org.au/fhir/core/StructureDefinition/au-core-procedure\n | \ny | \ny | \n\n | \n | code, date, patient, patient.identifier, patient+code+date, patient+date, patient+status, status | \n\n | \nProvenance:target \n | \n\n |
\nProvenance\n | \n\nhttp://hl7.org.au/fhir/core/StructureDefinition/au-core-provenance\n | \ny | \ny | \n\n | \n | \n | \n | \n | \n |
resolves
\nread
,search-type
.\ncreate
,update
,delete
,vread
,patch
,history-instance
.\n\n\n\n\nIf the server supports the AllergyIntolerance resource, the server SHALL support the AU Core profile and the conformance expectations for the AllergyIntolerance resource.
\n
Conformance | \nParameter | \nType | \nDocumentation | \n
---|---|---|---|
\n SHALL\n | \n\n patient\n | \n\n reference \n | \n\n \n \nThe client SHALL provide at least an id value and MAY provide both the Type and id values. \nThe server SHALL support both. \n | \n
\n SHOULD\n | \n\n patient.identifier\n | \n\n reference.token \n | \n\n \n \nThe client SHALL provide both the system and code values. \nThe server SHALL support both. \nThe client SHOULD support search using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. \nThe server SHOULD support search using the using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. \n | \n
\n MAY\n | \n\n clinical-status\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
Conformance | \nParameters | \nTypes | \n
---|---|---|
\n SHOULD\n | \n\n patient+ clinical-status\n | \n\n reference + token \n | \n
resolves
\nread
,search-type
.\ncreate
,update
,delete
,vread
,patch
,history-instance
.\n\n\n\n\nIf the server supports the Condition resource, the server SHALL support the AU Core profile and the conformance expectations for the Condition resource.
\n
Conformance | \nParameter | \nType | \nDocumentation | \n
---|---|---|---|
\n SHALL\n | \n\n patient\n | \n\n reference \n | \n\n \n \nThe client SHALL provide at least an id value and MAY provide both the Type and id values. \nThe server SHALL support both. \n | \n
\n SHOULD\n | \n\n patient.identifier\n | \n\n reference.token \n | \n\n \n \nThe client SHALL provide both the system and code values. \nThe server SHALL support both. \nThe client SHOULD support search using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. \nThe server SHOULD support search using the using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. \n | \n
\n MAY\n | \n\n category\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
\n MAY\n | \n\n clinical-status\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
\n MAY\n | \n\n code\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
\n MAY\n | \n\n onset-date\n | \n\n date \n | \n\n \n \nThe client SHALL provide a value precise to the second + time offset. \nThe server SHALL support a value precise to the second + time offset. \nThe client SHALL support these search comparators The server SHALL support these search comparators | \n
Conformance | \nParameters | \nTypes | \n
---|---|---|
\n SHALL\n | \n\n patient+ clinical-status\n | \n\n reference + token \n | \n
\n SHALL\n | \n\n patient+ category\n | \n\n reference + token \n | \n
\n SHOULD\n | \n\n patient+ category+ clinical-status\n | \n\n reference + token + token \n | \n
\n SHOULD\n | \n\n patient+ code\n | \n\n reference + token \n | \n
\n SHOULD\n | \n\n patient+ onset-date\n | \n\n reference + date \n | \n
resolves
\nread
,search-type
.\ncreate
,update
,delete
,vread
,patch
,history-instance
.\n\n\n\n\nIf the server supports the Encounter resource, the server SHALL support the AU Core profile and the conformance expectations for the Encounter resource.
\n
Conformance | \nParameter | \nType | \nDocumentation | \n
---|---|---|---|
\n SHALL\n | \n\n patient\n | \n\n reference \n | \n \n \n \n The client SHALL provide at least an id value and MAY provide both the Type and id values. \nThe server SHALL support both. \n | \n
\n SHOULD\n | \n\n patient.identifier\n | \n\n reference.token \n | \n \n \n \n The client SHALL provide both the system and code values. \nThe server SHALL support both. \nThe client SHOULD support search using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. \nThe server SHOULD support search using the using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. \n | \n
\n MAY\n | \n\n class\n | \n\n token \n | \n \n \n \n The client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
\n MAY\n | \n\n date\n | \n\n date \n | \n \n \n \n The client SHALL provide a value precise to the second + time offset. \nThe server SHALL support a value precise to the second + time offset. \nThe client SHALL support these search comparators The server SHALL support these search comparators | \n
\n MAY\n | \n\n discharge-disposition\n | \n\n token \n | \n \n \n \n The client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
\n MAY\n | \n\n identifier\n | \n\n token \n | \n \n \n \n The client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
\n MAY\n | \n\n location\n | \n\n reference \n | \n \n \n \n The client SHALL provide at least an id value and MAY provide both the Type and id values. \nThe server SHALL support both. \n | \n
\n MAY\n | \n\n status\n | \n\n token \n | \n \n \n \n The client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
\n MAY\n | \n\n type\n | \n\n token \n | \n \n \n \n The client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
Conformance | \nParameters | \nTypes | \n
---|---|---|
\n SHALL\n | \n\n patient+ date\n | \n\n reference + date \n | \n
\n SHOULD\n | \n\n patient+ class\n | \n\n reference + token \n | \n
\n SHOULD\n | \n\n patient+ discharge-disposition\n | \n\n reference + token \n | \n
\n SHOULD\n | \n\n patient+ location\n | \n\n reference + reference \n | \n
\n SHOULD\n | \n\n patient+ status\n | \n\n reference + token \n | \n
\n SHOULD\n | \n\n patient+ type\n | \n\n reference + token \n | \n
resolves
\nread
,search-type
.\ncreate
,update
,delete
,vread
,patch
,history-instance
.\n\n\n\n\nIf the server supports the Immunization resource, the server SHALL support the AU Core profile and the conformance expectations for the Immunization resource.
\n
Conformance | \nParameter | \nType | \nDocumentation | \n
---|---|---|---|
\n SHALL\n | \n\n patient\n | \n\n reference \n | \n\n \n \nThe client SHALL provide at least an id value and MAY provide both the Type and id values. \nThe server SHALL support both. \n | \n
\n SHOULD\n | \n\n patient.identifier\n | \n\n reference.token \n | \n\n \n \nThe client SHALL provide both the system and code values. \nThe server SHALL support both. \nThe client SHOULD support search using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. \nThe server SHOULD support search using the using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. \n | \n
\n MAY\n | \n\n date\n | \n\n date \n | \n\n \n \nThe client SHALL provide a value precise to the second + time offset. \nThe server SHALL support a value precise to the second + time offset. \nThe client SHALL support these search comparators The server SHALL support these search comparators | \n
\n MAY\n | \n\n status\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
\n MAY\n | \n\n vaccine-code\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
resolves
\nread
,search-type
. \ncreate
,update
,delete
,vread
,patch
,history-instance
. \n\n\n\n\nIf the server supports the Location resource, the server SHALL support the AU Core profile and the conformance expectations for the Location resource.
\n
Conformance | \nParameter | \nType | \nDocumentation | \n
---|---|---|---|
\n SHALL\n | \n\n address\n | \n\n string \n | \n \n |
\n SHALL\n | \n\n name\n | \n\n string \n | \n \n |
\n SHOULD\n | \n\n address-city\n | \n\n string \n | \n \n |
\n SHOULD\n | \n\n address-state\n | \n\n string \n | \n \n |
\n SHOULD\n | \n\n address-postalcode\n | \n\n string \n | \n \n |
\n MAY\n | \n\n identifier\n | \n\n token \n | \n \n \n \n The client SHALL provide at least a code value and SHOULD provide both the system and code values. \nThe server SHALL support both. \n | \n
resolves
\nread
.\nsearch-type
,create
,update
,delete
,vread
,patch
,history-instance
.\n\n\n\n\nMedicationAdministration, MedicationDispense, MedicationRequest, and MedicationStatement resources can represent a medication, using an external reference to a Medication resource. If the server supports the Medication resource, the server SHALL support the AU Core profile and the conformance expectations for the Medication resource.
\n
resolves
\nread
,search-type
.\ncreate
,update
,delete
,vread
,patch
,history-instance
.\n\n\n\n\nIf the server supports the MedicationRequest resource, the server SHALL support the AU Core profile and the conformance expectations for the MedicationRequest resource.
\n
Conformance | \nParameter | \nType | \nDocumentation | \n
---|---|---|---|
\n SHOULD\n | \n\n _id\n | \n\n token \n | \n\n |
\n SHALL\n | \n\n identifier\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
\n SHALL\n | \n\n patient\n | \n\n reference \n | \n\n \n \nThe client SHALL provide at least an id value and MAY provide both the Type and id values. \nThe server SHALL support both. \n | \n
\n SHOULD\n | \n\n patient.identifier\n | \n\n reference.token \n | \n\n \n \nThe client SHALL provide both the system and code values. \nThe server SHALL support both. \nThe client SHOULD support search using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. \nThe server SHOULD support search using the using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. \n | \n
\n MAY\n | \n\n authoredon\n | \n\n date \n | \n\n \n \nThe client SHALL provide a value precise to the second + time offset. \nThe server SHALL support a value precise to the second + time offset. \nThe client SHALL support these search comparators The server SHALL support these search comparators | \n
\n MAY\n | \n\n category\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
\n MAY\n | \n\n intent\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
\n MAY\n | \n\n status\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
resolves
\nread
,search-type
.\ncreate
,update
,delete
,vread
,patch
,history-instance
.\n\n\n\n\nIf the server supports the MedicationStatement resource, the server SHALL support the AU Core profile and the conformance expectations for the MedicationStatement resource.
\nThe MedicationStatement resources can represent a medication using either a code or refer to the Medication resource. When referencing Medication, the resource may be contained or an external resource. The server MAY choose any one way or more than one method, but if an external reference to Medication is used, the server SHALL support the
\n_include
parameter for searching this element. The client application SHALL support all methods.
Conformance | \nParameter | \nType | \nDocumentation | \n
---|---|---|---|
\n SHALL\n | \n\n patient\n | \n\n reference \n | \n\n \n \nThe client SHALL provide at least an id value and MAY provide both the Type and id values. \nThe server SHALL support both. \n | \n
\n SHOULD\n | \n\n patient.identifier\n | \n\n reference.token \n | \n\n \n \nThe client SHALL provide both the system and code values. \nThe server SHALL support both. \nThe client SHOULD support search using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. \nThe server SHOULD support search using the using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. \n | \n
\n MAY\n | \n\n effective\n | \n\n date \n | \n\n \n \nThe client SHALL provide a value precise to the second + time offset. \nThe server SHALL support a value precise to the second + time offset. \nThe client SHALL support these search comparators The server SHALL support these search comparators | \n
\n MAY\n | \n\n status\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
resolves
\nread
,search-type
.\ncreate
,update
,delete
,vread
,patch
,history-instance
.\n\n\n\n\nIf the server supports the Observation resource, the server SHALL support the AU Core profile and the conformance expectations for the Observation resource.
\n
Conformance | \nParameter | \nType | \nDocumentation | \n
---|---|---|---|
\n SHALL\n | \n\n patient\n | \n\n reference \n | \n\n \n \nThe client SHALL provide at least an id value and MAY provide both the Type and id values. \nThe server SHALL support both. \n | \n
\n SHOULD\n | \n\n patient.identifier\n | \n\n reference.token \n | \n\n \n \nThe client SHALL provide both the system and code values. \nThe server SHALL support both. \nThe client SHOULD support search using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. \nThe server SHOULD support search using the using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. \n | \n
\n MAY\n | \n\n category\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
\n MAY\n | \n\n code\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
\n MAY\n | \n\n date\n | \n\n date \n | \n\n \n \nThe client SHALL provide a value precise to the second + time offset. \nThe server SHALL support a value precise to the second + time offset. \nThe client SHALL support these search comparators The server SHALL support these search comparators | \n
\n MAY\n | \n\n status\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
Conformance | \nParameters | \nTypes | \n
---|---|---|
\n SHALL\n | \n\n patient+ category\n | \n\n reference + token \n | \n
\n SHALL\n | \n\n patient+ category+ date\n | \n\n reference + token + date \n | \n
\n SHOULD\n | \n\n patient+ category+ status\n | \n\n reference + token + token \n | \n
\n SHALL\n | \n\n patient+ code\n | \n\n reference + token \n | \n
\n SHOULD\n | \n\n patient+ code+ date\n | \n\n reference + token + date \n | \n
resolves
\nread
,search-type
.\ncreate
,update
,delete
,vread
,patch
,history-instance
.\n\n\n\n\nIf the server supports the Organization resource, the server SHALL support the AU Core profile and the conformance expectations for the Organization resource.
\n
Conformance | \nParameter | \nType | \nDocumentation | \n
---|---|---|---|
\n SHALL\n | \n\n address\n | \n\n string \n | \n\n |
\n SHALL\n | \n\n identifier\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and SHOULD provide both the system and code values. \nThe server SHALL support both. \nThe client SHOULD support search using HPI-O and ABN identifiers as defined in the profile. \nThe server SHOULD support search using HPI-O and ABN identifiers as defined in the profile. \n | \n
\n SHALL\n | \n\n name\n | \n\n string \n | \n\n |
\n SHOULD\n | \n\n _id\n | \n\n token \n | \n\n |
resolves
\nread
,search-type
.\ncreate
,update
,delete
,vread
,patch
,history-instance
.\n\n\n\n\nThe server SHALL support the Patient resource, the AU Core profile, and the conformance expectations for the Patient resource.
\nServers SHALL support the capability for a client application to access the patient record using any of the following API calls:
\n\n
\nGET [url]/Patient/[id]
\n\n
\nGET [url]/Patient?_id=[id]
\n\n
\nGET [url]/Patient?identifier=[identifier]
\nServers are not required to support any additional search parameters, and clients SHOULD NOT expect servers to do so.
\n
Conformance | \nParameter | \nType | \nDocumentation | \n
---|---|---|---|
\n SHALL\n | \n\n _id\n | \n\n token \n | \n\n |
\n SHALL\n | \n\n identifier\n | \n\n token \n | \n\n \n \n\n \n The client SHALL provide both the system and code values. \nThe server SHALL support both. \nThe client SHOULD support search using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. \nThe server SHOULD support search using the using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. \n | \n
\n SHOULD\n | \n\n name\n | \n\n string \n | \n\n |
\n SHOULD\n | \n\n family\n | \n\n string \n | \n\n |
\n MAY\n | \n\n birthdate\n | \n\n date \n | \n\n \n \nThe client SHALL provide a value precise to the day offset. \nThe server SHALL support a value precise to the day offset. \nThe client SHALL support these search comparators The server SHALL support these search comparators | \n
\n MAY\n | \n\n gender\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
\n MAY\n | \n\n indigenous-status\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
\n MAY\n | \n\n patient-gender-identity\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
Conformance | \nParameters | \nTypes | \n
---|---|---|
\n SHOULD\n | \n\n birthdate+ family\n | \n\n date + string \n | \n
\n SHOULD\n | \n\n birthdate+ name\n | \n\n date + string \n | \n
\n SHOULD\n | \n\n family+ gender\n | \n\n string + token \n | \n
\n SHOULD\n | \n\n gender+ name\n | \n\n reference + string \n | \n
resolves
\nread
,search-type
.\ncreate
,update
,delete
,vread
,patch
,history-instance
.\n\n\n\n\nIf the server supports the Practitioner resource, the server SHALL support the AU Core profile and the conformance expectations for the Practitioner resource.
\n
Conformance | \nParameter | \nType | \nDocumentation | \n
---|---|---|---|
\n SHALL\n | \n\n identifier\n | \n\n token \n | \n\n \n \nThe client SHALL provide both the system and code values. \nThe server SHALL support both. \nThe client SHOULD support search using a HPI-I identifier as defined in the profile. \nThe server SHOULD support search using a HPI-I identifier as defined in the profile. \n | \n
\n SHOULD\n | \n\n name\n | \n\n string \n | \n\n |
\n SHALL\n | \n\n _id\n | \n\n token \n | \n\n |
resolves
\nread
,search-type
.\ncreate
,update
,delete
,vread
,patch
,history-instance
.\n\n\n\n\nIf the server supports the PractitionerRole resource, the server SHALL support the AU Core profile and the conformance expectations for the PractitionerRole resource.
\n
Conformance | \nParameter | \nType | \nDocumentation | \n
---|---|---|---|
\n SHALL\n | \n\n identifier\n | \n\n token \n | \n\n \n \nThe client SHALL provide both the system and code values. \nThe server SHALL support both. \nThe client SHOULD support search using a Medicare Provider Number identifier as defined in the profile. \nThe server SHOULD support search using a Medicare Provider Number identifier as defined in the profile. \n | \n
\n SHALL\n | \n\n practitioner\n | \n\n reference \n | \n\n \n \nThe client SHALL provide at least an id value and MAY provide both the Type and id values. \nThe server SHALL support both. \n | \n
\n SHOULD\n | \n\n practitioner.identifier\n | \n\n reference.token \n | \n\n \n \nThe client SHALL provide at least a code value and SHOULD provide both the system and code values. \nThe server SHALL support both. \nThe client SHOULD support search using a HPI-I identifier as defined in the AU Core Practitioner profile. \nThe server SHOULD support search using a HPI-I identifier as defined in the AU Core Practitioner profile. \n | \n
\n SHOULD\n | \n\n _id\n | \n\n token \n | \n\n |
\n SHOULD\n | \n\n specialty\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
\n MAY\n | \n\n organization\n | \n\n reference \n | \n\n \n \nThe client SHALL provide at least an id value and MAY provide both the Type and id values. \nThe server SHALL support both. \n | \n
resolves
\nread
,search-type
.\ncreate
,update
,delete
,vread
,patch
,history-instance
.\n\n\n\n\nIf the server supports the Procedure resource, the server SHALL support the AU Core profile and the conformance expectations for the Procedure resource.
\n
Conformance | \nParameter | \nType | \nDocumentation | \n
---|---|---|---|
\n SHALL\n | \n\n patient\n | \n\n reference \n | \n\n \n \nThe client SHALL provide at least an id value and MAY provide both the Type and id values. \nThe server SHALL support both. \n | \n
\n SHOULD\n | \n\n patient.identifier\n | \n\n reference.token \n | \n\n \n \nThe client SHALL provide both the system and code values. \nThe server SHALL support both. \nThe client SHOULD support search using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. \nThe server SHOULD support search using the using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. \n | \n
\n MAY\n | \n\n code\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
\n MAY\n | \n\n date\n | \n\n date \n | \n\n \n \nThe client SHALL provide a value precise to the second + time offset. \nThe server SHALL support a value precise to the second + time offset. \nThe client SHALL support these search comparators The server SHALL support these search comparators | \n
\n MAY\n | \n\n status\n | \n\n token \n | \n\n \n \nThe client SHALL provide at least a code value and MAY provide both the system and code values. \nThe server SHALL support both. \n | \n
resolves
\nread
.\nsearch-type
,create
,update
,delete
,vread
,patch
,history-instance
.\n\n\n\n\nIf the server supports the Provenance resource, the server SHALL support the AU Core profile and the conformance expectations for the Provenance resource.
\n