Title | ||
|---|---|---|
Narrative description(Describe the inactivation scenario in a few lines) | ... | |
Details(Provide specifics about the scenario to support comparison to other scenarios) | What is being inactivated (concept/description/any component)? | ... |
| What is the reason for inactivation (description)? | ... | |
| Which inactivation value should be used? | ... | |
| Which historical association reference set should be used? | ... | |
Known issues(Describe any issues that may occur for this scenario and which may complicate interpretation of the inactivation) |
| |
Examples | Simple Example | 491931000000105 Breast and supplementary bottle fed at 4 months (finding) |
| Complex Example | ||
| Erroneous Example | 805601000000103 Necrotising enterocolitis (disorder) | |
Impact(Describe how specific stakeholders are affected by the inactivation) |
| |
| ||
| ||
| There is no impact until the component is actually moved. This seems useful for internal tracking and overall tracking of component movement across modules. It would be helpful to pair with "Moved to" once the component becomes inactive. End users must then decide if it is important to continue to represent the component in their terminology. There is a period of time where a component can be active in more than one module. Currently we track this by looking for duplication across different editions. | |
Potential improvement(Provide an indication of whether the current inactivation mechanism for this scenario is sufficient, or provide your ideas or thoughts on potential improvements) | ||
Supporting resources(Provide links to any resources relevant for this scenario) | <url> | <comment> |
Overview
Content Tools
Apps