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
| Official URL: http://medicaldirector.com/fhir/helix-base/ValueSet/helix-patient-status | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 2 | Computable Name: HelixAUCorePatientStatus | ||
References
http://medicaldirector.com/fhir/helix-base/CodeSystem/helix-patient-status
Expansion performed internally based on codesystem Helix Patient Status v0.1.0 (CodeSystem)
This value set contains 3 concepts
| Code | System | Display | Definition |
| 1 | http://medicaldirector.com/fhir/helix-base/CodeSystem/helix-patient-status | Provisional | '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. |
| 2 | http://medicaldirector.com/fhir/helix-base/CodeSystem/helix-patient-status | Existing | 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. |
| 3 | http://medicaldirector.com/fhir/helix-base/CodeSystem/helix-patient-status | Migrated | '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. |
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
| Code | The code (used as the code in the resource instance) |
| Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
| Definition | An explanation of the meaning of the concept |
| Comments | Additional notes about how to use the code |