Template:Data Integrity Check: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m arraymapping the relatedconcepts |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 57: | Line 57: | ||
#set: DICApp={{{DIC_app|not entered}}} }} {{ | #set: DICApp={{{DIC_app|not entered}}} }} {{ | ||
#set: DICSummary={{{DIC_summary|not entered}}} }}{{ | #set: DICSummary={{{DIC_summary|not entered}}} }}{{ | ||
#if:{{{DIC_related_concepts|}}}|{{#arraymap:{{{DIC_related_concepts}}}| | #if:{{{DIC_related_concepts|}}}|{{#arraymap:{{{DIC_related_concepts}}}|;|x|{{#set:DICRelatedConcepts=x}} }}|'''[[Has ICD10OldArticleLink::No corresponding old article]]'''}} | ||
<includeonly>[[Category:Data Integrity Checks]]{{#if:{{{DIC_app}}}|[[Category:{{{DIC_app}}}]]|}} </includeonly> | <includeonly>[[Category:Data Integrity Checks]]{{#if:{{{DIC_app}}}|[[Category:{{{DIC_app}}}]]|}} </includeonly> | ||
Revision as of 14:05, 2018 October 26
This template manages information related to Data Integrity Checks.
To use:
{{Data Integrity Check
| DIC_summary = what is the check (one-liner)
| DIC_related_concepts = list of related pages (probably the one it's on, but there might be others...)
| DIC_firmness = hard check (not allowed) or soft check (allowed, but give error; in CFE this means it has to go into the ... table, and cross checks have to consider that table)
| DIC_timing = complete always
| DIC_app = which of the following are checking this: CCMDB.mdb, Centralized data front end.accdb, SAS (new template call for each)
| DIC_coding = how to find this in containing program, eg. SAS file, function name, query name...
| DIC_status = implementation status (needs review, ready to implement, implemented, declined, not feasible)
| DIC_implementation_date = date change was rolled out / first applied
}}
== Related articles ==
{{Related Articles}}
- if ready to implement, the template should also put the check on the Requested Changes Page. Now there is a tricky thing! Means we actually need to template requested changes in the first place. And if we go there, should a requested change turn into a log entry? It all becomes really disjointed but also powerful.
| Data Integrity Checks | |
| Summary: | not entered |
| Related: | not entered |
| Firmness: | not entered |
| Timing: | complete (assumed default) |
| App: | not entered |
| Coding: | not entered |
| Status: | not entered |
| Implementation Date: | not entered |