What is Core? The common processes or tasks that are shared multiple times across clinical domains, technical activities, or project tasks. It is those.

System Review CORE Concepts
King Saud University Hospitals System Review CORE Concepts Ilham Hobba December 15, 2012

What is Core? The common processes or tasks that are shared multiple times across clinical domains, technical activities, or project tasks. It is those things that are required in order to get a Cerner Millennium™ application or applications installed. Core includes all the shared tables, standard code sets (as opposed to nonstandard or product-specific), and anything else that is used across the rest of Cerner’s products. Many groupings of shared information are used by HNA Millennium products. Some examples are security, event codes and event sets, person identification, locations, and organizations. Core also includes the alias pools used within these groupings.

Event Codes/Event Sets
What is Core? Organizations Security Locations Alias Pools Code Sets Event Codes/Event Sets Core is often thought of as “Reference Data” Once instance of this data exists in the database, and the various solutions refer back to that once instance.

Core Services Organizations

Organizations in Millennium
Organization: Any business entity that is affiliated with the health system. Organization Types Organizations are classified into different Organization Types Each type drives functionality within the Solutions Examples of Organization Types: Client Facility Employer Insurance Company Hospital Physician Offices Multiple Organization Types can be used to define an organization. Example: Cerner Hospital can be a Facility, Client, Hospital, and Employer Organizations are defined by being classified as different Organization Types. An Organization can be more than one Type, and the different Types drive different functionality within the system. For Example, if an Organization is a Facility, locations can be tied to it.

Organizations Organizations Facility Hospital Employer Ins. Company
Client Employers and insurance companies usually don’t end up being facilities. A facility is a TYPE of organization.

Organization Types Possible “Employment/Billing” Organizations:
Employers Insurance companies Clients (e.g. Industrial accounts) Employer: An organization that may be given as a place of work or health plan sponsor Insurance Company: An organization with one or many health plans associated underneath it. Ask audience what organizations from their health system would be considered Employer? What would be considered Insurance Company?

Organization is a Client if :
Organization Types Client: An organization that is used to represent a specific patient population for patient numbering, billing or report distribution. Organization is a Client if : Charging processes occur (designation needed in order to show is Charge Services tools) The organization is used for client/industrial billing Destination for Clinical Reporting Ask audience what organizations from their health system would be considered Client?

What are Core Organizations?
Possible “Patient Care” Organizations: Hospital Physician Office/Clinic Home Health Hospice Facility Physician Office/Clinic: Areas where health care services are given to patients who do not need to stay overnight. May include services usually provided in a Physician Office or Clinic. Ask audience what organizations from their health system would be considered Patient Care?

Core Organization Types
Facility An organization at which patient care activity takes place. Organization is a facility if: Patient care takes place Patient registration occurs Identifiable patient population (Charting, Security) ProFit billing entity (one tax id) Facilities can contain: One Pharmacy formulary One Order Catalog One Charge Description Master (CDM) One of the main reasons you need facilities is to build locations beneath them. Locations, such as buildings, nurse units, rooms, and beds, need to have a facility associated with them. Otherwise, the system will not know whether Room 105, Bed A is located at Hospital A or Hospital B. Any organization that will be affiliated with a data feed must also be a facility. Facilities are also established for work routing and report routing. And the last reason for facilities is charging capabilities. Usually each facility has separate financial numbers and billing numbers. Ask audience what organizations from their health system would be considered a Facility?

Core Services Security

Security Design Security Risks in Healthcare Security is not…
Unauthorized disclosure of patient information Unauthorized disclosure of sensitive information Substance abuse treatment, abortion, mental health, HIV/AIDS, genetics Unauthorized disclosure of intellectual property Security is not… An add-on to your solutions Built after workflow is designed Software that protects the configuration Recommended to be set up at an user-level Security for Cerner is not software that protects our build or something that lays over the Cerner Millennium components. Security is, in fact, inherent in the architecture of the core and application build and configuration. For example, you could look at Application/Task Security (the act of giving someone permission to access certain applications and their tasks) as a way of enabling someone to do their job. A radiologist needs access to the radiology applications and their tasks. But, that very act of enabling the radiologist to do her job also secures those applications and tasks against the Help Desk Clerk who should not have access. Security is not an add-on piece to Cerner Millennium. It is built into the architecture.

SECURITY Vital for Access Control in Millennium
What Solutions Can You Access? What Tasks Can You Perform? What Data Can You View? What Organizations Do You Have Access To?

Positions Defined Role based access to Cerner Applications
Should be based on the role the user has within scope of Cerner Solutions Not based on job title Position determines authorization within Cerner NOT the same as a job class or employee title Positions are not the same thing as the HR titles granted to each of your employees. Positions are designed based on the access of what that particular group of end-users needs access to within the Cerner System. For example, if a Lab Supervisor needs the same access within Cerner as Lab Management roles, they can all be grouped in the same POSITON. End-users will not see their position, it’s built into the system to determine what that end-user will have access to and be restricted from.

Position Collection Positions will be collected on Core Systems Positions DCW Start positions are outlined on the deliverable This deliverable is assigned to the Core team to complete two weeks prior to Design Review Solution teams will be required to assist the client in designing their positions based on Start content This is to be completed on weekly calls between System Review and Design Review Address position integration points between solutions as they arise The completion of this deliverable will ensure the successful design of position based security at Design Review

Encounter/Organization Security
Broad Level of Security Limits what Patient visits (encounters) each User can view, based on what organization the visit occurs at. Users are “tied” to Organizations Users may view information from Patient visit, if the visit occurs at an Organization they are associated with Users can be associated to one or many Organizations Will specific patient populations, such as behavioral health, need to be secured? If yes, each applicable location will be built as a separate facility and therefore require its own organization. Talk about sharing of information between organizations when there is a merging of the organizations. Security is still in place and documents are not shared or tightly controlled between the merged sites.

Encounter Organization Security
Information Available across all encounters/visits: Allergies Problems PowerNote Clincal Notes Procedures Form Browser (results) Histories (past medical, family, social) Immunizations Medication List (prescriptions and administrations) Encounter/visit-specific information: PowerOrders Diagnoses Provider Relationships Restrict individual results- HIV results, but not encounter org..

Confidentiality Code Security
If And User associated to Facility AND User assigned a Confid. Level Patient encounter occurs at Facility AND Encounter assigned a Confid. Level And 1 2 User’s Confid. Level Meets or exceeds Encounter Confid. Level Then > 2 1 User has access to view patient encounter Be familiar with fly in’s

Encounter/Organization Security
Dr. B Dr. A Dr. C Cerner Clinic Cerner Hospital C.H. Psych Unit Encounter 3 Encounter 1 Encounter 2 After First Arrow, ask client which doctor will have access to see Encounter 1. Repeat for Encounter 2 and Encounter 3.

Confidentiality Levels
Prerequisite - Encounter Organization Security Compare user and patient encounter codes to determine access Levels are client defined

Examples of Levels: Encounter Users Psych 7 Security 5 Sensitive 3
Routine Clinical 1 7 Psych users 5 Partial Restricted/Regular Users 3 Clinical Staff 1 PMLocator Users (patient directory) User with a Confid. Level of 5 can view any Encounters with a level 5, 3, or 1 Maximum of 4 levels recommended due to maintenance considerations

Within ERM: The Confid level can be assigned to each encounter via the Registration Conversation. The User’s level is assigned when their account is created- only have to do this once. Each encounter needs an assigned level, however is it possible to have a level always default in the conversation.

Without Cerner ERM Confidentiality Codes can be sent from ADT (Registration System) Sent in HL7 Message- PV2:22

After Encounter Org/Confid Level:

Positions Defined Role based access to Cerner Applications
Should be based on the role the user has within scope of Cerner Solutions Not based on job title Position determines authorization within Cerner NOT the same as a job class or employee title Positions are not the same thing as the HR titles granted to each of your employees. Positions are designed based on the access of what that particular group of end-users needs access to within the Cerner System. For example, if a Lab Supervisor needs the same access within Cerner as Lab Management roles, they can all be grouped in the same POSITON. End-users will not see their position, it’s built into the system to determine what that end-user will have access to and be restricted from.

Core Services Locations

Locations Generic term used to denote physical place in health care organization. Area where Patient Care takes place. Locations exist in the Location Hierarchy. Any Organization that is a Facility can have locations tied to it. Locations are nursing units, rooms, and beds. They also can be ambulatory care areas, such as Emergency Rooms, Clinics, and so on.

Location Hierarchy Facility (type of organization) Room Buildings
Nurse Unit Bed Cerner Hospital West Pavilion 2 South 202 A The diagram on this slide is an example of a location hierarchy. The hierarchy on the left shows the Cerner terminology. The hierarchy on the right shows the fictitious Cerner Hospital, with its West Pavilion building, Nurse Unit 2 south, and room 202, bed A. For each successive level of the hierarchy, the predecessor must be established. For example, you cannot build a bed without a room or build a room without a nursing station.

Buildings Defined Buildings A physical structure on hospital property
“Houses” registration locations Drives no product functionality (security, billing, etc.) Facility (type of organization) Room Buildings Nurse Unit Bed A building is a physical place within a facility. Buildings differentiate between locations with the same name. For example, the facility Cerner Medical System has two buildings: Cerner Hospital and Cerner Health Clinic. You must always have a building within the facility (which, again, is always an organization). The building is a prerequisite for establishing nursing units, rooms, and beds.

Nurse/Ambulatory Unit, Rooms, and Beds
Core Units Defined Nursing Unit Ambulatory Unit Facility (type of organization) Room Buildings Nurse Unit Bed Rooms and Beds Represents physical Rooms and Beds Hierarchy format allows for multiple Rooms and Beds with the same name The Location Hierarchy allows for multiple Rooms and Beds with the same names. For example, A Building May have two nursing units, 2 North, and 2 South. 2 North can have Room 101, Bed A. 2 South can also have Room 101 and Bed A. Because they are different in the Location Hierarchy, the system can accept multiple Room 101’s and Bed A’s.

LOCATION HIERARCHY INPATIENT
Facility Building Nurse Unit Room and Beds

LOCATION HIEARCHY DAY REHAB & OUTPATIENT
Facility Building Ambulatory Loc

Service Resources Core Locations Facilities Institutions Buildings
Two Sides Core Locations Facilities Buildings Nurse units Rooms Beds Service Resources Institutions Departments Sections Subsections Exam Rooms Organizations, patient locations, and alias pools are used across products, and this is another component of the database for which Core/OCF is responsible. Core/OCF's goal is to maintain consistency among the applications and how they identify patient locations. In Core/OCF we build organizations, facilities, buildings, nursing units or ambulatory locations, rooms, and beds. The product-specific work locations--called service resources--can involve institutions, departments, sections, subsections, and testing sites. Core Locations represents where the patient is physically located. Service Resources represent where the work takes place. Where work takes place, rather than where patients are registered. Laboratory, Resp Ther

What solutions use Core Locations?
Registration Scheduling PowerChart CareNet INet Charge Services PharmNet ProFile ProFit FirstNet Clinical Reporting PathNet AP Locations appear in most all Cerner solutions. It’s crucial that everyone understand what locations are, and that they have a good understanding of what Facilities, Units, Rooms, and Beds are built in your system. We suggest that everyone meet as a group to sign off on the final Location Hierarchy design.

Encounter/Organization Security Controls access to patient information by organization. Confidentiality Level Security Additional function available with Encounter Org Security that can be set per facility As previously discussed, Encounter Org Security and Confid Levels are designed and built by Core. All patient searches are affected by Encounter Org Security and Confid Levels, if implemented. Are there any additional questions regarding how these relate to Locations, particularly facilities?

Registration Patients registered to Facilities If an inter-facility transfer needs to occur, the alias pools for those two orgs must be set up exactly the same Registration can filter out patients by facility PMLocator (Cerner’s patient directory) Auto-discharge can be set up differently per facility (and by patient type) - but not per building, nurse unit, room, or bed Certain code sets can be filtered by facility Patient Type Medical Service Accommodation Code Discharge Disposition Discharge Location Remember from our Organization Discussion, a facility is an organization at which patient care takes place, or if patient registration occurs.

Registration In this screen capture, you are looking at an example of a “Registration Conversation.” This conversation is used to add new patients, or encounters to patients. Patients are registered to a facility, which will determine which Buildings and Units appear. The choice of Building and Unit determines the Rooms and Beds that a patient can be placed in, or registered to.

Person Search Window Search by location or facility Customize encounter results window with location hierarchy fields. This is a screen shot of the Person Search Window, which is seen throughout all Cerner Solutions. It is possible, should you choose to do so, to search based by a particular Facility or Unit. The results of what you searched for will display in the screens on the right- the person and encounter results screens. You can see that the Facility and Room appear with the Patient’s Visit to Baseline East, in Room 201. The choice of search and return fields is something you’ll be able to customize. Locations can appear if that’s something your end-users expect to be able to search on. We will capture this in our Person Search Screen Deliverable, later on- owned by Core.

Scheduling Patients will get scheduled to a “location”, this is typically an ambulatory location. The location and the facility can be passed into registration if the conversation is launched from the appointment. Relevant to outpatient process only

PowerChart Encounter Organization level security. An encounter that is hidden by the use of this type of security will not be accessible on the PowerChart Visit List tab or anywhere else in PowerChart/PowerChart Office. Encounters will also be hidden in the Patient Search for that organization Locations (nurse units/ambulatory) can be used to specifically lock down patient lists on individual computers Set up with a default location list Location patient lists can also be used to help organize work

PowerChart Organize Patients by Location This is a screen shot of a PowerChart Patient List. You can view lists of patients based on what location they’re at, or where they’re registered to.

CareNet Orders Locations used for routing and printing Orders requisitions Consent forms Reports Printed charts Patient location and ordering location can be used to flex order entry formats. Orderables can be virtualized to specific facilities Ordering is then controlled depending on whether patient is registered at that facility.

Inet can flex views based on the patient’s location Patient on the left is located in the adult ICU Patient on the right is located in the NICU

Charge Services Any organization that will be used for charge purposes will need to be built as an organization type of “Client” Charges can be flexed based on a multitude of fields Patient location Performing location Facility As mentioned earlier, any organization where charging processes occur must be an Org type of “Client.”

RadNet Service areas will be tied to existing locations from the hierarchy for routing. Organizations and facilities need to be built prior to building accession number site prefixes

PharmNet Formulary products can be flexed based on availability of products per each facility. If a formulary product is stocked on a floor and available via Omnicell/Pyxis, the product can also be associated with a nurse unit/ambulatory location to indicate this.

ProFile HIM Chart Tracking has the ability to track a paper chart based on both user-defined locations and locations defined in the hierarchy.

ProFit Revenue can be reported by: Patient location Performing location

FirstNet Any area where an emergency patient needs to be tracked (beds, hallways, waiting room, etc) will need to built as a location within the emergency department Lab label printing can be routed to different printers in the ED based on location, if necessary Tracking List tabs can be organized based on location Only displaying patients in Fast Track area

Clinical Reporting Chart distributions and expedites can be routed by patient location, which includes routing by facility, nurse unit, ambulatory location, or outpatient location. Keep in mind that if you are routing a distribution or expedite by patient location and you would like the ability to print charts to 2 locations within the ED, for instance, you would need to create 2 patient locations for the ED so that the chart can be printed to the respective device in that location. The location where the patient is registered to can also be printed in the chart header/footer. Again, this includes the facility, nurse unit, ambulatory location, and/or outpatient location.

Anatomic Pathology (AP) Uses the functions of Orders for all orders placed outside the pathology lab AP uses the functions of Charge Services and Profit to charge based on patient location AP uses Registration and Patient search functions Service resources are used to route internal orders to work lists and work queues Processing orders are added to work queues based upon routing Worklists and Labels are printed based on routing Reports are sent to review queues based on routing Calendars and Service Areas added to benches allow internal AP orders to be sent to the proper lab if there are multiple pathology labs working from the same database.

Outreach OSM Requisition Order Entry (ROE) Only Organizations built as clients and facilities are viewable.

Outreach Things that can driven by client for Outreach: Encounter type Financial class MRN assignment Insurance, health plan, subscriber (required vs not required) Registrations defaults (Client vs patient bill) Flexible registration Insurance companies Charting Billing

ePathLink Organizations built as clients and facilities can be used in ePathLink. Things that can driven by client for ePathLink: Encounter type Financial class MRN assignment Insurance, health plan, subscriber (required vs not required) Registrations defaults (Client vs patient bill) Flexible registration Insurance companies Charting Billing Options for utilization of ePathLink (new orders, results view only etc..)

Registration Scheduling PowerChart CareNet INet Charge Services PharmNet ProFile ProFit FirstNet Clinical Reporting PathNet AP Locations appear in most all Cerner solutions. It’s crucial that everyone understand what locations are, and that they have a good understanding of what Facilities, Units, Rooms, and Beds are built in your system. We suggest that everyone meet as a group to sign off on the final Location Hierarchy design.

Core Services Alias Pools

Sets of alphanumeric identifiers
Alias Pools? Sets of alphanumeric identifiers These numbers are used as boundaries for checking for duplicate persons, encounters, orders, personnel, and organizations. How are alias pools related to organizations? Assigned at organization level We use alias pools to store and compare the aliases that can’t be predefined in the system.

Alias Pools Pete Smith Cerner Hospital Cerner Clinic Patient
Pete visits Cerner Clinic. Pete checks into Cerner Hospital. Patient Pete Smith Pete visits Cerner Clinic for a second time. Cerner Clinic Clinic assigns Pete a MRN and a FIN Hospital assigns Pete a MRN and a FIN Cerner Hospital CH MRN Pool CC MRN Pool CH MRN: 223 Matches SSN and CMRN CC MRN: 223 Hospital adds his SSN and CMRN CH FIN: CH3334 CC FIN: B890 SSN: CH FIN Pool CC FIN Pool CC FIN: B2343 CMRN: 34543CM CH3334 B890 SSN: CMRN: 34543CM Matches MRN B2343 SSN Pool Adds FIN CMRN Pool 34543CM

Types of Alias Pools “Buckets” of numbers
Examples of data elements that require alias Personnel Organization Dr. # UPIN Provider Numbers Encounter FIN number Visit number Order Placer order number Person SSN MRN Organization Insurance company Employer There are actually five different types of alias pools. They are Person, Organization, Personnel, Order, and Encounter. These alias pools are used to identify a person or organization within the database, dependent on which type of information is being sent into the database. This data comes into Cerner, and we can’t predefine what the alias will be. We need to set up a pool (or think file cabinet) to see if the data already exists and we can match the person (encounter, order, prsnl,or org) or if we need to add it to the pool (file cabinet) and keep it for future transactions.

Alias Pools Association
Think of aliases in terms of the organization types rather than at the organization level. Does every Organization need alias pools? No, just certain types of Organizations need pools. Define what pools will be needed for the different types of Organizations Occasionally, there will be an identifier that is unique to one organization, but not apply to all others of the same type. Example: Cerner Hospital Assignes a MRN. Cerner Clinic Assigns a MRN. If the patient goes to Cerner Hospital, will they recognize the patient’s Cerner Clinic MRN? If so- the pools are shared. If not- they each assign unique MRN’s, and each need their own pool. Alias pools are buckets of numbers. These numbers are used as boundaries for checking for duplicate persons. When the system receives a person alias, the system asks, “Within this set of identifying numbers--this alias pool--have we seen this person before? Do we need to establish another person row on the person table, or can we add the information to a row we already have for this person?”

Alias Pools Explained Fin Number - If patients are being registered to the organization they will always have a FIN number pool. It will be system-assigned only if a client implements Cerner ERM. If it is system assigned you can identify a start number. The FIN number is an encounter alias. MRN - If patients are being registered to the organization they will always have a MRN pool. This works the same way as FIN as far as the start number and system assign. MRN is a person level and an encounter level alias pool. Some applications will look to the encounter specific MRN where other situations you will want to utilize person level or all MRNs. Health Plan - This is required if importing health plans. It is associated to the facility. This pool is used to store Health Plan aliases. This slide doesn’t need to be covered in-depth during the presentation. This slide is useful for auditing/assigning alias pools to organizations during the design phase. Whoever will be working with Cerner to design alias pools will find this information useful.

Alias Pools Explained cont…
Employer Code - This does not need to be associated to each Employer because this is one of the values that we know ahead of time what will be sent. The Employer Code alias pool should be tied to the main facilities. Encounter Organization Alias - This will need to be associated to all facilities. This is required to correctly stamp the encounter table. Insurance Code - This is the same as the Employer code. You need to have the pool built, but only need to tie to the main facilities. SSN - This pool will be shared by all organizations that patients are registered too. Masking is typically used so the SSN displays with the proper format. DOCDEA, DOCUPIN, External ID, and Organization Doctor - These are all personnel aliases that need to be tied to all facilities. This slide doesn’t need to be covered in-depth during the presentation. This slide is useful for auditing/assigning alias pools to organizations during the design phase. Whoever will be working with Cerner to design alias pools will find this information useful.

Alias pools may be shared across organizations Social security number
Shared Alias Pools Alias pools may be shared across organizations Social security number Community medical record number Community doctor number Remember that not all alias pools will be unique to an organization. Community medical record number may be shared. Social security number will definitely be shared across organizations. Why is this? Alias pools are designed to be associated to the organization that assigns them. The government or state will assign certain numbers, those are the same no matter which organization the patient goes to for care. For that reason, a social security number, for example, can be set up for only one SSN pool, shared across ALL organizations. That identifier, or alias, means the same thing to each organization, so they can all share one pool for matching.

Code Sets including Code Values and Code Value Aliases
Core Services Code Sets including Code Values and Code Value Aliases

What are code sets and what do they do?
Code Sets - Defined What are code sets and what do they do? Code Sets are groupings of like sets of reference data For example: Gender is a code set. Male, Female, Unknown are all possible reference data elements within the Gender code set. Code Sets also allow you to normalize information to be used across all solutions For example: By using code sets, the end user will see Female in both PowerChart and FirstNet, not Female in PowerChart and Woman in FirstNet Code sets are tables of data elements. Cerner predefines some code sets to which information cannot be added. Within the context of the predefined code sets, only those items built by Cerner have meaning in applications. The majority of our code sets, however, are created by clients.

Two types of code sets Standard Solution-specific Code Sets
Gender, state, marital status, Units of Measure Solution-specific Laboratory Code Sets (Body Site, Organisms) Code sets may be either application- or Core/OCF-specific. Core/OCF concentrates on code sets common to all applications, known as standard code sets.

Code Sets are also used to map information via an Interface
Code Sets - Interfaces Code Sets are also used to map information via an Interface Every data element coming into or out of Cerner from a foreign system must have an alias Think of these standard values coming in and out as descriptors Demographic descriptors – race, religion, gender Order Information descriptors – collection priority, mode of transportation, and report priority The first thing we have to do to begin the process of integrating disparate systems is to get everyone to agree on standard values. To return to the fast-food restaurant example, everyone has to understand what a cheeseburger is. In order to do this, we need standard code sets. Standard code sets are descriptors. For the person, think of demographic elements, such as race, religion, and gender. For an order or result, think of the elements used to describe the order, such as collection priority, mode of transportation, and report priority. Standard code sets are made up of code values and code value aliases. First we define a list of standard display values. For religion, these might be Baptist, Catholic, and Muslim. Next, we need to know what all the other systems use to represent these display values. When sending information about religion, one system might use “B” for Baptist, “C” for Catholic, and “M” for Muslim. These values would be the code value aliases, which provide the information necessary to interpret what is coming from other systems.

Code Sets - Interfaces Patient = John Smith Inbound Values
Gender Code Set Foreign ADT: “M” M = Male 1 = Male Foreign ADT: “F” gender display = Male F = Female 2 = Female Foreign Lab: “1” Foreign Lab: “2” The Core/OCF database can receive information from different feeder systems. Each feeder system may have a different way of indicating the same piece of information. For example, two feeds may use different methods to identify a person’s gender. In this picture, the registration system sends “M” for male and “F” for female. The lab system, however, sends “1” for male and “2” for female. In order to create a standardized set of information, the Core/OCF database needs to store the same code values for gender regardless of who sent the information. In this example, the Core/OCF database stores the code value “1” to indicate someone is male and the code value “2” to indicate female. To store the appropriate value for an individual, the database must be able to interpret the information coming from the feeder systems. Aliases allow for the interpretation of information from feeder systems. For example, after the aliases “M” and “1” are defined, the system knows to store the code value for male when it receives these aliases from the feeds. After “F” and “2” are defined, the system knows to store the code value for female when it receives these aliases. In this way, aliases normalize information coming into the Core/OCF database to the standardized display values. When requests are made for information from the database about a person’s gender, the system displays “male” or “female” based on the code value stored in the database as the gender for the person. The display values are defined in the standard code set for gender, where the labels “male” and “female.”

Allow for site customization of data elements
Benefits of Code Sets Allow for site customization of data elements Cerner provides Start data elements for you to use Provide for standardization or normalization of data display across all solutions Common display values Sets of data come into the Core/OCF database referencing individual codes. The sets of data are called contributor sources and the individual codes are called aliases. Therefore, each alias comes from a specific contributor source. Because of Standard Code Sets, the system can understand and translate each alias so the data can be stored and displayed in common terms.

Event Codes and Event Sets
Core Services Event Codes and Event Sets

What is a Flowsheet? This slide simply shows you the flowsheet view from PowerChart. This slide is first so you can capture the audiences attention. When you talk about the flowsheet, describe what it is an how it is used and what the benefits are of it. What is a flowsheet? allows clinicians to trend historical clinical events (graphing function for WBC Results) allows clinicians to view these clinical events in logical way (UA Dipstick Results are all grouped together) allows for ability to groups like clinical events together together (different flowsheets – Lab, Radiology, Vital Signs)

What is a Clinical Event?
Often called a result Result of a question Result of a diagnostic test Result of an assessment Result of a consult A clinical event is a result. It can be: the result of a question – such as “do you smoke?” or the result of a diagnostic test such as a chest x-ray It can be the result of an assessment – such as the patient’s heart rage It can also be the result of a consult – such as a consult note All clinical events are stored in Event Codes.

What is an Event Code? Event Code: It is the reference data element against which each clinical event is stored Event Code Result Reference Data Element Activity Data Element So, what is an event code? An event code is the reference data element against which each result in the clinical event table is stored. Without an event code, the result cannot be stored to the clinical_event table and an error is received, usually a “failure to ensure result” error. The system must be able to determine which event code should be used to store a result. Another way to think of event codes is this --- a result is just a number or a textual string or an image --- the event code defines the meaning of the result. The result is “13”… the event code tells us it is a “hemoglobin”. The integrity and clear definition of event codes is very important.

Only ONE event code should ideally exist per concept.
More about Event Codes Only ONE event code should ideally exist per concept. It is not a good idea to purposely build more than one event code that conceptually means the same thing. The GOAL and RECOMMENDATION is to strive for ONE event code for each result-able concept. Only ONE event code should ideally exist per concept. It is not a good idea to purposely build more than one event code that conceptually means the same thing. The GOAL and RECOMMENDATION is to strive for ONE event code for each result-able concept. The Cerner Millennium database can technically handle multiple event codes for the same concept in most situations. In some cases, however, multiple event codes for the same concept can lead to issues This will be discussed further throughout Clinical Event series

Event Code Integrity Once an event code is paired with a production result, the two must be an inseparable pair forever. Therefore, event codes that have a result against them on production patients on the clinical event table should: NOT be changed (meaning should not be changed) BE viewable Event Code Result Reference Data Element Activity Data Element Let’s discuss event code integrity for a moment. It is important to know and remember that once an event code is paired with a production result, the two MUST be an inseparable pair forever. Once an event code written against a real production patient’s result on the clinical_table, then it is imperative that this event code NOT be changed to the point that it’s meaning is changed. Furthermore, this result needs to be viewable.

Flowsheet – Event Codes
Event Code is the placeholder for result Brining this slide back to demostrate where the event code is represented The discrete result is NOT the event code. The event code is just the storage place for the result. For example, 8 is the result, not the event code. You do not actually see the event code when you look at the flowsheet

Viewing Event codes and results?
Event codes are how results are stored in the system. For most solutions, however, we do NOT view event codes. Thus, we introduce the Event Set. Event Codes need to be paired with an Event Set for viewing. Event Set Event Code So how do we view event codes and results? We now understand that event codes are how results are stored in the system. For most solutions, however, we do NOT view event codes. Thus, we introduce the Event Set. Event Codes need to be paired with an Event Set for viewing.

No activity data is stored against an event set.
What is an Event Set? Event Set: Event Sets are used to group/organize event codes for viewing and printing (clinical reporting). The organization of event sets is hierarchical, thus called the event set hierarchy. No activity data is stored against an event set. Event Sets are used to group/organize event codes for viewing and printing. The organization of event sets is hierarchical, thus called the event set hierarchy. Event sets themselves are stored in the code_value table (code set 93) as well as the v500_event_set_code table. The hierarchical structure of the event sets is stored in the v500_event_set_canon table. No activity data is stored against an event set.

Event Sets are What You Can See
Flowsheet – Event Sets Event Sets are What You Can See All rows here, BOTH dark and light blue bars, are event sets. So, event sets are what you can see. In this screen shot, the dark and light bars, whether they are green or blue, are event sets.

More about Event Sets Event Set Hierarchy: The event sets are organized in a hierarchical structure called the event set hierarchy (ESH). Grouper Event Sets: Like event sets are grouped together into grouper event sets. Primitive Event Set: At the lowest level of the hierarchy, there must be a connection to an event code in order for results viewing to occur. This lowest level event set is called the primitive event set. Therefore, an event set within the ESH can be EITHER a grouper event set OR a primitive event set. It cannot be BOTH. ESH As stated previously, the event sets are organized in a hierarchical structure called the event set hierarchy (ESH). Event sets are logically arranged within the ESH in a parent-child fashion. Like event sets are grouped together into grouper event sets. At the lowest level of the hierarchy, there must be a connection to an event code in order for results viewing to occur. This lowest level event set is called the primitive event set. Therefore, an event set within the ESH can be EITHER a grouper event set OR a primitive event set. It cannot be BOTH.

Diagram of the Required Event Sets
All OCF Event Sets All Result Sections All Specialty Sections All Service Sections All Document Sections Other Results Other Documents This diagram depicts the required core event sets as well as the required hierarchical structure for these required event sets. There are two sides to the event set hierarchy: All Result and All Specialty. These are the required building blocks of the event set hiearchy

ESH Structure Event Codes Grouper Event Sets Primitive Level
Parent All OCF Events Child Grouper Event Sets All Result Sections Parent Child All Service Sections Parent Child Parent Laboratory Child Parent Hematology Urinalysis Child CBC Parent UA Dipstick Primitive Level WBC RBC Hgb Bilirubin Urine Dipstick POC Blood Urine Dipstick POC Glucose Urine Dipstick POC Child Event Codes WBC RBC Hgb Bilirubin Urine Dipstick POC Blood Urine Dipstick POC Glucose Urine Dipstick POC This slide depicts many of the concepts we have discussed related to event sets: The ESH is a sequence of parent/child relationships until the lowest level of the hierarchy is reached. At this level, there must be a connection to an event code for results view to occur for that event. The event set hierarchy allows for results to be organized into logical grouper event sets. The lowest level of the hierarchy defines the primitive event sets.

Flowsheet – Grouper and Primitive Event Sets
Vital Signs would be considered a Grouper Event Set while Temperature Tympanic, Respiratory Rate etc. are Primitive Event Sets. Vital Signs is the Parent of these primitive event sets The Event Code of Respiratory Rate is tied to the Event Set Respiratory Rate There are no Event Codes tied to Grouper Event Sets So, event sets are what you can see. In this screen shot, the dark and light bars, whether they are green or blue, are event sets.

“All Results” Organization Analogy
Event Codes = Paper (Results of WBC, RBC, Hgb are written on different sheets of paper) Grouper Event Sets = Sections & Drawers WBC, RBC & Hgb are filed into CBC. CBC goes to “Hematology” Divider in the “Laboratory” Drawer. Primitive Event Sets = Files All WBC, RBC & Hgb papers are filed into separate WBC, RBC, & Hbg files All papers, files, dividers, and drawers are logically organized and sequenced in appropriate SIDE of the “All Results” cabinet.

“All Results” Organization Analogy
All OCF Events Grouper Event Sets All Result Sections FILE Cabinet All Service Sections Side of the FILE Cabinet Laboratory DRAWER Hematology Urinalysis SECTIONS CBC UA Dipstick SECTION Primitive Level WBC RBC Hgb Bilirubin Urine Dipstick POC Blood Urine Dipstick POC Glucose Urine Dipstick POC FILES Event Codes PAPER WBC RBC Hgb Bilirubin Urine Dipstick POC Blood Urine Dipstick POC Glucose Urine Dipstick POC This slide depicts many of the concepts we have discussed related to event sets: Let’s compare this slide to our file cabinet analogy.

Questions

What is Core? The common processes or tasks that are shared multiple times across clinical domains, technical activities, or project tasks. It is those.

Similar presentations

Presentation on theme: "What is Core? The common processes or tasks that are shared multiple times across clinical domains, technical activities, or project tasks. It is those."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

What is Core? The common processes or tasks that are shared multiple times across clinical domains, technical activities, or project tasks. It is those.

Similar presentations

Presentation on theme: "What is Core? The common processes or tasks that are shared multiple times across clinical domains, technical activities, or project tasks. It is those."— Presentation transcript:

Similar presentations

About project

Feedback