New way for handling plugin “default” mapper, fhir server:
Currently, plugin self-identifies as default for the whole app:
[Config... plugin type enum:[ g, m, f, fD, mD ] ]
Currently, plugin self-identifies as default for the whole app:
What feature solves it and why?
[Config... plugin type enum:[ g, m, f] ]
default_FHIR_piid << should be on the list of mapper dependencies
Default_mapper_piid
What problem(s) do you aim to solve?
New way for handling plugin “default” mapper, fhir server: Currently, plugin self-identifies as default for the whole app: [Config... plugin type enum:[ g, m, f, fD, mD ] ]
Currently, plugin self-identifies as default for the whole app:
What feature solves it and why?
[Config... plugin type enum:[ g, m, f] ] default_FHIR_piid << should be on the list of mapper dependencies Default_mapper_piid
What implementation(s) do you suggest?
Anything else? Leave blank, as needed