Description
Background and context
Briefly describe the background or context of this user story. Include relevant links to documents or diagrams created in the planning phase, or dependencies.
This is currently a section in a concept's detail view that shows in which collection(s) a concept is used in. It's essentially a way to show where your concepts apply. One example is PEPFAR's metadata, which shows in which code list a data element is used. Another example (not currently working) is a CIEL concept that is used in the official CIEL COVID-19 Starter Set (note that you can see the concept being used in that collection via the Concept Version History section but not the Collection Membership section, for some reason).
Note that there are a couple of potential subgroups of this:
- Repos owned by the concept owner (e.g. a CIEL concept in a CIEL collection)
- Repos owned by another implementer (e.g. UgandaEMR using a CIEL concept in their collection)
User Story
As a: terminology consumer (who isn't overly familiar with the content)
I want: to see where a concept is being leveraged, either for a particular use case/project or by other implementers
So that: I can identify even more relevant sets of content, which may increase my efficiency when reusing other content
Design: UX / UI documentation
Attach links to Zeplin documentation
Dependencies
Identify any dependencies or related tickets that must be completed before or alongside this task and link them in Zenhub.
Technical Requirements
- Specific technical requirements
- Any constraints
- Performance criteria
- Security considerations
- Integration points.
Acceptance Criteria
- Given: context or scenario,
When: action taken,
Then: expected outcome or result.
Testing Criteria
Outline specific testing criteria or scenarios to ensure the feature meets the user story requirements.
Notes, comments and assumptions
Additional notes or comments for clarification, including potential risks or uncertainties.
Metadata
Metadata
Assignees
Type
Projects
Status