This repository was archived by the owner on Jul 31, 2023. It is now read-only.
add practitionerRole and org/location #29
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When building the resource bundle for CQL execution, DTR was ignoring the practitioner role, even if it was included as a data requirement in the library. This PR adds the practitioner role to the CQL bundle as well as its organization/location references.
The result is that when prepopulating the Prescriber Enrollment Form, the CQL is able to pull in information from the PractitionerRole resource, like the "specialty" of the practitioner. To test that this works, use it with the other REMS-179 pull requests and go through a normal turalio workflow, using the Prescriber Enrollment Form, to see the prepopulation work.