You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Jackie Hughes Authoring Organization(s)
CEDS Email address [email protected] Use Case Title
Add Usage Note to Element with Option set "Other" Use Case Description
During the Collaborator Use Case Working Group, MI proposed Issue 647 with the usage note as follows
"The option set is left open to be defined by the SEA."
This note should be applied across any elements listing "Other" as an option set.
Use Case Background
Provide information related to why these changes/additions are needed.
Location of Element in the Domain Entity Schema
The text was updated successfully, but these errors were encountered:
A small suggested revision to the use case: This note should be applied across any elements where "Other" is the only prepopulated option in the option set.
(Virtually every option set has an "Other" in it, and we don't want to add this usage note to all of the option sets. Only the ones that are supposed to be considered 'open' ) 😁
This is for capturing needs not currently supported by the CEDS model. Please do not send or share actual data as examples in this issue or in attachments.
Author(s)
Jackie Hughes
Authoring Organization(s)
CEDS
Email address
[email protected]
Use Case Title
Add Usage Note to Element with Option set "Other"
Use Case Description
During the Collaborator Use Case Working Group, MI proposed Issue 647 with the usage note as follows
"The option set is left open to be defined by the SEA."
This note should be applied across any elements listing "Other" as an option set.
Use Case Background
Provide information related to why these changes/additions are needed.
Location of Element in the Domain Entity Schema
The text was updated successfully, but these errors were encountered: