Handle canonical attributes

[elsiehoffet-94]

Problem

We want to be able to handle the canonical data type on Pyrog.
One example is the questionnaire attribute of the QuestionnaireResponse resource. This attribute must point to the URI of the Questionnaire instance in the database. (ex: Questionnaire/123)

Description

The goal is to provide Pyrog with elements to build a FHIR request to the api, to fetch questionnaire meta data and fill the canonical attribute correctly.
The search request template is api/<ResourceType>?identifier=<system>|<value>, for instance api/Questionnaire?identifier=http://terminology.arkhn.org/Questionnaire|1234

Then, fhir-river must do this api call and concatenate <ResourceType>(from pyrog), and the id (from the result bundle) to fill the canonical attribute with <ResourceType>/id.

The problem we face is that pyrog users do not have this uri at their disposal, and do not wish to fill it with a static value.

Client

For a canonical data type, display a button to select :

• the <ResourceType> : ResourceType, the same way it already exists for type attributes.
• the <system> : (Source + Table) the same way it already exists for system attributes.
• the <value> : Input table and column, the same way it already exists for any attribute.

Server

1. Change the data model to adapt to this new kind of canonical input (different from static and sql)
2. Adapt fhir-river to handle this kind of inputs.
3. Prepare for possible cases where : there are multiple results returned by the search, no results are returned...

Additional context

For now, we will only enable canonical references to be made on the identifier attribute of a resource.
For external canonical references, it should still be possible to fill the attribute with a static value or a sql input.

Implementation

• I would be interested in implementing this feature.