Report Description | ||||
This is a report that provides timeliness data based on the TADT documents but produces a report that’s more human-readable, with more information and limited by program. | ||||
Report Name | Menu Path | Client Based | Report RDL Name | |
CalMHSA Timely Access Document Report | CalMHSA Timely Access Document Report (My Office) | No | RDLCalMHSATimelyAccessDocReport | |
Parameters | Data Type | Hidden | Comments | |
StartDate | Date | N | A date filter that allows users to specify the beginning of the data range of the Documents’ “Date of First Contact to Request Services” dates for the report to use | |
EndDate | Date | N | A date filter that allows users to specify the end of the data range of the Documents’ “Date of First Contact to Request Services” dates for the report to use | |
ReportTypes | Multiple Select | N | A multiple select that allows users to specify which type of document the report pull data from. The 4 values are hard code in this dropdown. | |
Programs | Multiple Select | N | A multiple select that allows users to specify which program association the report will use when pulling the timeliness document data. | |
Clinical Data Access GroupId | Integer | Y | Passed by system at report run time based on currently logged in Staff | |
ExecutedByStaffId | Integer | Y | Passed by system at report run time based on currently logged in Staff | |
DataSets | Form(s) | CDAG enforced | Comments | |
Psych | MH Non-Psychiatric SMHS Timeliness Record (Client) | Y | This dataset calls for a stored procedure labeled “csp_RDLCalMHSATimelinessReportPsychiatric”. In the stored procedure, it pulls in the following parameters:
The stored procedure is designed to return data base on the following criterias:
Things to note with the stored procedure:
| |
NonPsych | MH Psychiatric SMHS Timeliness Record (Client) | Y | This dataset calls for a stored procedure labeled “csp_RDLCalMHSATimelinessReportNonPsychiatric”. In the stored procedure, it pulls in the following parameters: · StartDate · EndDate · Programs · ExecutedByStaffId · ClinicalDataAccessGroupId The stored procedure is designed to return data base on the following criterias: · Only pull the MH Non-Psychiatric SMHS timeliness document data where the associated client have a non-soft deleted plan record, the plan’s InsuredId is not blank, and the plan record’s CoveragePlanId is equal to 2 · Only pull MH Non-Psychiatric SMHS timeliness document data where the associated program is within the selected Programs from the Program parameters · Only pull the MH Non-Psychiatric SMHS timeliness document data where the document’s status is not equal to 26 (cancel status) · Only pull the MH Non-Psychiatric SMHS timeliness document data where the timeliness’s Document record and CustomDocumentCalMHSAMHNonPsychiatricTADTrecord is not soft deleted. · Only pull the MH Non-Psychiatric SMHS timeliness document data where the Staff member who is running the report have access to the client of that the MH Non-Psychiatric SMHS timeliness document data was created for. · Only pull the MH Non-Psychiatric SMHS timeliness document data where the Date First Contact to Request Services date is within the date range setup by the Start and End date parameters. Things to note with the stored procedure: · The “SignedDate” data that is returned is from the MH Non-Psychiatric SMHS timeliness document’s most current version signed date · Regarding the “IsUrgent” data that is returned, it will only show ‘Yes’ as long the IsUrgent column from the CustomDocumentCalMHSAMHNonPsychiatricTADTrecord is equal to ‘Y’. If the value is any other value (i.e. ‘N’, NULL, Blank, etc…) then it would show ‘No’ · Regarding the “HoursElapsed” data that is returned, as long the IsUrgent column from the CustomDocumentCalMHSAMHNonPsychiatricTADTrecord is equal to ‘Y’ the store procedure will display the hour differences from the DateFirstContactToReqServices and FirstServiceApptOfferedDate columns of the CustomDocumentCalMHSAMHNonPsychiatricTADTrecord. If the IsUrgent column is not equal ‘Y’, then the store procedure will display NULL · Regarding the “PriorAuthorizationRequired” data that is returned, if the IsUrgent and PriorAuthorizationRequired column from the CustomDocumentCalMHSAMHNonPsychiatricTADTrecord is both equal to ‘Y’ then the store procedure will display ‘Yes’. If the PriorAuthorizationRequired column from the CustomDocumentCalMHSAMHNonPsychiatricTADTrecord is NULL or not equal to ‘Y’ then the store procedure will display ‘No’. · Regarding the “WaitList” data that is returned, the store procedure will display ‘Yes’ as long the ReasonForDelay column of the CustomDocumentCalMHSAMHNonPsychiatricTADTrecord have value that is not blank or NULL. If the value is blank or NULL, then display ‘No’ · Regarding the “FollowUpAppt” data that is returned, the store procedure will display ‘Yes’ as long the IsFollowupApptNotOffered column of the CustomDocumentCalMHSAMHNonPsychiatricTADTrecord have value that is blank or NULL. If the value is equal to ‘Y’, then display ‘No’ · Regarding the “FollowupApptWaitTimeExt” data that is returned, the store procedure will display ‘Yes’ as long the DocumentationOfWaitTimeExt column of the CustomDocumentCalMHSAMHNonPsychiatricTADTrecord have value that is not blank or NULL. If the value is blank or NULL, then display ‘No’ · Regarding the “CIN” data that is returned, the store procedure will display the MAX (biggest) InsuredId columns of all non-soft deleted, CoveragePlanId = 2 ClientCoveragePlans records that are associated to the client that the CustomDocumentCalMHSAMHNonPsychiatricTADTrecord is associated to.
| |
Opioid | DMC-ODS Opiod Timeliness Record (Client) | Y | This dataset calls for a stored procedure labeled “csp_RDLCalMHSATimelinessReportOpioid”. In the stored procedure, it pulls in the following parameters: · StartDate · EndDate · Programs · ExecutedByStaffId · ClinicalDataAccessGroupId The stored procedure is designed to return data base on the following criterias: · Only pull the DMC-ODS Opioid timeliness document data where the associated client have a non-soft deleted plan record, the plan’s InsuredId is not blank, and the plan record’s CoveragePlanId is equal to 2 · Only pull DMC-ODS Opioid timeliness document data where the associated program is within the selected Programs from the Program parameters · Only pull the DMC-ODS Opioid timeliness document data where the document’s status is not equal to 26 (cancel status) · Only pull the DMC-ODS Opioid timeliness document data where the timeliness’s Document record and CustomDocumentCalMHSADMCODSOpioidTADT record is not soft deleted. · Only pull the DMC-ODS Opioid timeliness document data where the Staff member who is running the report have access to the client of that the DMC-ODS Opioid timeliness document data was created for. · Only pull the DMC-ODS Opioid timeliness document data where the Date First Contact to Request Services date is within the date range setup by the Start and End date parameters. Things to note with the stored procedure: · The “SignedDate” data that is returned is from the DMC-ODS Opioid timeliness document’s most current version signed date · Regarding the “IsUrgent” data that is returned, it will only show ‘Yes’ as long the IsUrgent column from the CustomDocumentCalMHSADMCODSOpioidTADT record is equal to ‘Y’. If the value is any other value (i.e. ‘N’, NULL, Blank, etc…) then it would show ‘No’ · Regarding the “HoursElapsed” data that is returned, as long the IsUrgent column from the CustomDocumentCalMHSADMCODSOpioidTADT record is equal to ‘Y’ the store procedure will display the hour differences from the DateFirstContactToReqServices and FirstServiceApptOfferedDate columns of the CustomDocumentCalMHSADMCODSOpioidTADT record. If the IsUrgent column is not equal ‘Y’, then the store procedure will display NULL · Regarding the “PriorAuthorizationRequired” data that is returned, if the IsUrgent and PriorAuthorizationRequired column from the CustomDocumentCalMHSADMCODSOpioidTADT record is both equal to ‘Y’ then the store procedure will display ‘Yes’. If the PriorAuthorizationRequired column from the CustomDocumentCalMHSADMCODSOpioidTADT record is NULL or not equal to ‘Y’ then the store procedure will display ‘No’. · Regarding the “WaitList” data that is returned, the store procedure will display ‘Yes’ as long the ReasonForDelay column of the CustomDocumentCalMHSADMCODSOpioidTADT record have value that is not blank or NULL. If the value is blank or NULL, then display ‘No’ · Regarding the “FollowUpAppt” data that is returned, the store procedure will display ‘Yes’ as long the IsFollowupApptNotOffered column of the CustomDocumentCalMHSADMCODSOpioidTADT record have value that is blank or NULL. If the value is equal to ‘Y’, then display ‘No’ · Regarding the “FollowupApptWaitTimeExt” data that is returned, the store procedure will display ‘Yes’ as long the DocumentationOfWaitTimeExt column of the CustomDocumentCalMHSADMCODSOpioidTADT record have value that is not blank or NULL. If the value is blank or NULL, then display ‘No’ · Regarding the “CIN” data that is returned, the store procedure will display the MAX (biggest) InsuredId columns of all non-soft deleted, CoveragePlanId = 2 ClientCoveragePlans records that are associated to the client that the CustomDocumentCalMHSADMCODSOpioidTADT record is associated to.
| |
Outpatient | DMC-ODS Outpatient Timeliness Record (Client) | Y | This dataset calls for a stored procedure labeled “csp_RDLCalMHSATimelinessReportOutpatient”. In the stored procedure, it pulls in the following parameters: · StartDate · EndDate · Programs · ExecutedByStaffId · ClinicalDataAccessGroupId The stored procedure is designed to return data base on the following criterias: · Only pull the DMC-ODS Outpatient timeliness document data where the associated client have a non-soft deleted plan record, the plan’s InsuredId is not blank, and the plan record’s CoveragePlanId is equal to 2 · Only pull DMC-ODS Outpatient timeliness document data where the associated program is within the selected Programs from the Program parameters · Only pull the DMC-ODS Outpatient timeliness document data where the document’s status is not equal to 26 (cancel status) · Only pull the DMC-ODS Outpatient timeliness document data where the timeliness’s Document record and CustomDocumentCalMHSADMCODSOutpatientTADT record is not soft deleted. · Only pull the DMC-ODS Outpatient timeliness document data where the Staff member who is running the report have access to the client of that the DMC-ODS Outpatient timeliness document data was created for. · Only pull the DMC-ODS Outpatient timeliness document data where the Date First Contact to Request Services date is within the date range setup by the Start and End date parameters. Things to note with the stored procedure: · The “SignedDate” data that is returned is from the DMC-ODS Outpatient timeliness document’s most current version signed date · Regarding the “IsUrgent” data that is returned, it will only show ‘Yes’ as long the IsUrgent column from the CustomDocumentCalMHSADMCODSOutpatientTADT record is equal to ‘Y’. If the value is any other value (i.e. ‘N’, NULL, Blank, etc…) then it would show ‘No’ · Regarding the “HoursElapsed” data that is returned, as long the IsUrgent column from the CustomDocumentCalMHSADMCODSOutpatientTADT record is equal to ‘Y’ the store procedure will display the hour differences from the DateFirstContactToReqServices and FirstServiceApptOfferedDate columns of the CustomDocumentCalMHSADMCODSOutpatientTADT record. If the IsUrgent column is not equal ‘Y’, then the store procedure will display NULL · Regarding the “PriorAuthorizationRequired” data that is returned, if the IsUrgent and PriorAuthorizationRequired column from the CustomDocumentCalMHSADMCODSOutpatientTADT record is both equal to ‘Y’ then the store procedure will display ‘Yes’. If the PriorAuthorizationRequired column from the CustomDocumentCalMHSADMCODSOutpatientTADT record is NULL or not equal to ‘Y’ then the store procedure will display ‘No’. · Regarding the “WaitList” data that is returned, the store procedure will display ‘Yes’ as long the ReasonForDelay column of the CustomDocumentCalMHSADMCODSOutpatientTADT record have value that is not blank or NULL. If the value is blank or NULL, then display ‘No’ · Regarding the “FollowUpAppt” data that is returned, the store procedure will display ‘Yes’ as long the IsFollowupApptNotOffered column of the CustomDocumentCalMHSADMCODSOutpatientTADT record have value that is blank or NULL. If the value is equal to ‘Y’, then display ‘No’ · Regarding the “FollowupApptWaitTimeExt” data that is returned, the store procedure will display ‘Yes’ as long the DocumentationOfWaitTimeExt column of the CustomDocumentCalMHSADMCODSOutpatientTADT record have value that is not blank or NULL. If the value is blank or NULL, then display ‘No’ · Regarding the “CIN” data that is returned, the store procedure will display the MAX (biggest) InsuredId columns of all non-soft deleted, CoveragePlanId = 2 ClientCoveragePlans records that are associated to the client that the CustomDocumentCalMHSADMCODSOutpatientTADT record is associated to. | |
Programs | CDAG Details | Y | This dataset calls for a stored procedure labeled “ssp_SCGetCDAGPrograms”. In the stored procedure, it pulls in the following parameters: · Clientid · CDAGid · LoggedInStaffid The stored procedure is designed to return either the following based on if the clientid is equal to 0 or not: · All active, non-soft deleted, and associated programs records that the clientid parameter have ClientProgram records in · Return all active, non-soft deleted programs records that is associated to the CDAGid parameter. | |
|
|
| Default User Roles | |
|
|
|
| |
