WO2017100833A1

WO2017100833A1 - A method of using a computer system to support a triage assessment

Info

Publication number: WO2017100833A1
Application number: PCT/AU2016/051221
Authority: WO
Inventors: Chris Raftery; Martin Snide
Original assignee: Etrihealth Pty Ltd
Priority date: 2015-12-16
Filing date: 2016-12-12
Publication date: 2017-06-22
Also published as: AU2015101805A4

Abstract

The invention relates to a method (18) of using a computer system to support a triage assessment process. The method includes configuring the computer system such that the computer system is enabled for triggering (20) a sequence of events that render on a screen, input screen components that include interrogative triage constructs. The method also includes receiving (22) at least some inputs from at least some of the input screen components during the sequence of events, and in response, determining (24) declarative triage constructs corresponding to the received at least some inputs. Using the declarative triage constructs, the computer system generates (26) a narrative triage construct for rendering on the screen in a format that supports the making of a triage assessment finding. The invention extends to a computer system that is configured to perform the method, and to a computer program product that is used to configure the computer system.

Description

A METHOD OF USING A COMPUTER SYSTEM TO SUPPORT A TRIAGE

ASSESSMENT PROCESS

FIELD OF INVENTION

The present invention relates to a method of using a computer system to support a triage assessment process, and to a computer system that is configured to execute that method. The invention extends to a computer system installation that includes such computer systems. BACKGROUND OF THE INVENTION

Hospital emergency departments are under immense pressure to perform triage assessments and to treat patients under demanding and difficult circumstances. Doctors, nurses and other staff that conduct triages assessments are under time critical constraints to assess a patient's needs and to prioritize that patient correctly and adequately. There is often a queue of patients awaiting triage assessments. In addition, there can be duplication of effort by personal that are involved in the triage assessment process. This duplication and redundancy slows the processing of patients and as to how soon they can be attended to by medical staff.

OBJECT OF THE INVENTION

The object of the current invention is to provide improvements in processing patients through a triage assessment process by providing methods of using computer systems to support triage assessment processes and computer systems configured to execute such methods, that are useful, or to provide alternative methods and computer systems having useful features, at least to provide users with a useful choice.

SUMMARY OF THE INVENTION

The inventors of the current invention identified the problems of collecting and processing patient information where different staff members provide input from different perspectives. The inventors developed a process and system that was patient-centric rather than focussed on medical staff enquiries and collating information from the separate views of the nurses, doctors, other medical staff, pharmacists, or paramedics as the patient passes through these various stations.

In one aspect the present invention provides a method of using a computer system to support a triage assessment process, the method including configuring the computer system such that the computer system is enabled for

triggering a sequence of events that render on a screen, input screen components that include interrogative triage constructs;

receiving at least some inputs from at least some of the input screen components during the sequence of events;

in response, determining declarative triage constructs corresponding to the received at least some inputs; and

using the declarative triage constructs, generating a narrative triage construct for rendering on the screen in a format that supports the making of a triage assessment finding by a triage assessor.

In each case that support is required for the triage assessment process, the sequence of events can include stepping through a sequence of main triage assessment events, and

rendering, during each main triage assessment events, input screen components that include interrogative triage constructs that are associated with that main triage assessment event.

The method can include, during each main triage assessment event, receiving at least some inputs from at least some of the input screen components that are rendered during that main triage assessment event, and

depending on the received at least some inputs

either rendering further input screen components that include interrogative triage constructs that are associated with that main triage assessment events,

or progressing to a next step in the sequence of main triage assessment events.

The sequence of main triage assessment events can include an initial main triage assessment event that renders input screen components that include interrogative triage constructs that relate to personal details of a patient that needs to be assessed. The sequence of main triage assessment events can include intermediate main triage assessment events that render input screen components that include interrogative triage constructs that relate to any one of clinical conditions or issues, symptoms, and medical histories.

The sequence of main triage assessment events can include a final main triage assessment event that renders input screen components that include the narrative triage construct for rendering on the screen in a format that supports the making of the triage assessment finding by a triage assessor, and input screen components that include triage finding constructs for receiving inputs of a triage finding made based on the the narrative triage construct.

Determining declarative triage constructs corresponding to the received at least some inputs can include selecting for at least some of the at least some received inputs associated pre-constructed declarative triage constructs.

Generating the narrative triage construct can include constructing a personal details narrative construct and a clinical narrative construct.

The clinical narrative construct can include selecting pre-constructed declarative triage constructs that correspond to the received inputs during the intermediate events of the sequence of main triage assessment events, and arranging those declarative triage constructs in an order that corresponds with a sequence in which the at least some inputs were received during that intermediate events of the sequence of main triage assessment events.

The method can include using the declarative constructs to populate a triage assessment register, for example by interfacing with a triage assessment register of of an existing emergency patient management system.

The method can include using the declarative constructs to populate a medical record register, for example by interfacing with a medical record register of an existing electronic medical records system.

According to another aspect the invention provides a computer system that is used to support a triage assessment process, the computer system being configured to execute the method as herein defined, described, and illustrated.

According to yet another aspect the invention provides a computer system installation that is used to support a triage assessment process, the computer system installation including a plurality of terminal computer systems that are in data communication with a server computer system, the terminal computer systems and server computer system being configured to execute the method as herein defined, described, and illustrated.

According to another aspect of the invention, there is provided a computer program product that includes computer readable instructions, which when executed, enables a computer system to perform the method as herein defined, described, and illustrated.

The invention extends to a method substantially as herein described and illustrated with reference to the drawings.

The invention extends to a computer system substantially as herein described and illustrated with reference to the drawings.

The invention extends to a computer system installation substantially as herein described and illustrated with reference to the drawings.

The features described with respect to one aspect also apply where applicable to all other aspects of the invention. Furthermore different combinations of described features are herein described and claimed even when not expressly stated. BRIEF DESCRIPTION OF THE DRAWINGS

In order that the present invention can be more readily understood reference will now be made to the accompanying drawings which illustrate a preferred embodiment of the invention and wherein:

Figure 1 shows a diagrammatic drawing of a computer system, in accordance with the invention, that includes a plurality of terminal computer systems that are in data communication with a server computer system over a data communication network and that are used to support a triage assessment process;

Figure 2 shows a function flow diagram of a method, in accordance with the invention, of using a computer system to support a triage assessment process;

Figure 3 shows a function flow diagram of a main triage assessment event that forms part of the method in Figure 1 ;

Figure 4 shows a functional flow diagram of a main triage assessment event in Figure 3 in more detail; Figure 5 shows a functional flow diagram of another main triage assessment event in Figure 3 in more detail;

Figure 6 shows a functional flow diagram of another main triage assessment event in Figure 3 in more detail;

Figure 7 shows a functional flow diagram of another main triage assessment event in Figure 3 in more detail;

Figure 8 shows a functional flow diagram of another main triage assessment event in Figure 3 in more detail;

Figure 9 shows a functional flow diagram of another main triage assessment event in Figure 3 in more detail;

Figure 10 shows a representation of screen components that are rendered for a start up screen of the terminal computer system for starting a sequence of triage assessment events;

Figure 1 1 shows a representation of screen components that are rendered for a first screen during execution of the functional flow shown in Figure 4;

Figure 12 shows another representation of screen components that are rendered during execution of the functional flow shown in Figure 4;

Figure 13 shows another representation of screen components that are rendered during execution of the functional flow shown in Figure 4;

Figure 14 shows a representation of screen components that are rendered during execution of the functional flow shown in Figure 5;

Figure 15 shows another representation of screen components that are rendered during execution of the functional flow shown in Figure 5;

Figure 16 shows another representation of screen components that are rendered during execution of the functional flow shown in Figure 5;

Figure 17 shows another representation of screen components that are rendered during execution of the functional flow shown in Figure 5;

Figure 18 shows a representation of screen components that are rendered during execution of the functional flow shown in Figure 6;

Figures 18A to 18F show representations of further screen components that could be rendered during execution of the functional flow shown in Figure 6;

Figure 19 shows a representation of screen components that are rendered during execution of the functional flow shown in Figure 7; Figure 20 shows another representation of screen components that are rendered during execution of the functional flow shown in Figure 7;

Figure 21 shows a representation of screen components that are rendered during execution of the functional flow shown in Figure 8;

Figure 22 shows another representation of screen components that are rendered during execution of the functional flow shown in Figure 8;

Figure 23 shows another representation of screen components that are rendered during execution of the functional flow shown in Figure 8;

Figure 24 shows another representation of screen components that are rendered during execution of the functional flow shown in Figure 8;

Figure 25 shows another representation of screen components that are rendered during execution of the functional flow shown in Figure 8;

Figure 26 shows a representation of screen components that are rendered during execution of the functional flow shown in Figure 9;

Figure 27 shows another representation of screen components that are rendered during execution of the functional flow shown in Figure 9;

Figure 28 shows a representation of the population of a triages assessment register based on the main triage assessment events; and

Figure 29 shows a representation of the population of a medical record based on the main triage assessment events.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

In the drawings, reference numeral 10 refers generally to a computer system, in accordance with the invention, that supports a triage assessment process. Broadly, the computer system 10 includes a plurality of terminal computer systems 12 that are in data communication with a server computer system 14 over a data communication network 16.

As illustrated in Figure 1 , the terminal computer systems 12 and the server computer system 14 includes computer readable instructions, 12.1 and 14.1 respectively, which when executed, enable the computer system to perform a method, in accordance with the invention. Although so illustrated, in which part of the instructions are executed client side and other server side, it is meant to include other configurations such as where most of the instructions are executed server side and a thin client is used at client side mainly to render screen components. Also, with terminal computer system is meant to include PCs, tablets, smart phones, and the like.

By way of example, the terminal computer systems 12 are in the form of kiosks that include touch screens and that are installed at a reception area of the emergency department in a hospital where triage personnel have to perform triage assessments. For ease of explanation, the operation of the computer system 10 is explained from a kiosk's 12 point of view.

Broadly, referring to Figure 2, reference numeral 18 refers to a method, in accordance with the invention, in which in the case that support is required for the the triage assessment process, a kiosk 12 is used for triggering, at 20, a sequence of events that render on a screen input screen components that include interrogative triage constructs. At 22, the kiosk 12 receives at least some inputs from at least some of the input screen components during the sequence of events, and in response, at 24, determines declarative triage constructs corresponding to the received at least some inputs. Subsequently, at 26, by using the declarative triage constructs, a narrative triage construct is generated for rendering on the screen in a format that supports the making of a triage finding by triage personnel.

Referring to Figure 10, a start up screen 28 that includes screen components is shown which includes four selectable soft buttons. One button 30 which, if selected, trigger the sequence of main triages assessment events, as is further explained below. An emergency button 32 is provided which can be triggered in the case that patent needs attention as a matter of urgency. In such case, the kiosk 12 is still used in emergency mode, for example by a clinician, as opposed to the patient, to enter the required information.

Another soft button, 34, is rendered which when selected enables a patient to select a preferred language that would be used to render the interrogative constructs, as is explained in more detail below.

The startup screen also includes a soft button for selecting a GP letter option, 36, which when selected prompts a patient to present a code, such as a bar code, QR code, pin code, or the like, that when entered, automatically populates the relevant fields that are used for the triage assessment events. In that regard the kiosk can include an appropriate scanner, for example a QR scanner that scans a QR code that is printed on a letter that is provided to a patient by a GP who has already completed the triage assessment process for example from a remote terminal computer system.

When soft button 30 is selected, then the kiosk 12 triggers the sequence of main triage assessment events through which are stepped during the triage assessment process.

In each case that the kiosk 12 is used for support in the triage assessment process a similar sequence of main triage assessment events are followed. Figure 3 shows the main triage assessment events 50. Also, during execution of the main triage assessment events 50, a progression bar is rendered on the screen to indicated progress through the triage assessment events. See for example Figure 12 that shows a progression bar 64. The main triage assessment events 50 that are followed includes triggering successive events that render screen components that include interrogative constructs to receive inputs relating to personal details of the patient, at 52, relating to a main clinical condition or issue, at 54, relating to further detail about the main clinical condition to issue, at 56, relating to symptoms of the main clinical condition or issue, at 58, relating to a medical history of the patient, at 60, and rendering the triage assessment narrative and triage assessment input screen components, at 62.

Referring now to Figure 4, execution if the main triages assessment event 52, is shown in more detail. At 72, screen components are rendered by the kiosk 12, which includes two soft buttons 40 and 42 (see Figure 1 1 ). At 74, if soft button 40 is selected, then the kiosk 12 activates, at 82, a scanner which is capable of scanning an ID card of a patient. The ID card is then scanned, at 84, from which personal details of the cardholder is received, and stored, at 80. If the soft button 42 is activated, then screen components are rendered, at 76, as shown in Figure 12. The screen components include text input boxes 82, 84, 86, for entering a name, surname, and date of birth, and two soft buttons, 88 and 90, for selecting a gender. In this embodiment, a pop up soft keyboard 92 (see for example Figure 13) is used to enter details into text input boxes 82, 84, 86.

At 78, the inputs or details are received, and at 80, the inputs or details are stored. The kiosk 12 then triggers the next main triage assessment event 54, for example by receiving an input by activating the soft button 94.

Figure 5 shows the next main triage assessment event 54 in more detail. At 94, a plurality screen components are rendered in the form of an array of soft buttons of which 104, 106, 107, and 108 are examples. Each soft button, such as 104, 106, 107, and 108, includes an interrogative construct of which 1 10, 1 12, 1 14, and 1 16 are examples. Broadly, the interrogative constructs, 1 10, 1 12, 1 14, and 1 16, are constructed using words that are indicative of questions or commands that relate to clinical conditions or issues for prompting the patient to respond by selecting relevant soft buttons. The interrogative constructs can be a single word, such as 1 12, a collection of words, such as 1 10. The interrogative constructs can therefore indicate main classes of clinical conditions or issues, such as 'BREATHING' as indicated by 1 14, and related subclasses such as 'breathless', 'cough', and 'asthma'.

At 96, the kiosk 12 receives inputs from one or more of the soft buttons as they are activated by a patient, and, at 98, the received inputs are noted by the computer system, for example stored or flagged, so that the computer system can determine which inputs were triggered and hence the interrogative constructs that relates to those inputs that are used later to construct the declarative constructs.

The kiosk then proceeds and generates screen components, at 98, that are associated with one of the received inputs, at 96. Figure 15 shows screen components 1 18 that are in the form a soft buttons and that include interrogative constructs, such as 120. In the screen shot, the interrogative constructs are sub classes of the main classes of clinical conditions or issue 'BREATHING'.

Figures 16 and 17 show other example of screen components that are generated for example when the soft button 'PAIN' is activated, at 96. Figure 16 shows a plurality of screen components in the form of soft buttons 122, each soft button includes an interrogative construct, for example 124. Another screen component 126 is in the form of a representation of a human body and is divided into body zones that correspond to the interrogative constructs included in the soft buttons 122. It follows that when a soft button, say 130, is activated then a corresponding zone 128 on the representation of the human body is highlighted. Further screen components are then generated in response, as for example in Figure 17, that shows a screen component 134 that are a blown up view of the selected zone 128. In the blown up view 134, that zone 128 is further divided into sub-zones as indicate by numerals 1 to 10. A patient can thus select specific zones of the body where pain is experienced. At 100, the kiosk determines if another main class of clinical conditions or issues has been selected and if so, then proceeds to 98 and render the associated screen components and their interrogative constructs. Else, the kiosk proceeds and note the received inputs, at 102, for example by storing or flagging the inputs so that the computer system can determine which inputs were triggered and hence the interrogative constructs that relates to those inputs, and proceed to the next main triage assessment event 56.

Figure 6 shows the main triage assessment event 56 when executed in more detail. At 138, screen components 158 (Figure 18) are rendered in the form of soft buttons that include interrogative constructs relating to time periods, for example 'Minutes', 'Hours', 'Days' and the like, and soft buttons 146 that include the ten numerals, which are used to enter a time frame that a patient has experienced the clinical condition or issue.

Also two soft buttons 148 are rendered, each including an interrogative construct for selecting a 'YES' or 'NO' for indicating whether or not such condition has been experienced before. Similarly, two soft buttons 150 and four soft buttons 152 are rendered having interrogative constructs that relate to whether or not the patient have approached anyone else in the past about the matter and whom.

Yet further, soft buttons 154 and 156 are rendered that include interrogative constructs that relate to whether or not a patient has taken medication for the clinical condition or issue at hand.

At 140, the kiosk 12 receives the inputs from those soft buttons as they are activated by a patient, and, at 142, the received inputs are noted by the computer system, for example stored or flagged, so that the computer system can determine which inputs were triggered and hence the interrogative constructs that relate to those inputs. The kiosk then proceeds to main triage assessment event 58.

Figures 18A to 18F show other screenshots that include screen components that could be rendered at the main triage assessment event 56 about asking more details, depending on the inputs received in the previous may triage assessment event.

Figure 18A shows screen components 280 that include interrogative constructs relating to an injury. That permits a patient to enter information about how long ago the injury occurred, how the injury occurred, for example bay way playing sports, a fall, a accident, assault, or the like. Also, the patient can input information n a textbox about what happened, and indicate if the patient has seen anyone yet about it and if the patient has taken any medication yet.

Figure 18B shows screen components 282 that include interrogative constructs relating to toxicology. Those screenshots includes textboxes that enable a patient to input information about what toxic substance the patient indigested, how much of it, and how long ago. Also, soft buttons are provided to indicate if the event was accidental or intentional, and also whether or not the patient has been drinking alcohol.

Figure 18C shows screen components 284 that include interrogative constructs relating to scripts and includes soft buttons that that enables a patient to input information about the type of script, who normally writes the script, the reasons for coming to the emergency department for the script, whether or not the patient has seen the emergency department for their condition, the duration of taking the medical, and a textbox for entering the medication requested.

Figure 18D shows screen components 286 that include interrogative constructs relating to a certificate. Those screen components 286 includes soft buttons that enable a patient to input information about the type of certificate, whether or not the patient has already been seen by the emergency department about their condition and if they have seen anyone else about it. Also, information can be entered about a condition for the certificate, and the reasons for obtaining the certificate. Text boxes are provided for entering dates for a time period for which the certificate is to be issued.

Figure 18E shows screen components 288 that include interrogative constructs relation to a having test results done. The screen components 288 includes soft button that enable a patient to input information about the type of test results, whether or not the emergency department ordered the test, or else who. Information can also be input about when the tests were done and who requested that the patient go to the emergency department.

Figure 18F shows screen components 290 that include interrogative constructs relating to a follow-up. The screen components 290 includes soft buttons that enable a patient to enter information about the type of follow-up, whether or not they have been seen by the emergency department before or by anyone else. Also, information can be entered about when they were seen last, and how the condition has been since. The main triage assessment event 58 relates to symptoms of the clinical condition or issue that the patient is experiencing. At 162, the kiosk determines which main class of clinical condition and/or subclass of clinical condition were selected, at 54, and renders associated screen components in the form of soft buttons, for example such as 170 (see Figure 19), which includes interrogative constructs, for example 172. Figure 20 shows another example of screen components in the form of soft buttons 174 that includes interrogative constructs 176 that are associated with a different main class of clinical condition and/or subclass of clinical conditions that were selected, at 54.

Inputs by activating the soft buttons 170 or 174 as the case can be, are received, at 164. The kiosk determines, at 166, if other screen components need to be generated that are associated with another main class of clinical condition and/or subclass of clinical condition that were selected, at 54, and if so, then proceeds to generate those screen components, at 164. Otherwise, the kiosk 12 proceeds to note the received inputs, at 168, for example by storing or flagging, so that the computer system can determine which inputs were triggered and hence the interrogative constructs that relate to those inputs. The kiosk 12 then proceeds to main triage assessment event 60.

The main triage assessment event 60 relates to a medical history and further personal details of the patient. At 180, the kiosk 12 triggers a sequence of screen components, and at 182, the kiosk 12 receives the inputs from the screen components. At 184, the kiosk 12 determines if further screen components in the sequence have to be rendered in the sequence, and if so, returns to 182, else it proceeds to note the received inputs, at 186, for example by storing or flagging, so that the computer system can determine which inputs were triggered and hence the interrogative constructs that relate to those inputs. The kiosk 12 then proceeds to main triage assessment event 62.

Figures 21 to 25 show a sequence of screen components that are rendered during the main triage assessment event 60. Figure 21 shows an array of screen components in the form of soft buttons 190 that include interrogative constructs, for example 192, that relate to any medication that the patient regularly uses. Figure 22 shows an array of screen components in the form of soft buttons 194 that include interrogative constructs, for example 196, that relate to any medical conditions that the patent has experienced in the past. Figure 23 shows screen components in the form of soft buttons 198 and 200 that include interrogative constructs, for example 202, that relate to any allergies that the patient has and for whether or not the patient has any allergies respectively.

Figure 24 shows further screen components on lifestyle history in the form of soft buttons 204, 206 and 208, that include interrogative constructs that relate to whether or not a patient smokes and details about past or present smoking habits. Soft buttons 210 and 212 includes interrogative constructs that relate to the use of alcohol and detail about it. Soft buttons 214 includes interrogative constructs that relate to whether or not a patient uses recreational drugs.

Figure 25 show further screen components on social history in the form of soft buttons 216 that includes interrogative constructs that relate to whether a patient is right handed or left handed, and soft buttons 218 and 220 includes interrogative constructs that relate to whether a patient uses prescription glasses and more detail about it. Soft buttons 222 includes interrogative constructs that relate to a patient's work situation, and soft buttons 224 and 226 includes interrogative constructs that relate to a living situation and relationship status of the patient respectively.

Main triage assessment event 62 relates to generating a triage narrative and receiving an input about a triage assessment category or score. At 230, screen components are generated (see Figure 26) that include a text box 242, a text box 244, soft buttons 248 and 250 that include triage finding constructs for input about of a triage category or score fining and for input of further observations made by triage personnel respectively.

The kiosk 12 determines, at 232, inputs received during the previous main triage assessment events, and determine or generate corresponding declarative constructs. At 234, the kiosk 12 determines if another previously received input exists for which a declarative construct has to be determined, and if so, then return to 232. Otherwise, the kiosk proceeds to generate or compile, at 235, the narrative triage construct which includes a personal detail narrative construct 252 that is populated into text box 244, and a clinical narrative construct 254 that is populated into the text box 242. The clinical narrative construct 254 is generated by stringing together the earlier determined declarative constructs that correspond with various interrogative constructs of the earlier received inputs.

As is illustrated in Figure 26 the declarative constructs are compiled to form meaningful expressions based on the interrogative constructs which can be nothing more than a single word. For example, an input received from a soft button that includes an interrogative construct 'breathless' can be used with inputs received from the soft buttons that includes the interrogative constructs about the during of the symptoms to form a declarative construct in the form of an meaningful expressing 'breathless for 6 hours'. Similarly, an input received by the soft button that includes the interrogative construct 'yes' when asked which medication has been used, together with the interrogative construct 'pharmacy' can be used to generate an declarative construct in the form of a meaningful phrase 'has had pharmacy medication with moderate effect', and the like.

To this end, the declarative constructs can also be generated to include meaningful statements that are suitably worded for what triage personal and medical practitioners would need. For example, see Figure 27 in which the clinical narrative construct in text box 242 includes declarative constructs that includes medical terms for use by the medical practitioner, whereas the interrogative constructs rendered for the patient to use on earlier screens are general terminology.

Moreover, the interrogative components can be rendered in any one of a preconfigured language, in which case, the declarative constructs and ultimately the triages assessment narrative can be generated and rendered in a different language.

At 236, an alert is generated to notify triage personnel that the kiosk 12 is awaiting a triage clinician input. The triage personnel then can physically assess the patient's appearance and also see the clinical narrative construct 254 to determine a triage assessment category or score, which is then input using the soft buttons 248 as well as inputs about other observations as needed with soft buttons 250.

At 240, the information is made available for use by other integrated computer systems. For example, a triage register of an existing emergency patient management system can be populated, as shown in Figure 28, which includes a list of patient names who have been triaged, their details, the triage categories or scores allocated, and abridgements of the clinical conditions or issues, and the like. Also, the information or constructs can be used to populate a medical record as shown in Figure 29.

In another embodiment (not shown) a kiosk 12 can include peripheral instruments that are interfaced with the kiosk 12, such a weight scale on which a patient stands during completion of the triage assessment events, and an infrared thermometer, as well as a pulse oximeter that measures pulse and oxygen levels, blood pressure monitoring device, an electrocardiograph, and the like.

Those physiological measurements can then be presented as part of the triage assessment narrative.

Further, the kiosk can be configured automatically to perform other tasks based on input constructs received such as ordering x-rays, blood tests or medications.

Also, trigger comments can be configured for health professionals such as the general practitioner, when for example a time frame is entered about the duration that the symptoms persisted that is above a time threshold, for example longer than

12 months, a prompt can be generated to consider a referral to specialist outpatients as oppose to the emergency department.

The computer system 10 can also include a statistical analysis module for use by emergency management to analyze the entered data based on the frequency of each soft button being pressed at what time.

In a further embodiment, the kiosk can be configured to detect if a patient is less than sixteen years of age, in which case, screen components are rendered that include interrogative constructs relating to specific paediatric details, such as to include the immunization status of the patient.

Throughout the main triage assessment events, an emergency soft button

260 (see for example Figures 12 and 13) is rendered so that a patient can immediately call for help if the condition deteriorates while interfacing with the kiosk

12. A soft button 262 for help (see for example Figure 25) will alert triage personnel that assistance is required.

Built into the system, there are various notifications can be generated, for example if a letter with a QR code that was received from a general practitioner is scanned by the kiosk's scanner, then the general practitioner can be notified automatically by email, SMS, or the like.

The various screen components can also include a soft button that activates free text entries, such as soft button 264 shown on Figure 20.

Moreover, when triage personnel interface with the kiosk, an ID card of the personnel can be scanned with the kiosk's scanner to identify and record the specific person that dealt with the matter. ADVANTAGES

Advantageously, the present embodiment improves the efficiency at which triage assessment can be performed in the emergency department of a hospital. For example, many patients can use separate kiosks at the same time while less time is required from triage personnel to make the final triage assessment and as such saving time.

The embodiment also eliminates variation in which more than one triage personnel might otherwise deal with a patient and document the triage. Further, the interrogative constructs are so devised that only the necessary questions are asked and only specific answers can be given in the context of what information is being sort, avoiding irrelevant information provided by the patient, which further improves the triage efficiency process.

A similar main triage assessment process is followed each time by using the embodiment, which results in consistency in terminology and narrative construction.

The embodiment is also useful in that on the front end the terminology used is of general nature appealing to a patient, and the narratives are generated using terminology and formats that appeal to the medical practitioner.

The interface or screen components are easy to answer multi-choice and interactive components and questions which require minimum textual input, in some cases, none at all, and effectively requires only a click through process which is fast and efficient.

The embodiment also advantageously enables completion of the triage assessment process up to the point at which a triage assessment narrative is generated by using remote terminal computer systems. That enable a general practitioner, paramedic, or a patient (through a personal app version) to proceed with the triage assessment process prior to even arriving at the emergency department, further improving efficiency of the triage process.

Also, the kiosk is patient driven which also contributes to save time, in particular for triage personnel, enabling more focus on meaningful treatment beyond the triage process.

The kiosk is able to render screen components in different languages, and still render the triage assessment narrative in the language needed for the medical practitioner, effectively translating the interrogative constructs from one language to a triage assessment narrative in another language. The data that is captured with the system is consistent in format, which makes the data rich in information for ease of statistical analysis of who is presenting to the emergency department, when and with what conditions needing what resources. VARIATIONS

It will of course be realised that while the foregoing has been given by way of illustrative example of this invention, all such and other modifications and variations thereto as would be apparent to persons skilled in the art are deemed to fall within the broad scope and ambit of this invention as is herein set forth.

Throughout the description the term 'interrogative' is used in a broad sense and is meant to include 'imperative'.

In the specification, including the claims, where the context permits, the term "comprising" and variants thereof such as "comprise" or "comprises" are to be interpreted as including the stated integer or integers without necessarily excluding any other integers.

It is to be understood that the terminology employed above is for the purpose of description and should not be regarded as limiting. The described embodiments are intended to be illustrative of the invention, without limiting the scope thereof. The invention is capable of being practiced with various modifications and additions as will readily occur to those skilled in the art.

Moreover, every combination of the above described elements, activities, and all possible variations thereof are encompassed by the claimed subject matter unless otherwise clearly indicated herein, clearly and specifically disclaimed, or otherwise clearly contradicted by context.

The use of any and all examples, or exemplary language (e.g., "such as") provided herein, is intended merely to better illuminate one or more embodiments and does not pose a limitation on the scope of any claimed subject matter unless otherwise stated. No language in the specification should be construed as indicating any non-claimed subject matter as essential to the practice of the claimed subject matter.

Accordingly, every portion (e.g., title, field, background, summary, description, abstract, drawing figure, etc.) of this application, other than the claims themselves, is to be regarded as illustrative in nature, and not as restrictive, and the scope of subject matter protected by any patent that issues based on this application is defined only by the claims of that patent.

The use of the terms "a", "an", "said", "the", and/or similar referents in the context of describing various embodiments (especially in the context of the following claims) are to be construed to cover both the singular and the plural, unless otherwise indicated herein or clearly contradicted by context. The terms "comprising," "having," "including," and "containing" are to be construed as open- ended terms (i.e., meaning "including, but not limited to,") unless otherwise noted.

Claims

1 . A method of using a computer system to support a triage assessment process, the method including configuring the computer system such that the computer system is enabled for

triggering a sequence of events that render on a screen input screen components that include interrogative triage constructs;

using the declarative triage constructs, generating a narrative triage construct for rendering on the screen in a format that supports the making of a triage assessment finding.

2. A method as claimed in claim 1 , wherein in each case, the sequence of events includes stepping through a sequence of main triage assessment events, and rendering, during each of the main triage assessment events, input screen components that include interrogative triage constructs that are associated with the main triage assessment events.

3. A method as claimed in claim 1 , wherein the method includes receiving at least some inputs from at least some of the input screen components that are rendered during that main triage assessment event, and

depending on the received at least some inputs

either rendering further input screen components that include interrogative triage constructs that are associated with that main triage assessment events, or

progressing to a next step in the sequence of main triage assessment events.

4. A method as claimed in any one of the preceding claims, wherein the sequence of main triage assessment events includes an initial main triage assessment event that renders input screen components that include interrogative triage constructs that relate to personal details of a patient that needs to be assessed.

5. A method as claimed in any one of the preceding claims, wherein the sequence of main triage assessment events includes intermediate main triage assessment events that render input screen components that include interrogative triage constructs that relate to any one of clinical conditions or issues, symptoms, and medical histories.

6. A method as claimed in any one of the preceding claims, wherein the sequence of main triage assessment events includes a final main triage assessment event that renders input screen components that include the narrative triage construct for rendering on the screen in a format that supports the making of the triage assessment finding by a triage assessor, and input screen components that include triage finding constructs for receiving inputs of a triage finding made based on the narrative triage construct.

7. A method as claimed in any one of the preceding claims, wherein determining declarative triage constructs corresponding to the received at least some inputs includes selecting one or more of the at least some received inputs associated pre- constructed declarative triage constructs.

8. A method as claimed in claim 1 or 2, wherein generating the narrative triage construct includes constructing a personal details narrative construct and a clinical narrative construct.

9. A method as claimed in any one of the preceding claims, wherein the clinical narrative construct includes selecting pre-constructed declarative triage constructs that correspond to the received inputs during the intermediate events of the sequence of main triage assessment events, and arranging those declarative triage constructs in an order that corresponds with a sequence in which the at least some inputs were received during that intermediate events of the sequence of main triage assessment events.

10. A method as claimed in any one of the preceding claims, wherein the method includes using the declarative constructs to populate a triage assessment register, for example by interfacing with a triage assessment register of an existing emergency patient management system.

1 1 . A method as claimed in any one of the preceding claims, wherein the method includes using the declarative constructs to populate a medical record register, for example by interfacing with a medical record register of an existing electronic medical records system.

12. A computer system that is used to support a triage assessment process, the computer system being configured to execute the method as claimed in any one of claims 1 to 1 1 .

13. A computer system installation that is used to support a triage assessment process, the computer system installation including

a plurality of terminal computer systems that are in data communication with a server computer system, the terminal computer systems and server computer system being configured to execute the method as claimed in any one of claims 1 to 12.

14. A computer program product that includes computer readable instructions, which when executed, enables a computer system to perform the method as claimed in any one of claims 1 to 13.