Ocelot FOLLOW-UP-ACTIVITY Class Documentation

Class FOLLOW-UP-ACTIVITY

Subclasses:

Documentation: "Action(s) carried out by qualified personnel to verify and evaluate trial participants' adherence and response to experimental and comparison treatments."

Template Slots

Slot name Documentation Type Allowed Values/Classes Cardinality Default

term-information "Pointer to a UMLS preferred term or terms, if available, that capture the major clinical concepts in this data class (e.g, diabetes mellitus)." Instance Term-information 1:*

follow-up-activity "Machine-interpretable description of this follow-up activity." Instance Event-entity 0:1

follow-up-compliance "Points to information on compliance with followup activities for relevant study populations." Instance Follow-up-compliance

for-population "Followup activity for the stated populations. If this followup activity applied to all subjects, then the slot |for-population| should include instances of all STUDY-ARM-POPULATIONs. If only some populations had this followup activities, then the slot |for-population| will point only to those populations ( e.g., a SUBGROUP-POPULATION ) ." Instance Analyzed-population

name "A 'pretty name' for referring to this entity." STRING 0:1

description-of-followup-activity STRING 0:1

personnel-conducting-followup "Who performed the e.g., clinic visits, followup phone calls, etc." STRING 0:1

protocol-changes Instance Protocol-change

roles "Tells which class and slot will take instances of this class depending on the role of the instance. The format is (role OWNER-CLASS |owner-slot|) e.g., if this class is DATE and the instance's role is recruitment-start-date, (recruitment-start-date RECRUITMENT |start-date|) tells us that this instance of date should be the value of the slot |start-date| in an instance of class RECRUITMENT." SYMBOL 0:1

Return to index

Generated on Mon Dec 15 11:40:40 2008

Template Slots
Slot name	Documentation	Type	Allowed Values/Classes	Cardinality	Default
term-information	"Pointer to a UMLS preferred term or terms, if available, that capture the major clinical concepts in this data class (e.g, diabetes mellitus)."	Instance	Term-information	1:*
follow-up-activity	"Machine-interpretable description of this follow-up activity."	Instance	Event-entity	0:1
follow-up-compliance	"Points to information on compliance with followup activities for relevant study populations."	Instance	Follow-up-compliance
for-population	"Followup activity for the stated populations. If this followup activity applied to all subjects, then the slot \|for-population\| should include instances of all STUDY-ARM-POPULATIONs. If only some populations had this followup activities, then the slot \|for-population\| will point only to those populations ( e.g., a SUBGROUP-POPULATION ) ."	Instance	Analyzed-population
name	"A 'pretty name' for referring to this entity."	STRING		0:1
description-of-followup-activity		STRING		0:1
personnel-conducting-followup	"Who performed the e.g., clinic visits, followup phone calls, etc."	STRING		0:1
protocol-changes		Instance	Protocol-change
roles	"Tells which class and slot will take instances of this class depending on the role of the instance. The format is (role OWNER-CLASS \|owner-slot\|) e.g., if this class is DATE and the instance's role is recruitment-start-date, (recruitment-start-date RECRUITMENT \|start-date\|) tells us that this instance of date should be the value of the slot \|start-date\| in an instance of class RECRUITMENT."	SYMBOL		0:1