8. Select a save location. Click the name of the folder in which you want to save your document on
the left side of the window. For example, to save your document on the desktop, you would
scroll up and click Desktop in the left-hand sidebar.
9. Enter a name and the “html” file extension. Click the “File name” text box, then type in
index.html.
10. Click Save. Doing so turns your current Notepad document into an HTML document. At this
point, you can proceed with setting up your webpage’s structure. If Notepad inadvertently
closes or you have to come back to your document later, you can right-click the HTML file and
then click Edit in the resulting drop-down menu.
11. Add your webpage’s language tag. The first tag you’ll need to add to Notepad tells the rest of
the document to use HTML.
12. Add the “head” tags. These tags mark the beginning and end of the page title, which you’ll
create in the next step. For now, just type
after the “” tag, press ↵ Enter twice to
leave a space, and type in .
13. Add page title to your website. The title, which is placed between “
” tags, goes in
the space between the “head” tags. This title dictates the website’s name as it appears on the
browser tab.
14. Add the “body” tags. All of your webpage’s code will go between these tags, which should go
below the “” tag.
15. Close the HTML language tag. The last tag to go in your document will be a closing HTML tag to
signify the end of the page. Type below the “
” tag to close the HTML tag.
16. Add your website’s main heading. Type
in between the “body” tags, then type
whatever you want your webpage’s main heading to be in between the “
” tags.
17. Add paragraph text to the page. Type in the paragraph tags, which are “”, and then
enter whatever you want to use as your paragraph in between the tags.
18. Force a paragraph break. If you want to add extra spaces between paragraphs or heading, type
after the line’s closing tag.
19. Add sections and formatting tags as needed.
Step 3: Download Filezilla and upload html file named index.html and picture file. Make sure the file
name of the picture matches what is in the html.
https://td.wku.edu/TDClient/KB/ArticleDet?ID=3175
Step 4: E-mail/Upload via Blackboard the html file and txt version of file along with link to site
Evaluation Criteria
Evaluation for grade
1. Correct Use of html tags in html file
2. Working link to site at people.wku.edu/firstname.lastname
3. All sections populated as listed above
4. All required connections made for LinkedIn site
https://td.wku.edu/TDClient/KB/ArticleDet?ID=3175
Savingyour .txt and .html file.
Once you have completed your website using a text editor like Notepad, save the file as a .txt file in a
folder on your
computer.
Before closing the .txt file, go to the File menu and Select ‘Save As…’. In the Save as type drop down,
select the ‘All Files’ option.
Add .html to the end of the index file name and save that version of the file in a folder on your
computer.
Also save your picture file in a folder on your computer with the filename referenced in your html file.
Once you have downloaded Filezilla, login using the criteria found here. Find the index.html file in the
folder on your computer using the ‘Local Site’ window on the left. Select that index.html file and drag it
to the ‘Remote site’ window on the right. Follow the same process to drag and drop your picture file.
https://td.wku.edu/TDClient/KB/ArticleDet?ID=3175
Beloware screenshots to help with the HCA 447 Website Project.
1. Write the html in notepad and save as index.txt.
2. Save the txt file when finished and save a second copy of the file as index.html.
3. Open the index.html file using a web browser like Internet Explorer to ensure it meets the
requirements of the assignment.
4. Upload the index.html and image using Filezilla.
HCA447 – Healthcare Informatics
Spring 2020 (1 credit hour course)
Project Documentation Project
Document the Major Features and Functional Requirements of an IT system that you need for one of the
healthcare settings below along with Functional Requirements.
Healthcare Settings: Ambulatory, Health Information Exchange, Hospital, Insurance/Billing, Lab,
Long Term Care, Pharmacy, Radiology, Rehab, Telemedicine
The Vision & Scope with Requirements (VSR) should contain the following:
1. Project Scope
2. Executive Summary of the Project
3. Business Opportunity or Problem Statement
4. Business Risks and Benefits
5. Assumptions and Dependencies
6. Vision Statement
7. At least 5 Major
Features
8. Project Success Measures
9. Stakeholders and Users
10. At least 5 Functional Requirements for each of the 5 Major Features
11. Testing Requirements
Evaluation Criteria
Evaluation for grade
1. Clear and concise Project Scope
2. Appropriate Major Features for Project Scope
3. Appropriate Functional Requirements that answer the what, who and why to Cover Major
Features
4. Appropriate Testing Requirements
1
| P a g e
VISION AND SCOPE WITH REQUIREMENTS
UK HEALTHCARE –EPIC SYSTEMS – JOHN
SMITH
Clarity/Project Number: 1
Version Number: 1.0
Version Date: 12/1/18
2 | P a g e
REVISION HISTORY
Date Version Description Author
12/1/18 1 Official Proposal for new EHR systems John Smith
3 | P a g e
PROJECT OVERVIEW
UK HEALTHCARE CURRENTLY USES 5 DIFFERENT EHR PROGRAMS THROUGHOUT ALL
DEPARTMENTS. THE GOAL OF THIS PROJECT IS TO INTRODUCE ONE EHR SYSTEM THAT WILL BE
USED UNIVERSALLY AT UK HEALTHCARE. THIS NEW SYSTEM WILL BE USED BY ALL
DEPARTMENTS AND WILL COVER THE NEEDS OF ALL DEPARTMENTS.
THE PURPOSE OF THIS TYPE OF UNIVERSAL SYSTEM IS TO INCREASE CONTINUITY OF CARE FOR
ALL PATIENTS WITHIN THE CARE OF UK HEALTHCARE AND TO INCREASE PATIENT OUTCOMES
AND SATISFACTION BY GIVING PROVIDERS FULL ACCESS TO ALL MEDICAL RECORDS AT THE
TIME OF SERVICE.
4 | P a g e
1. PROJECT DESCRIPTION
This project was requested by executive leadership at UK Healthcare.
The purpose of this project is so identify and implement a new Electronic Health Record system that can
be used universally within the enterprise.
The EHR system that would best suit the needs of UK Healtrhcare would be EPIC Systems. This system
will eliminate the need for multiple other programs for charting. Paper charts will also be eliminated.
All memebrs of the committee and executive leadership must agree unanimously to move forward with
the purchase of this system.
This new system will reduce the amount of medical errors and increase patient outcomes by putting all
patient information into one uniform system.
This project will not change how outside records are reviewed or scanned into the system.
While this project will come with a very high cost, the better outcomes and patient satisfaction will pay
for itself as it helps to increase reimbursements from insurance providers. This system will also eliminate
the need to update multiple large software programs which can be time consuming and costly as well.
Our target date for completion of upload, training, and implementation is Fall of 2019.
5 | P a g e
1.1 SCOPE (MAJOR FEATURES)
1) Epic Systems was built to be an all inclusive charting system that can effectively be shared by an
entire healthcare community.
2) Predictive analytics and embedded decision support tools support clinical practice to yield better
outcomes.
3) Allow case managers to achieve the best possible outcomes with tools to proactively identify high
risk patients, close care gaps, coordinate care delivery and ensure upcoming services are covered.
4) Network-based provider recommendations at the point of service so your providers and staff can
make financially responsible decisions about members’ care.
5) Patients have personal and family health information at their fingertips with MyChart. They can
message their doctors, attend e-visits, complete questionnaires, schedule appointments, and be more
involved in managing their health.
1.2 REQUIREMENTS:
FR # Detail of Requirement Done When
1.1 As a user I need the system to provide consistent tools
and templates
The system provides consistent
tools and templates
1.2 As a user I need the system enable collaborative
communication
between departments
The system enables
collaborative communication
between departments
1.3 As a user I need the system to reduce the need for
multiple system upgrades
The system reduces the need for
multiple upgrades
1.4 As a user I need all patient orders located in one system The system contains all patient
orders
1.5 As a user I need the system to reduce duplicate testing The system reduces duplicate
testing
2.1 As a user I need the system to provide tools for
simplifying provider workflow built into system
They system provides tools for
simplifying provider workflow
2.2 As a user I need the system to reduce errors The system reduces errors
2.3 As a user I need the system to provide built in warnings
for drug interactions
The system provides built in
warnings for drug interactions
2.4 As a user I need the system to provide built in warnings
for fall risks
The system provides built in
warnings for fall risks
2.5 As a user I need the system to provide built in predictive
analytics to aid
providers in decision making
The system provides built in
predictive analytics to aid
providers in decision making
3.1 As a user I need the system to make insurance
information and eligibility information
readily available
The system makes insurance
and eligibility information
readily available
3.2 As a user I need the system to provide referral
coordination
The system provides referral
coordination
3.3 As a user I need the system to accept outside orders for
testing
The system accepts outside
orders for testing
6 | P a g e
3.4 As a user I need the system to provide outreach to rural
communities and better quality patient record keeping
The system provides outreach
to rural hospitals
3.5 As a user I need the system to provide transfer of
care
simplified by precise printing options
The system provides transfer of
care
4.1 As a user I need the system to provide utilization
management tools
The system provides utilization
management tools
4.2 As a user I need the system to cross check insurance to
make sure services are covered
The system checks insurance
for covered services
4.3 As a user I need the system to provide warning pop ups
for costly procdures/drugs
The system provides warnings
for costly procedures/drugs
4.4 As a user I need the system to provide pharmacy options
for cheaper generics
The system provides pharmacy
options for cheaper generics
4.5 As a user I need the system, to provide options for
different clinical routes that may save the patient money
The system provides options for
different clinical routes based
on patient cost
5.1 As a user I need the system to provide patient secure
access to their own chart
The system provides the patient
secure access to their chart
5.2 As a user I need the system to help in reduction of
manual medical record requests
The system helps reduce
manual medical record requests
5.3 As a user I need the system to provide better patient
understanding of services offered.
The system provides better
patient understanding of
services offered
5.4 As a user I need the system to provide a more thorough
patient friendly explanation of test results
The system provides a patient
friendly explanation of test
results
5.5 As a user I need the system to provide a secure way to
directly message providers with questions and concerns
The system provides a secure
way to directly message
providers
1.3 IT SOLUTION: NEW UNIVERSAL EHR SYSTEM
1.4 TEST CASES AND OUTCOMES:
• Testing requirements will involve a team of providers, nurses, and administrative staff that will
use a mock version of the software for 2 weeks.
• Software will be inspected by this team and evaluated using a utilization checklist and a lengthy
survey at the end of the trial period.
• All information will be presented to executive leadership for discussion.
1.5 OPERATIONAL READINESS:FALL OF 2019
1.6 DEPLOYMENT NOTES:
7 | P a g e
1.7 ASSUMPTIONS:
1.8 EXTERNAL DEPENDENCIES:
1.9 PROJECT PLAN:
TASKS DUE DATE RESPONSIBLE NOTES
Kickoff Meeting 12/1/18 John Smith
VSR/Blueprint Complete 12/1/18 John Smith
IT Development Complete
Test Plan/Strategy Complete
Operational Readiness Document
Complete
SIT Testing Complete
UAT Testing Complete
Technical Turn Complete
PPV Complete
Obtain Business Owner Signoff
Close Project in Clarity/SharePoint
1.10 APPROVALS:
Date Name Role Method
8 | P a g e
2. APPENDIX
HCA 447
Project Documentation Project Overview
Health Care Information Systems: A Practical Approach for Health Care Management
Karen A. Wager I Frances Wickham Lee I John P. Glaser
Vision & Scope with Requirements
HCA 447 Project Overview
• Imagine you are a healthcare administrator of a facility of your choice with a
need for a new computer system.
• Document the Major Features and Functional Requirements that describe
from a business perspective what functionality you need in an IT system for
your healthcare setting.
• Project Scope, Executive Summary of the Project, Business Opportunity or
Problem Statement, Business Risks and Benefits, Assumptions and
Dependencies, Vision Statement, Success Measures, Stakeholders, Testing.
• At least 5 Major Features.
• At least 5 Functional Requirements for each of the 5 Major Feature.
• Well written functional requirements that contains 5 parts (Who Does What
Why? Done When?)
Health Care Information Systems: A Practical Approach for Health Care Management, 4th edition K. Wager I F. Lee I J. Glaser 10
Requirements
• A well written requirement contains 5 parts
• Who?
• Does?
• What?
• Why?
• Done When?
Health Care Information Systems: A Practical Approach for Health Care Management, 4th edition K. Wager I F. Lee I J. Glaser 12
http://www.iiba.org/babok-guide.aspx
http://www.iiba.org/babok-guide.aspx
Requirements
• To Elicit Business Needs:
• What do you have? (current state)
• What do you want? (future state)
• What do you need? (gap analysis)
• To Elicit Requirements:
• What do you want the solution to do?
• How well do you want it to do it?
• Under what circumstances must it do it?
Health Care Information Systems: A Practical Approach for Health Care Management, 4th edition K. Wager I F. Lee I J. Glaser 12
http://www.iiba.org/babok-guide.aspx
http://www.iiba.org/babok-guide.aspx
Requirements
• Major Features
• Either he added or removed functionality between the current state and the
future state
• Functional Requirements:
• Who is the actor
• Does one action only
• What is the thing
• Why does the actor do the thing
• Done when the requirement is met (success/acceptance criteria)
Health Care Information Systems: A Practical Approach for Health Care Management, 4th edition K. Wager I F. Lee I J. Glaser 12
http://www.iiba.org/babok-guide.aspx
http://www.iiba.org/babok-guide.aspx
Turn in your highest-quality paper Get a qualified writer to help you with