: Public Class
Created: 7/24/2009 1:26:31 PM
Modified: 8/14/2018 1:59:03 PM
Project:
Advanced:
DEFINITION:<br/>An activity defined at a global library level that is an action whose immediate and primary intention is the alteration of the physical condition of the subject.<br/><br/>EXAMPLE(S):<br/>Procedures may involve the disruption of some body surface (e.g. an incision in a surgical procedure).<br/><br/>Conservative procedures such as reduction of a luxated joint, including physiotherapy such as chiropractic treatment, massage, balneotherapy, acupuncture, shiatsu.<br/><br/>OTHER NAME(S):<br/><br/>NOTE(S):<br/>The documented use cases from life sciences are limited to procedure and observations.  Use cases for other kinds of activities in life sciences are needed to support this relationship at Activity level.   In the next release, this relationship will have to be re-assessed. <br/>
Attribute
Public ST
  nameCodeModifiedText
Details:
Map:BRIDGSCC=Model Integrity
Map:PGx v1.0=BE.BEMODIFY
Notes: DEFINITION:<br/>A character string that is a revision of the original text of the procedure to enable the coding of the text.<br/><br/>EXAMPLE(S):<br/>If the original text is "message", the nameCodeModifiedText could be set to "massage", so that the text can be successfully coded.<br/><br/>OTHER NAME(S):<br/><br/>NOTE(S):<br/>In the context of BRIDG, text modification occurs a single time for a given instance of originalText.<br/>
Public CD
  methodCode
Details:
Map:BRIDGv2.2=PlannedProcedure.methodCode
Map:CTRPv3.8=PlannedProcedure.methodCode
Map:CTRv1.0=DefinedProcedure.methodCode
Map:FDA HL7 SD SD DSTU2012=PlannedSubjectActivity/Procedure.methodCode
Map:HCTv1.0=CDE 2748795:Therapies.What malignant cell removal method was used to treat the product?
Map:HCTv1.0=CDE 2750692:Graft Manipulation.Specify the ex vivo graft manipulation other than for RBC removal or volume reduction:
Map:HCTv1.0=CDE 2750679:Graft Manipulation.What was the method of ex vivo graft manipulation other than for RBC removal or volume reduction?
Map:HCTv1.0=CDE 2774532:Techniques.Specify the other erythrocyte reduced methods
Map:HCTv1.0=CDE 2774742:Techniques.Specify the other T-cell depletion method:
Map:LSDAMv2.2.3Plus=InvivoCharacterization.procedureCode
Map:LSDAMv2.2.3Plus=DefinedSpecimenFixed.fixationType
Map:LSDAMv2.2.3Plus=InvitroCharacterization.assayType
Notes: DEFINITION:<br/>A coded value specifying the technique that is used for the procedure.<br/><br/>EXAMPLE(S):<br/>Finger stick, veni puncture, Abdominal/ ascites effusion, Biopsy, Bronchial alveolar lavage (BAL) (for specimen collection)<br/><br/>Capillary electrophoresis and HPLC (for In Vitro Characterization)<br/><br/>Cell counting, flow cytometry (for In Vivo Characterization)<br/><br/>Open, laparoscopic (for cholecystectomy)<br/><br/>OTHER NAME(S):<br/><br/>NOTE(S):<br/>
Public CD
  targetAnatomicSiteCode
Details:
Map:BRIDGv2.2=PlannedProcedure.targetSiteCode
Map:CTRPv3.8=PlannedProcedure.targetSiteCode
Map:CTRv1.0=DefinedProcedure.targetAnatomicSiteCode
Map:FDA HL7 SD SD DSTU2012=PlannedSubjectActivity/Procedure.TargetSiteCode
Map:LSDAMv2.2.3Plus=DefinedProcedure.targetAnatomicSiteCode
Map:PGx v1.0=BE.BELOC
Map:SDTM IGv3.1.1=EX.EXLOC
Map:SDTM IGv3.1.1=VS.VSLOC
Map:SDTM IGv3.1.1=PE.PELOC
Map:SDTM IGv3.1.1=AE.AELOC
Map:SDTM IGv3.2=ED.EDLOC
Notes: DEFINITION:<br/>A coded value specifying the anatomic location that is the focus of a procedure.<br/><br/>EXAMPLE(S):<br/>Kidney for a nephrectomy<br/><br/>OTHER NAME(S):<br/><br/>NOTE(S):<br/>Multiple contiguous sites within the same organ system may be referenced.<br/><br/>Sources that capture anatomic site and laterality separately should map both to this attribute. For implementation models based on BRIDG where site and laterality are captured separately, you may wish to capture both concepts as a post-coordinated code structure or as multiple code repetitions.<br/>
Public CD
  targetAnatomicSiteLateralityCode
Details:
Map:CTRv1.0=DefinedProcedure.targetAnatomicSiteLateralityCode
Map:PGx v1.0=BE.BELOC
Map:SDTM IGv3.1.1=PE.PELOC
Map:SDTM IGv3.1.1=EX.EXLOC
Map:SDTM IGv3.1.1=AE.AELOC
Map:SDTM IGv3.1.1=VS.VSLOC
Map:SDTM IGv3.2=ED.EDLAT
Notes: DEFINITION:<br/>A coded value specifying the side of the body (or a paired organ) that is a target site for a procedure. <br/><br/>EXAMPLE(S):<br/>bilateral, left, right<br/><br/>OTHER NAME(S):<br/><br/>NOTE(S):<br/>This attribute was deprecated in BRIDG 3.1 but undeprecated in 4.0 since source use cases for separate laterality include SDTM and CTOM.  This change ensures that users of the BRIDG model are not bound to a particular kind of vocabulary, such as pre- or post-coordinated vocabularies.  Collapsing laterality into the target site code is an implementation option.<br/>
Public CD
  approachAnatomicSiteCode
Details:
Map:BRIDGv2.2=PlannedProcedure.approachSiteCode
Map:CTRv1.0=DefinedProcedure.approachAnatomicSiteCode
Map:FDA HL7 SD SD DSTU2012=PlannedSubjectActivity/Procedure.approachSiteCode
Map:FDA HL7 SD SD DSTU2012=PlannedSubjectActivity/SubstanceAdministration.approachSiteCode
Map:LSDAMv2.2.3Plus=DefinedProcedure.approachAnatomicSiteCode
Map:SDTM IGv3.1.1=PE.PELOC
Map:SDTM IGv3.1.1=VS.VSLOC
Map:SDTM IGv3.1.1=AE.AELOC
Map:SDTM IGv3.1.1=EX.EXLOC
Notes: DEFINITION:<br/>A coded value specifying the anatomic location or access point for a procedure.<br/><br/>EXAMPLE(S):<br/>Arm for an injection<br/>Trans-abdominal for a nephrectomy<br/><br/>OTHER NAME(S):<br/><br/>NOTE(S):<br/>Sources that capture anatomic site and laterality separately should map both to this attribute. For implementation models based on BRIDG where site and laterality are captured separately, you may wish to capture both concepts as a post-coordinated code structure or as multiple code repetitions.<br/>
Public CD
  approachAnatomicSiteLateralityCode
Details:
Map:CTRv1.0=DefinedProcedure.approachAnatomicSiteLateralityCode
Map:LSDAMv2.2.3Plus=DefinedProcedure.approachAnatomicSiteLateralityCode
Map:SDTM IGv3.1.1=EX.EXLOC
Map:SDTM IGv3.1.1=VS.VSLOC
Map:SDTM IGv3.1.1=PE.PELOC
Map:SDTM IGv3.1.1=AE.AELOC
Notes: DEFINITION:<br/>A coded value specifying the side of the body (or a paired organ) that is an access point for a procedure. <br/><br/>EXAMPLE(S):<br/>bilateral, left, right<br/><br/>OTHER NAME(S):<br/><br/>NOTE(S):<br/>This attribute was deprecated in BRIDG 3.1 but undeprecated in 4.0 since source use cases for separate laterality include SDTM and CTOM.  This change ensures that users of the BRIDG model are not bound to a particular kind of vocabulary, such as pre- or post-coordinated vocabularies.  Collapsing laterality into the target site code is an implementation option.<br/>
Public DSET<CR>
  additionalQualifierCode
Details:
Map:APSRv2.1=SB: Procedure Steps Section - hl7:ClinicalDocument > hl7:component > hl7:structuredBody > hl7:component [Proc Steps] > hl7:section > hl7:entry > hl7:procedure > hl7:code > hl7:qualifier
Map:APSRv2.1=SB: Procedure Steps Section - hl7:ClinicalDocument > hl7:component > hl7:structuredBody > hl7:component [Proc Steps] > hl7:section > hl7:entry > hl7:procedure > hl7:code > hl7:qualifier > hl7:value > @nullFlavor
Map:APSRv2.1=SB: Procedure Steps Section - hl7:ClinicalDocument > hl7:component > hl7:structuredBody > hl7:component [Proc Steps] > hl7:section > hl7:entry > hl7:procedure > hl7:code > hl7:qualifier > hl7:value
Map:APSRv2.1=SB: Procedure Steps Section - hl7:ClinicalDocument > hl7:component > hl7:structuredBody > hl7:component [Proc Steps] > hl7:section > hl7:entry > hl7:procedure > hl7:code > hl7:qualifier > hl7:name > @displayName
Map:APSRv2.1=SB: Procedure Steps Section - hl7:ClinicalDocument > hl7:component > hl7:structuredBody > hl7:component [Proc Steps] > hl7:section > hl7:entry > hl7:procedure > hl7:code > hl7:qualifier > hl7:name > @codeSystem
Map:APSRv2.1=SB: Procedure Steps Section - hl7:ClinicalDocument > hl7:component > hl7:structuredBody > hl7:component [Proc Steps] > hl7:section > hl7:entry > hl7:procedure > hl7:code > hl7:qualifier > hl7:name > @code
Map:APSRv2.1=SB: Procedure Steps Section - hl7:ClinicalDocument > hl7:component > hl7:structuredBody > hl7:component [Proc Steps] > hl7:section > hl7:entry > hl7:procedure > hl7:code > hl7:qualifier > hl7:name
Notes: DEFINITION:<br/>A coded value specifying a supplemental characterization of the procedure.<br/><br/>EXAMPLE(S):<br/><br/>OTHER NAME(S):<br/><br/>NOTE(S):<br/>For APSR, this is used only in staining and other procedures without values in SCT or LOINC or DICOM vocabulary, e.g. immune stains.  This attribute ought not to be used if there are dedicated attributes for that purpose in this class.<br/>
Public CD
  targetAnatomicSiteDirectionalityCode
Details:
Map:SDTM IGv3.1.2=EC.ECDIR
Notes: DEFINITION:<br/>A coded value specifying the directional portion of the anatomic site that is a target site for a procedure. <br/><br/>EXAMPLE(S):<br/>upper, interior<br/><br/>OTHER NAME(S):<br/><br/>NOTE(S):<br/>This attribute complements the target anatomic site code and target anatomic site laterality code.<br/>
Element Source Role Target Role
Product
Class   		Name: usingDefinedProcedure
  		Name: usedProduct
 
Details:
DESCRIPTION:<br/>Each DefinedProcedure might use one or more Product. Each Product might be used during one or more DefinedProcedure.<br/><br/>DEFINITION:<br/><br/>EXAMPLE(S):<br/><br/>OTHER NAME(S):<br/><br/>NOTE(S):<br/><br/>
Tag Value
Map:CDMHv1.0 DefinedProcedure
Details:
 
Map:CTRPv3.8 PlannedProcedure
Details:
 
Map:CTRR Intervention Name
Details:
 
Map:CTRRr3 DefinedProcedure
Details:
 
Map:CTRv1.0 DefinedProcedure
Details:
 
Map:LSDAMv2.2.3Plus DefinedProcedure
Details:
 
Constraint Type Status
use actualIndicator Qualifier Invariant Approved
Details:
Only Product with actualIndicator = “false” is valid.<br/>
use Association Set Qualifier Invariant Approved
Details:
The association from ExperimentalActivityItem is only valid if the DefinedProcedure is occurring in the context of an Experiment or a SpecimenProcessing project, and in such case the association to Product is not valid.<br/>
Object Type Connection Direction Notes
DefinedSubstanceAdministration Class Generalization From DESCRIPTION: Each DefinedSubstanceAdministration always specializes one DefinedProcedure. Each DefinedProcedure might be specialized by one DefinedSubstanceAdministration. DEFINITION: EXAMPLE(S): OTHER NAME(S): NOTE(S):
DefinedActivity Class Generalization To DESCRIPTION: Each DefinedProcedure always specializes one DefinedActivity. Each DefinedActivity might be specialized by one DefinedProcedure. DEFINITION: EXAMPLE(S): OTHER NAME(S): NOTE(S):
DefinedSpecimenCollection Class Generalization From DESCRIPTION: Each DefinedSpecimenCollection always specializes one DefinedProcedure. Each DefinedProcedure might be specialized by one DefinedSpecimenCollection. DEFINITION: EXAMPLE(S): OTHER NAME(S): NOTE(S):
DefinedMaterialProcessStep Class Generalization From DESCRIPTION: Each DefinedMaterialProcessStep always specializes one DefinedProcedure. Each DefinedProcedure might be specialized by one DefinedMaterialProcessStep. DEFINITION: EXAMPLE(S): OTHER NAME(S): NOTE(S):