Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using Laboratory Catalogue #260

Open
lpg-tech opened this issue Jun 25, 2023 · 0 comments
Open

Using Laboratory Catalogue #260

lpg-tech opened this issue Jun 25, 2023 · 0 comments
Labels
Request of feature useful extensions that can be implemented in later versions

Comments

@lpg-tech
Copy link
Collaborator

lpg-tech commented Jun 25, 2023

The prescription of laboratory tests is based on the assumption that the client wishes to order certain individual tests or test panels. In doing so, he encounters specifications of the laboratory (pre-analytical conditions, additionally required information) or legal regulations (e.g. limitations of the analysis list). This data is available in the laboratory catalogue, also known as the laboratory compendium. Since laboratory techniques and legal requirements are constantly changing, it should be possible to feed all this data dynamically to the prescribing system. This requires the possibility of dynamically pre-filling the questionnaire for the laboratory prescription with data from the laboratory catalogue. This could be implemented as follows:

  1. the questionnaire can very well contain the element item.answerOption.valueReference = Reference(ServiceRequest/SomeTest). However, this item.type cannot be displayed in the LHC Forms rendering: (https://github.com/lhncbc/lforms/blob/master/r4-support.md)
  2. The prescribing system should be able to fetch FHIR Resources, e.g. a specific PlanDefinition or a specific SpecimenDefinition, from a FHIR server and pre-populate data in the Questionnaire.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Request of feature useful extensions that can be implemented in later versions
Projects
None yet
Development

No branches or pull requests

2 participants