Finally found time to read chapter 6 of the snomed guide. It now makes much more sense to me. The key takeaway for me is that the soft default context can be overruled by the information model, but must be computer processable. So a findings default context can be overruled by using it in a family history archetype. But it can’t be overruled from free texts ppm since computers cannot be assumed to understand that. I do hope all snomed implementers are aware of this, and they don’t just collect a list off all snomed codes for a patient in a single db column (without specifying the information model context. )
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Terminology bindings ... again | 171 | 19 | 5 April 2018 | |
| How to make mappings easier to query and to document in openEHR | 33 | 621 | 19 April 2024 | |
| More generic reference model | 92 | 9 | 13 September 2016 | |
| What happens once the Pulse/Heart beat archetype is replaced? | 48 | 372 | 2 October 2025 | |
| Coding element and event names | 56 | 1173 | 4 December 2024 | |
| SNOMED | 31 | 16 | 10 May 2016 | |
| SNOMEDCT - correct representation | 49 | 4 | 20 May 2017 | |
| Suggestions re Term binding in Archetype Editor | 49 | 5 | 8 January 2007 | |
| How to represent "other" for coded values | 43 | 2694 | 12 August 2021 | |
| [EHRbase] Storing and querying data without an standalone archetype | 39 | 982 | 17 April 2024 |