Epic Data Structure Flashcards

1
Q

What is Chronicles in Epic?

A

Chronicles is Epic’s database management system that manages data interactions in Hyperspace.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

How do users interact with Chronicles?

A

Users interact with Chronicles by asking for data, editing data, or saving new data while using Hyperspace.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What analogy is used to describe Chronicles?

A

Chronicles can be thought of as a giant filing cabinet that stores all data entered by staff and clinicians.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are master files in Chronicles?

A

Master files organize information in Chronicles, with each file storing data about one type of entity.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is an example of a master file?

A

Information about patients is stored in the Patient master file, while information about users is in the User master file.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What does the INI represent in master files?

A

The INI is a three-character abbreviation for each master file, such as EPT for Patient and EMP for User.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is a record in the Chronicles data structure?

A

A record stores information about one specific entity within a master file.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

How many records does each patient have?

A

Each patient has one record in the Patient (EPT) master file.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What does each record contain?

A

Each record has a name and a unique identification number (ID).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is the significance of IDs in records?

A

IDs must be unique within the same master file, even if names are the same.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What does each folder represent in the filing cabinet analogy?

A

Each folder represents one record in the Chronicles data structure.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is a contact in Chronicles?

A

A contact is a date-specific snapshot of the data within a record that allows for changes to be effective on a specific date.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What happens prior to the effective date of a contact?

A

The old values will be used.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What happens on the date of the contact and beyond?

A

The new values will become effective.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Will all data in a record be contact-specific?

A

No, not all data in a record will be contact-specific.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

How does changing a patient’s name in their most recent contact affect other contacts?

A

It will change across all contacts in that patient’s record.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

How are contacts represented in the filing cabinet diagram?

A

Contacts are represented by dated sheets of paper in the file folder.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

What do contacts represent in the User master file?

A

Contacts represent when a user’s job or responsibilities change.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

What is stored in a contact in the Patient master file?

A

Information about a patient that is specific to one hospital stay is stored in a contact, or encounter.

20
Q

What is unique about the Patient master file?

A

It includes many different types of encounters.

21
Q

Do all master files utilize contacts?

A

No, not all master files have contacts.

22
Q

What happens to changes made in records without contacts?

A

Any changes you make in the record take effect immediately.

23
Q

Do all master files have contacts?

A

No, not all master files have contacts. Changes made in the record take effect immediately.

24
Q

What are items and values in a master file?

A

Items are like question prompts on a standardized form, while values are like the answers.

25
Q

Do all records in a master file contain the same items?

A

Yes, every record in a master file contains the same items, but the values will vary between records.

26
Q

What happens if an item is not applicable in a record?

A

Many items will have no values, or blank values, in a record/contact when they are not applicable for the situation.

27
Q

What is the foundation for everything done in Epic?

A

The underlying data structure.

Understanding this structure helps answer questions and investigate the system.

28
Q

What is Chronicles in the context of Epic?

A

Epic’s database management system.

It is essential to understand basic terms related to Chronicles.

29
Q

What will this chapter introduce?

A

The basic terms for Chronicles and the structure of some of Epic’s master files.

It will also explore tools like Record Viewer.

30
Q

What tool can be used to investigate issues in Epic?

A

Record Viewer.

This tool helps in exploring the structure of Epic’s master files.

31
Q

What is Hyperspace in Epic?

A

Hyperspace is Epic’s front-end user interface, typically accessed on the Hyperdrive client. It’s what most users think of as ‘Epic’ and what you used in your Fundamentals class.

32
Q

Who logs in to Hyperspace?

A

End users log in to Hyperspace to complete their workflows and do their jobs. Administrators and builders also log in to configure the system and to test/troubleshoot build.

33
Q

What is Chronicles in Epic?

A

Chronicles is Epic’s database management system, often referred to as ‘the database.’ All the data that users access in Hyperspace actually lives in Chronicles.

34
Q

What happens when a user logs in to Hyperspace?

A

When a user logs in to Hyperspace and opens a patient’s chart, Hyperspace is requesting data from Chronicles.

35
Q

What occurs when a user documents in a patient’s chart?

A

When a user documents in a patient’s chart, they are saving data to Chronicles.

36
Q

What is Text?

A

Text is a text-based, back-end interface with Chronicles data, used solely by administrators for creating, editing, and analyzing records.

37
Q

Where does Text run?

A

Text runs directly on the server that hosts Chronicles.

38
Q

How do you connect to Text?

A

You connect to Text via a terminal emulator (like PuTTY or Reflection; we use PuTTY in training).

39
Q

What are some applications included in Text?

A

Text includes applications such as Clinical Administration, Chronicles, Training Tools, and Security.

40
Q

What is the purpose of Clinical Administration in Text?

A

Clinical Administration is used for various clinical apps.

41
Q

What does Chronicles do in Text?

A

Chronicles is used for importing, duplicating, hiding, searching for, or otherwise managing records.

42
Q

What are Training Tools in Text?

A

Training Tools include things like patient duplication.

43
Q

What is the role of Security in Text?

A

Security provides various user-provisioning and access management tools.

44
Q

Will Text continue to be used?

A

Text isn’t going anywhere; some tools and editors will always exist only in Text.

45
Q

How will training specify the use of Text or Hyperspace?

A

In training, we will always specify whether you should be building something in Text or Hyperspace.