Helix AU Core
0.1.0 - ci-build
Helix AU Core
0.1.0 - ci-build
Helix AU Core - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
These define constraints on FHIR resources for systems conforming to this implementation guide.
| Helix AU Core AllergyIntolerance | |
| Helix AU Core Appointment | |
| Helix AU Core Claim | |
| Helix AU Core Condition | |
| Helix AU Core DiagnosticReport | |
| Helix AU Core DocumentReference | |
| Helix AU Core Encounter | |
| Helix AU Core Endpoint | |
| Helix AU Core FamilyMemberHistory | |
| Helix AU Core HealthcareService | |
| Helix AU Core Immunisation |
An immunisation statement in Helix. |
| Helix AU Core Location | |
| Helix AU Core MedicationRequest | |
| Helix AU Core MedicationStatement | |
| Helix AU Core Observation | |
| Helix AU Core Organization | |
| Helix AU Core Patient |
A patient in the context of MedicalDirector Helix. |
| Helix AU Core Practitioner |
A practitioner in the context of MedicalDirector Helix. |
| Helix AU Core PractitionerRole | |
| Helix AU Core RelatedPerson | |
| Helix AU Core Schedule | |
| Helix AU Core Slot |
Slot resources are used to provide time-slots that can be booked using an appointment. |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| Helix AU Core Medical Objects Routing ID |
Medical Objects Routing ID - see https://kb.medical-objects.com.au/display/PUB/Provider+Identifiers |
| Helix AU Core Medical Record Number |
Medical record number |
| Helix AU eRx ETP Identifier |
eRx ETP Identifier - see https://fhir.medicationknowledge.com.au/0.2.0/guidance-mk.html |
| Helix Base Authoring Key |
System of origin for a particular resource |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| Appointment Status History | |
| Helix AU Core Endpoint Receiving Facility |
Indicates the receiving facility name. |
| Helix AU Core Immunisation Consent Provided By |
Description of who provided consent to administer the vaccine. |
| Helix AU Core Patient SMS Opt-in |
Indicates if the patient opted in to recieve SMS. |
| Helix Base Practitioner Is HCP User |
Is HCP User |
| Helix Patient Status |
This extension applies to the Patient resource and it reflects the possible states that a patient's record can be in within Helix. |
These define sets of codes used by systems conforming to this implementation guide.
| Appointment Type |
The Helix Appointment Type code system reflects the possible type values that can be assigned to a given appointment. |
| Document Category |
The Document Category outlines the different categories that can be assigned to a document. Contains a subset of the 'Record artefact foundation reference set' <https://healthterminologies.gov.au/fhir/ValueSet/sctau-reference-set-32570161000036106>. |
| Helix AU Core Appointment Types |
Allowed subset of AppointmentStatus for Helix AU Core |
| Helix Patient Status | |
| Practitioner Role Specialty |
The Practitioner Role Specialty outlines the diverse specializations accessible to practitioners within the Helix platform |
These define new code systems used by systems conforming to this implementation guide.
| Appointment Service Type |
Appointment Service Type refers to the method by which the appointment is to take place |
| Appointment Type |
The Helix Appointment Type code system reflects the possible type values that can be assigned to a given appointment. Appointment Type refers to the reason for which the appointment has been made. This list is the default supplied list of appointments for a new Helix customer. |
| Appointment Type External |
Appointment Type External is a combination of the Appointment Type and Appointment Service Type with a hyphen separating the two. Note that the AppointmentType itself can also include hyphens. |
| Helix Patient Status |
The Helix Patient Status code system reflects the possible states that a patient's record can be in within Helix. 'Provisional' patients are those which have incomplete or not yet validated demographics. An example of when a patient with a 'Provisional' status is created is for ad-hoc appointment bookings over the phone or via Online Booking systems where the patient is not required to provide all the mandatory fields required to be an 'Existing' patient in Helix. An 'Existing' patient can most easily be interpreted as a normal patient who has visited the practice or health care provider more than once; their demographic details are complete and have been validated by someone in the Helix system.Finally, ' Migrated ' records is a special-case status for records that have been migrated to the Helix database from another clinical system. They are similar to 'Provisional' records in that they are not yet validated in terms of demographics, but in addition to that, they may also have clinical information that needs to be reviewed and validated by a Health Care Professional in the Helix System |
| Practitioner Role Specialty |
The Practitioner Role Specialty outlines the diverse specializations accessible to practitioners within the Helix platform. |