-
Notifications
You must be signed in to change notification settings - Fork 0
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
Revise the use of Organization.alias as Acronym #76
Comments
Using identifier sounds good, but i see a few possible issues. What schould be the system URL? How do we ensure uniqueness (required by the identifier type)? Maybe we could look to the BBMRI-Directory, if they ensure the uniqueness. |
Yes, you are right, we should clarify that first. |
Ok, so "Alias"-values are arbitrary text fields in the Directory. No strict uniqueness / rules applied. Should we try tp think of another approch or close this issue? |
I would suggest to use an extension here. We should not constrain the number of aliases to one and also alias is something different as an acronym. What do you think? |
I agree with using an extension. Since it would require updating examples, we should first migrate all profiles and extensions connected to biobank and collection to FSH. |
We use Organization.alias in the Biobank and the Collection profile as a mapping for "acronym" from the Directory and MIABIS.
In FHIR the definition of Organization.alias is:
As it may be possible to count an acronym as an alternative name, we rely on restricting the cardinality to a maximum of one in order to have at most one alias to choose from and map to acronym. Restricting the alias on such a way hinders interoperability because biobanks/collections no longer can have multiple alternative names.
I would suggest to use an identifier for the acronym.
The text was updated successfully, but these errors were encountered: