API calls
Introduction
Posos APIs allow you to structure unstructured medical text (prescriptions, paragraphs, etc.). By structuring we mean the identification of medical entities (drugs, dosages, pathologies, etc.) and the standardization of these entities towards medical ontologies (ATC, UCD, SNOMED, etc.). APIs also make it possible to provide clinical decision support by proposing therapeutic alternatives, drug interactions, indications, etc.
How it works ?
The integration relies on HTTP calls to our servers. These calls are secured by an identity token (JWT).
Authorisation
The application requests an identity token from the authentication API (see Identity token authentication)
Good to know: The service account private key is different for each environment. We will send you the
productionkey once testing is complete.
API call
The application calls the API of its choice by passing the identity token in the Authorization header of the HTTP request in Bearer mode.
A response in JSON format is returned by the API.
URL of API calls
The base url is https://api.{env}.posos.co where {env} is the following environment: preprod for validation, production for live.
https://api.preprod.posos.coAPIs available
We distinguish four types of APIs:
Clinical decision support
These APIs make it possible to retrieve therapeutic alternatives, drug interactions, indications but also adverse effects.
Structuring medical text
These APIs allow you to structure unstructured medical text (prescription, paragraphs, etc.). By structuring we mean the identification of medical entities (drugs, dosages, pathologies, etc.) and the standardization of these entities towards medical ontologies (ATC, UCD, SNOMED, etc.).
Prescription scan
This API allows you to convert a typewritten prescription into a structured prescription in FHIR format.