AHCCCS Search Engine. Conceptual Design. Anthony Christianson Author Position Date 11/28/07. Version: 1.0

Size: px

Start display at page:

Download "AHCCCS Search Engine. Conceptual Design. Anthony Christianson Author Position Date 11/28/07. Version: 1.0"

Steven Harris
8 years ago
Views:

1 AHCCCS Search Conceptual Design Author Anthony Christianson Author Position Date 11/28/07 Version: /28/2007

2 Revision & Sign-off Sheet Change Record Date Author Version Change Reference 12/4/07 Anthony Christianson Reviewers Name Version Approved Position Date Distribution Name Position Document Properties Item Details Document Title Conceptual Design Author Creation Date Last Updated 11/28/2007

Position Date Distribution Name Position Document Properties Item

3 Table of Contents AHCCCS Search... 1 Conceptual Design... 1 Revision & Sign-off Sheet... 1 Table of Contents... 1 Conceptual Design Summary... 2 Business Situation... 2 Overview of Conceptual Solution Alternatives... 2 Solution Architecture... 3 Patient Record Publish... 3 Patient Search... 4 Patient Record Search /28/2007 1

.. 2 Overview of Conceptual Solution Alternatives... 2 Solution Architecture.

4 Conceptual Design Summary The purpose of the AHCCCS Search is to consolidate a patient s demographic data into a patient index to minimize the number of items returned during a patient lookup. The design of the RLS mandates that each patient record is a single entry. Therefore, a single patient could feasibly have one or more entries in the RLS system. The AHCCCS Search will store each patient as a single entry, eliminating duplicate patient entries. As a result, the number of entries in the engine will be significantly less than the amount of entries in the RLS system. The smaller size of the engine will result in faster searches. In addition, the AHCCCS Search will store possible aliases of a patient. If two patient records in the RLS system are for the same patient, but there is minor discrepancy of the patient demographic data, depending on business rules, it will be possible for the engine to identify these records as belonging to the same patient and merge the second set of demographics in with the patient s current demographics. Business Situation When publishing a patient, the accuracy of the published data can be questionable. Whether it is a spelling variation of a name or inaccurate data entry, the potential for a patient to have records in the RLS under varied data is to be expected. The AHCCCS Search will be populated with information that consolidates a patient s information into fewer, more accurate items to increase the intelligence and performance of a search. Overview of Conceptual Solution Alternatives The alternative to not creating an AHCCCS Search is to not create an engine and allow searching the RLS system directly. This would pass the patient search criteria directly to the RLS. This would require the querying entity to filter out duplicates or possibly display hundreds of matches for the same patient or display no matches for the patient due to inaccurate search criteria. Advantage of not creating the AHCCCS Search Patient data stored in a single place eliminating redundant data Reduce development time for designing, creating and testing the patient index Disadvantage of not creating the AHCCCS Search Patient search performance Patient search inaccuracy 11/28/2007 2

The AHCCCS Search will store each patient as a single entry, eliminating duplicate patient entries.

5 Solution Architecture The AHCCCS Search will be a separate component within the RLS system. The AHCCCS Search will be utilized when called directly from the Patient Directory service or when the RLS identifies that an incoming request should use the component. The AHCCCS Search data store will contain the consolidated patient information in a search optimized format with enough information to accurately identify a patient. The patient index will be populated in real-time when new patient records are published to the RLS system. Patient Record Publish Data Partner 1. Publishes EMR 3. EMR Forwarded with RLS Key 2. EMR Metadata written RLS AHCCCS Search 4. EMR demographic RLS Data Data 1. Data Partner publishes an EMR to the RLS system 2. RLS insert/updates the EMR s metadata in the RLS 3. RLS forwards the EMR to the AHCCCS Search with the RLS EMR key 4. Patient Index writes the EMR demographic data to the engine data store including the RLS patient key for cross-referencing 11/28/2007 3

The AHCCCS Search data store will contain the consolidated patient information in a search optimized format with enough information to accurately identify a patient.

6 Patient Search 1. Searches for Patient User 2. Forwards Parameters 3. Performs Lookup Patient List Viewer AHCCCS Search 6. Displays Patient List 5. Formats and returns Patient List Data 4. Returns Patient List 1. User searches for Patient information 2. Viewer validates search parameters and forwards parameters to Patient Index 3. AHCCCS Search performs lookup using parameters 4. AHCCCS Search receives patient list that match given parameters 5. AHCCCS Search compile list returns to Viewer 6. Viewer displays patient list 11/28/2007 4

Viewer validates search parameters and forwards parameters to Patient Index 3. AHCCCS Search performs lookup using parameters 4.

7 Patient Record Search 1. Requests Patient Record Descriptors Data User 2. Forwards Request to RLS 3. Invokes Patient Index 4. Queries for Patient Cross- Reference Data Viewer RLS AHCCCS Search Display 6. Returns Record Descriptor CCD 5. Queries for Record Descriptors 7. Convers CCD to Dataset for Display RLS Data 1. User requests a patients record descriptors 2. Viewer creates message with AHCCCS Search index and AHCCCS Search code system 3. RLS identifies the search code system and forwards parameters to AHCCCS Search 4. AHCCCS Search queries engine data for RLS cross-reference keys 5. AHCCCS Search queries RLS for records descriptors. 6. AHCCCS Search formats RLS results into CCD 7. Viewer converts CCD into dataset for display 11/28/2007 5

Convers CCD to Dataset for Display RLS Data 1. User requests a patients record descriptors 2. Viewer creates message with AHCCCS Search index and AHCCCS Search code system 3.

COMPONENTS in a database environment

COMPONENTS in a database environment DATA data is integrated and shared by many users. a database is a representation of a collection of related data. underlying principles: hierarchical, network, relational