TrakCare Solution Guide

Section 2: TrakCare Modules

2.1 TrakCare Core Components

TrakCare is based upon the core software components supporting the Electronic Patient Record and the Patient Master Index. In addition, TrakCare provides application functionality to support the needs of the healthcare information system across clinical, administrative, and departmental requirements.

2.1.1 Electronic Patient Record (EPR)

The EPR within TrakCare is designed to capture the continuum of clinical and administrative information about a patient. The record contains patient demographics, medical history, previous admission information, previous surgery information, and obstetric history. Patient information can be captured from legacy systems linked through the TrakCare Integration Platform, or the information can be obtained directly from the full set of TrakCare applications.

To access the EPR, the patient is identified by number, or name, or from an optional favourites list if he is seen often by the clinician. The EPR provides a visual display of all information that has been collected.

The EPR includes:

  • Patient History allows healthcare professionals to view, amend, or add to the patient¡¯s past medical, social, and family history.
  • Allergies and Alerts allows healthcare professionals to view previously recorded allergies and alerts as well as add those newly identified. In addition to notifying clinicians of potential risk to the patient, information about the nature and severity of allergic reactions is also available if it has been captured. The severity can be colour-coded to provide a visual display of allergic sensitivities.
  • Results and Order History presents the results and order history of diagnostic and investigative procedures. Results can be sent from the departmental system to the EPR via the TrakCare Integration Platform. This gives healthcare professionals access to results within the EPR view. Results can be displayed in a singular or cumulative format and are presented with clinical indicators, including abnormal results, reference ranges, and criticality status where applicable. System-based highlights and icons act as alerts to abnormal as well as new results.
  • Diagnosis Entry allows the input of multiple diagnoses and diagnosis status for each patient episode, including admitting diagnosis, suspected diagnosis, final diagnosis, and discharge diagnosis. The diagnoses may be based on ICD-10 or a similar coding system.
  • Patient Notes Entry allows the clinician to enter and view patients¡¯ conditions. Notes Entry tools include strikethrough to view modifications to notes and coded text entry, facilitating the quick entry of standard phrases and comments.
  • Clinical Summary History, also referred to as discharge summary, allows the clinician to view previous discharge summaries generated for a patient. This can be viewed in text or tabular format.
  • Time Line graphically displays the patient¡¯s EPR. It also allows healthcare professionals to select one or more episodes to view patient data concurrently in the format of the defined EPR charts.

2.1.2 Patient Master Index (PMI)

The PMI is the cornerstone of the TrakCare system, supporting the patient-centric EPR. As well as being able to run the PMI functions independently, these functions are an integral part of each TrakCare module (e.g., when a patient is admitted to the hospital, the PMI Search and Registration functions can be included as part of the workflow for the admission process).

The Patient Master Index is the cornerstone of the TrakCare system, supporting the patient-centric EPR. The PMI can be run as a stand-alone within the hospital (or group of hospitals) or can be part of a larger state or national system.

The PMI can be run as a stand-alone within the hospital (or group of hospitals) or can be part of a larger state or national system. In the latter situation, a patient may have a local identifier as well as a state or national identifier. The TrakCare system allows for this identifier to be assigned by the appropriate provider.

A unique hospital identifier differentiates each patient. The format of this identifier is definable by the hospital and may be purely numeric or a combination of alpha and numeric characters. The hospital identifier can be automatically assigned to the patient or manually entered at registration time.

The TrakCare PMI provides healthcare facilities with the ability to record extensive information about a patient. The details displayed can be configured by the hospital using the TrakCare Layout Editor.

Typically, this screen would contain:

  • Fields for entering a patient¡¯s socio-demographic details to defining mandatory fields (e.g., patient title, surname, given name, sex, date of birth, address, language spoken, country of birth, etc.)
  • Links to other screens for entering:
    • Other address details (e.g., previous addresses, postal address, and mailing address)
    • Contact details (e.g., next of kin, nearest relative, or guarantor)
    • Alerts (e.g., medical, administrative, and clinical)
    • Alias details (e.g., names, sex, date of birth)
    • General practitioner details (or viewing these details)
    • Family doctor history
    • Links (e.g., family, mother/baby)
    • Audit details, such as who last updated the record, all changes made to the record, and details of who has viewed the record Other functionality within the PMI includes:
    • Specific edit restraints set for each field
    • If the patient¡¯s name, sex, or date of birth fields are changed, the user is asked whether to create an alias of the old details
    • If the address or phone number information of the patient is changed, a history of previous addresses/phone is maintained
    • When the suburb is entered, a postcode search facility is available
    • If the patient¡¯s exact date of birth is unknown, an estimated date can be recorded and a flag can be set to indicate this

2.1.3 Application Integration Platform

TrakCare derives much of its power from the fact that it has been built on InterSystems Ensemble¢ç, a rapid integration platform. Designed with today¡¯s Web and service-oriented architectures in mind, TrakCare excels at quickly creating and deploying new business solutions that leverage the functionality of existing applications, orchestrate new business processes, and integrate data from across the entire hospital, outsourced service providers, and community health services.

2.1.4 Healthcare Applications

TrakCare offers a comprehensive set of application modules that assist in the smooth functioning of healthcare facilities. By design, the system focuses on the patient, managing both clinical and administrative information via the EPR. Modules include:

  • TrakCare Clinicals
  • TrakCare Patient Administration System
  • TrakCare Community
  • TrakCare Emergency Management
  • TrakCare Laboratory

TrakCare supports the entire continuum of care, providing the right information to the right healthcare professional at the right time.

TrakCare Supports the Continuum of Care

Previous Page

Previous Page
Section 1

Table of Contents

Next Page
Section 2.2

Next Page