Page tree


Status  In progress
Version 1.2
Version in PROD 1.0



1.1. Descriptions:

Term

description type

Language/acceptability

Language/acceptability

Case significance

Aspiration of [substance] from [body structure] using [device] (procedure)

FSN us:P gb:P ci
Aspiration of [substance] from [body structure] using [device] PT us:P gb:P ci

  

1.2. Concept model:

Attribute Group Cardinality

Attribute Cardinality

Attribute cardinality

in role group

Attribute

Value

0..0 1..1 0..0
1..*
1..1


0..1


0..1



0..1


0..1


0..1


0..1
0..*
1..1


0..1


0..1



0..1


0..1
0..*

1..1



0..1


1..1
0..*
1..1

129284003 |Surgical action (qualifier value)|



1..1

1.3. Definition status:  

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

1.4. Applies to:

1.5. Template language:


71388002 |Procedure (procedure)| :
[[~1..* @AspirationRoleGroup]]{
[[~1..1]] 260686004 |Method (attribute)| = [[ +id ( << 129316008 |Aspiration - action (qualifier value)| ) @AspirationAction ]] , 
[[~0..1]] [[ +id (<< 363704007 |Procedure site (attribute)|) ]] = [[ +id ( < 442083009 |Anatomical or acquired body structure (body structure)| ) @Bodysite ]] , 
[[~1..1]] [[ +id (< 405815000 |Procedure device (attribute)| ) ]] = [[ +id ( < 49062001 |Device (physical object)| ) @AspDevice ]] , 
[[~0..1]] 363701004 |Direct substance (attribute)| = [[ +id ( < 105590001 |Substance (substance)| ) @DirSubstance ]] , 
[[~0..1]] 363703001 |Has intent (attribute)| = [[ +id ( < 363675004 |Intents (nature of procedure values) (qualifier value)| ) @AspIntent ]] , 
[[~0..1]] [[ +id (<< 405816004 |Procedure morphology (attribute)|) ]] = [[ +id ( < 49755003 |Morphologically abnormal structure (morphologic abnormality)| ) @Aspmorph ]] ,
[[~0..1]] 260507000 |Access (attribute)| = [[ +id ( < 309795001 |Surgical access values (qualifier value)| ) @Access ]] 
[[~0..1]] 425391005 |Using access device| = [[ +id ( <<  49062001 |Device (physical object)| ) @AccDevice ]]} , 
[[~0..* @ImagingRoleGroup]]{
[[~1..1]] 260686004 |Method (attribute)| = [[ +id ( << 360037004 |Imaging - action (qualifier value)| ) @ImagingAction ]] , 
[[~0..1]] 363703001 |Has intent (attribute)| = 429892002 |Guidance intent (qualifier value)| , 
[[~0..1]] 424361007 |Using substance (attribute)| = [[ +id ( < 385420005 |Contrast media (substance)| ) @Contrast ]] , 
[[~0..1]] 363700003 |Direct morphology (attribute)| = [[ +id ( < 49755003 |Morphologically abnormal structure (morphologic abnormality)| ) @Dirmorph ]] , 
[[~0..1]] 405813007 |Procedure site - Direct (attribute)| = [[ +id ( < 442083009 |Anatomical or acquired body structure (body structure)| ) @ImagSite ]]} , 
[[~0..* @PunctureRoleGroup]]{
[[~1..1]] 260686004 |Method (attribute)| = [[ +id ( 129300006 |Puncture - action (qualifier value)| ) @PunctureAction ]] , 
[[~0..1]] 405813007 |Procedure site - Direct (attribute)| = [[ +id ( < 442083009 |Anatomical or acquired body structure (body structure)| ) @PuncSite ]] ,
[[~1..1]] 424226004 |Using device (attribute)| = [[ +id ( << 79068005 |Needle, device (physical object)| ) @PuncDevice ]] , 
[[~0..1]] 260507000 |Access (attribute)| = [[ +id ( < 309795001 |Surgical access values (qualifier value)| )  ]] ,
[[~0..1]] 363703001 |Has intent (attribute)| = [[ +id ( < 363675004 |Intents (nature of procedure values) (qualifier value)| ) @PuncIntent ]] , 
[[~0..1]] 363700003 |Direct morphology (attribute)| = [[ +id ( < 49755003 |Morphologically abnormal structure (morphologic abnormality)| ) @Dirmorph ]] },
[[~0..* @OtherActions]]{
[[~1..1]] 260686004 |Method (attribute)| = [[ +id ( < 129284003 |Surgical action (qualifier value)| ) ]] , 
[[~0..1]] 363704007 |Procedure site (attribute)| = [[ +id ( < 442083009 |Anatomical or acquired body structure (body structure)| ) ]] }





Link to the misaligned concept report:

https://docs.google.com/spreadsheets/d/1xopDZvfTvXZ7iezkxuca-t1pgQRTyX6aQ4icsXgCP4M/edit#gid=0

1.6. Rules for generating descriptions:

  1. Apply General rules for generating descriptions for templates;
  2. Apply Enhancements for the Template Language;
  3. If specific substance being aspirated is unknown, don't state "substance" in descriptions. Only state the substance if known. 

1.7. JIRA ticket:



  • No labels

11 Comments

  1. Mark Banks - I have amended the template. Are you able to create the template language please. Thanks, Monica

  2. Hi Yongsheng Gao , can you review this template please? 

  3. Peter G. Williams - I have reworked this template. Would you create the template language please. thanks, Monica

    1. Did you want Contrast Media in the 2nd role group to be descendants of ?

    2. I've done a first pass on the template language, Monica Harry 

      I'll wait until I hear back from you on these two questions before I try testing it.    I want to use it in a report to be sure it's right.

      I'd love us to have a proper template manager that could auto generate this stuff automatically!

  4. I think we need to add a column for the slot name (the @ thing)   because when you use the same slot name, you're saying that you're using the same value.   Here, The template language is telling me that the morphology in the imaging role group must be the same as that in the puncture role group, and I think that instruction should be evident in the table as well.   But the body structure that is imaged, could be different from that being punctured,    Are these statements all true?

    CC Yongsheng Gao 

  5. I will leave it to Yong to answer the 1st Q. The morphology in imaging, yes should be same as in puncture though a bigger Q is whether the morphology+body structure is required in the Imaging RG? Added by MB but I have not seen this previously.  and yes body structure could be diff. from morphology e.g. CYST of KIDNEY. thanks, Monica

  6. Monica Harry please check production status re 1.2 vs 1.0

  7. Peter G. Williams  - There is no template in production on the AP. Version 1.2 is correct. thanks, Monica

    1. Agree there is no template in production, so possibly someone updated this page prematurely to say 1.0 was in Prod.

      Is 1.2 ready to deploy to production, and if so, does that need a ticket to go to Yong to progress that?   Thanks!