Centricity EMR LinkLogic - GE Healthcare Centricity Customer and ...

GE Healthcare 

Confidential and Proprietary Information 

Centricity ® 

Centricity ® Services 

Electronic Medical 

Record 9.2 

EMR 9.2 

LinkLogic 

Manual 

©2009 General Electric Company – All rights reserved. 

General Electric Company reserves the right to make changes in specifications and features shown herein, or discontinue the product 

described at any time without notice or obligation. This does not constitute a representation or warranty or documentation regarding the 

product or service featured. Contact your GE Representative for the most current information. 

GE, GE Monogram and Centricity are trademarks of General Electric Company. 

General Electric Company, by and through its GE Healthcare division 

1/ 

GE / 

1

Confidentiality and Proprietary Rights and Limitations and Conditions of Use 

This document is the confidential property of GE Healthcare, a division of General 

Electric Company (“GE Healthcare”) and is furnished to you, a current GE Healthcare 

customer, pursuant to an agreement between you and GE Healthcare. If you are 

not (i) a current GE Healthcare customer, and (ii) subject to a non disclosure 

obligations pursuant to an agreement with GE Healthcare, you are not authorized to 

access this document. No part of this document may be reproduced in any form, by 

photostat, microfilm, xerography, or any other means, or incorporated into any 

information retrieval system, electronic or mechanical, without the written 

permission of GE Healthcare. Contact your GE Healthcare representative with any 

inquiries regarding copying and/or using the materials contained in this document 

outside of the limited scope described herein. 

GE Healthcare reminds you that there may be legal, ethical, and moral obligations 

for medical care providers to protect sensitive patient information when dealing 

with vendors such as GE Healthcare. You should obtain explicit written consent from 

both the patient and GE Healthcare before you disclose sensitive patient information 

to GE Healthcare. 

Trademarks 

GE, the GE Monogram, and Centricity are trademarks of General Electric Company. 

All other product names and logos are trademarks or registered trademarks of their 

respective companies 

Copyright Notice 

Copyright 2009 General Electric Company. All rights reserved. 

Disclaimers 

Any information related to clinical functionality is intended for clinical professionals. 

Clinical professionals are expected to know the medical procedures, practices and 

terminology required to monitor patients. Operation of the product should neither 

circumvent nor take precedence over required patient care, nor should it impede the 

human intervention of attending nurses, physicians or other medical personnel in a 

manner that would have a negative impact on patient health. 

General Electric Company reserves the right to make changes in specifications and 

features shown herein, or discontinue the products described at any time without 

notice or obligation. This does not constitute a representation or warranty regarding 

the product or service featured. All illustrations or examples are provided for 

informational or reference purposes and/or as fictional examples only. Your product 

features and configuration may be different than those shown. 

GE Healthcare 

540 West Northwest Highway 

Barrington, IL 60010 U.S.A. 

www.gehealthcare.com 


2

What is the Purpose of LinkLogic? 

LinkLogic enables the efficient and intelligent 

sharing of data between the EMR application 

and a variety of external systems, such as 

practice management, transcription, 

laboratory, hospital information, and clinical 

data repositories. 

LinkLogic uses interfaces to share data. 

©2008 General Electric Company – All rights reserved. 

General Electric Company reserves the right to make changes in specifications and features 

shown herein, or discontinue the product described at any time without notice or 

obligation. This does not constitute a representation or warranty or documentation 

regarding the product or service featured. All illustrations are provided as fictional 

examples only. Your product features and configuration may be different than those shown. 

Information contained herein is proprietary to GE. No part of this publication may be 

reproduced for any purpose without written permission of GE. 


3

How is LinkLogic Managed? 

LinkLogic is managed by the LinkLogic Manager. 

The LinkLogic Manager is responsible for: 

• day-to-day monitoring of LinkLogic 

• resolving any mismatches or errors that occur 

This training is intended for your site’s LinkLogic 

Manager(s), who will learn how to manage LinkLogic. 


4

Enable LinkLogic on a Workstation 

If the LinkLogic button is not present on your workstation: 

1. Exit & Completely Close Centricity EMR 

2. Click the Windows start button 

3. Select Programs > Centricity Practice Solutions EMR 9.2> EMR Setup. 

4. On the next menu, select the “modify” option. 

5. Be sure that the checkbox next to LinkLogic has been checked 

6. Follow the prompts to complete the update. 

7. After this is done, the LinkLogic button will be available on the 

workstation for users with privileges to access LinkLogic. 

8. If you use shortcuts on your desktop to launch the EMR, be sure to 

discard any old shortcuts & create a new shortcut on your desktop. 

Note: The instructions above assume you are running EMR on a fat client. 


5

Jobs Tab 

“State” Column 

LinkLogic queues and processes jobs to import or export data. 

The Data Transfer Station handles jobs automatically. Jobs can also be imported or 

exported manually from the jobs tab. 

Some jobs can appear in the jobs tab when errors are opened up in the errors tab, 

and then canceled out prior to resolving. These will need to be processed manually 

to place them back in the errors tab in order to resolve the corresponding errors. 

“Manual” will appear in the state column when this is necessary. 

You should organize the jobs tab to “All Stations” & save as your preference to 

ensure that you can see and process all jobs that appear in “Manual” state when 

this occurs. 


6

Process Jobs in “Manual” State 

“State” Column 

To process jobs in “manual” state: 

1. Highlight job(s). 

2. Click the Process button to send job(s) back to the errors tab. 

3. Also, click OK to any screens that pop up during this process. 


7

DTS Monitor Tab 

The DTS Monitor tab will show you whether or not the Data Transfer Station (DTS) is 

“active”. You should see a line item that states the DTS Status is “Active”. 

If there is not a line item in the DTS tab that states that the Data Transfer Station (DTS) 

is “Active”, or if the DTS Status is “Error”, the DTS needs to be restarted. 

VERY IMPORTANT FOR CENTRICITY PM / EMR CUSTOMERS: 

ANY TIME Oracle is shut down & restarted, the DTS needs to be restarted. 

MIK & Rosetta Stone also need to be restarted to re-establish the connection between 

PM & EMR. 

Order for restarting: 

1. Rosetta Stone 

2. MIK (Note: If set to automatic as shown on page 40, MIK will restart on its own after 

restarting Rosetta Stone.) 

3. DTS 

Note: If all of these reside on the same server, stop in this order: DTS, Rosetta Stone, 

Oracle, MIK, SQL; then restart in reverse order. 

See pages 40 and 49 of this manual for instructions on restarting MIK & Rosetta Stone. 


8

Activity Log Tab 

Message Type Seen in 

Severity Column 

The Activity Log lists notes, warnings, and error messages for every job manually 

imported or exported, and for every job the DTS processes. 

If you import and export many jobs, the log can get extremely large. If the activity log 

gets too many messages in it, the DTS can stop processing until the activity log is 

cleaned out. 

Under most circumstances, it is important that the activity log be organized so that 

messages are viewed for All Stations. This should be saved as your preference, which 

will ensure that you are viewing ALL messages when clearing the log. 


9

Activity Log Message Types 

Message Types Seen in 

Severity Column 

The message type is indicated in the “severity” column. The 3 different message 

types are: 

•Errors 

• Warnings 

•Notes 

Error messages indicate a possible problem in importing or exporting data. 

Warning messages inform you about LinkLogic actions, indicate missing data in 

optional fields, or data that is not used by the EMR application. 

Note messages primarily convey information. You typically do not need to take any 

action. 

Go to “LinkLogic Activity Log Message Codes” in HELP (F1) to understand the notes, 

warnings, and errors you see in the Activity Log. 


10

Filter to Specific Message Codes 

Filtering to specific message codes is one way to organize the current view, making 

it easier to clear multiple items at one time. 

In the message code range area, enter the minimum & maximum code range, then 

click the OK button. Only messages in the specified range will be seen until the view 

is reorganized. 

To view every instance of a specific message code, enter the same number in the 

minimum code range field and the maximum code range field. 

Messages in the activity log can also be organized to specific dates and/or interface 

type. 


11

Removing Activity Log Messages 

To clear messages in the current view: 

1. Click the SELECT button, which will highlight every* message in the 

current view. 

2. Once all messages are highlighted, click the REMOVE button. 

3. After all messages in the current view are removed, click the ORGANIZE 

button again, then click OK to view all remaining messages in the activity 

log. 

*The maximum number of messages the select button will highlight is 14,000, so 

you may have to follow this process multiple times to remove all instances. 

NOTE: Activity log messages should not be cleared out prior to working the 

associated errors in the errors tab, as these messages can sometimes be 

helpful when resolving the errors. 


12

Automatically Manage Activity Log 

Go to Setup > Settings>LinkLogic>Defaults. 

To automatically remove error* entries from the Activity Log: 

1. Check “Automatically remove error entries from the Activity Log”. 

2. Enter the number of days in the “Remove entries after” field. 

To automatically remove warning and note* entries: 

1. Check “Automatically remove warnings and note entries from the Activity Log”. 

2. Enter the number of days in the “Remove entries after” field. 

NOTE: Activity log messages should not be cleared out prior to working the 

associated errors in the errors tab, as these messages can sometimes be 

helpful when resolving the errors. Be sure you set the “number of days” fields 

far enough out so that the activity log messages are not removed sooner than 

you will be working the errors. 

*Message types appear in the severity column of the Activity Log. 


13

Exclude Messages From Activity Log 

Enter Message Codes Here Separated by Commas 

Every time a job is queued, LinkLogic adds message code 7 to the Activity 

Log. LinkLogic adds message code 1 every time a job completes. If you 

don’t want these messages to accumulate in the Activity Log, you can 

modify the cfw.ini file to filter or exclude these messages from the log. 

To exclude specific messages from the Activity Log: 

1. Navigate to C:\Program Files\Centricity EMR 9.2. 

2. Locate & open the cfw.ini file in Notepad. 

3. Find the L3IgnoreMessages entry. 

4. Type the message codes you don’t want to see, separated by commas. 

For example: 

L3IgnoreMessages=1,7 

5. Shut down & restart Centricity EMR on the workstation or the Data Transfer 

Station (as applicable). 

**This must be done all on workstations with access to Linklogic, including 

the Data Transfer Station.** 


14

Errors Tab 

Activity Log Messages 

Associated to Highlighted 

Error Above 

When you import and export data, errors can occasionally occur. Errors can occur for 

many reasons. The following list shows some of the reasons for errors: 

• LinkLogic can’t process the import file, possibly due to a patient mismatch or the 

wrong data format. 

• LinkLogic can’t find the responsible provider. 

• LinkLogic can’t find a relationship for the data, or the header record in the data file 

isn’t correct. 

• LinkLogic can’t process the job, due to a missing configuration file or a bad export 

segment. 

• LinkLogic can’t import the data because the patient’s chart is being updated by 

another user. 

• LinkLogic can’t find the appointment book or the appointment type. 

The Errors tab in LinkLogic contains the Pending Errors to be resolved as well as associated 

Activity Log messages for each error. The associated activity log messages can sometimes 

be used to help determine what you need to do to resolve the errors. 


15

File Extensions / Error Types 

.HR = Lab Results, PatientLink, Docutrak Observations 

.HD = Demographic Messages 

.HT = Docutrak and Noteslink Documents 

.SL = Scheduling Messages 


16

Viewing HL7 Files 

HL7 (Health Level 7) is a standard for electronic data exchange in healthcare 

environments. LinkLogic’s use of this format is defined in the Interface Specifications 

for each interface type. These specifications can be found in the Managing Interfaces 

manual for Centricity Practice Solutions 9.2 on the EMR Support web site: 

http://support.medicalogic.com/ 

Many of the error files you will work with will be HL7 files. To avoid horizontal scrolling 

through the messages, set viewing options to “Wrap to Window”. 

If Using Word Pad to view the files: 

1. Click on the “View” menu. 

2. Click Options. 

3. Click Wrap to Window, then OK. 

If Using Note Pad to view the files: 

1. Click on the “Format” menu. 

2. Click “Word Wrap”. 


17

Typical Segments in HL7 Messages 

MSH = message segment header 

/-/ comment section describing the error /-/ 

EVN = event segment – contains message date / time information 

PID = patient ID segment – contains demographic information 

PV1 = patient visit segment – contains provider and location of care info 

NK1 = next of kin segment – may also contain referring provider information 

GT1 = guarantor segment 

IN1 = insurance segment 

ORC, OBR = lab orders 

OBX = observation / result 

NTE = notes & comments 

SCH = schedule information 

RGS = resource group 

AIS, AIG, AIL, AIP = appointment information 

HL7 Specifications can be downloaded for more information if desired. Download the 

Managing Interfaces manual for Centricity Practice Solutions 9.2 from: 

http://support.medicalogic.com/ 

You will need your site’s user ID & password to download this manual. 


18

Reading HL7 Files 

Field Numbers 

1 2 3 

Segment 

Name 

4 5 6 7 8 etc. 

PID|||MR-101-003|MR-101-003|Ellis^Virgil||19431208|M 

||B|2545 SW 78th^^PortlandÔR^97229ÛSA||503-292- 

3590|503-225-2147|English|D|||815-83-5639| 

In the example PID segment above, individual fields are separated by vertical bars or 

“pipes”. 

When counting fields, empty fields are also counted. 

Segment names and field numbers are referenced together for identification purposes. 

Example: PID-1, PID-2, PID-3, etc. 

Error messages frequently refer to specific segments and fields, where data is missing 

or formatted incorrectly. 


19

Typical Error:Demographic Interface 

Comment Section Appears in HL7 File When 

Message Errors Out. 

Errors referring to missing or bad demographic information should NOT be 

resolved in LinkLogic. These should be resolved in your Practice Management 

system. 

For this example, you should: 

1. Find the patient’s date of birth. 

2. Enter it into the patient’s record in the Practice Management system. 

(Doing this will generate a new HL7 message, which will be sent to the 

EMR.) 

3. Verify that the record was created / updated in EMR. 

4. Remove the error from the errors tab. 

Always follow the procedure above to ensure that data is kept in synch between 

systems. 

Always remember that your Practice Management system is the MASTER system 

and that the EMR is the RECEIVING system. 


20

Typical Error:Demographic Interface 

PID|||MR-101-003|MR-101-003|Ellis^Virgil||19431208|M||Black|2545 

SW 78th^^PortlandÔR^97229ÛSA||503-292-3590|503-225- 

2147|English|D|||815-83-5639| 

To resolve this error, do the following: 

1. Edit the open HL7 file to change “Black” to “B” in PID-10. Be VERY careful 

not to remove any other characters in the HL7 file. (For “field too long” 

error types, refer to HL7 specifications for EMR supported field values.) 

2. Save & close the edited file. 

3. With the file still highlighted in the errors tab, click resolve. 

To prevent this error in the future, correct MIK Mapping. 

Instructions for MIK Mapping begin on page 38 of this manual. See page 37 of this 

manual for supported EMR values for Race, Marital Status, Patient Relations, and 

Patient Employment Status. 


21

Typical Error: Scheduling Interface 

Missing Appt Book Error: 

Activity Log Message 

Code 2081 

Errors like the one shown here occur when an appointment book 

related to the imported appointment message is not set up in the 

EMR. Example associated activity log message: 

• Appointment book ‘Star’ could not be found. 

To resolve: 

1. Set up appointment book in Centricity EMR as applicable. 

(Go>Setup>Settings>Appointments) 

2. Double-click the highlighted message in the errors tab. 

3. Select the appropriate appointment book as applicable & click OK. 

Tip: Highlight the associated activity log message for the error, as shown above. 

Activity log message code # 2081 will show what came across the interface for the 

appointment book. Checking here will reduce the amount of time spent going back 

and forth from PM Scheduling and LinkLogic and help you resolve these errors 

quickly. 


22


Errors like the one shown here occur when an appointment type 

related to the imported appointment message is not set up in the 

EMR. Example associated activity log message: 

• Appointment type ‘Asthma Checkup’ is not defined….. 


Missing Appt Type Error: 

Activity Log Message 

Code 2073 

To resolve: 

1. Set up appointment type in Centricity EMR as applicable. 

(Go>Setup>Settings>Appointments) 

2. Double-click the highlighted message in the errors tab. 

3. Select the appropriate appointment type as applicable & click OK. 

Tip: Highlight the associated activity log message for the error, as shown above. 

Activity log message code # 2073 will show what came across the interface for the 

appointment type. Checking here will reduce the amount of time spent going back 

and forth from PM Scheduling and LinkLogic and help you resolve these errors 

quickly. 

23


This error was generated because the appointment book was not mapped in MIK or 

the appointment cross-reference file, as applicable. 

• Appointment Book ’53’ could not be found. (Activity Log Message Code 

#2081) 

To resolve: 

1. Double-click the highlighted error in the errors tab. 

2. Select the appointment book as applicable from the drop-down list & click OK. 

To prevent this error in the future, correct MIK Mapping or your 

Appointment Cross-Reference file (as applicable). 

Refer to instructions for MIK Mapping beginning on page 38 of this Manual if needed 

or the Cross-Reference section of this Manual, beginning on page 57. 


24

Resolve Appt Book / Type Errors 

Missing Appointment Book and/or Type errors will be resolved using the screens 

above. There are no associated HL7 files for these. Select the book and/or type 

from the dropdown or binoculars. 


25

Typical Error: Lab Results Interface 

PV1|1|R|^^^128Êast Surg||||hwinston^Winston^Harry^S. 

To resolve: 

1. Very carefully type the location of care abbreviation in place of the 

number in PV1-3, without removing any other characters in the message. 

2. Save & close the HL7 file. 

3. Click RESOLVE. 

To prevent this error in the future, correct MIK Mapping or your 

Location of Care Cross-Reference file (as applicable). 

Refer to instructions for MIK Mapping beginning on page 38 of this Manual if needed 

or the Cross-Reference section of this Manual, beginning on page 57. 


26

Typical Error: “No Existing Data…” 

This type of error is possible for all interface types. 

Follow the directions on pages 27-29 to resolve this type of error. 

NOTE: It is sometimes helpful to highlight the patient’s external ID in PID-2 or PID-3, 

right click & copy the patient ID, and then paste this ID into the EMR patient search 

dialog when working to resolve this type of error. (See step 1 on page 27 & step 5 on 

page 28.) 


27

Resolve “No Existing Data…” Errors 

Comments 

Section of 

HL7 File 

To resolve: 

1. Make note of the patient’s demographic information in the comments 

section of the HL7 file, then close the file. (You may opt to copy the 

external patient ID in PID-2 or PID-3 and use this in step 5 on the next 

page.) 

2. With the error still highlighted, click Resolve. 


continued on next page…… 

28


…….continued from previous page 

3. Highlight the entry in the “Data to Patient Matching” window. 

4. Click “Set Patient” button. 

5. Click “Search” on the “Find Patient” window. (Note: If searching by external ID, 

paste the ID copied from PID-2 or PID-3 and verify that the “search by” field has 

been changed to “External ID” prior to clicking the “Search” button.) If you 

believe the patient could be inactive, uncheck the “Search active patients only” 

checkbox prior to clicking the “Search” button. 

6. Highlight the correct patient’s name, then click OK. 


continued on next page……. 

29



7. Highlight the “User-Specified Match” line item in the “Data to Patient Matching” 

window, then click OK. 

8. Click OK again when processing is complete. 


30

Merging Charts 

If you have duplicate charts, you should merge them prior to resolving related 

LinkLogic errors. 

Note: There can be no unsigned documents in either chart and no other user can be 

in either chart when you perform this function. 

If you have privileges to merge charts, follow these steps: 

1. Open the chart you want to merge (the “bad” chart) 

2. Make sure you are on the summary tab of the patient’s chart 

3. Go to “Actions” in the toolbar 

4. Choose Administration>Merge Chart….. 



NOTE: If the source chart is completely blank with no documents (including filed in 

error) you may choose to Delete the chart instead, eliminating the need to merge. 

Proper privileges are also required to perform this function. 

31


……continued from previous page 

5. After clicking Actions>Administration>Merge, the Find Patient Dialog appears. 

6. Find the Destination Patient (the duplicate chart that you want to keep) 

7. Highlight the correct patient and click OK. 


32



The left side of the screen shows the source chart (“bad” chart), and the right side 

shows the destination chart (the one you want to keep & will contain the merged 

data). 

8. Uncheck the checkboxes for “Merge Insurance Information” and “Merge Contact 

Information” 

9. Check the checkbox for “Delete Source after Merge”. This will delete the “bad” 

chart after the merge. 

10. Click Merge 

11. The charts are now merged. Click OK to the message that appears. 


33

MIK 

Mapping 


34

MIK Mapping: 4 Key Items 

1 

2 

3 

4 

PM 

Appointment Types 

Doctors 

Facilities 

Resources 

EMR 

Appointment Types 

Responsible 

Providers 

Locations of Care 

Books 

Relationship 

1 to 1 

1 to 1 

1 to Many 

1 to 1 

Who from the customer site is the key person to learn how to maintain these items? 

These items will need to be maintained long term. 


Integration: 

Manual/Scripted 

Script can be run at first set up, 

then add manually through MIK, 

Linking the List Name to External 

ID* (*same naming convention) 

Manual through MIK, 

Linking the List Name to External 

ID* 

(*EMR Login Name for Doctor – 

hwinston) 

Manual through MIK 

Assistance through Rosetta Stone 

[RS] 

Manual through MIK 

ANY time you add appointment types, doctors, facilities, or resources to the 

Practice Management system, you will need to do the following: 

1. Set up corresponding items in Centricity EMR.* 

2. Map in MIK. 

This should be done as soon as possible to avoid generation of LinkLogic errors. 

*To set up corresponding items in Centricity EMR: 

Go>Setup>Settings>Appointments>Types 

Go>Setup>Settings>Users>Users 

Go>Setup>Settings>System>Locations of Care 

Go>Setup>Settings>Appointments>Books 

35

Mapping Examples . . . 

PM 

Appointment types 

New Patient 30 

Doctors 

Winston MD, Harry S 

Facility 

Millennium Health System 

Resources 

Winston MD, Harry S 


Appointment types* 

New Patient 30 

EMR login names 

hwinston 

Location of Care abbreviation 

MHS 

Appointment Books* 

Winston 

*Mappings are case sensitive. Also do not include any punctuation in Book 

Names in EMR Setup or MIK Mapping. 


36

MIK Mapping: Additional Items 

1 

2 

3 

PM 

Marital Status 

Patient Relationship 

Race 


Marital Status* 

Patient Relations* 

Race* 

*See page 37 for supported EMR values. 

Notes 

Types used in EMR must be in PM 


This item is in direct conflict between applications 

PM (pt’s relationship to guarantor/ins party) 

EMR (guarantor/insured party to pt) 

Types used in EMR must be in PM 

Should refrain from using this field for other uses. 

37

Supported EMR Values 

Marital Status 

Patient Relations 

Race 

Patient Employment Status 

Supported EMR values include the following initials: 

A (Separated), D (Divorced), M (Married), S (Single), W (Widowed), 

O (Other), U (Undetermined - default) 


S (Self), M (Marriage), P (Parent), O (Other) 


B (Black), C (Chinese), F (Filipino), H (Hispanic), J (Japanese), N 

(Native American), I (Native Hawaiian), M (Multiracial), O 

(Oriental/Asian), P (Pacific Islander), W (White), T (Other), U 

(Undetermined - default) 


F (Full-time), P (Part-time), I (Self-employed), R (Retired), S 

(Student), C (Child), U (Unemployed) 

Refer to the HL7 Specifications in the Managing Interfaces manual for Centricity EMR 

9.2 for complete information. 

This documentation can be downloaded from the EMR Support web site: 

http://support.centricityservices.com/ 

You will need your site’s user ID & password to log in to the Support web site. 


38

MIK Mapping 

The MIK application is located on the PM server. You will need access to the PM 

server to set up and maintain MIK Mapping. 

To open the application & set up MIK Mapping: 

1. Double-click the “Shortcut to Server Setup” icon on the desktop or launch 

from Program Files menu. 

2. Click the “Advanced Setup Options” radio button. 

3. Click NEXT. 


continued on next page…. 

39

Integration Kit Configuration 

…..continued from previous page 

4. Click the “Millbrook Integration Kit Configuration” radio button. 

5. Click NEXT. 



40



6. Click NEXT here & on the following screens until you arrive at the 

Destination LinkLogic window. 



NOTE: Startup Type should be set to Automatic as shown above. MIK can also be 

stopped and started from this screen as needed.* 

1. Click the STOP button to stop the MIK Service. 

2. Click the START button to restart the MIK Service. 

*An alternate method of stopping / starting the MIK service, would be from Control 

Panel>Administrative Tools>Services on the server. 

41


….continued from previous page 

7. With Destination LinkLogic highlighted, click MODIFY. 



42

MIK Mapping 

….continued from previous page 

8. Click Modify Map. 

9. Click the Mapping tab to see mapped items. 

10. Highlight the item in the list (i.e. Appointment Types) that you wish to 

map and click Modify. 



43

MIK Mapping: Appointment Types 

“List names” in the left column are the items that are currently set up in PM. (List 

names appear automatically as items are set up in PM.) The external ID column is for 

EMR equivalents of those items. 

Map Appointment Types in PM to Appointment Types in EMR. 

1. Highlight “List Name” item to map 

2. Click MODIFY. 

3. Type EMR value for item in External ID field.* 

4. Click OK. 

*This value must exactly match what is set up in the EMR. Appointment types are case 

sensitive and should contain no punctuation in EMR setup or mapped external ID fields. 

(Go>Setup>Settings>Appointments>Types) 

Copy / paste can be used in this process as desired to ensure exact matching of values. 

TIP: To move between items in the list, use NEXT and PREV buttons. 


44

MIK Mapping: Doctors 

Map Doctors in PM to Providers’ User IDs in EMR. 


45

MIK Mapping: Facilities 

Map Facilities in PM to Location of Care Abbreviations in EMR. 


46

MIK Mapping: Resources 

Map Resources in PM to Books in EMR. 

Appointment books are case sensitive and should contain no punctuation in EMR 

setup or mapped external ID fields. 


47

Save Mapping Changes 

IMPORTANT: To save any mapping you have done: 

1. Click NEXT until you get to the Installation window. 

2. Once you arrive at this window, click NEXT again to SAVE your mapping 

changes! 

3. You will see a “return” button on the next window & a message at the top of the 

screen that says “MIK configuration is complete!” 

4. At that point, it is o.k. to click EXIT. 


48

Rosetta 

Stone 


49

Stop / Start Rosetta Stone Service 

Rosetta Stone is an interface engine that works with the MIK to format messages 

sent to & from PM with the proper format. 

Anytime the connection with Oracle needs to be re-established, it will be necessary 

to restart Rosetta Stone*. 

To stop and restart Rosetta Stone: 

1. Double-click the Rosetta Stone icon to launch the console. 

2. Right click on local machine & click stop. 

3. Right click on local machine again & click start. (Will see green arrow.) 

4. Go to FILE, EXIT to close the Rosetta Stone console. (The Rosetta Stone 

service will still be running even after closing the console.) 

*You will need access to the PM Server to restart Rosetta Stone. An alternate 

method of stopping / starting Rosetta Stone, would be from Control 

Panel>Administrative Tools>Services on the server. 


50

Rosetta Stone Errors 

Rosetta Stone should be checked often for possible errors. 

To check for errors: 

1. Click the plus sign next to local machine. 

2. If there is a number next to the errors folder, expand it to resolve the errors there. 

The number represents the number of errors in the folder. 

3. Items that have not crossed over to the EMR will be found in this errors folder. If 

the data shown on the right side of the screen contains an HL7 formatted 

message, you can click the resolve button to resolve the highlighted error, which 

will send the message through to the EMR. 

4. Call Support as needed regarding technical errors that appear here. You can 

click the delete button to delete the highlighted error if the technical error is 

routine in nature. 

5. Go to FILE, EXIT to close the Rosetta Stone console. (The Rosetta Stone service 

will still be running even after closing the console.) 


51

Resending Charges 

to 

Centricity PM 


52

MIK Rejection Report 

The MIK Rejection Report contains messages regarding charges that did not 

cross from EMR to PM. Billing message errors do not appear in the LinkLogic 

module of the EMR, but will be addressed utilizing the MIK Rejection Report. 

To work the MIK Rejection Report: 

1. Double-click the MIK Rejection Report icon to begin addressing the 

errors.* 

2. Resolve applicable problems in PM Admin prior to resending charges.** 

3. Check the boxes next to the items on the MIK Rejection Report that have 

been addressed, and scroll to the bottom of the screen. 

4. Click the Delete button to delete checked items from the report. 

*The MIK Rejection Report can be accessed from any computer where the 

following URL has been set up: 

http://servername/pmdatabasename/mikrejectionreport.asp 

(Note: You will need to insert your site’s server name & PM database name in 

place of the generic items shown in the URL example above.) 

**The procedure for resending charges from EMR to PM is explained on pages 

53-54. 


53

Resending Charges to PM 

To resend procedures to PM: 

1. Work through the MIK Rejection Report (as described on page 52). 

2. Address any Admin setup issues in Centricity PM. 

3. On the LinkLogic Jobs tab in Centricity EMR, click the EXPORT button. 


continued on next page…… 

54

Exporting Procedures 


4. Click the plus sign next to the yellow Procedures folder to expand. 

5. Highlight the name of the Procedures interface. 

6. Click the radio button next to “Specific procedures / specific patient”. 

7. Click the ellipsis button to search for & select the patient. 

8. Highlight procedures to resend in list below patient name. Tip: To select multiple 

procedures, press the CTRL key on your keyboard while selecting procedures 

with the mouse. 

9. Click OK to export selected procedures. 

Note: Codes being sent from Centricity EMR must be present in Centricity PM. 

Monthly updates for Centricity EMR do not update codes in Centricity PM. 

Updates for Centricity PM should be requested from Support or individual codes 

may be entered manually in Centricity PM as necessary. 


55

Importing External Charges - PM 

In PM, you can filter the billing criteria to only show visits that are waiting for 

external charges. 


56

Importing External Charges - PM 

In PM, external charges can be imported or retrieved from the Billing screen or Visit 

screen as shown above. 


57

Cross-Reference 

Files 


58

Cross-Reference Files 

Some interfaces require the creation & use of cross reference files. 

Creating cross-reference files is very similar to MIK Mapping. 

Cross reference files translate data field values to values that can be 

recognized by the EMR application on import or the external system 

on export. 

For example, if you import laboratory results, you will need a crossreference 

file to translate laboratory test result codes to the EMR 

application observation terms. 

See Managing Interfaces manual for Centricity Practice Solutions EMR 

9.2 for complete information about cross-reference files. 


59

Sample Cross-Reference File: 

Lab Results 

H,xrf,Lab Result Heading Conversion Cross 

Reference,1.0,19960926093832 

F,ResultID 

I,55001000,LOI-1714-5 

I,25001400,LOI-1751-7 

I,25002000,LOI-1783-0 

I,50029000,LOI-1798-8 

I,45060000,LOI-5047-6 

I,55057200,LOI-2170-9 

I = Import Relationship 

The first value after I = laboratory test result code 

The last value = matching code for EMR observation term 

Tip: Search for obs terms in the terms.fot file that is included in downloaded & 

extracted observations terms clinical kits. You can use notepad or wordpad to open 

& view this file. 


60

Using the Terms.Fot File to Find EMR 

Observation Term Codes 

If using Notepad, select “Find” from the Edit menu. (If using Wordpad, click the 

binoculars icon.) 

The example above shows a search for the obs term “pap smear”. The FindNext 

button was repeatedly clicked until the exact obs term was found in the file. 

The code shown on the left side of the page is the code to add to the cross-reference 

file so that pap smear results will populate the Pap Smear observation term in the 

flowsheet when pap result documents are signed. (Do not include the quotes with 

the value.) 

Example: 

I,1234567,CPT-88150 

------------------------------------------------------------------------------------- 


The first value after I = laboratory test result code 

The last value = matching code for EMR observation term 


61


Document Types 

H,xrf,Note Type cross-reference file NotesLink and 

LabLink,1.0,20020528164000 

F,noteType,RequestorField1 

I,CM,Clin Updt 

I,CS,Summary 

I,CN,Cons Rpt 

I,DR,Diag Rpt 

I,ER,ER Rpt 

I,EK,EKG Rpt 

I,GC,Ext Corr 

I,PRE,Preload 

I,ZZ,Ext Oth 


The first value after I = document type being imported from outside system 

The last value = corresponding document type abbreviation in EMR 

This type of cross reference file is needed when importing scanned documents. 

See Managing Interfaces manual for Centricity EMR 9.2 for complete list of 

supported document types. 


62

Sample Cross-Reference File: Providers 

H,xrf,Care Provider ID Conversion Cross 

Reference,3.0,20070106191530 

F,provider,CareProvider,OrderingProvider,AttendingDoctor,Filler 

ContactPerson,PrimActivityProvider,Originator,AuthenticationP 

ersonTimeStamp,transcriptionist,ResponsibleObserver,DocAuth 

enticator,DistributedCopies,SendCopiesTo,OrderedByCode,Enter 

edByCode 

/-/ This XRF file was generated with LinkLogic Version LinkLogic 

8.0.0_126 \-\ 

I,C78945,hwinston 

I,D87546,smitchell 


The first value after I = Provider’s UPIN number (or other appropriate ID) 

The last value = corresponding Provider’s user ID in EMR 

Using this type of cross reference file prevents related LinkLogic errors and ensures 

that lab results go to the corresponding provider’s desktop. 


63


Locations of Care 

H,xrf,Location of Care Conversion Cross 

Reference,3.0,20070106191530 

F,CareUnitID,AssignedPatientLocation,Location,SendingFacility, 

ReceivingFacil,PatAccount 

/-/ This XRF file was generated with LinkLogic Version LinkLogic 

8.0.0_126 \-\ 

I,128,EAST 

I,135,SOUTH 


The first value after I = Location or Facility Number from Outside System 

The last value = corresponding Location of Care abbreviation in EMR 

(Note: This is handled in the MIK for the PM to EMR / EMR to PM interfaces.) 


64

Maintaining Cross-Reference Files 

Cross-Reference files should be edited any time your site 

adds new providers, locations of care, or document 

types. 

The lab results cross-reference file should also be edited 

any time your site begins ordering new laboratory tests 

to ensure that the corresponding lab results will 

populate flowsheets. 

To edit cross reference files, navigate to the LinkLogic 

folders located on the Data Transfer Station (DTS). 

You will need to locate the drive on the DTS where LinkLogic is loaded.* 

The files will be located in the config\local folder. Each file will have a .xrf extension. 

Example path: \Program Files\Centricity EMR 

9.2\llogic\config\local 

To Edit: 

1. Open the file you want to edit, using Notepad. 

2. Go to the very end of the file contents, using CTRL-END. 

3. On a new line, add another I with a comma. 

4. Add the new information, making sure to follow the same formatting you 

see in the file. 

5. Add each new item as applicable, per instructions in steps 3 & 4 above. 

6. Save & close the file when finished. 

7. Simultaneously press the following keys on your keyboard & release: 

CTRL-SHIFT-D This will clear the LinkLogic cache. (Note: If you are 

navigating to the LinkLogic path on the network from your computer, it 

may be necessary to physically perform this procedure on the DTS 

computer / server.) 

8. Click OK to the pop-up stating that the LinkLogic cache will be destroyed 

the next time a job is run. 

*Check with your site’s network administrator if you cannot locate the crossreference 

files you need to edit. 


65

Centricity 

Clinical 

Gateway 

(CCG) 


66

Centricity Clinical Gateway (CCG) 

The Centricity Clinical Gateway (CCG) provides seamless communications between 

Centricity products and external healthcare interfaces. The CCG is installed on the 

Interface Engine server. The primary component of the CCG is the Quovadx 

Cloverleaf interface engine. 

The interface engine receives messages from various internal and external sources 

in a variety of protocols. Messages are converted as necessary and routed to the 

appropriate destination. Sources and destinations include the Centricity 

applications and the defined CCG sites (interfaces). 

The following features make use of this interface capability: 

• Immunization Registry 

• Lab Orders Export 

The interfaces are managed through the Cloverleaf Integration Services graphical 

user interface (GUI). Interfaces are installed and activated through the GUI. The GUI 

also includes tools to monitor the traffic through the interface engine. 


67

Centricity Clinical Gateway (CCG) 

Immunization Registry: 

Batch export of immunization information can be scheduled through the Data Transfer 

Station (DTS) and sent to an immunization registry through the Centricity Clinical 

Gateway (CCG) system. For patients who opt in, immunization information is exported 

as demographic information and observations data via LinkLogic to CCG, which 

transforms the data into messages before sending it on to the registry. 

When the immunization registry has updated information regarding a patient, the new 

immunization data is sent to CCG and then imported to Centricity EMR via LinkLogic. 

The immunization data is routed as a document to the patient's responsible provider. 

Note: With the initial release, only the following are supported: Scientific Technologies 

Corporation (STC) – Maryland & Washington, Wisconsin Immunization Registry (WIR) – 

Massachusetts. 

Lab Orders Export: 

Lab orders can be exported in a standard HL7 electronic format to lab service 

providers. The appropriate messages can be generated and exported through the Data 

Transfer Station (DTS), and sent to the corresponding lab service organizations through 

the Centricity Clinical Gateway (CCG) system. Both new and canceled orders are 

supported. Note: With the initial release, the lab order export messages support 

LabCorp® specific protocols. 


68

Viewing the Processes 

Status Colors 

Green 

means 

active. 

Yellow 

means 

pending. 

Red 

means 

down. 

Both threads part of process1. 

Active but waiting 

for origin system 

to connect 


Active and 

connected to 

destination system 

Shown above is an example of the Cloverleaf Integration Services graphical user 

interface (GUI). Process statuses are color-coded, as indicated. Examples of 

additional statuses are shown on the next page. 

69 / 


69

Green - Up 

Yellow - Up 

Red - Up 

Green - Opening 

Yellow - Opening 

Red - Opening 

Red - Down 

Process Statuses / Color Schemes 


70

CCG Services 

The CCG Service Tools are web based. The following services must be running In 

order for the tools to be available: 

• Centricity Clinical Gateway Service Tools 

• Centricity Clinical Gateway Webmin Service 

(Start these services via Control Panel>Administrative Tools>Services) 


71

Accessing the Webmin Tool 

The Webmin tool in CCG allows errors to be viewed and re-sent through the 

Interface Engine. 

The tools may be accessed via the Microsoft Internet Explorer web browser. If you 

are working on the server where CCG is installed, the URL is: 

http://localhost:10000 

NOTE: If you are working remotely, type http://:10000/ 

The default port for Webmin service is 10000. It is recommended that you don’t 

change this port. 

The default Username is: geservice 

The default Password is: geservice 

After logging on, the Service Tools page is displayed. Click the Interface Monitor link 

on the Service tab, as shown above. 


72 / 


72

CCG Interface Monitor 

The CCG Interface monitor provides a snapshot of the current status of active 

interface sites (Cloverleaf sites) on the CCG. 

The CCG Interface monitor has an error message browser, which allows you to: 

• Browse the list of messages in the Cloverleaf error database for the 

selected site 

• Re-send one or more messages (Messages that are successfully re-sent 

are deleted from the error database.) 

• Delete one or more messages without re-sending (Messages that are 

deleted without being re-sent are also deleted from the error database.) 

When you click a link showing the number of errors for a particular site, the CCG 

Interface Monitor displays a list of all the messages in the Cloverleaf error database 

for that site. 

Click the “Monitor all sites” link to review statistics for all interfaces. 


73

Viewing & Working With Errors 

Clicking the message ID link, as shown above, will open the specific HL7 message 

that errored out in the CCG. 

The message can be resent by clicking the Send button at the bottom of the screen 

for the message shown.** 

To resend multiple messages, click the checkboxes next to the specific messages to 

be resent (or click the Select All button at the bottom of the window). Click the 

Resend button at the bottom of the window to resend the selected messages. 

Messages that are successfully resent are deleted from the error database. 

To delete multiple messages, click the checkboxes next to the specific messages to 

be deleted (or click the Select All button at the bottom of the window). Click the 

Delete button at the bottom of the window to delete the selected messages from 

the error database. 

**Note: If editing is required, this cannot be done within the CCG Interface 

Monitor at this time. You will need to contact a designated person on your IT 

staff or GE Support for help, so that the source of the error messages can be 

corrected. 


74

Appendix: 

Integration Between 

Centricity PM 

and Centricity EMR 


75

Data Flow Between Systems 

LinkLogic 

(Centricity EMR) 

Procedures 

Limited 

Demographics 

(1-time upload) 

Integration 

Kit 

(LMIK – 

Includes 

Rosetta 

Stone) 

Demographics 

Scheduling 

MIK 

QUEUE 


Centricity 

PM 

76

Shared Demographics 

Name 

Address 

Phone Number 

Date of Birth 

SSN 

Sex 

Patient Relationship 

Insurance Carrier(s) 

Doctor 

Referring Physician 

Primary Care Physician (found in EMR under contacts) 

Contacts 


77

Demographic Field Comparison 

Centricity PM Fields: 

Practice Management ID - “Patient ID” 

Name (Prefix, First, Middle, Last, Suffix) 

Date of Birth 

Social Security Number 

Sex 

PM “Facility” 

Centricity EMR Fields: 

EMR “External ID” 

DOB - Required field 

Sex - Required field 

EMR “Location of Care” 


First and Last Names – Required fields 

Recommended but not required 

It is recommended that the following fields be set up as required fields in Centricity PM, 

as these are required fields in Centricity EMR: 

•First name 

•Last name 

•Date of Birth 

•Sex 

78

Other Related Fields 

1 

2 

. 

3 

4 

5 

6 

. 

PM 

Doctor or Other Provider 

Modifiers 

CPT 

ICD-9 


Primary Care Physician 


Person “ordering” in 

“Authorized by” field must 

be a billable provider in PM 

Modifiers 

CPT 

ICD-9 


Contacts 

Set Up Considerations: Administration 

Required to be a billable provider in PM 

Must match in both products to work 



Most CPT codes are in EMR. Therefore ALL codes must be loaded 

into PM. 


ALL ICD-9 codes are in EMR Therefore ALL codes must be loaded 

into PM. 

Also Shows in EMR 

Registration, Contact Tab – as a “contact” 

Shows in EMR Registration, Contact Tab – as a contact type of 

Other on the 1 st Address Line 

79

Patient Appointments 

Centricity PM fields that flow to Centricity EMR 

Patient Name 

Appointment Type 

Date and Time 

Duration 

Basic Information 

Scheduled with Resource in PM & appears in Book in EMR 

Appointment Status (Arrived in PM puts black “dot” next to appointment in EMR) 

For Cancellations to transfer, the Appointment Type in PM should be set to Delete=N 

Appointments in a Set or Chain will transfer/update in the EMR. However, the linkage or 

association is maintained in PM. 

If only the Resource is modified via Modify Appointment, Appt Clipboard, or drag and drop, 

the Appointment information will not update from PM to EMR. Workaround: When 

modifying an appointment, add 1 min. to the start time, or Cancel and then Book as a new 

appointment. 


80

Non-Patient Appointments 

Centricity PM sends data to Centricity EMR: 

Appointment Type 

Date and Time 

Duration 

Resource (“Book” in EMR) 

Appointment Status 

Resource and Block Out Appointments are associated with a dummy patient in 

EMR named “Block Scheduling.” 


81

Centricity EMR LinkLogic - GE Healthcare Centricity Customer and ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?