Articles in this section

Trans Care BC Corrupt Form Bug

  • Updated

Problem

There is a bug that causes a .NET Framework error to appear when Trans Care BC (TCB) users try to load their form filters from Work Centre > Forms. 

This happens when there is a "corrupt" TCB-USR form. When there is a "corrupt" TCB-USR form and the user goes to load the TCBC -USR form filter, the .NET Framework error message appears and prevents the system from loading the filter.

For more information on the bug, refer to EMR-3021.

Note: This bug has been fixed in version 9.0.

 

Workaround

The workaround is to locate the "corrupt" form, and then ask the user to re-create the form and delete the old one. Note that you can only find the "corrupt" form if it was modified prior to today's date. If it was modified today, you will have to wait until the next business day to locate the form as we need to wait for EMR Support to refresh with today's data.

1. Narrow Down Referral Status of "Corrupt" Form

  1. In EMR Support, log into TCB as a Sys-Admin user
  2. Go to Work Centre > Forms
  3. Change the view filter to TCBC - USR and confirm that you get the .NET Framework error
    • If you do not get the error, it indicates there is no "corrupt" form in the Support environment and you may need to troubleshoot the next business day after the environment refreshes
  4. Click OK to close the error message and exit out of any subsequent error windows (you should return to the Work Centre > Forms window)
  5. Click through each of the other TCBC - USR view filters until you get the .NET Framework error again
  6. Once you get the .NET Framework error, note which filter caused the error. Close out of any error message windows so that you return back to the Work Centre > Forms window
  7. Click Edit... for the view filter and go to the More Filters tab
  8. Expand the Form Data nodule and scroll down to find the TCB - referral status nodule (should be marked by a green square)
  9. Expand the TCB - referral status nodule. In the Value column, determine which referral status is causing the error by removing all but one of the statuses and clicking Apply (note that each status is separated by a comma)
    • For example, if the referral statuses under Value are: "Waiting with Surgeon, Sx Booking form submitted"; then remove "Sx Booking form submitted" and click Apply
    • If the .NET Framework error appears, then "Waiting with Surgeon" is the referral status that is causing the error. If the error does not appear, change the referral status to another value (e.g. Sx Booking form submitted) and click Apply again
  10. Once you've determined which referral status is causing the problem, note it down and close any error windows that appear

2. Run Query

  1. Go to Report > Find Objects and click on the Register Form button
  2. From the left-hand panel, select "TCB-USR", click on Add button, and click Apply
  3. Click OK to close the window
  4. In the Find Objects window, click on the Import query from desk file icon and import the "TCB-USR_query.ihq" located here: G:\PCAC_EMR\01 - PCCEMR\Work Items\00 - All Items (JIRA)\EMR-3021 TCB-USR and TBC-SRA dotNET Framework Bug\Analysis
  5. In the Where section, change:
    • The Modified On value to the date the error first appeared
    • The Value to the referral status that you determined is causing the problem (e.g. Waiting with Surgeon)
  6. Run the query 
    • You will get a list of clients that had TCB-USR forms modified on the date the error occurred - one of these client's have a form in their Medical Record that is causing the error
    • Keep this window open 

3. Locate the "Corrupt" Form

  1. With the find objects query results open in the background, go back to Work Centre > Forms and reload the filter that was causing the .NET Framework error
  2. Click Edit... for the view filter and go to the More Filters tab
  3. Expand the Patient nodule, scroll down to find the Last Name nodule
  4. Tick the Last Name nodule box and change the Condition to "is equal to" 
  5. In the Value column, enter one of the client's last names from the query and click Apply
  6. If the .NET Framework error does not appear, change the last name value to another client's from the query and click Apply again
  7. Once the .NET Framework error appears, you have located the client with the "corrupt" form (hurray)!
  8. Provide the requestor with the client's PID/FileNum. The requestor will then re-create the TCB-USR form for the client and delete the "corrupt" one which will fix the error

NOTE: If you're having troubles locating the corrupt form with the above steps, reach out to a developer to assist you.