PL SamePHIN Site Diff chart: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m Text replacement - "{{DT" to "{{TT"
No edit summary
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Data Integrity Check
{{DISPLAYTITLE:PL_SamePHIN_Site_Diff_chart}}{{Data Integrity Check
|DIC_summary=Another record exists for this [[Service/Location]] with the same [[PHIN ]] and a different [[Chart number]].
|DIC_summary=Another record exists for this site with the same [[PHIN]] and a different [[Chart number]].
|DIC_related_concepts=PHIN field; Service/Location field; Chart number
|DIC_related_concepts=PHIN field; Chart number
|DIC_firmness=hard check
|DIC_firmness=soft check
|DIC_timing=always
|DIC_coding=query PL_SamePHIN_Site_Diff_chart
|DIC_coding=query PL_SamePHIN_Site_Diff_chart
|DIC_status=implemented
|DIC_status=implemented
|DIC_LProblem=No
|DIC_app=Centralized data front end.accdb
|DIC_app=Centralized data front end.accdb
|DIC_backlogged=No
}}
}}
This query compares the chart numbers and PHINs of profiles started in the last 30 days to any charts in our database.


{{TT | _dev_CFE 1
The query takes several minutes to run. Tina reviewed it 2021-07-15 and could not see further ways to streamline it.
this query has reached the 2GB limit, must see if I can lean it out or otherwise reduce the size }}
 
== Log ==
* 2026-05-07 Realized during troubleshooting for [[PL_SameCHART_Site_Diff_PHIN]] that there is a more efficient way to do these queries so updated this one to work on same principle. Set up with .._new and .._old copies for now for testing. In this case the query actually found additional problems so the old one must not be working right...
* 2022-04-13 - didn't have an explicit D_ID field so would not have worked with PatientList; wonder if it's been used at all
* 2021-07-15 - updated to overcome 2GB limit, it now only compares the required data components, and the second datset is only the last 30 days


== Related articles ==
== Related articles ==

Latest revision as of 01:22, 8 May 2026

Data Integrity Checks
Summary: Another record exists for this site with the same PHIN and a different Chart number.
Related: PHIN field, Chart number
Firmness: soft check
Timing: always
App: Centralized data front end.accdb
Coding: query PL_SamePHIN_Site_Diff_chart
Uses L Problem table: No
Status: implemented
Implementation Date: not entered
Backlogged: No
  • Cargo


  • SMW


  • Categories:  
  • form:

This query compares the chart numbers and PHINs of profiles started in the last 30 days to any charts in our database.

The query takes several minutes to run. Tina reviewed it 2021-07-15 and could not see further ways to streamline it.

Log

  • 2026-05-07 Realized during troubleshooting for PL_SameCHART_Site_Diff_PHIN that there is a more efficient way to do these queries so updated this one to work on same principle. Set up with .._new and .._old copies for now for testing. In this case the query actually found additional problems so the old one must not be working right...
  • 2022-04-13 - didn't have an explicit D_ID field so would not have worked with PatientList; wonder if it's been used at all
  • 2021-07-15 - updated to overcome 2GB limit, it now only compares the required data components, and the second datset is only the last 30 days
Related articles: