Query s tmp EuroSCORE II checks: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m →Log |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Data Integrity Check | {{Data Integrity Check | ||
| DIC_summary = Each of the | | DIC_summary = Each of the two Euroscore II project entries must have one entry and the float_var must be between 0 and 23.99 if [[RecordStatus]] is complete | ||
| DIC_related_concepts = EuroSCORE II; Service/Location field | | DIC_related_concepts = EuroSCORE II; Service/Location field | ||
| DIC_firmness = hard check | | DIC_firmness = hard check | ||
Latest revision as of 15:43, 2023 September 27
| Data Integrity Checks | |
| Summary: | Each of the two Euroscore II project entries must have one entry and the float_var must be between 0 and 23.99 if RecordStatus is complete |
| Related: | EuroSCORE II, Service/Location field |
| Firmness: | hard check |
| Timing: | complete |
| App: | CCMDB.accdb |
| Coding: | query s_tmp_EuroSCORE_II_checks |
| Uses L Problem table: | not relevant for this app |
| Status: | implemented |
| Implementation Date: | 2023-07-12 |
| Backlogged: | true |
Any admission with Service tmp entry "SBGH Cardiac / Cardiac Surgery" Or "SBGH Critical Care / Cardiac Surgery" must have exactly one EuroSCORE II entry.
If this ever changes, consider also Query s_tmp_ABO_TEE_checks
Log
- 2023-08-16 - updated to allow scores up to 100
- 2023-07-26 - added exception to score requirement for Value = "excluded"
- 2023-07-12 - implemented
Related articles
| Related articles: |