Page History

The use of SNOMED CT for recording Allergy, Hypersensitivity, and Intolerance requires the definition of an information model and terminology bindings. This will ensure that the information is captured in a consistent and standardized way, which can be used to facilitate better communication and decision-making between healthcare providers. Furthermore, it will enable the sharing of health information between different systems and facilitate better analysis of health data. By defining an information model and terminology bindings, healthcare organizations can ensure that their data is accurately recorded and can be used in a meaningful way.

The use of HL7® FHIR® with SNOMED CT has gained considerable momentum in recent years, and HL7 FHIR has therefore been selected as the preferred information model in this guide. The following pages will discuss recommended approaches for binding SNOMED to HL7 FHIR for documenting Allergies, Hypersensitivity, and Intolerance in the EHR

...

This part of the guide presents any information model relevant for this project, as determined by the project objectives

• This may be a newly developed information model, or an abstract logical model, which provides part of the solution presented in this project.
  • In this case, the rationale and summary of experiences that were the basis of this model should be presented, and
  • Examples of how existing information models support the 'new' model may be provided
• This may be existing information models designed to support the described use cases
  • In this case, just a high-level introduction should be given, and links to the source documentation should be provided 

This section also describes the role of SNOMED CT within the described model(s), and this may include:

• An introduction to SNOMED CT subsets that may be used as value sets
• Details about relevant bindings

Notes on target audience for this chapter:

• Information managers involved with the review or development of subsets or queries to be used within an implementation are key stakeholders for this section. 
• Software developers and people involved with the design and configuration of clinical systems are key stakeholders for this section, as it will specify the bindings to be performed.

...

...

.

{