Use the Incident tab to record details of the current medical incident. That is, the reason why the person has been signed in to the sick bay.
| Expand | ||
|---|---|---|
| ||
To open the Incident tab:
|
.png?version=2&modificationDate=1648654035077&cacheVersion=1&api=v2&width=1000)
Medical Maintenance - Incident tab key fields and buttons
Incident Summary area fields and buttons
Fields
| Field | Description |
|---|---|
| Start Date and Time | Date and time of the medical incident. |
| Location | Location where the medical incident |
| was reported. For example, |
| Sick bay. | |
| Type of Incident | Type of medical incident. For example, head injury. Tip: You can type into the drop-down list to filter the list of medical incidents. |
| Presentation | Initial diagnosis |
of the |
patient when they presented at the sick bay. |
Injury details fields
Note: You need to add these fields by clicking .png?version=1&modificationDate=1648223048020&cacheVersion=1&api=v2&height=32){kind=small}
.
...
Buttons
...
Documents area fields, links and buttons
Fields
...
Source of the document. Typical examples include:
- Archive
- Magazine
- Newspaper
- School Photo
- Website.
Note: Document sources are maintained in the luDocumentSourceCode lookup table. See luDocumentSourceCode lookup table in the System maintenance manual.
...
Links
...
Buttons
...
| Field | Description |
|---|---|
| Treated by | Name of the person that treated the community member. |
| Injury description | Description of the injury sustained by the community member. |
| Severity | Severity of the injury sustained by the community member. Note: You can maintain medical condition severity levels including the colour assigned to each severity level using the luMedicalConditionSeverity lookup table. See the luMedicalConditionSeverity lookup table in the Synergetic System maintenance manual. |
| Cause | Cause of the injury. |
| Action taken | Action taken to treat the injury. |
| Treatment referral | Whether the community member has been referred to a specialist for treatment. |
| Follow-up actions | Follow-up actions required to ensure the community member recovers from the injury. |
| Witnesses | Witnesses of the incident that caused the injury. |
Follow up fields
Note: You need to add these fields by clicking .
| Field | Description |
|---|---|
| Follow-up date | Date to follow-up on the medical incident. |
| Details | Details to be covered during the follow-up appointment. |
Buttons
| Field | Description |
|---|---|
| Click this button to add additional fields to the medical incident report. You can add:
Note: The fields in these sections are described above. |
| Sign out the community member. |
.png?version=1&modificationDate=1648223145207&cacheVersion=1&api=v2&height=32){kind=small}
Common fields and buttons
Common fields
Field | Description |
|---|---|
| Default email | Default email address of the community member. Note: The default email address is defined using the Default Email field on the Phone bar of Community Maintenance. See Community Maintenance - Phone bar. |
| Home address | Home address of the community member. Note: The home address is defined using the Home Address bar of Community Maintenance. See Community Maintenance - Home Address bar. |
Common buttons
Button | Description |
|---|---|
| Click to display the Add reminder window.
When the medical details of the selected community member need to be updated, you can use this window to create a reminder action centre message with details of the update. |
| Click to display a list of available medical reports. Note: This currently supports the Medical Incident Note report. |
| Used to navigate between the records of community members signed into medical maintenance. Tip: You can navigate to a specific page by typing the page number into the Go to field and pressing Enter. |
.png?version=1&modificationDate=1648225896033&cacheVersion=1&api=v2&height=32){kind=small}
.png?version=1&modificationDate=1648225898407&cacheVersion=1&api=v2&height=250)
.png?version=1&modificationDate=1648225898453&cacheVersion=1&api=v2&height=42){kind=small}