You use the Log Case page to add or edit a case record. The entity and case type determine the fields displayed on the Log Case page.
The Log Case page contains fields in the following panels:
You can open or close certain panels. Click (the plus sign) beside a panel to open the panel. Click
(the minus sign) to close the panel.
Field | Description |
---|---|
These fields display information about the entity the case concerns. None of these fields can be edited. The fields displayed are determined by the entity type: |
|
Enrolled Provider Fields | |
Case Record Number |
ND MMIS generated number assigned when a case record is initially created. It cannot be modified. |
Entity Type |
The type of organization, institution, or individual. Example: Provider |
Provider ID |
Unique identifier used for a provider of healthcare services. Format: Up to 15 alphanumeric characters |
ID Type |
Unique code that indicates the type of provider ID entered. Examples: DEA, NPI, SSN/EIN |
Payer ID |
Unique identifier of the payee/payer. |
Status |
The enrollment status of the provider. |
Name |
The name of the provider that the case is about. Examples: Assumption Community Hospital, John Smith, etc. |
Specialty |
The provider's certified medical specialty. The provider specialty is based on the Level Ill Area of Specialization of the Taxonomy Code Set. Examples: Allergy, Blood Banking, Dentistry, Dermatology, Podiatry |
Provider Type |
The provider classification. Based on the Level I Provider Type of the Taxonomy Code Set. Examples: Dental, Pharmacy, Hospital, Vision, Physician |
Phone | The phone number for the provider's service location. |
County | The name of the county associated with the address of the provider. |
Enrolled Provider - Alternative Identifiers Fields | |
Type |
A code to identify type of alternate identifier. Examples: SSN, ME (Medicaid), BC (Basic Care) |
Alternate ID |
An additional unique identifier being used for a provider. |
Line of Business |
The unique code that identifies the line of business, a high-level payer, or funding source such as Medicaid. |
Case Record Number |
ND MMIS generated number assigned when a case record is initially created. It cannot be modified. |
Un-enrolled Provider Fields | |
Case Record Number |
ND MMIS generated number assigned when a case record is initially created. It cannot be modified. |
Entity ID |
One of the following identifiers:
|
Entity Type |
The type of organization, institution, or individual. Example: Un-enrolled Provider |
Status |
The status of the provider's enrollment application. |
Name |
The name of the un-enrolled provider. Examples: Assumption Community Hospital, John Smith, etc. |
Specialty |
The provider's certified medical specialty. The provider specialty is based on the Level Ill Area of Specialization of the Taxonomy Code Set. Examples: Allergy, Blood Banking, Dentistry, Dermatology, Podiatry |
Provider Type |
The provider classification. Based on the Level I Provider Type of the Taxonomy Code Set. Examples: Dental, Pharmacy, Hospital, Vision, Physician |
Phone | The phone number for the un-enrolled provider's office. |
County | The name of the county associated with the address of the un-enrolled provider. |
Enrolled Member Fields | |
Case Record Number |
ND MMIS generated number assigned when a case record is initially created. It cannot be modified. |
Entity Type |
The type of organization, institution, or individual. Example: Member |
Member ID |
A unique identifier assigned to a member. |
ID Type |
The kind of ID entered in the Entity ID field. Examples: Medicaid ID, Member MMIS ID, SSN, etc. |
SSN |
Social Security Number. A nine-digit number assigned by the Federal government, usually assigned at the time of birth and used for tax purposes. Format: NNN-NN-NNNN or NNNNNNNNN Example: 123-45-6789 Note: This field cannot contain all zeros. |
Name | The name of person associated with the member ID. |
The e-mail address of the user. Example: ijones@myemail.com |
|
Category of Eligibility |
The member's type of eligibility coverage under Medicaid. Example: BCCP - Breast/Cervical Cancer Program |
District Office |
The regional office where members go to get information. For example, picking up or signing documents. |
Date of Birth |
The date the person was born; the person's date of birth. Format: MM/DD/YYYY Example: 05/23/1935 |
Previous Name |
A previous name that the member may have used. This could be the person's former married name if they are divorced or their single name if they are now married. |
Residential Address | The entity's home address or where an entity lives. |
Mailing Address | The address where mail is received. |
Phone | The phone number for the member. |
County | The name of the county associated with the residential address of the member. |
Enrolled Member - Alternative Identifiers Fields | |
Type |
A code to identify type of alternate identifier. Examples: SSN, ME (Medicaid), BC (Basic Care) |
Alternate ID |
An additional unique identifier for a member.
|
Line of Business |
The unique code that identifies the line of business, a high-level payer, or funding source such as Medicaid. |
Un-enrolled Member Fields | |
Case Record Number |
ND MMIS generated number assigned when a case record is initially created. It cannot be modified. |
Entity Type |
The type of organization, institution, or individual. Example: Un-enrolled Member |
CM Entity ID |
Unique identifier for the contact management entity to identify the un-enrolled entities. |
SSN |
Social Security Number. A nine-digit number assigned by the Federal government, usually assigned at the time of birth and used for tax purposes. Format: NNN-NN-NNNN or NNNNNNNNN Example: 123-45-6789 Note: This field cannot contain all zeros. |
Name | The member's current name. |
The e-mail address of the person. Example: ijones@myemail.com |
|
Gender |
The gender of a person, usually male or female. In some cases, the gender may also be unknown. |
Date of Birth |
The date the person was born; the person's date of birth. Format: MM/DD/YYYY Example: 05/23/1935 |
Phone | The phone number for the un-enrolled member. |
County | The name of the county associated with the residential address of the un-enrolled member. |
TPL Carrier Fields | |
Case Record Number |
ND MMIS generated number assigned when a case record is initially created. It cannot be modified. |
Entity Type |
The type of organization, institution, or individual. Example: TPL Carrier |
TPL Carrier ID |
The unique identifier of the organization responsible for the third-party coverage. |
Carrier Name |
The descriptive name of the organization responsible for the third-party coverage. |
TPL Policy Holder Fields | |
Case Record Number |
ND MMIS generated number assigned when a case record is initially created. It cannot be modified. |
Entity Type |
The type of organization, institution, or individual. Example: TPL Policyholder |
TPL Policyholder ID | The TPL policyholder's identification. |
Policyholder Name | The policy holder's name. |
TPL Policy Number | The policy number. |
Trading Partner Fields | |
Case Record Number |
ND MMIS generated number assigned when a case record is initially created. It cannot be modified. |
Entity Type |
The type of organization, institution, or individual. Example: Trading Partner |
Trading Partner ID | The trading partner's identification number. |
Status | The status of the trading partner's enrollment application. |
Name | The provider's name |
Classification |
The kind of trading partner. Automatically displayed. |
Contact | The contact person for the trading partner. |
Other or Attorney Fields | |
Entity Type |
The type of organization, institution, or individual. Examples: Provider, Member, Attorney, TPL Carrier |
CM Entity ID |
Unique identifier for the contact management entity to identify the un-enrolled entities. |
Name |
The name of the organization, institution, or individual. |
Phone | The phone number for the entity's office. |
Professional ID Number | The unique identifier associated with the entity for professional purposes. |
County | The name of the county associated with the address of the entity that initiates the correspondence. |
Field | Description |
---|---|
Step |
The current step in the processing of the case. |
Created By |
User who initially created the case record. |
Assigned To |
The user to whom the case record is currently assigned. |
Created Date |
Date the case record was created. This date is automatically assigned by ND MMIS when the user initially saves the case record. Format: MM/DD/YYYY |
Days Opened or Days to Close |
The number of days the case has been open, or the number of days it took to close the case, depending on the case's status. |
Reporting Unit |
The reporting unit of the user who is currently assigned the case record (the Assigned To user). Examples: State, Medical Services |
Business Unit |
The business unit of the user who is currently assigned the case record. Example: Level of Care Determination |
Work Unit |
The work unit of the user who is currently assigned the case. Examples:Customer Service, Support Staff |
Case Type |
Indicates what a case is about. Examples: Provider Appeal, Level of Care Determination |
Status |
The stage of the case. The status changes depending on the case type and where it is in the resolution process. |
Priority |
The level of importance of the inquiry or request. Examples: High, Medium, or Low |
Case Title | The title of the case. |
Line of Business |
The unique code that identifies the line of business, a high-level payer, or funding source such as Medicaid. |
Source | The original source for the case. |
Resolution | The final outcome of the case. |
Supervisor Approval Required |
Indicates if a supervisor is required to review and approve a case before it is closed. |
If you select the Provider Appeal Case Type, to display the Provider Add Appeal page and add an appeal, click Continue. You are directed to the Provider Appeals Page If you select the Member Appeal Case Type, to display the Member Add Appeal page and add an appeal, click Continue. You are directed to theMember Add Appeal Page. |
|
This section of detail fields changes based upon the Case Type you select. |
|
These fields display for Level of Care Determination case types, in addition to the fields that display for all case types. | |
Level of Care Determination Status |
Indicates whether the level of care determination case is new, under review, or a reapplication. Examples: New, Reapplication |
Start Date | The date of the contact filled out the case. |
End Date | The completion date of the case. |
Level of Care Effective Date |
The date that the level of care determination is active. Format: MM/DD/YYYY Default: Start Date plus 90 days |
Long Term Care (LTC) Level of Care Determination Review Fields
These additional fields are displayed if the case type indicates LTC Level of Care Determination |
|
Review Required |
Indicator specifying that a review is required. |
Amended Start Date |
The date the review starts. Format: MM/DD/YYYY |
Amended End Date |
The date the review is scheduled to end. Format: MM/DD/YYYY |
Last Update Date |
The date information was last received for review. Format: MM/DD/YYYY |
Level of Need Fields
These fields provide information on the decisions reached for all types of Level of Care Determination cases. |
|
Waiver Date |
The date the decision was made on the case. Format: MM/DD/YYYY |
Level of Need |
The level of care needed to support the decision. |
Additional Case Details Fields Custom fields to record additional case details may be displayed based on the case type. The following are some typical custom fields. |
|
Sent to Regional Office |
Indicator specifying whether the case has been sent to the regional office. |
File to Supervisor Date |
The date that the case file was sent to the supervisor. Format: MM/DD/YYYY |
Findings |
Indicates the status of the case findings. Example: Pending |
Other Insurance Indicator: |
Indicator specifying whether other insurance is involved in the case. |
Project Location: |
The location site where this case records are located. |
Type of Action: |
The current state or action taken in regards to the case. |
Additional Case Entities Fields To add an additional entity to the case, use the Inquiring About Case Entity Search page. To delete an entity, in the Additional Case Entity table, click the appropriate row and, on the Additional Case Entities action bar, click Delete. None of these fields can be edited. |
|
Entity ID |
The unique identifier used for an entity in ND MMIS about which healthcare information needs to be maintained. Note: Entity ID depends on Entity Type. For example, a Provider Entity Type requires a Provider ID. |
Name |
The name of the organization, institution, or individual. |
Entity Type |
The type of organization, institution, or individual. Examples: Provider, Member, Attorney, TPL Carrier |
Field | Description |
---|---|
To add an association to a record (such as a service authorization or a claim), click Add Associated Records. To edit, in the Associated Records table, click the appropriate row. To delete a record association, on the Associated Records action bar, click Delete. | |
Record Type |
The kind of record associated. Examples: SA, TCN, TPL Recovery Case, External Claim, Miscellaneous |
ID |
The unique identifier for the record. When editing, links to the appropriate page containing specific details for this record. For example, if you click a claim transaction control number, the Claims Inquiry page is displayed. |
Type | The specific kind of record. Displayed only in the table. |
Member | The name of the member associated with the record. Displayed only in the table. |
Provider | The name of the provider associated with the record. Displayed only in the table. |
Status |
The status of the record. Examples: Pending, Open, Paid |
Begin Date |
The beginning date associated with the record. Displayed only in the table. Examples: The first date of service, the date of the transaction, the start date of the recovery case |
End Date | The ending date associated with the record. Displayed only in the table. |
Field Name | Description |
---|---|
To add a routing assignment, click Add Routing Assignment. To edit, in the Routing table, click the appropriate row. |
|
Date | The date a record was routed. Automatically completed with the current system date. |
Routed By | The name of the user who assigns a record to another user or work unit. |
Routed To | The name of the user or workgroup to whom a record is routed. |
Watchlist or |
A check mark indicates the record displays in your watchlist for monitoring. |
Created By | The name of the user that added the record. Automatically displayed. |
Assigned To | The name of the user or work unit to whom the record is currently assigned. Automatically displayed. |
Reporting Unit | The name of the reporting unit of the user or work unit who is currently assigned the record. Automatically displayed. |
Show |
The filter associated with the routing. Examples: Business Unit, Work Units, Users. |
Business Unit | The business unit for this record. When adding, this field is displayed only if showing business units. Cannot be changed after routing is saved the first time. |
Work Unit Name | The name of the work unit for this record. When adding, this field is displayed only if showing work units. Cannot be changed after routing is saved the first time. |
Assign This Record To | The user or user group to whom a record is routed. When adding, this list changes according to the filter selected in the Show field. Cannot be changed after routing is saved the first time. |
User Work Unit Name | The name of the work unit of the user to whom the record is routed. When adding, this field is displayed only if showing users. Cannot be changed after routing is saved the first time. |
Field | Description |
---|---|
All previously created case and correspondence records created within a pre-determined time period for the entity ID are displayed in the Existing Case Records and Existing Correspondence Records tables. To manually search for other records, in either the Case or Correspondence section, click Search. The fields used to search are described in the Case Record Search and Correspondence Record Search table later in this topic. The record that matches your search filters is displayed in the search results table. In the search results table, click Link to add an association for that record to the current case. Other cases and CRs already associated with this case are displayed in the Case Records Associated with this Case and Correspondence Records Associated with this Case tables. To view details or detach a record, click the appropriate row. |
|
Correspondence Fields | |
Select All Rows | A check box which, if selected, inserts check marks in the Link field for all rows in the table. This associates all existing case records and CRs with the current case record. |
Deselect All Rows | A checkbox which, if selected, removes check marks from the Link field in all rows of the table. This disassociates all existing case records and CRs from the current case record. |
ID | Correspondence record number |
Create Date | The date the correspondence record (CR) was opened or created. |
Category | A CR's category based on call reason. |
Subject | A second call reason that is based on the category selected. |
Contact | A representative of the entity for which the CR is created. |
Link |
Indicates the CR is linked to the current case record. |
Case Fields |
|
Select All Rows | When selected inserts check marks in the Link field for all rows in the table. This associates all existing case records and CRs with the current case record. |
Deselect All Rows | When selected removes check marks from the Link field in all rows of the table. This disassociates all existing case records and CRs from the current case record. |
ID | Case record number. |
Created Date | The date the case record was created. |
Status |
Status of the case record. Examples: Open, Closed, Denied, Pending, Withdrawn, etc. |
Link |
Indicates the case record is linked to the current case record. |
Field | Description |
---|---|
To edit, in the Attachments table, click the appropriate row. To remove the association to an attachment, on the Attachment action bar, click Detach. The document remains in the Attachment table, but the hyperlink is removed. |
|
Date Added | The date an attachment was added to a record such as a case record, CR, or third-party liability record. This field is only displayed when editing and cannot be changed. |
Added By | The user that added the attachment. This field is only displayed when editing and cannot be changed. |
File Name or File |
The name of the attached document. When adding, it is automatically displayed after the document is selected. |
Description | An explanation of what the attachment is about. If the record to which the document is attached is closed, this field cannot be changed. |
Attached | When editing, indicates if the document is currently attached to the record. |
Field | Description |
---|---|
To edit, in the Letters & Responses table, click the appropriate row. To create a letter, click Create Letter. To view the letter request, click View Letter Request. To view an image of the letter in the EDMS, click View Letter. Note: The View Letter option is only available if the letter request status is Generated. |
|
Created Date | The date the letter request was created. |
Template |
The name of the template used to create a letter or response. |
Date Sent | The date the response or letter was processed (imaged in EDMS and sent to the print vendor and letter recipients). |
Days Due Back | The number of days in which the recipient is expected to respond to the letter. This field is also used to calculate the due date. |
Due Date | The date the recipient is expected to respond to the letter. The due date is based on the value in the Days Due Back field. |
Date Received | The date requested information was received from the letter recipient. |
Notify Via Alert | The user that receives an alert about the letter or response. |
Alert Based On | An action that causes the alert to be sent. For example, an alert can be dependent on the due date, created date, or date sent. |
Recipient Name | The recipient's name. |
Letter Request ID | The identification number of the letter request. |
Send Alert # of Days | The number of days before or after an event to send an alert. This field is based on the value in the Alert Based On field. For example, if the alert is based on the created date, an alert sent a number of days before or after the created date. |
Status |
The current status of the letter. Examples: New, In Review, Approved, Generated, Rejected, Deleted |
Supv Appr. Req |
Indicates that a supervisor needs to review and approve the letter request. Note: This field is automatically selected on the Letter Generation Request page if the pre-defined template has Supervisor Approval Required selected on the Maintain Templates page. |
Explanation | An explanation of why the letter request was created. You can enter up to 255 characters. |
Field | Description |
---|---|
To add a new case event, click Add Case Events. To edit, click the appropriate row in table. To delete a case event, in the Case Event action bar, click Delete. To add a letter or response, click Create Letter. |
|
Created Date | The date the case event was created. This field cannot be changed after it is saved the first time. |
Type |
The type or kind of case event Examples: Appointment, Reminder, etc. |
Description | Description of the case event or what the case event is about. |
Event Date | Date when the case event is expected to be completed. |
Time | The time when the case event is expected to be completed. |
Notify Via Alert | The user to be notified by alert when a case event is added to the user's inbox. |
Alert Based On | An action that triggers the alert to be sent. For example, an alert can be dependent on a due date, open date, etc. |
Send Alert # of Days Before/After | The number of days the automatic alert should be sent before or after, as indicated, the action in the Alert Based On field. |
Status | Status of the case event, for example, pending, canceled, etc. |
Disposition Date | The date of the disposition. |
Template | The name of the template used to create a letter or response. |
Diagnosis #1 and #2 |
Diagnosis associated with this case. This field is available only if SRT Appt event type. |
Exam Test 1 and 2 |
Exam test associated with this case. This field is available only if SRT Appt event type. |
Provider/ Hospital | All enrolled and un-enrolled providers associated with this case. |
Field Name | Description |
---|---|
To add a new alert, click Add Alert. To edit, in the Alerts table, click the appropriate row. | |
Due Date | The date when a user should respond to an alert. The user changes the status to Completed. |
Alert Type | The kind of alert, such as an appointment, reminder, or approval. |
Description | Explanation of what the alert is about. |
Notify Via Alert | The name of the user to receive the alert. |
Status |
The status of an alert, such as Open or Closed. |
Field | Description |
---|---|
The case steps are predefined based on the type of case. To add a new case step, click Add Case Steps. To edit, click the appropriate row in the table. |
|
Order | Pre-defined order of how the case steps are to be completed. |
Description | Description of the case step. |
Route To | The user to whom the case record is routed. |
Status | Status of the case step. |
Date Started | Date when the case step started. Automatically generated. |
Expected Days to Complete | The number of days required to complete the case step. |
Completion Based On | An event that determines the completion of a case step. |
Expected Completion Date | The required date to complete the case step. Automatically calculated if Expected Days to Complete field is completed. |
Completion Date | The actual date the case step was completed. Automatically generated. |
Notify Via Alert | The name of the user to receive the alert. |
Alert Based On | An action that triggers the alert to be sent. For example, an alert can be dependent on a due date, open date, etc. |
Send Alert # of Days Before/After | The number of days the automatic alert should be sent before or after, as indicated, the action in the Alert Based On field. |
Template | The name of the template used to create a letter or response. |
Field | Description |
---|---|
If you came to this page from the Notes link on a record, to add a new note, on the Notes action bar, click Add New Note. Existing notes are listed in the Notes History table. To view the complete text of a note, click the appropriate row. To print notes, in the Notes History table, select the notes to be printed, and then on the Notes action bar, click Print Selected. |
|
Current Note |
The complete text of either the most recent note created or the note selected in the Notes History table. |
Notes History Fields To view a previous note, click the appropriate row. To print all notes, in the table header, click the check box. To select a note to be printed, on the appropriate row, click the check box. |
|
Print Selection (unlabeled) |
Check box that indicates if the note is to be printed. If the check box in the Notes History table header is selected, all notes are selected. |
Date/Time | Date and time when the note was created. |
User ID | The ID of the person who created the note. |
Note |
Note text. When you select a note to view, the note text in the highlighted row is displayed in the Current Note field. |
Component |
The business name associated with the note. Displayed in the Notes History table only after searching for notes from the Notes option on the Contact Management menu. |
Usage Type Code |
The business purpose for which the note was written. The codes displayed are specific to the job responsibilities of the user entering the note. |
Characters Remaining |
Counter that indicates how many characters you have available when entering text. It decreases by one for each character entered and increases when a character is deleted. This field is displayed when adding a note. |
Filters Fields To display filter fields, on the Notes action bar, click Filter. To activate the filter, on the Notes action bar, click Apply Filter. To clear all filter information and complete filter options again, click Reset. |
|
Begin Date |
Beginning date range for filtering notes. Format: MM/DD/YYYY |
End Date |
End date range for filtering notes. Format: MM/DD/YYYY |
User ID | The ID of the user who entered the note. |
Usage Type Code |
The business purpose for which the note was written. The codes displayed are specific to the job responsibilities of the user entering the note. The Notes History table is filtered to show only notes with the usage type selected. |
Tip: You cannot search for a note while you are in a case. However, you can add a new note while you are working on a case record. Depending on your security permissions, you may be allowed to add notes to a closed case record, as well.
Version as of 5/16/14.
Copyright © 2017 Conduent, Inc. All rights reserved. Conduent and Conduent Agile Star are trademarks of Conduent, Inc. and/or its subsidiaries in the United States and/or other countries.