CST2234-Stakeholders SRS Midterm
docx
keyboard_arrow_up
School
Algonquin College *
*We aren’t endorsed by this school
Course
2234
Subject
Information Systems
Date
Dec 6, 2023
Type
docx
Pages
2
Uploaded by ChefWaterOyster28
Medtronic Seamlessly Integrates Nerve Monitoring System Data with
Backend EHR
Project Stakeholders
List out at least 6 project stakeholders.
+ Medtronic
+ Emids
+ Surgeons and Operating Room Staff
+ Patients
+ Hospital IT Departments:
+ Regulatory Bodies
Overall Description
Assumptions
List at least 3 project assumptions.
-
Compatibility: Assumption that the NIM system can be seamlessly integrated with EHR systems, including
compatibility with existing EHR software.
-
Data Security: Assumption that the integrated system will adhere to data security and privacy standards,
safeguarding patient information.
-
User Adoption: Assumption that surgeons and hospital staff will adopt and effectively use the new
integrated system, leading to improved patient care.
Dependencies
List at least 3 project dependencies.
-
FHIR and HL7 Standards: The project depends on the effective use of FHIR and HL7 standards for data
exchange, requiring adherence to these standards.
-
Cloud-Based Solutions: The successful integration may depend on the stability and performance of cloud-
based solutions for data transfer.
-
Device-Specific Information: The availability and accuracy of device-specific information provided by the
NIM system play a vital role in the integration.
Requirements
Functional Requirements
List at least 4 functional requirements.
The system shall:
SWF1: Data Integration - The system must integrate data from the NIM system into the EHR, ensuring
real-time and accurate updates of patient information.
SWF2: Patient Record Lookup - The integration should allow for efficient patient record lookup to prevent
patient mismatches, enhancing patient safety.
SWF3: Ease of Use - The integrated system should be user-friendly, enabling operating room staff to
upload reports with minimal effort.
SWF4: Futureproofing - The system must support FHIR as one of the most popular standards for health
data exchange, ensuring its relevance in the evolving healthcare landscape.
Non-Functional Requirements
List at least 4 non-functional requirements.
The system shall:
SWNF1: Data Security - The integrated system must meet stringent data security and privacy requirements,
safeguarding patient records from unauthorized access.
SWF2: Performance - The system should operate with minimal latency, ensuring that data updates and
record uploads occur in a timely manner.
SWF3: Scalability - The solution should be scalable to accommodate the needs of different healthcare
facilities, from small clinics to large hospitals.
SWF4: Reliability - The integrated system should operate reliably without frequent disruptions, as
downtime could have serious consequences for patient care.
2
SOFTWARE REQUIREMENTS SPECIFICATION
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help