Page tree

StatusIn progress
Version

0.1


Descriptions:

Termdescription typeLanguage/acceptabilityLangauge/acceptabilityCase significance
[property] of [component] in [direct site] (observable entity)FSNUS:PTGB:PTci
[Long common name from LOINC Terminology]PTUS:PTGB:PTCS
[property] of [component] in [direct site]AcceptableUS:AcceptableGB:Acceptableci


Concept model:

Definition status:  


900000000000073002 |Sufficiently defined by necessary conditions definition status (core metadata concept)|

Applies to:

< 363787002 |Observable entity (observable entity)|

Template language:



Rules for description generation:

  1. Apply rules from the LOINC Process document 
  2. Some of the General rules for generating descriptions for templates may apply

JIRA ticket: 


2 Comments

  1. Farzaneh Ashrafi Suzanne Santamaria I found out why the groupers are coming out as primitive.   It's the Property attribute.   In the FSN we're saying "Measurement of", but the template here says we must supply an attribute value that's  118598001 |Property (qualifier value)|, and we have no generic "Measurement" property.  Specifically, LP447904-6 "{Measurement}" is not mapped to anything.   I'll code around this for now.

  2. Peter G. Williams 

    Ah, yes. The LP representing the grouper measurement property should be mapped to 685451010000100 |Measurement property (qualifier value)|, which was created in LE-252 (it is not promoted to the project yet).

    I think if we specifically use the same task, LE-252, as the base task for LOINC ontology update, this mapping can be hard coded for now–I am not sure we can do the mapping in the mapping tool at anytime soon because this property has been created exclusively for the LOINC ontology.

    CC: Suzanne Santamaria