Difference between revisions of "Patient Record (PAS) Lookup"
| Line 2: | Line 2: | ||
Your PTS application is likely to be connecting to a patient record database of some sort. This is the facility that looks up the patient details on the booking in screen. | Your PTS application is likely to be connecting to a patient record database of some sort. This is the facility that looks up the patient details on the booking in screen. | ||
By far the most popular choice is to connect PTS to the JAC/WellSky/CMM dispensing database. Our technician will have created this link for you during installation if the option was available to them. | By far the most popular choice is to connect PTS to the JAC/WellSky/CMM (hereafter "CMM") dispensing database. Our technician will have created this link for you during installation if the option was available to them. | ||
When the CMM database (or other patient record database) is moved (e.g. as part of an upgrade and server decommission) the link between PTS and the patient record database will be broken. | When the CMM database (or other patient record database) is moved or modified (e.g. as part of an upgrade and server decommission) the link between PTS and the patient record database will be broken. | ||
It's worth pointing out that PTS remains usable even if the patient lookup goes down - users can just enter patient details automatically. | |||
==Amending the patient record connection information== | ==Amending the patient record connection information== | ||
Starting in 2022 new patient record implementations are implemented | Starting in 2022 new patient record implementations are implemented with an ODBC data source called <strong>"PTSPAS"</strong> on the PTS application server. It is best to simply amend this data source to point it to the new location. If the data source drivers are outdated (e.g. requires the new IRIS drivers) or are otherwise invalid (e.g. moving from one patient record ecosystem to another) it's easiest to completely remove the PTSPAS datasource and create a new one with the same name. | ||
Assuming the data structure of the patient record database remains the same, the patient lookup should now be working again in your PTS application (note there hasn't been a "breaking change" to the CMM patient record data structure since 2014). | |||
==When PTSPAS data source is not yet in use, or there is another complication== | |||
You should contact TMSi to arrange a date and time for one of our support technicians to remote access your PTS server and create and configure the PTSPAS ODBC data source for you and point PTS to it. | |||
Have the following information handy: | |||
<ol> | |||
<li>The connection details of your old patient record database (server name, database/namespace name, uid, password, port etc.).</li> | |||
<li>The same connection details for your new patient record database.</li> | |||
<li>The date and time the patient record migration/update/etc is taking place.</li> | |||
<li>A date and time after this you would like the remote update to take place.</li> | |||
</ol> | |||
Note: CMM seems to use the same database name, uid and password across the board, so we can usually infer these. | |||
Revision as of 16:44, 21 March 2022
Overview
Your PTS application is likely to be connecting to a patient record database of some sort. This is the facility that looks up the patient details on the booking in screen.
By far the most popular choice is to connect PTS to the JAC/WellSky/CMM (hereafter "CMM") dispensing database. Our technician will have created this link for you during installation if the option was available to them.
When the CMM database (or other patient record database) is moved or modified (e.g. as part of an upgrade and server decommission) the link between PTS and the patient record database will be broken.
It's worth pointing out that PTS remains usable even if the patient lookup goes down - users can just enter patient details automatically.
Amending the patient record connection information
Starting in 2022 new patient record implementations are implemented with an ODBC data source called "PTSPAS" on the PTS application server. It is best to simply amend this data source to point it to the new location. If the data source drivers are outdated (e.g. requires the new IRIS drivers) or are otherwise invalid (e.g. moving from one patient record ecosystem to another) it's easiest to completely remove the PTSPAS datasource and create a new one with the same name.
Assuming the data structure of the patient record database remains the same, the patient lookup should now be working again in your PTS application (note there hasn't been a "breaking change" to the CMM patient record data structure since 2014).
When PTSPAS data source is not yet in use, or there is another complication
You should contact TMSi to arrange a date and time for one of our support technicians to remote access your PTS server and create and configure the PTSPAS ODBC data source for you and point PTS to it.
Have the following information handy:
- The connection details of your old patient record database (server name, database/namespace name, uid, password, port etc.).
- The same connection details for your new patient record database.
- The date and time the patient record migration/update/etc is taking place.
- A date and time after this you would like the remote update to take place.
Note: CMM seems to use the same database name, uid and password across the board, so we can usually infer these.