The UCUM codes, UCUM table (regardless of format), and UCUM Specification are copyright 1999-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. https://ucum.org/trac/wiki/TermsOfUse
This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed
or info@snomed.org
.
The contents of this FHIR Implementation Guide serves to provide examples and information on the recommended ways to integrate with the Medtech ALEX® API, including use-cases, examples, FHIR Profiles, and validation/conformance artifacts. ( src
)
HPI-O - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
HPI-O Status - Definitions - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
HPI-O Status - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
HPI-O Status - Mappings - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
HPI-O Status - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
HPI-O Status - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
HPI-O Status - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
HPI-O Status - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Home - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
ICPC2 Plus CodeSystem for Condition - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
ICPC2 Plus CodeSystem for Condition - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
ICPC2 Plus CodeSystem for Condition - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
ICPC2 Plus CodeSystem for Condition - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
ICPC2 Plus CodeSystem for Condition - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
If the request was accepted, the identity provider will provide a response containing the access token. The access token can now be used to make requests to the Medtech FHIR® API. ( src
)
Immunisation Vaccine Codes - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Immunisation Vaccine Value Set - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Immunisation Vaccine Value Set - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Immunisation Vaccine Value Set - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Immunisation Vaccine Value Set - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Immunisation Vaccine Value Set - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
In order for a vendor application to make requests to the Medtech FHIR® API, a valid access token must be included in the requests. To obtain an access token, an authentication request is made to the identity provider service and the returned access token is then included in the headers of subsequent requests to the Medtech FHIR® API. ( src
)
Individual Healthcare Identifier Record Status - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Individual Healthcare Identifier Record Status - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Individual Healthcare Identifier Record Status - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Individual Healthcare Identifier Record Status - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Individual Healthcare Identifier Record Status - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Individual Healthcare Identifier Status - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Individual Healthcare Identifier Status - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Individual Healthcare Identifier Status - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Individual Healthcare Identifier Status - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Individual Healthcare Identifier Status - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Interpretation Value Set for Observation - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Interpretation Value Set for Observation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Interpretation Value Set for Observation - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Interpretation Value Set for Observation - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Interpretation Value Set for Observation - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Medtech ALEX® AU Implementation Guide - Local Development build (v1.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions ( src
)
PractitionerRole profile - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Priority for Medication Request - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Priority for Medication Request - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Priority for Medication Request - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Priority for Medication Request - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Priority for Medication Request - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Privacy metadata indicating the level of protection required to safeguard potentially stigmatizing information, which if disclosed without authorization, would present a high risk of harm to an individual's reputation and sense of privacy.*Usage Note:* The level of protection afforded restricted confidential information is dictated by specially protective organizational or jurisdictional privacy policies, including at an authorized individual's request, intended to engender patient trust in providers of sensitive services.Privacy policies mandating additional levels of protection by restricting information access preempt less protective privacy policies when the information is used in the delivery and management of healthcare. May be pre-empted by jurisdictional law (e.g., for public health reporting or emergency treatment).Confidentiality code total order hierarchy: Restricted (R) is less protective than *V*, and subsumes all other protection levels (i.e., *N, M, L, and U*).**Examples:** Includes information that is additionally protected such as sensitive conditions mental health, HIV, substance abuse, domestic violence, child abuse, genetic disease, and reproductive health; or sensitive demographic information such as a patient's standing as an employee or a celebrity. May be used to indicate proprietary or classified information that is not related to an individual (e.g., secret ingredients in a therapeutic substance; or the name of a manufacturer). ( src
)
Prompt Value Set for Measurement - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Prompt Value Set for Measurement - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Prompt Value Set for Measurement - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Prompt Value Set for Measurement - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Prompt Value Set for Measurement - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Reason for Request - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Reason for Request - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Reason for Request - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Reason for Request - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Reason for Request - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Sex at Birth extension - Definitions - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Sex at Birth extension - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Sex at Birth extension - Mappings - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Sex at Birth extension - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Sex at Birth extension - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Sex at Birth extension - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Sex at Birth extension - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Allergy Intolerance - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Allergy Intolerance - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Allergy Intolerance - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Allergy Intolerance - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Allergy Intolerance - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Condition - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Condition - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Condition - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Condition - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Condition - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Immunisation - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Immunisation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Immunisation - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Immunisation - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Immunisation - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Medication Request - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Medication Request - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Medication Request - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Medication Request - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Medication Request - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Medication Statement - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Medication Statement - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Medication Statement - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Medication Statement - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Status for Medication Statement - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Table of Contents - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
The DVA Entitlement for Patient - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
The DVA Entitlement for Patient - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
The DVA Entitlement for Patient - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
The DVA Entitlement for Patient - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
The DVA Entitlement for Patient - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
The Medtech ALEX® API provides a secure connection for services and applications like patient portals, telehealth or kiosks to exchange information with your PMS. Without ALEX® third parties can only connect to your PMS by making their own read/write requests directly to the Medtech PMS database. There are no approved security standards or appropriate safeguards for this connection, and your informed consent may not have been requested. This connection unnecessarily exposes your (vulnerable) patient, staff and financial data to inadvertent sharing or extraction. It also slows down the operation of your PMS and when Medtech releases an update, these connections can break and it is difficult to identify the source of the issue in order to fix it. With ALEX® data can only be accessed or extracted from your site for a required and permitted healthcare event, and only with your practice consent. ( src
)
The access_token which was obtained from the identity provider can now be used to make authenticated requests to the Medtech FHIR® API. ( src
)
There are examples where a medication request may include the option of an oral dose or an Intravenous or Intramuscular dose. For example, "Ondansetron 8mg orally or IV twice a day as needed for nausea" or "Compazine® (prochlorperazine) 5-10mg PO or 25mg PR bid prn nausea or vomiting". In these cases, two medication requests would be created that could be grouped together. The decision on which dose and route of administration to use is based on the patient's condition at the time the dose is needed. ( src
)
This StructureDefinition describes the NCTS Complete Code System, a profile of the FHIR® CodeSystem resource. The NCTS Complete Code System is designed to represent terminologies published as part of the National Clinical Terminology Service, and maximise interoperability within the NCTS ecosystem. ( src
)
This StructureDefinition describes the NCTS Composed Value Set, a profile of the FHIR® ValueSet resource. The NCTS Composed Value Set is designed to represent value sets published as part of the National Clinical Terminology Service, and maximise interoperability within the NCTS ecosystem. ( src
)
This document covers the Authentication process, Request Message details and Error Messages that will be required to integrate with Medtech’s FHIR® API Solution (ALEX). ( src
)
This resource includes SNOMED Clinical Terms™ (SNOMED CT®) which is used by permission of the International Health Terminology Standards Development Organisation (IHTSDO). All rights reserved. SNOMED CT®, was originally created by The College of American Pathologists. “SNOMED” and “SNOMED CT” are registered trademarks of the IHTSDO. ( src
)
Type of Allergy Intolerance - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Type of Allergy Intolerance - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Type of Allergy Intolerance - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Type of Allergy Intolerance - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Type of Allergy Intolerance - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Type of Allergy Intolerance Reaction - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Type of Allergy Intolerance Reaction - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Type of Allergy Intolerance Reaction - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Type of Allergy Intolerance Reaction - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Type of Allergy Intolerance Reaction - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Unique identifier of the Medtech FHIR® API. Provided to the vendor by Medtech. ( src
)
Unit Value Set for Observation Component - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Unit Value Set for Observation Component - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Unit Value Set for Observation Component - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Unit Value Set for Observation Component - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Unit Value Set for Observation Component - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Vaccine Vial Serial Number - Definitions - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Vaccine Vial Serial Number - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Vaccine Vial Serial Number - Mappings - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Vaccine Vial Serial Number - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Vaccine Vial Serial Number - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Vaccine Vial Serial Number - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Vaccine Vial Serial Number - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Verification Status for Condition - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Verification Status for Condition - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Verification Status for Condition - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Verification Status for Condition - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Verification Status for Condition - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Writeback Action Type CodeSystem - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Writeback Action Type CodeSystem - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Writeback Action Type CodeSystem - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Writeback Action Type CodeSystem - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Writeback Action Type CodeSystem - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Writeback Action Type Value Set - JSON Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Writeback Action Type Value Set - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Writeback Action Type Value Set - TTL Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Writeback Action Type Value Set - Testing - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
Writeback Action Type Value Set - XML Representation - Medtech ALEX® AU Implementation Guide v1.0.0 ( src
)
The codes SHOULD be taken from For example codes, see
Body Site http://hl7.org/fhir/ValueSet/body-site|4.0.1
( preferred
to https://healthterminologies.gov.au/fhir/ValueSet/body-site-1
)
This identifier profile defines a Healthcare Provider Identifier - Organisation in an Australian context (see Australian Digital Health Agency
for further information). An HPI-O is assigned under the HI Service to an organisation (such as a hospital or medical clinic) where healthcare is provided.
The codes SHOULD be taken from For example codes, see
Reason Vaccine Administered http://hl7.org/fhir/ValueSet/immunization-reason|4.0.1
( preferred
to https://healthterminologies.gov.au/fhir/ValueSet/reason-vaccine-administered-1
)
The codes SHOULD be taken from
Reason Vaccine Administered
( preferred
to https://healthterminologies.gov.au/fhir/ValueSet/reason-vaccine-administered-1
)
The codes SHOULD be taken from
Vaccination Target Disease
( preferred
to https://healthterminologies.gov.au/fhir/ValueSet/vaccination-target-disease-1
)
In some circumstances, systems may capture date or dateTime data that has unknown or estimated parts. This coding indicates the accuracy of the day, month and year parts. This concept is equivalent to Australian Institute of Health and Welfare data element 294418 Date—accuracy indicator
.
Unless not suitable, these codes SHALL be taken from
Common Languages in Australia
( extensible
to https://healthterminologies.gov.au/fhir/ValueSet/common-languages-australia-2
)
Unless not suitable, these codes SHALL be taken from The codes SHOULD be taken from
Common Languages in Australia http://hl7.org/fhir/ValueSet/languages|4.0.1
( extensible
to https://healthterminologies.gov.au/fhir/ValueSet/common-languages-australia-2
)
