Prescription import

Introduction

POSOS enables hospital users to import the list of drugs (and associated dosages) on a prescription directly into their PGI. This documentation explains the functions available, the formats used and the possible integration methods.

Prerequisites

The user is registered on POSOS and uses the application on a cell phone or a computer equipped with a webcam.

The establishment’s DPI is integrated with POSOS and allows prescriptions to be imported.

The user account is configured to enable the prescription import function.

Prescriptions to be read are typed.

Intelligent scan technology is capable of recognizing most drugs and structuring the most common dosage formulations. However, there will always be a risk that this won’t be possible, so the CIO needs to take this possibility into account, or use the Scan & Go validation interface.

How does it work?

This involves importing into the DPI a list of drugs and associated dosages as described on a paper prescription. This list can be used, for example, to supply an ongoing treatment record or a medication reconciliation tool.

Output file format

Scanned and interpreted prescriptions are saved as a JSON file containing all the information and using the representations proposed by the FHIR standard. Detailed documentation is available and referenced at Prescription export model.

How to integrate with the DPI

1. patient identity retrieval

Integration involves sending the following information to the DPI:

• prescription content
• the identity of the doctor performing the operation
• the identity of the patient concerned

The first is provided directly by the scan, the second corresponds to the doctor’s current user account, and the third is indispensable information that is less trivial to obtain.

The first step is therefore to provide the Posos application with a means of linking the prescription it scans to the patient. We propose a simple integration, minimizing both the manipulation of personal information and the development work required by the third-party editor.

What Posos needs is a technical identifier that enables the DPI to make the link with the patient file. Posos does not require any identifying information such as INS, surname or first name. We offer two different integration modes.

QR Code display

To transmit this technical identifier, the DPI can display a QR Code on the patient file (in a dedicated pane or window, for example), encoding the necessary information (facility identifier + patient identifier). This QR code will then be scanned by the doctor at the same time as the prescription, and the Posos application will read everything it needs.

See the documentation for the QR Code generation API

Scan & Go integration

Posos can also integrate an application into your software to collect prescription files, transcribe them and display a validation and correction interface. This interface also adds file sending modes (by workstation webcam or by drag & drop of local files).

See Scan & Go documentation

2. Transferring the prescription to the CIO

The second step is to transfer the scanned prescription to the CIO. There are two possibilities, depending on the architecture of the receiving CIO.

For a CIO with a web-based API

Posos can develop a connector to the available API, transforming the prescription scan file if necessary.

For CIOs without an Internet-accessible API

This is the situation that requires the most preliminary study, but the most common solution will be to set up a mailbox accessible from the establishment’s information system:

• either in the form of a file repository (in the most suitable format, with Posos able to produce a specific format if required); this is often the simplest solution to implement, but is the least “real-time”.
• or in the form of a web-based API that allows the CIO to “pull” prescriptions in real time or asynchronously; here too, Posos can offer to produce a format more suited to the destination CIO. This destination API can be an ad-hoc API or a FHIR warehouse detailed in the guide: Access the FHIR warehouse.

Terminologies used

Prescriptions, particularly in the city, are not systematically exhaustive and do not necessarily enable the precise identification of a prescribed drug speciality. To overcome this problem, Posos codes each prescription line with several terminologies:

• if possible, the Specialty Identifier Code (SIC)
• if possible, the drug’s generic or brand name
• if not, at the very least, its Common Name (as identified in Medicabase and soon in the ANS Référentiel d’Interopérabilité du médicament when it becomes available)
• and its ATC class

This multiple coding enables the receiving DPI to process the information with the utmost precision in all circumstances.

Alternatively, you can use the Scan & Go interface to specifically send the final UCD/CIS (see section Scan & Go integration).