SNOMED CT Templates

Page tree

StatusArchived
Version

0.9

 

Descriptions:

Termdescription typeLanguage/acceptabilityLangauge/acceptabilityCase significance
LOINC FSN + (Observable entity)FSNUS:PTGB:PTCS
LOINC FSNPTUS:PTGB:PTCS
LOINC unique IDSYNUS:AGB:ACS
Published UUIDSYNUS:AGB:ACS
Correlation IDDefinitionUS:PTGB:PTCS


Concept model:

AttributeValuerole group number


116680003 |Is a (attribute)|


363787002 |Observable entity (observable entity)|

0


704321009 |Characterizes (attribute)|


<<  719982003 |Process|

0


704324001 |Process output (attribute)|


0


  704322002 |Process agent (attribute)|


0


  704323007 |Process duration (attribute)|


<  7389001 |Time frame|  

0


  370130000 |Property (attribute)|


<<  118598001 |Measurement property|

0


  704327008 |Direct site (attribute)|


0


  370132008 |Scale type (attribute)|


0

Definition status:  


900000000000073002 |Defined (core metadata concept)|  


Rules for description generation:

N/A

6 Comments

  1. Kai Kewley

    Hi Farzaneh Ashrafi. Although I understand we will not be publishing the FSN or PT of these LOINC concepts I'm wondering if having descriptions for internal use might be useful during authoring to help search and browsing?

    We may need to create a dummy FSN and PT by simply concatenating all the attribute values together to avoid validation issues in the authoring platform.

    CC: Yongsheng Gao

  2. Farzaneh Ashrafi

    Hi Kai Kewley

    Thanks for your review and the comment. Yong, Suzanne, and I met today to discuss some of the questions that we had for him related to template-based authoring, and we talked about descriptions as well. Here is a summary of our discussion:
    1) While concatenating all the attribute values together is an option, we don't think it is practical in that there are at least five attributes associated with each LOINC term. Putting together the descriptions associated with each one can create descriptions that are very long and possibly outside of the character number limit. Instead, we suggest adding the LOINC fully-specified name (+ and - semantic tag) for FSN and PT. These descriptions will be added to the import file we will be sending to the Development team. Here is an example for LOINC FSN: "Amobarbital:PrThr:Pt:Urine:Ord:Confirm". We can change ":" to another character if it is not acceptable in FSN).
    2) We also talked about other information that is required in the Refset, such as LOINC ID (Map Target ID in the RefSet), Published Unique ID (via beta release scheduled for publication at the end of March), and Correlation ID. We thought that we might be able to use synonyms and definitions for this information (which we can add to the import file we will be sending to the Development team).
    3) Lastly, we talked about templates themselves and the possibility of having optional attributes. We have 4 master template types, but each has a few sub-templates with all the required attributes. The number of sub-templates varies for each master template. Our estimate is that we might have around 25-30 sub-templates. For example, the template in this page will have two sub-templates with minor modifications; each has one extra attribute: technique or precondition. Should we create 1) Four master templates with all optional values or 2) should we create all separate sub-templates with only required values (>25)?
     
    Thanks and best wishes,
    Farzaneh
    CC: Suzanne Santamaria Yongsheng Gao Please feel free to add anything that I might have missed. Thanks,

    1. Suzanne Santamaria

      Thanks for the summary, Farzaneh.

      All,

      In regards to the last question in Farzaneh's comment, is there another option: 3) Create 4-5 master templates, each having a subset of required common values and a smaller subset of optional values (like technique, precondition, units, etc.)?

  3. Suzanne Santamaria

    Hi Kai Kewley, Yongsheng Gao, 

    We've added all the templates for the LOINC expressions to date. There are 34 total and all are marked "ready for technical development." Please let us know if any modifications are required.

    Thanks,

    Suzanne Santamaria

    Farzaneh Ashrafi

  4. Suzanne Santamaria

    Note, Inherent location removed. It should not have been included in this table.

  5. Suzanne Santamaria

    Inheres in also removed from table. It has not been used as an attribute for process observables to date (this may change in future).