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

AcceleratorKitProcessor - Decouple "Base Profile" and "Extension Needed" #206

Open
sliver007 opened this issue Mar 13, 2021 · 0 comments
Open

Comments

@sliver007
Copy link
Collaborator

The AcceleratorKitProcessor currently expects that the column used for specifying a base profile is also hijacked to indicate whether or not an extension is needed (expects that to be indicated by entering the value "Extension Needed"). In the case that an extension is needed, then the profile created for the data element just uses the corresponding base FHIR resource as it's baseDefinition. This means that we don't support extensions on profiles based on anything other than the base FHIR spec resources.

The notion of whether or not an extension is required for the mapping and what the base profile for the generated profile should be need to be decoupled. A "Extension Required|Needed" column should be added to the spreadsheets and the processor should be made aware of and read this column's value in. The logic in the current "extensionRequired" method should be adjusted to use the value from this new column rather than from the base profile column.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant