Name for Template
Name of Confluence page should be presented Template Name with Status, For example,
- Computed tomography of [body structure] (procedure) - In PROD
- [Fracture morphology] of [bone structure] (disorder) - Ready for implementation
Format for Templates
- Descriptions:
- All essential descriptions
- Fully specified name (FSN)
- Preferred term (PT)
- Synonym (SYN)
- Metadata about descriptions
- Description type (FSN, PT, SYN)
- Language and acceptability
- Case significance
- Variables in description should be presented by square brackets [ ] with label inside the brackets. The label should be the representative of value rather than attribute name. For example, [bone structure] is a suitable slot name. The attribute finding site is not a suitable slot name. The same label should be used for the variable in concept model.
- All essential descriptions
- Concept model:
- Attribute cardinality
- IS A relationship for proximal primitive parent concept
- Attribute and values constraints
- Role group cardinality for A/V
- Variables in description should be presented by squire brackets [ ] with label inside the brackets and followed by the expression constraint
- Definition status:
- The value should be 900000000000073002 |Sufficiently defined concept definition status (core metadata concept)|
- The value should be 900000000000073002 |Sufficiently defined concept definition status (core metadata concept)|
- Applies to:
- Domain for the template which can be presented by expression
- Domain for the template which can be presented by expression
- Replaced by:
- Link to the new template
- Link to the new template
- Rules for generating descriptions
- describing rules for generating different description. For example, removing semantic tag and word 'structure' for body structure are standard rules for all descriptions
- Additional rules can be added for specific template in order to generate readable FSNs
- JIRA ticket
- Link to the JIRA ticket for template development and implementation workflow
Template status
- In progress
- For review
- Ready for implementation
- In PROD
- On hold
- Outdated (still in production before it is replaced by new template)
- Archived (Include the link to the new template under Replaced by section)
Notes:
- The expression constraint language should be used to indicate range
- All concepts in template should be presented by concept id and FSN by using 'SNOMED CT Expression' macro. (open the macro browser by selecting + for insert more content or entering '{' on the page, then search 'sct' and select the macro)
- The hierarchical relationships between templates should be arranged by subpages in Confluence