You will receive a copy of a Statement of Requirements produced as part of a tendering process (request for proposals) a few years ago by the HSE. Your task for this assignment is to study this document and So, your 'requirements elicitation' will be don
polapraveen
Specificationassignment-3.rtf
Contents
Background……………………………………................... 3
Glossary ………………………………...............................4
Data Model and Entity Relationship Model ………............5
Data Dictionary ……………………………….....................6-12
Quality Requirements …………………………………........13-17
2
Background-
In the current technology driven healthcare world, implementation of high quality healthcare management software has become a subject of great concern. In order to develop a high-quality software for the health care industry, it is paramount that all the necessary data and quality requirements are well specified. On this regard, this paper focuses on coming up with a well-designed requirements specification document via an account of an Epilepsy lighthouse project that is based on the epilepsy electronic patient record (EPR) system at Beaumont Hospital.
Epilepsy Lighthouse project is promoted by eHealth Ireland with the objective of increasing comprehension and appreciation of the potential Electronic Health Records Systems. The project focuses on an Epilepsy EPR system at Beaumont Hospital. It also has the goal of supporting clinical research and facilitate efficient monitoring and planning of health services. The requirements specification process will entail analysis of the request for proposals as well as a predefined set of reference numbers such as the Health Information Numbers.
3
Glossary of terms
Term
Definition
AAN
American Academy of Neurology.
Ambulatory
Entails medical care delivered on the basis of outpatient basis.
care
Epilepsy
Refers to a neurological disorder that is identified by sudden recurring incidents of sensory disturbance,
unconsciousness and abnormal brain electrical activity.
Chart note
A document prepared by a healthcare provider to explain details of a particular patient’s encounter.
Healthcare
The process of maintaining and improving the physical and mental health of an individual through provision
of medical services.
Hospital
An institution where medical treatment and care for sick or ill people is provided
Medicine
The practice of diagnosing, treating or preventing a disease
Patient
An individual receiving or recorded to have medical treatment
Data model – The proposed EPR system data model is shown below
4
5
Data dictionary
Patient
Attribute name
Data type
Field length
Constrain
Description
Unique Identifier
Number
10
Primary key
Unique Patient Identifier ID, Autogenerated
HIN
Number
100
Not null
Identifier number
Medical card number
Number
50
Not null
Patient card number
Gender
Variable character
100
Not null
Sex of the patient
Date of birth
Date
100
Not null
Original birth date of the patient
Address
Variable character
100
Not null
Full physical address of the patient
Partial address
Variable character
100
Not null
Patient partial address
6
Telephone Encounter reason
Attribute name
Data type
Field length
Constrain
Description
ID
Number
10
Primary key
Unique Telephone encounter ID, Autogenerated
Seizure related
Variable character
100
Not null
Patient seizure related issues
Treatment related
Variable character
100
Not null
Patient treatment related issues
Cognitive issues
Variable character
100
Not null
Cognitive issues for the patient
Education issues
Variable character
100
Not null
Patient education issues
Seizure provoking issues
Variable character
100
Not null
Patient seizure provoking issues
Other
Variable character
100
Not null
Any other patient issue
System testing
Attribute name
Data type
Field length
Constrain
Description
Test ID
Number
10
Primary key
Unique Test ID, Autogenerated
Test name
Variable character
100
Not null
Name of the specific test
Details
Variable character
100
Not null
Summarized test details
7
Training
Attribute name
Data type
Field length
Constrain
Description
Training ID
Number
10
Primary key
Unique Training ID, Autogenerated
Name
Variable character
100
Not null
Specific training name
Details
Variable character
100
Not null
Summarized details of the training
Neurological examination
Attribute name
Data type
Field length
Field length
Default values
ID
Number
10
Primary key
Unique examination ID, Autogenerated
Cranial nerves
Variable character
100
Not null
Summary of cranial nerves
Pupils
Variable character
100
Not null
Summary of pupils status
Gait
Variable character
100
Not null
Gait summary
Mental status
Variable character
100
Not null
Summary of patient mental status
Plantars
Variable character
100
Not null
Summary of patient plantars
8
Physiological examination
Attribute name
Data type
Field length
Constrain
Description
ID
Number
10
Primary key
Unique examination ID, Autogenerated
Vital signs
Variable character
100
Not null
Summary of patient vital signs
Epilepsy surgery details
Variable character
100
Not null
Summary of epilepsy surgery details
Screen for injuries
Variable character
100
Not null
Summary of injuries screen
Healthcare professional
Attribute name
Data type
Field length
Constrain
Description
ID
Number
10
Primary key
Unique Professional ID, Autogenerated
Name
Variable character
100
Not null
Professional Full name
Address
Variable character
100
Not null
Contact address of the healthcare professional
Phone
Number
100
Not null
Phone number of the healthcare professional
Workstation
Variable character
100
Not null
Healthcare professional’s workstation
9
EPR user
Attribute name
Data type
Field length
Constrain
Description
UserID
Number
10
Primary key
Unique EPR user ID, Autogenerated
User type
Variable character
100
Not null
Type of system user
Password
Variable character
100
Not null
User defined password
Organization
Variable character
100
Not null
Specific organization a user is login in for
System manager
Attribute name
Data type
Field length
Constrain
Description
Manager ID
Number
10
Primary key
Specific ID of the system manager
Username
Variable character
100
Not null
Manager’s username
Password
Variable character
100
Not null
Strong password for the system manager
Contact address
Variable character
100
Not null
Address of the manager
Phone
Number
100
Not null
Managers office phone number
10
Epilepsy history
Attribute name
Data type
Field length
Constrain
Default values
Episode ID
Number
10
Primary key
Unique Episode ID, Autogenerated
Episode name
Variable character
100
Not null
Name of the episode
Episode date
Date
100
Not null
Exact date when an episode occurred
Duration
Variable character
100
Not null
Time length of the episode
Comment
Variable character
100
Not null
Any other comment about the episode
Organization
Attribute name
Data type
Field length
Constrain
Description
Organization ID
Number
10
Primary key
Unique Organization ID, Autogenerated
name
Variable character
100
Not null
Full name of the organization
Contact address
Variable character
100
Not null
Full contact address for the organization
11
Medical patient identifier
Attribute name
Data type
Field length
Constrain
Description
Identifier number
Number
10
Primary key
Unique patient Identifier number, Autogenerated
Name
Variable character
100
Not null
Identifier name
Details
Variable character
100
Not null
Details of the specific medical patient identifier
12
Quality requirements
Requirement #:1 Requirement Type: 9 Event/Use Case #: n/a
Description: The product shall allow EPR users to search patients’ data based on items listed on each database entity
Rationale: Expand patient search to capture all necessary details about patients
Source: Healthcare professional
Fit Criterion: A list of search options to include Unique Patient Identifier, HIN, Medical card number, Gender, Date of Birth, Address and Partial Address
Customer Satisfaction: 5
Customer Dissatisfaction: 5
Dependencies: R #1 (Patient appointment search)
Conflicts: none
Supporting Materials: Patient epilepsy history
History: Created November 2016
13
Requirement #:2 Requirement Type: 9 Event/Use Case #: n/a
Description: The product shall allow system managers to perform audit trails for all system activities
Rationale: To allow managers to have a summarized audit trail of which record was viewed, who viewed a record and date and time it was viewed.
Source: System manager
Fit Criterion: Audit trail detail will include details of every recorded including exact time, date and specific user attached to the activity
Customer Satisfaction: 5
Customer Dissatisfaction: 5
Dependencies: n/a
Conflicts: none
Supporting Materials: Audit log
History: Created November 2016
14
Requirement #:3 Requirement Type: 9 Event/Use Case #: n/a
Description: The product shall ensure that healthcare professional get automated updates on patients’ health status
Rationale: To allow healthcare professionals to implement enhanced automated epilepsy EPR system monitoring and health checks
Source: Epilepsy Patient data
Fit Criterion: Summarized details of the patient’s health status.
Customer Satisfaction: 5
Customer Dissatisfaction: 5
Dependencies: n/a
Conflicts: none
Supporting Materials: none
History: Created November 2016
15
Requirement #:4 Requirement Type: 9 Event/Use Case #: n/a
Description: The system shall limit access to different types of data.
Rationale: To allow system manager to authorize specific EPR users to access a predefine set of patient records
Source: System manager
Fit Criterion: A specific predefined set of patient data to be made available depending one’s data access privileges.
Customer Satisfaction: 5
Customer Dissatisfaction: 5
Dependencies: n/a
Conflicts: none
Supporting Materials: none
History: Created November 2016
16
Requirement #:5 Requirement Type: 9 Event/Use Case #: n/a
Description: The product must facilitate specific user access details from logging in using different organizations. Allow organizational based login data.
Rationale: Using a drop down menu at logon screen, the system shall allow EPR users to access data that is specific to the organization they want to work on.
Source: EPR user
Fit Criterion: A drop down list of all organizations to be provided during user login.
Customer Satisfaction: 5
Customer Dissatisfaction: 5
Dependencies: R#4 Health professional access privileges
Conflicts: none
Supporting Materials: none
History: Created November 2016
17
18
