PRACTO TECHNOLOGIES

FUNCTIONAL SPECIFICATION DOCUMENT

EMERGENCY REGISTRATION CHANGES

DOCUMENT VERSION 1.2

25-10-2019
AUTHORS

Name Role Department

Jyothi Rajesh Business Analyst Insta BU

DOCUMENT HISTORY
Date Version Document Revision Description Document Author

10-10-2019 1.0 Emergency registration draf Jyothi Rajesh

12-10-2019 1.1 Emergency registration patients demographical inclusion Jyothi Rajesh

APPROVALS
Approval Approved
Approver Role Approver
Date Version

20-10-2019 1.2 Sathya Project Manager

Table of Contents

1. Introduction.....................................................................................................................................4
1.1 Purpose of the document..............................................................................................................4
1.2 Project Scope................................................................................................................................4
1.3 Related documents........................................................................................................................4
1.4 Terms/Acronyms and Definitions...................................................................................................4
1.5 Risks and Assumptions...................................................................................................................4
2. Functional Specifications.........................................................................................................................5
2.1 Emergency Registration.................................................................................................................5
2.2 Emergency and unidentified patient..............................................................................................7
3. Reporting Requirements........................................................................................................................10
4. Data Migration/ Conversion Requirements............................................................................................10
 1. Introduction

This document discuss about emergency registration enhancements and it’s impact after the inclusion of
emergency registration in other modules.

1.1 Purpose of the document

1. Emergency Registration (ER)

Currently, system does not fully support the registration ER patients. Now, expected the system to have
emergency registration functionality

2. Registration Preferences (for unidentified patient in case of ER registration)

At present, as mentioned above system does not emergency registration. Also, there is no field to
mention the patient as unidentified patient. Now, expected to have an option to specify the patient as
unidentified

1.2 Project Scope

This document discussed about the ER registration and it’s attributes

1.3 Related documents

Check the BRD details as mentioned below

Component Name (with link to the document) Description

BRD ER Business requirement document ER BRD

1.4 Terms/Acronyms and Definitions

<State any terms and its definition that are described in the functional specifications. Include any
acronyms that are mentioned in the document.>

Term/Acronym Definition Description

ER Emergency Room or department

1.5 Risks and Assumptions

No Assumptions
2. Functional Specifications
1. Emergency Registration

2. Emergency and unidentified patient and changes to be made in Registration Preference (inclusion of
new fields incase unidentified patient registration)

2.1 Emergency Registration

2.1.1 Purpose/ Description
1. A new check box to be added in the registration screen, the users select the check box if the patient is
an emergency patient.

2. After the selecting the check, the user will fill the other details however he did before. No changes in
other fields.

2.1.2 Mock-up

2.1.3 Functional Requirements

Spec ID Specification Description Business Rules/ Data Dependency

1 Emergency checkbox User selects the check incase of emergency patient
registration
 2.1.4 Field level specifications

Form Elements:

Data
UI Default
Call-out Field Label Mand? Editable Data Type Value Set Exampl Data Source
Control Value
e
2.1.2 Emergency checkbox No Yes None NA NA NA User entry

Form Business Rules and Dependencies:

Data
Validation / Business Rules Additional
Field Label Error Messages Dependenci
Info/ Notes
es
Emergency The emergency is a checkbox and NA NA NA
it should be editable

2.2 Emergency and unidentified patient

2.2.1 Purpose/ Description
It is an emergency registration and patient is unidentified, the patient is unconscious and user suppose to
do the registration. To achieve this

1. A new checkbox to be added next to emergency checkbox called as “Unidentified”, this checkbox
should enabled after selecting the Emergency checkbox

2. Two text boxes to be added in the registration preferences as Emergency First Name and Emergency
Last Name. In the preferences the admin or IT admin specify the default Emergency First Name and
Emergency Last Name. Ex: John Doe

Upon the patient selection as unidentified the system should fill the first name and last name at the
patient registration screen as per the registration preferences entry (patient unidentified first name and
patient unidentified last name)
2.2.2 Mock-up

Registration Preference

2.2.3

Functional Requirements

Spec ID Specification Description Business Rules/ Data Dependency

2 Unidentified
3 Unidentified First Name
4 Unidentified Last Name
It should display after the selection of emergency
checkbox and it should editable
It is a text box, it should be editable and the data
entered here should be displayed in the registration
screen patient first name upon selection as the
patient is unidentified
It is a text box, it should be editable and the data
entered here should be displayed in the registration
screen patient last name upon selection as the
patient is unidentified
 2.2.4 Field level specifications
<Specify all the field data elements related to the functional requirement in both tables below.>

Form Elements:

Data Value Default

Call-out Field Label UI Control Mand? Editable Data Example Data Source
Type Set Value
2.2.2 Unidentified checkbox No Yes None None NA NA User Entry
2.2.2 Unidentified Text box Yes No Alpha- none NA John No
Patient First numer
Name ic
2.2.2 Unidentified Text box Yes No Alpha- none NA John No
Patient Last numer
Name ic

Form Business Rules and Dependencies:

Data
Validation / Business Rules Additional
Field Label Error Messages Dependenci
Info/ Notes
es
Unidentified It should be displayed or NA NA NA
enabled once selection of
Emergency checkbox in the
registration screen
Unidentified Patient First Name 1. In the registration It should not be empty None None
preferences master, user
enters the Unidentified
Patient First Name.
Ex: John

Unidentified Patient Last Name
2. In registration screen, if
the user choose the patient
as Unidentified Patient then
the patient first name should
be filled automatically as per
registration preference
master
1. In the registration It should not be empty None None
preferences master, user
enters the Unidentified
Patient First Name.
Ex: John

2. In registration screen, if
the user choose the patient
as Unidentified Patient then
the patient last name should
be filled automatically as per
 registration preference
master

Buttons, Links and Icons:

Button,
OnClick Enabled Vs
Link, Icon Other Event Visible Navigate To Validation Dependencies
Event Disabled
Label
Unidentifi It should Upon the It should It should be None It should be It should be
ed Patient be selection by not be displayed displayed displayed upon the
Checkbox displayed the user, the displayed upon the upon the selection of
upon patient first default selection of selection of emergency
selection name and last emergency emergency checkbox
of name should checkbox checkbox
Emergency be filled
Checkbox automatically
based
registration
preferences
master

3. Reporting Requirements

There are 2 attributes added as part of the Visit Details Report Builder to identify the visit registrations
done against Emergency and Unidentified patients.

4. Data Migration/ Conversion Requirements

The introduction these new changes will not bring any changes to previous entries