Online Booking API - Addition of SearchClient endpoint
Currently, when a booking is made via the online booking API. OpenVPMS has built-in logic to try and identify the client and patient record, and associate the appointment in the diary with the correct records.
We want to expand on this logic, but also be able to report back to the clinic in instances where it does not match as to why so they can understand and improve their record keeping.
To adjust this would require further development work by OpenVPMS but also means that it remains the same for each and every OpenVPMS user, which we do not believe is the best way forwards.
In order for Vetstoria to do this, we will require a 'SearchClient' endpoint to be added to your API.
The spec required for this is detailed here:
If you could log this request and provide me back with a reference for my records, that would be greatly appreciated.
Re: Online Booking API - Addition of SearchClient endpoint
I agree that its frustrating when the client enters details that dont match the record - and that recording logging why it didnt match is important for clinic record keeping.
I dont really see the need to open the security risk of a Client Search particular not one that returns more than just a true false match
It would be better that a set of match rules be expanded in tne application that can be set at the clinic admin level. Giving the clinics the ability to make it more fuzzy if they wish - BUT I think Not matching should be the default.
My staff match clients pretty easily now if one exists. Booking applications could add a field that the end user selects if they are NEW or existing and feed that back to the booking notes to help staff if required.
Adding a search api seems more problematic than beneficial?
Re: Online Booking API - Addition of SearchClient endpoint
How would you use this API? My concern is that it could be used to disclose details of other customers.
There are a couple of outstanding JIRAs to improve booking: