Page History

...

• Storing the entire expression as a string in the relevant field of the patient's record (as described in 8.2.1.6in section 3.1 of [6]the Record Services Guide). This requires the maximum length of the field to be large enough to support the required expressions;
• Storing a list of expressions in an Expressions table, and associating each expression with a local identifier. (Please refer to sections 7.8.2.4.section 12.6.1 and 8.2of the Terminology Services Guide and section 3.3 .2 of the SNOMED CT Technical Implementation Guide [6]Record Services Guide). These local expression identifiers are then stored within the relevant field of the patient's record. The Expressions table enables a lookup service to match the local expression identifier stored in the patient's record with the associated postcoordinated expression. This allows shorter identifier strings to be recorded within the patient record, instead of the longer postcoordinated expressions. While this approach may have a slightly detrimental effect on the retrieval of a patient record, it can reduce the storage requirements and enable indexing over expressions for faster searching. These local identifiers, however, cannot be shared with other applications, which do not have access to the associated postcoordinated expressions;
• Using a shared expression repository to generate expression identifiers that can be stored in the relevant field of the patient's record. This approach allows shorter identifiers to be recorded in the patient records (as per the previous approach), while using identifiers which can be shared between applications that share access to the same expression repository.

...

For alternative approaches for storing postcoordinated expressions, that do not use SNOMED CT Compositional Grammar, please refer to section 8.2 of [6]3 of the Record Services Guide.