APPEAL_GRV_LETTER

Description: |
Letters that were sent or were attempted to have been sent from an appeal or grievance record.

Primary Key

Column Name | Ordinal Position |
--- | --- | ---
APPEAL_GRV_ID | 1 |
LINE | 2 |

Column Information

| Name | Type | Discontinued? |
--- | --- | --- | --- | ---
1 | APPEAL_GRV_ID | NUMERIC | No |
The unique identifier (.1 item) for the appeal/grievance record.
2 | LINE | INTEGER | No |
The line number for the information associated with this record. Multiple pieces of information can be associated with this record.
3 | CM_PHY_OWNER_ID | VARCHAR | No |
The Community ID (CID) of the instance that owns this record or line. This is only populated if you use IntraConnect.
4 | LETTER_SENT_DOCUMENT_ID | VARCHAR | No |
The contents of the letter that were delivered or are waiting to be delivered.
5 | APPEAL_GRV_LETTER_STS_C_NAME | VARCHAR | No |
Where this letter is in the generation process.
May contain organization-specific values: No
Category Entries:
Successfully Sent
Queued
Failed
Canceled
6 | LETTER_GUID | VARCHAR | No |
Unique identifier for this letter. This column can be used to join to APPEAL_GRV_LETTER_GEN_HX.LETTER_HX_GUID.
7 | APPEAL_GRV_LETTER_TYPE_C_NAME | VARCHAR | No |
Which letter type this line counts as. Released letters correspond to common letter types for timeliness requirements and will be automatically triggered during the workflow with no additional build.
May contain organization-specific values: Yes
Category Entries:
Acknowledgement
Extension Taken
Dismissal
Upheld Decision
Overturned Decision
Request to Expedite Denial
Partially Overturned Decision
Request to Expedite Approval
Extension Denial
Decision Effectuation
Grievance Resolution
Upheld Dismissal
Vacated Dismissal
8 | RECIPIENT_CLASS_EVENT_ID | VARCHAR | No |
The recipient class used to determine the specific recipient to send to.
9 | RECIPIENT_CLASS_EVENT_ID_EVENT_NAME | VARCHAR | No |
The name of the event.
10 | RESOLVED_FEV_SEND_TO_C_NAME | VARCHAR | No |
The specific type of the recipient found with the recipient class.
May contain organization-specific values: No
Category Entries:
Patient
Referred By Provider
Referred To Provider
Referred To Vendor
PCP
Other
Vendor
Provider
Subscriber of Coverage
Payer of Coverage
Referred By Location/POS
Referred To Location/POS
Referring Physician
Pool
Distribution Scheme
CRM Creator
CRM Current Recipients
CRM Task Owners
Admitting Provider
Attending Provider
Treatment Team
Current PCP
Primary Transporter
Secondary Transporter
Transport Manager
Transport Sending Unit
Transport Receiving Unit
MC Coverage PCP
MC Coverage Current PCP
Referred To Department
Referred To Specialty
Care Team
IP Sign In - Sending Unit User
IP Sign In - Receiving Unit User
IP Sign In - Current Unit User
Bed Planning IB Pager - Sending Unit
Bed Planning IB Pager - Receiving Unit
Emergency Contacts
Bed Request Admitting Provider
Bed Request Attending Provider
Billing Account
CC Receiver
Information Requester
Referred By Department
Transfer Center Request Owner
ADT Visit Contacts
Technician
Supervisor
Inspector
Manager
Start Location Unit Pager
End Location Unit Pager
Other Technicians
All Qualified Techs In Sector
Primary Qualified Techs In Sector
Authorized Representative
User Group Referred By Location
User Group Referred To Location
User Group Referred By Provider
User Group Referred To Provider
Operating Provider
Other Provider
Rendering Provider
Supervising Provider
Review Entity
Agency
Requesting Provider
Unified Communications Group - Sending Unit/Location
Unified Communications Group - Receiving Unit/Location
Unified Communications Group - Current Unit/Location
Unified Communications Group - Specific Group
Attached Chat Conversations
User Group Requesting Provider
Follow-Up Providers
Follow-Up Locations
Trading Partner
Subscribed Payer
Admitting Hospital UR Department
Prior Admission Last Attending Provider
Prior Admission Discharge Provider
Prior Admission Treatment Team
Provider Assigned to Bed
Nurse Assigned to Bed
Referred To Subspecialty
Referred For Treatment
Referred For Condition
First Contact
Appointment Staff
Patient Care Organizations
11 | RESOLVED_RECIPIENT_INI | VARCHAR | No |
The INItials of the master file containing the record of this letter's recipient.
12 | RESOLVED_RECIPIENT_ID | VARCHAR | No |
The ID of the record of this letter's recipient. The corresponding value in RESOLVED_RECIPIENT_INI indicates what table this can be used to join to.
13 | RESOLVED_RECIPIENT_GUID | VARCHAR | No |
The GUID of this letter's recipient. This column can be used to join to MEMBER_RESP_PERSON.MEM_RESP_GUID and will be populated when column RESOLVED_FEV_SEND_TO_C is set to 58 (Authorized Representative).
14 | DELIVERY_LOGIC_C_NAME | VARCHAR | No |
When resolving a delivery method for a particular recipient, this is how we chose that delivery method.
May contain organization-specific values: No
Category Entries:
Electronic or Physical
Electronic Only
Physical Only
15 | RESOLVED_FEV_DLVR_MTHD_C_NAME | VARCHAR | No |
The ideal delivery method chosen for the recipient of this letter.
May contain organization-specific values: No
Category Entries:
Letter
Fax
Note
EDI Notification
In Basket Message
Letter Review
Extension
ADT Autoprint using table
ADT Autoprint a report
Default Letter
Default Fax
Default In Basket Message
Admission Notification
E-mail
CE Message
Page
Triage
Immediate Transfer of Care
Pend Transfer of Care
Text
MyChart Message
MyChart Letter
eReferral to PCEHR
MyChart Scheduling Ticket
Mobile App Notification
Mobile App Notification and Page
Mobile App Notification, fall back to Page
Page, fall back to Mobile App Notification
Discharge Notification
Show In Bed Planning
Generate Document
Default MyChart
Clinical Attachment
Mail
Direct Message
Communication Management
External Notification
UM Notification
Chart Abstraction Registry
Payer Platform Notification
Default Payer Platform Notification
Automatically Determined
CRM Letter
Internal Payer Notification
Default Internal Payer Notification
Desktop Notification
Desktop + Mobile App Notification
16 | BATCH_PRINT_LTR_HX_JOB_TYPE_C_NAME | VARCHAR | No |
If a letter was submitted to batch print to be mailed out, this is the job type that the letter was queued to.
May contain organization-specific values: Yes
Category Entries:
All
17 | BODY_SMARTTEXT_ID | VARCHAR | No |
When the letter was created, this is the SmartText template that we used to generate the contents of the body.
18 | BODY_SMARTTEXT_ID_SMARTTEXT_NAME | VARCHAR | No |
The name of the SmartText record.
19 | COVER_SMARTTEXT_ID | VARCHAR | No |
When the letter was created, this is the SmartText template that we used to generate the cover sheet which was rendered before the body.
20 | COVER_SMARTTEXT_ID_SMARTTEXT_NAME | VARCHAR | No |
The name of the SmartText record.
21 | BACK_SMARTTEXT_ID | VARCHAR | No |
When the letter was created, this is the SmartText template that we used to generate the back sheet which was rendered after the body.
22 | BACK_SMARTTEXT_ID_SMARTTEXT_NAME | VARCHAR | No |
The name of the SmartText record.
23 | RESOLVED_IB_POOL_ID | NUMERIC | No |
If this letter was sent as an In Basket message, this will store the pool that we delivered to.
24 | RESOLVED_IB_POOL_ID_REGISTRY_NAME | VARCHAR | No |
The name of the In Basket registry in the HIP master file.
25 | RESOLVED_PROV_ADDR_UNIQUE_ID | VARCHAR | No |
The unique ID of the provider's address when the resolved recipient is a provider. This can be used to join to CLARITY_SER_ADDR in combination with column RESOLVED_RECIPIENT_ID when RESOLVED_RECIPIENT_INI = 'SER'.
26 | CITY | VARCHAR | No |
The city of this letter's recipient. A city may be recorded, even if the letter was not mailed.
27 | STATE_C_NAME | VARCHAR | No |
A category value for the state of this letter's recipient. A state may be recorded, even if the letter was not mailed. This is usually the same as the internal ID. If you use IntraConnect, this is the Community ID (CID).
May contain organization-specific values: Yes
28 | ZIP | VARCHAR | No |
The ZIP code of this letter's recipient. A ZIP code may be recorded, even if the letter was not mailed.
29 | DISTRICT_C_NAME | VARCHAR | No |
A category value for the district of this letter's recipient. A district may be recorded, even if the letter was not mailed. This is usually the same as the internal ID. If you use IntraConnect, this is the Community ID (CID).
May contain organization-specific values: Yes
30 | COUNTY_C_NAME | VARCHAR | No |
A category value for the county of this letter's recipient. A county may be recorded, even if the letter was not mailed. This is usually the same as the internal ID. If you use IntraConnect, this is the Community ID (CID).
May contain organization-specific values: Yes
31 | COUNTRY_C_NAME | VARCHAR | No |
A category value for the country of this letter's recipient. A country may be recorded, even if the letter was not mailed. This is usually the same as the internal ID. If you use IntraConnect, this is the Community ID (CID).
May contain organization-specific values: Yes
32 | BUILDING_NUMBER | VARCHAR | No |
The building/house number of this letter's recipient. A building/house number may be recorded, even if the letter was not mailed.
33 | RECIPIENT_NAME | VARCHAR | No |
The name of this letter's recipient.