The Structure of EpicCare Home Health Flashcards
0
Q
Hyperspace
A
architecture that hosts all Epic’s applications
When patient admitted:
- document demographic/clinical info
- HH visits can be scheduled - Cadence
- other tools POC Review / PPS Review
1
Q
Three components
A
- Hyperspace
- Remote Client
- Server
2
Q
Server
A
All applications
- store data/retrieve data
- info doc in Hyperspace/ Remote Client
3
Q
Remote Client
A
HH laptop application
- users must synchronize
- transfer updated patient, IB, schedule data fr. laptop to server & vice versa
4
Q
Typical Patient Care Cycle
A
- Admission & Registration
- Episode Creation
- Certification Periods & Home Visits
- Discharging the Patient
5
Q
Admission and Registration
A
Every pt receiving HC must first be registered and admitted
Two Types of patients
- pts who are referred by MD w/in organization
- pts referred by an outside MD no access to Epic
6
Q
Episode Creation
A
All HH patients have an episode created
Entire time a patient spends in HH care for a specific problem constitutes one episode
7
Q
Episode
A
- HH episode of clincal care
- Certification period
- Centers for Medicare and Medicaid Services (CMS) episode certification period
8
Q
Certification Periods and Home Visits
A
- episode can contain one or more certification periods
- billing periods
- recertification period has a 60-day duration
9
Q
Discharging the Patient
A
Remote Client end users create a Discharge Assessment
- Close any open HH visits
- Remove pt from Remote Client
- Discharge pt from your agency
10
Q
OASIS
A
Outcome and Assessment Information Set
- your agency must fill out OASIS data every 60 days to recertify
- assessments comprised of M-Codes
- all assessments linked to certification periods
- Start of Care assessment: require creation of new certification periods
11
Q
Assessments (6)
A
- Start of Care (SOC)
- Transfer
- Resumption of Care (ROC)
- Recertification
- Significant Change in Condition (SCIC)
- Discharge
12
Q
Start of Care Assessment
A
- first assessment created for a patient
13
Q
M-Codes (OASIS items)
A
- contain fields to enter data correspond to CMS
1. Patients name
2. Who
3. Date
4. Reason - dx
5. ADLs
14
Q
Patient Care Plan
A
- care plan represents the strategy being used to treat a patient
- patient’s anticipated visits, problems, goals, treatments in the Care Plan task
- one care plan can cover multiple certification periods/created for entire episode