Configuring Centricity Connection Information - Integration for GE Centricity - English - Foundation 22.1 - OnBase - external - OnBase/Integration-for-GE-Centricity/English/Foundation-22.1/Integration-for-GE-Centricity/Configuration/Centricity-Front-Office-Scanning-Configuration/Configuring-Centricity-Connection-Information - 2022-08-18

Integration for GE Centricity

Platform
OnBase
Product
Integration for GE Centricity
Release
Foundation 22.1
License

To configure Front Office Scanning to pass credentials and Keyword information to the appropriate Centricity database, you must add the Centricity element to the Front Office Scanning configuration file.

<Centricity datasource="JohnMain24" username="JDoe333" password="John Pass3" schema="DBSCHEMA" patientid="Patient ID #" patientlast="Last Name" patientfirst="First Name" patientmiddle="Middle Name" chartid="Chart ID #" patientdob="Date of Birth" patientssn="Social Security #" providername="Provider" carelocation="Location" clinicdate="Clinical Date" doctypecomment="Comment" linked="Linked Status" signed="Signed Status" sensitive="Sensitive Status" />

The table below describes the settings that are found in the Centricity element. As you must configure a scan queue for a Centricity Document Imaging solution that will be used in conjunction with your Centricity Front Office Scanning solution, ensure that you map these settings below to the same credentials and Keyword Types in the Front Office Scanning configuration file that you map them to in the Assign Process Options for <scan queue> dialog box. For more information on mapping these settings for scan queues, see Scan Queue Configuration.

Note:

All of the settings listed below that correspond to OnBase Keyword Types (e.g., patientid, patientlast, patientfirst, etc.) must also be defined within the Front Office Scanning configuration file's DataSet element. Although the Front Office Scanning client does not pull Keyword information from Data Sets in the normal fashion when passing information to a Centricity database, the Front Office Scanning client must still create temporary Data Sets in memory for the documents being captured and uploaded.

Centricity Element Settings

Description

datasource

This setting allows you to specify the name of the local ODBC source that connects to the appropriate Centricity database.

Note:

This ODBC source is often created automatically by Centricity software.

Set the datasource setting to the appropriate ODBC source name (e.g., datasource="JohnMain24").

username

This setting allows you to specify the user name that will be used to connect to the appropriate Centricity database.

Set the username setting to the appropriate Centricity database user name (e.g., username="JDoe333").

password

This setting allows you to specify the password that will be used to connect to the appropriate Centricity database.

Set the password setting to the appropriate Centricity database password (e.g., password="JohnPass3").

schema

This setting allows you to specify the name of the schema that contains configuration information for the appropriate Centricity database.

See the schema setting to the name of the appropriate database schema (e.g., schema="DBSCHEMA").

patientid

This setting allows you to specify the OnBase Keyword Type that has been configured to hold the current patient's ID number.

Set the patientid setting to the name of the OnBase Keyword Type you wish to map to the Patient ID value that exists within the appropriate Centricity database (e.g., patientid="Patient ID #").

patientlast

This setting allows you to specify the OnBase Keyword Type that has been configured to hold the current patient's last name.

Set the patientlast setting to the name of the OnBase Keyword Type you wish to map to the Patient Last Name value that exists within the appropriate Centricity database (e.g., patientlast="Last Name").

patientfirst

This setting allows you to specify the OnBase Keyword Type that has been configured to hold the current patient's first name.

Set the patientfirst setting to the name of the OnBase Keyword Type you wish to map to the Patient First Name value that exists within the appropriate Centricity database (e.g., patientfirst="First Name").

patientmiddle

This setting allows you to specify the OnBase Keyword Type that has been configured to hold the current patient's middle name.

Set the patientmiddle setting to the name of the OnBase Keyword Type you wish to map to the Patient Middle Name value that exists within the appropriate Centricity database (e.g., patientmiddle="Middle Name").

chartid

This setting allows you to specify the OnBase Keyword Type that has been configured to hold the current patient's chart ID number.

Set the chartid setting to the name of the OnBase Keyword Type you wish to map to the Chart ID value that exists within the appropriate Centricity database (e.g., chartid="Chart ID #").

patientdob

This setting allows you to specify the OnBase Keyword Type that has been configured to hold the current patient's date of birth.

Set the patientdob setting to the name of the OnBase Keyword Type you wish to map to the Patient Date of Birth value that exists within the appropriate Centricity database (e.g., patientdob="Date of Birth").

Note:

You must set the patientdob setting to a Date Keyword Type within OnBase(as opposed to a Date & Time Keyword Type).

patientssn

This setting allows you to specify the OnBase Keyword Type that has been configured to hold the current patient's Social Security Number.

Set the patientssn setting to the name of the OnBase Keyword Type you wish to map to the Patient SSN value that exists within the appropriate Centricity database (e.g., patientssn="Social Security #").

providername

This setting allows you to specify the OnBase Keyword Type that has been configured to hold the name of the current patient's primary provider.

Set the providername setting to the name of the OnBase Keyword Type you wish to map to the Primary Provider Name value that exists within the appropriate Centricity database (e.g., providername="Provider").

If the user needs to assign multiple primary providers, set the providername setting to a delimited list of the names of all OnBase Keyword Types you wish to map to the Primary Provider Name value that exists within the appropriate Centricity database (e.g., providername="Provider1,Provider2").

carelocation

This setting allows you to specify the OnBase Keyword Type that has been configured to hold the name of the current patient's assigned location of care.

Set the carelocation setting to the name of the OnBase Keyword Type you wish to map to the Location of Care value that exists within the appropriate Centricity database (e.g., carelocation="Location").

clinicdate

This setting allows you to specify the OnBase Keyword Type that has been configured to hold the date and time of the current patient's appointment.

Set the clinicdate setting to the name of the OnBase Keyword Type you wish to map to the Clinic Date value that exists within the appropriate Centricity database (e.g., clinicdate="Clinical Date").

Note:

You must set the clinicdate setting to a Date & Time Keyword Type within OnBase(as opposed to a Date Keyword Type).

doctypecomment

This setting allows you to specify the OnBase Keyword Type that has been configured to hold a comment for the assigned Document Type.

Set the doctypecomment setting to the name of the OnBase Keyword Type you wish to map to the Document Type Comment value that exists within the appropriate Centricity database (e.g., doctypecomment="Comment").

linked

This setting allows you to specify the OnBase Keyword Type that has been configured to hold the linked status of the assigned Document Type. If the Document Type's linked status is YES, documents belonging to this Document Type are exported to the Centricity database once the documents are uploaded from the Front Office Scanning client to OnBase and processed through the configured scan queue. If the Document Type's linked status is NO, documents belonging to this Document Type are not exported to the Centricity database and only exist within the OnBase repository.

Set the linked setting to the name of the OnBase Keyword Type you wish to map to the Linked value that exists within the appropriate Centricity database (e.g., linked="Linked Status").

Note:

You must set the linked setting to an Alphanumeric Keyword Type within OnBase, as the value for this Keyword Type will be either YES or NO.

signed

This setting allows you to specify the OnBase Keyword Type that has been configured to hold the signed status of the assigned Document Type. If the Document Type's signed status is YES, documents belonging to this Document Type are marked as signed. If the Document Type's signed status is NO, documents belonging to this Document Type are marked as unsigned.

Set the signed setting to the name of the OnBase Keyword Type you wish to map to the Signed value that exists within the appropriate Centricity database (e.g., signed="Signed Status").

Note:

You must set the signed setting to an Alphanumeric Keyword Type within OnBase, as the value for this Keyword Type will be either YES or NO.

sensitive

This setting allows you to specify the OnBase Keyword Type that has been configured to hold the sensitive status of the assigned Document Type. If the Document Type's sensitive status is YES, documents belonging to this Document Type are marked as sensitive. If the Document Type's sensitive status is NO, documents belonging to this Document Type are marked as not sensitive.

Set the sensitive setting to the name of the OnBase Keyword Type you wish to map to the Sensitive value that exists within the appropriate Centricity database (e.g., sensitive ="Sensitive Status").

Note:

You must set the sensitive setting to an Alphanumeric Keyword Type within OnBase, as the value for this Keyword Type will be either YES or NO.