Use the Incidents tab to list and maintain medical incidents at your organisation.
The Incidents tab consists of:
In the following example, the student's injury on the 16/05/2011 is selected. The corresponding details for this incident can be seen to the right - in this case the Summary sub-tab.
Note: Sick bay staff members usually maintain incidents.
Summary sub-tab
Use the Summary sub-tab of the Incidents tab to:
Medical Maintenance - Incidents tab - Summary sub-tab key fields and buttons
Fields
Field |
Description |
---|---|
Date |
The date the incident occurred. The date defaults to today's date, if you click |
Type |
The type of incident. Maintain the type of incident in the luMedicalIncidentType lookup table. See Maintaining lookup tables in the System maintenance manual. This is useful for reporting on types of incidents, for example how may sporting injuries occur in a given period. |
Venue |
The venue at which the incident occurred. Select from the drop-down list. Maintain the venue of the incident in the luMedicalVenue lookup table. See Maintaining lookup tables in the System maintenance manual. |
Time In |
The time the person arrived at the sick bay. The time defaults to the current time, if you click If the patient is a student, the time they checked into the medical centre will appear next to their name in the Attendance Maintenance window for the class they should have been attending at the time of the incident. This time may also appear on the student's timetable in Current Student Maintenance depending on the ShowInSynergeticTimetableFlag in the luMedicalIncidentType lookup table. See Maintaining lookup tables in the System maintenance manual. |
Time Out |
The time the person left the sick bay. Either:
If the patient is a student, the time they checked out of the medical centre will appear next to their name in the Attendance Maintenance window for the class they should have been attending at the time of the incident. This time may also appear on the student's timetable in Current Student Maintenance depending on the ShowInSynergeticTimetableFlag in the luMedicalIncidentType lookup table. See Maintaining lookup tables in the System maintenance manual. |
Diagnosis |
Initial diagnosis made at your organisation of the:
|
Despatch |
Details of where the person was sent from your organisation for further treatment and any medications used. |
Comment |
Additional details of the incident. |
Follow Up |
Select to follow up on the date specified. Specify follow up comments, if required. The Crystal Report, MEDINCF, can be used to identify medical incidents requiring follow up. |
Buttons
Button |
Description |
---|---|
Click to launch the Discharge Confirmation window to set the time and type of the student's discharge from the medical centre. |
|
Create a report with the details of this incident. Note: Incident reports are linked using the Incident:HotReports configuration setting. See Incidents:HotReports configuration setting in the System maintenance manual. |
Grid area fields
All fields in the grid area are entered on the Summary sub-tab.
Field |
Description |
---|---|
Date |
Date of the incident. |
Type |
Type of incident. |
F/up |
Selected if a follow up is required on the Follow Up Date specified. |
Diagnosis |
Initial diagnosis made at your organisation. |
Despatch |
Details of where the person was sent from your organisation for further treatment and any medications used. |
Follow Up |
Follow up comments. |
Follow Up Date |
Date the follow up is scheduled for. |
Tip: When modifying an existing incident, first select the incident in the Incidents grid area.
Grid area buttons
Button |
Description |
---|---|
Add a new row in the Incidents grid area and then edit the incident details on each of the sub-tabs. |
|
Delete the incident highlighted in the Incidents grid area. |
Last modified: 7/10/2013 12:06:04 PM
© 2013 Synergetic Management Systems. Published 15 October 2013.