Data Extract Name
Life of a Chase
About This Data Extract
This data extract shows all historical events that have been performed to chases.
Best For
Deep dive into technical analysis
Using This Report
This raw data extract can be analyzed in Excel or loaded into a BI system. It can be sorted, filtered, and aggregated by every type of measure to produce in-depth analyses for specific use cases.
What Information Can I Filter?
| Field |
| Project |
Life of a Chase can be pre-filtered by Project. After downloading, it can be further filtered by any measure within Excel or a BI system.
What Do The Fields Mean?
| Field | Data Dictionary Definition |
| Client ID | The internal identifier associated with a client |
| Client Name | Name of the Client |
| Project ID | The internal identifier associated with a project |
| Project Name | The name associated with a project |
| ChaseID | The internal identifier associated with a chase |
| Chase Type | Defines whether or not a chase is an original chase (no parent chase id) or a pursuit |
| Chase Client Chase Key | The identifier provided by the client for a chase |
| Parent Chase ID | Defines whether or not a chase is an original chase (no parent chase id) or a pursuit |
| Measure Code | Determines the type of an associated chase, which indicates what the coder is seeking to validate |
| Line of Business | The type of business associated with this chase: Medicare, Medicaid, Commercial |
| Product | Further detail for Line of Business, this can be Medicare HIOS number, a Plan ID or Health Plan |
| Compliance Code | An abbreviation indicating the compliance associated with a given Member |
| Compliance Code Description | An abbreviation indicating the compliance associated with a given Member |
| Compliance Code | An abbreviation indicating the compliance associated with a given Member |
| Compliance Code Description | An abbreviation indicating the compliance associated with a given Member |
| Current Chase Status | The status of a chase, based upon its workflow status and pend and invoice status |
| Current Process Step | The current workflow state of a given chase |
| Chase Create Date | Date that the chase was first created |
| Chase Create User Name | Name of user that created this chase |
| Expected Retrieval Method | The expected method to retrieve medical charts for a given chase |
| Actual Retrieval Method | The way that medical records were uploaded into Reveleer |
| Retrieved Date | Date when medical record is attached to a chase |
| EMR System | The EMR software where the medical record is |
| Page Count | Number of pages attached to the document |
| Commitment Date | Data item provides the appointment date when the documentsource is either 'EMR' or 'Field Tech', otherwise provides the commitment date |
| Appointment Date | The scheduled date of physical/virtual chart retrieval |
| Abstraction Date | The date that the chart attached to a chase has been coded or abstracted |
| Abstraction User Name | The name of the user who abstracted the chart |
| Overread Date | The date that a chase was overread |
| Overread User Name | The name of the user who completed overread 1 for the given chase |
| Overread 2 Date | The date that a chase was overread2 |
| Overread 2 User Name | The name of the user who completed overread 2 for the given chase |
| AID | Internal identifier (AID) associated with a chase address that has been cleaned/combined and added to the master document source table |
| Aidstatus AID Status | Contact status of an AID |
| Address Grouping | Data loaded grouper to associate various address IDs into client-desired groups |
| Group Name | Name of the facility associated with a processed data load (master) address |
| Address1 | First line of processed data load (master) address |
| Address2 | Second line of processed data load (master) address |
| City | City associated with a processed data load (master) address |
| State | Geographical state associated with a processed data load (master) address |
| Master Document Source Zip Code | Zipcode associated with a processed data load (master) address |
| Master Document Source Contact Details AID Phone Number | Phone number associated with an AID |
| Master Document Source Contact Details AID Fax Number | Fax number associated with an AID |
| Tempprovider NPI | National Provider Identifier |
| Provider Name | Full name for the provider |
| Service Provider ID | The internal identifier applied to a service provider after clean up and deduplication is performed |
| Member ID | The internal identifier associated with a member |
| Member Source Alias ID | AKA Client Member Key - Client-generated identifier associated with a member |
| Member DOB Date | The date of birth of the member |
| Member Gender | The gender of a member |
| Member Full Name | Full name of the member |
| Member First Name | First name of the member |
| Member Last Name | Last name of the member |
| Current Pend Code | An internal identifier for the various reasons that a chase may be pended, awaiting further action/or info to collect or code a medical record |
| Owner | Indicates whether the responsibility for a pend is associated with Reveleer (organization) or the client |
| Pend Status Name | Name associated with a given pend status |
| Pend Created By | The name of the user that created the most recent pend for a given chase |
| Pend Created Date | The date that the most current pend was created for a given chase |
| Pend Company | The internal identifier indicating the pend company associated with a 3rd party chase |
| Co Retrieval Owner | The organization that is retrieving the chase |