Difference between revisions of "Patient Record (PAS) Lookup"
| Line 23: | Line 23: | ||
</ul> | </ul> | ||
Assuming the data structure of the new patient record database remains the same as before, more than likely you'll only need to amend the <strong>PASDSNS</strong> setting and/or the server data source itself to repoint it to the new database location, however an advanced user could redesign the queries here if necessary | Assuming the data structure of the new patient record database remains the same as before, more than likely you'll only need to amend the <strong>PASDSNS</strong> setting and/or the server data source itself to repoint it to the new database location, however an advanced user could redesign the queries here if necessary. | ||
===Query guidelines=== | ===Query guidelines=== | ||
====Patient ID parameter==== | ====Patient ID parameter==== | ||
Revision as of 12:31, 1 July 2022
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 or Ascribe/EMIS database, and our technician will have created this link for you during installation if the option was available to them.
When the patient record database is moved or modified (e.g. as part of an upgrade or 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 manually.
PTS 5.0.3.1 and newer
Starting in PTS 5.0.3.1, the PAS link information is stored in Application Settings and is modifiable by a system administrator. The relevant settings are as follows:
- LOCALIDF
Format of Local ID. This allows prefix or suffix characters to be added to Local IDs. You could handle this in the query itself but it may be tidier to format it here. - LOCALIDQRY
Query used by booking-in screen when searching for a patient using localID. - NATIDF
Format of National ID. This allows prefix or suffix characters to be added to National IDs. You could handle this in the query itself but it may be tidier to format it here. - NATIDQRY
Query used by booking-in screen when searching for a patient using nationalID. - PASDSNS
Patient Lookup DSNs. This can also be set to a direct connection string. You can specify multiple comma-separated entries here which is useful for switchover periods.
Assuming the data structure of the new patient record database remains the same as before, more than likely you'll only need to amend the PASDSNS setting and/or the server data source itself to repoint it to the new database location, however an advanced user could redesign the queries here if necessary.
Query guidelines
Patient ID parameter
Include "{PATIENTID}" (without quotes) in your WHERE clause at the point PTS should pass through what the user entered in the Patient ID field.
No matter whether the local or national ID is used, the input parameter remains {PATIENTID}.
Output
The query should return values with the following field names. Use an "AS" command to rename columns with an alias. You don't have to return fields you don't want to use.
- NationalID
- LocalID
- Title
- Forename
- FamilyName
- Gender
- Mobile
- DOB
- Address
Example query
PTS 5.0.3.0 and older
If you are running a slightly older version of PTS the data source name will be hardcoded - PTSPAS - so you should locate this data source on the PTS server and either modify it, or replace it with a new data source while retaining the PTSPAS name.
Much older versions of PTS had the patient record connection information embedded in a DLL file that cannot be modified. If this is the case you should contact us to arrange a PTS software update.