Page tree

StatusIn PROD
Version

1.0

Descriptions:

Termdescription typeLanguage/acceptabilityLangauge/acceptabilityCase significance
Computed tomography of [body structure] (procedure)FSNus:Pgb:Pci
CT of [body structure]SYNus:Pgb:PCS
Computed tomography of [body structure]SYNus:Agb:Aci


Concept model:

Applies To:

STL (enhanced for attribute type slot capability):

71388002 |Procedure (procedure)|:

[[~1..1]] { 260686004 |Method (attribute)| = 312251004 |Computed tomography imaging - action (qualifier value)|,

       [[~1..1]] [[+id(<<363704007 |Procedure site (attribute)|) @procSite]] = [[+id(<< 442083009 |Anatomical or acquired body structure (body structure)| ) @procSite]] }


Definition status:  


900000000000073002 |Defined (core metadata concept)|


Rules for description generation:

  1. Remove the semantic tag, e.g. (body structure)
  2. Remove 'Structure of' from [body structure] if term starts with 'Structure of'   e.g. 709530002|Structure of phalanx of hand (body structure)|
  3. Remove 'structure' from [body structure] if term contains 'structure', e.g. 69536005|Head structure (body structure)|   24097009|Bone structure of hand (body structure)|

5 Comments

  1. As of RP 1.16 (expected in Production around 18 March 2021) we'll have the ability to have a slot for an attribute type as well as the attribute value.

    This allows us to specify the different variants of procedure site :  <<363704007 |Procedure site (attribute)|   rather than just direct.

    The AP cannot yet support this enhancement, so I'll put both STL in the page above.

    See QI-807 for a misaligned concepts report run against this enhanced template.

  2. Monica Harrywhen I ran this for the specified "Applies To", I was seeing a lot of guidance concepts which I think we have another template for?

    I'm re-running now with these filtered out, so I wonder if the "Applies To" would be better as:

    << 77477000 |Computerized axial tomography (procedure)| : [0..0] 363703001 |Has intent (attribute)| -> 429892002 |Guidance intent (qualifier value)|

    similarly filter out the "with contrast" concepts and also allow for multiple role groups when more than one body site is being considered.

  3. Yes, we have a sep. template for guidance and with contrast. So yes in the first instance the plain CT of body structure is the one to run. Thanks, Monica

    1. Ok great, I'll filter these out above then.

  4. Here's the last thing I ran (in UAT) ECL:   << 77477000 |Computerized axial tomography (procedure)| : [0..0] 363703001 |Has intent (attribute)| = 429892002 |Guidance intent (qualifier value)|, [0..0] 424361007 |Using substance (attribute)| = 385420005 |Contrast media (substance)|

    And Template:   71388002 |Procedure (procedure)|:

    [[~1..*]] {  

         [[~1..1]] 260686004 |Method (attribute)| = 312251004 |Computed tomography imaging - action (qualifier value)|,

         [[~1..1]] [[+id(<<363704007 |Procedure site (attribute)|) @procSite]] = [[+id(<< 442083009 |Anatomical or acquired body structure (body structure)| ) @procSite]] }