-
**Section Number** [2:3.68.4.1.2 Message Semantics](https://profiles.ihe.net/ITI/MHD/ITI-68.html#2368412-message-semantics)
**Issue**
At the European Connectathon, we have seen multiple vendors us…
-
When using the populate operation against a questionnaire and supplying a Patient reference e.g.
https://FHIRSERVER.COM/fhir/Questionnaire/OSA/$populate?subject=Patient/A1
the QuestionnaireRespo…
-
**Describe the bug**
When matching with `_id` field, the search param matcher uses `StringParam` instead of `TokenParam`. This should be `TokenParam` according to the [FHIR specifications](https://hl…
-
The specification can be found here: [https://build.fhir.org/terminology-service.html]()
Currently only the `CodeSystem/$lookup` is partially implemented, it supports querying a code through the URL …
-
**Describe the bug**
According to https://build.fhir.org/ig/HL7/smart-app-launch/app-launch.html#obtain-access-token, following parameter is required
code_verifier | required | This parameter is u…
-
I think it would be helpful to add a human readable identifier to the yaml mapping file, of the mapping itself, not just the archetype. The identifier should also be versioned.
If this spec will (po…
-
If the IG’s ImplementationGuide resource includes the fcp-approved-specification Boolean parameter with a value of ‘true’ as follows:
```
```
then th…
-
**Can the FHIR spec for travel history be shared** that was used to determine these specific codes were appropriate when querying for travel information during case report generation?
There are many…
-
##Problème rencontré
Plusieurs éléments d'en-tête reprennent les spécifications du Volet de structuration minimale. L'auteur du document, le legalAuthenticator,... seront a priori toujours les logi…
-
It seems as though the spec has been updated with respect to the semantics of the boundary functions, but the implementations within this library have not been changed to reflect this.
Here is the …