The Structure of EpicCare Home Health Flashcards
Hyperspace
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
Three components
- Hyperspace
- Remote Client
- Server
Server
All applications
- store data/retrieve data
- info doc in Hyperspace/ Remote Client
Remote Client
HH laptop application
- users must synchronize
- transfer updated patient, IB, schedule data fr. laptop to server & vice versa
Typical Patient Care Cycle
- Admission & Registration
- Episode Creation
- Certification Periods & Home Visits
- Discharging the Patient
Admission and Registration
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
Episode Creation
All HH patients have an episode created
Entire time a patient spends in HH care for a specific problem constitutes one episode
Episode
- HH episode of clincal care
- Certification period
- Centers for Medicare and Medicaid Services (CMS) episode certification period
Certification Periods and Home Visits
- episode can contain one or more certification periods
- billing periods
- recertification period has a 60-day duration
Discharging the Patient
Remote Client end users create a Discharge Assessment
- Close any open HH visits
- Remove pt from Remote Client
- Discharge pt from your agency
OASIS
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
Assessments (6)
- Start of Care (SOC)
- Transfer
- Resumption of Care (ROC)
- Recertification
- Significant Change in Condition (SCIC)
- Discharge
Start of Care Assessment
- first assessment created for a patient
M-Codes (OASIS items)
- contain fields to enter data correspond to CMS
1. Patients name
2. Who
3. Date
4. Reason - dx
5. ADLs
Patient Care Plan
- 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
Plan of Care (POC)
- for every certification period, you will have corresponding Plan of Care
- written order of treatment
- signed by the physician
- pulls data from the assessment, care plan, meds and durable medication equipment (DME)
- Epic uses the 485 format
Care Plan
- umbrella over
- patient’s Plan of Care
- any collected assessment information
Introduction to Hyperspace (Activities - modules)
- HH Intake
- Verbal Order Information Summary
- Plan of Care Review
- used by end users in other Epic applications: IB, Chart Review, SnapShot, reporting/scheduling activities
Getting Started with Hyperspace
architecture that hosts Epic’s integrated suite of products
- Register
- Schedule
- Document
- Bill
Your Startup Activities - Foundation System
Cannot exit startup activities:
- Schedule
- Dashboards
- In Basket
Hyperspace Toolbar
- offers a way to get to most commonly used functions for particular role
- each option on toolbar has icon
Epic Button
- tools used less frequently
- to reduce number of buttons on Hyperspace toolbar
Patient Workspace and Activities
- open pt’s scheduled appt
- double click on appt slot on schedule
New 2014: widescreen view (multi-column screen layout)
Default activity for nurse
Rooming activity
- offers a table of contents
Activity Toolbars
- work in different activities while in patient’s workspace
- each offers activity-specific options
Securing
- bookmarking
- only applies to Hyperspace
- does not apply to Remote Client
How do you open and use a SmartList
- icon of 3 post its
What does a wild card look like
- 3 asterisks
Few more steps to complete a workflow (3)
- associating the order with a dx
- documenting your notes
- closing the encounter
