No Current Link To VocabularyCoded With ExtensionsCoded No Extensions
COCT_MT841300UV09
E_PublicHealthPlace universal

Derived from RMIM: COCT_RM841300UV09 and HMD: COCT_HD841300UV09
 
Place

Design Comments: A place that is of interest to public health. The place may be the subject of a public health case or investigation. More: A physical place or site with its containing structure. May be natural or man-made. The geographic position of a place may or may not be constant.

Design Comments: HL7: Place is an entity that documents a location. Note that the mobileInd has been included to handle vehicles which can be considered as places that move. Place does have a playing association to a manufactured product role to convey aspects of a vehicle that are more properly a material.

classCode [1..1] (M)
Place (CS) {CNE:V:EntityClassPlace, root= "PLC"}
determinerCode [1..1] (M)
Place (CS) {CNE:V:EntityDeterminer}
code [0..1]
Place (CD) {CWE:D:PlaceEntityType}

Design Comments: A coded value that further identifies the type of place or location.

quantity [0..1]
Place (PQ)

Design Comments: The number or quantity of the Entity, with appropriate units.

name [0..*]
Place (COLL<EN>)

Design Comments: A non-unique textual identifier or moniker for the place.

desc [0..1]
Place (ED)

Design Comments: A textual or multi-media depiction of the place.

existenceTime [0..1]
Place (IVL<TS>)

Design Comments: An interval of time specifying the period in which the place physically existed.

Rationale: The relevance of this attribute is in planning, availability and retrospective analysis.

riskCode [0..1]
Place (CD) {CWE:D:EntityRisk}

Design Comments: A value representing the type of hazard or threat associated with the Place. The place may be contaminated with a hazardous substance, organism, radioactivity or other harmful substance. The place may be a dangerous location in the first place, such as the top of Mount Everest.

handlingCode [0..1]
Place (CD) {CWE:D:EntityHandling}

Design Comments: A value representing special handling requirements for the place. Since places may be mobile, they may need special handling.

Rationale: This attribute is used to describe special handling required by the Entity to avoid damage to it or other entities.

mobileInd [0..1]
Place (BL)

Design Comments: RIM: An Indication of whether the facility has the capability to move freely from one location to another. Examples:Ships, aircraft and ambulances all have the capability to participate in healthcare acts.

directionsText [0..1]
Place (ED)

Design Comments: A free text note that carries information about locating or accessing the place.

UsageNotes: The default ED datatype supports both free text entries as well as binary attachments. Probably needs to be constrained to simpler datatype unless this full range of functionality is required.

asIdentifier [0..*] (Identifier)

Design Comments: This role is primarily used to communicate identifiers that are not intended to be interoperable. Interoperable IDs should be carried in the OtherIDs class and associated with the appropriate Role class code.

Rationale: Identifiers handled separate from entity so that scoping organization information and type code (role.code) for identifier can be communicated.

Design Comments: The scoping organization carries sufficient information to contact the organization regarding the entity in the identified role.

asTerritorialAuthority [0..*] (TerritorialAuthority)

Design Comments: Relates a place entity (player) as the region over which the scoper (typically an Organization) has certain authority (jurisdiction).

asEntityInContainer [0..*] (EntityInContainer)

Design Comments: EntityInContainer associates the content (player) with a container (scoper). This role is traversed from player to scoper.

asPartOfWhole [0..*] (PartOfWhole)

Design Comments: An association between an entity (player) and another entity (scoper) where the playing entity is considered in a "part" of the other entity, e.g. body part. This role should be used only if other roles in the model such as MBR (member), INGR (ingredient), LOCE (located entity) or CONT (content) are not appropriate. Note the model includes a 'quantity' attribute for relationships that can be quantified as a numeric ratio.

Design Comments: HL7: This role is identical to the Part role, except that it reverses the direction of traversal.

asLocatedPlacePartOf [0..*] (LocatedPlacePartOf)

Design Comments: An association of a place to other places that contain it. This supports a hierarchy of places, for example a bed location (playing entity) located within a room (scoping entity)

asMemberOf [0..*] (MemberOf)

Design Comments: An entity may be a member of a group. Entities may be grouped together for a variety purposes ranging from formal groups (such as organizations) to informal groupings for a variety of purposes (such as all the pencils in a pencil holder). The member role is played by the entity and scoped by a group.

asObserved [0..1] (Observed)

Design Comments: A public health entity may have additional characteristics that are describe via this role and its associated observations.

Design Comments: HL7: Observed is a role that associates an entity with a set of observations. The entity is the subject of the observations.

asOtherIDs [0..*] (OtherIDs)

Design Comments: An identifying relationship between the focal entity and a scoping organization. Note that this could be an identifier used by the primary scoping organization in a different context. The ids carried in this role are intended to be interoperable because they are associated with a specific Role class code.

asManagingEntity [0..*] (ManagingEntity)

Design Comments: The ManagingEntity role class associates a playing entity which either owned by, hold by, maintained by or accessed through the scoping entity. This class is traversed from the player to the scoper. Depending upon jurisdiction or culture, there may be restrictions on what entities can act as owners, and what entities can be owned.

asProductEntity [0..*] (ProductEntity)

Design Comments: The ProductEntity class is used to associate a product (player) with the organization (scopes) that distributes, retails, manufactures, regulates or warrants the product.

contactParty [0..*] (ContactParty)

Design Comments: Captures contact information for a person who can provide information regarding the public health entity.

part [0..*] (Part)

Design Comments: An association between an entity (player) and another entity (scoper) where the playing entity is considered in a "part" of the other entity, e.g. body part. This role should be used only if other roles in the model such as MBR (member), INGR (ingredient), LOCE (located entity) or CONT (content) are not appropriate. Note the model includes a 'quantity' attribute for relationships that can be quantified as a numeric ratio.

Design Comments: HL7: This role is identical to the PartOfWhole role, except that it reverses the direction of traversal.

locatedEntity [0..*] (LocatedEntity)

Design Comments: Used to associate a place with a spatial coordinate

locatedPlaceHasParts [0..*] (LocatedPlaceHasParts)

Design Comments: An association of a place to other places contained within it. This supports a hierarchy of places, for example a building wing (scoping entity) contains rooms (playing entity).

 
Identifier

Design Comments: This role is primarily used to communicate identifiers that are not intended to be interoperable. Interoperable IDs should be carried in the OtherIDs class and associated with the appropriate Role class code.

Rationale: Identifiers handled separate from entity so that scoping organization information and type code (role.code) for identifier can be communicated.

Design Comments: The scoping organization carries sufficient information to contact the organization regarding the entity in the identified role.

classCode [1..1] (M)
Role (CS) {CNE:V:RoleClassIdentifiedEntity, root= "IDENT"}
id [1..1] (M)
Role (II)

Design Comments: A unique identifier by which the identified entity is known.

code [0..1]
Role (CD) {CWE:D:IdentifiedEntityType}

Design Comments: A code further identifying the type of identified entity role.

effectiveTime [0..1]
Role (IVL<TS>)

Design Comments: Time period in which the identification information is in effect and is appropriate for use.

assigningOrganization [0..1] (E_OrganizationUniversal)
 
TerritorialAuthority

Design Comments: Relates a place entity (player) as the region over which the scoper (typically an Organization) has certain authority (jurisdiction).

classCode [1..1] (M)
Role (CS) {CNE:V:RoleClassTerritoryOfAuthority, root= "TERR"}
code [0..1]
Role (CD) {CWE:D:TerritorialAuthorityRoleType}

Design Comments: A code further identifying the type of territorial authority or jurisdiction.

governingOrganization [1..1] (E_PublicHealthOrganizationUniversal)
 
EntityInContainer

Design Comments: EntityInContainer associates the content (player) with a container (scoper). This role is traversed from player to scoper.

classCode [1..1] (M)
Role (CS) {CNE:V:RoleClassContent, root= "CONT"}
containerManufacturedMaterial [1..1] (E_PublicHealthManufacturedMaterialUniversal)
 
PartOfWhole

Design Comments: An association between an entity (player) and another entity (scoper) where the playing entity is considered in a "part" of the other entity, e.g. body part. This role should be used only if other roles in the model such as MBR (member), INGR (ingredient), LOCE (located entity) or CONT (content) are not appropriate. Note the model includes a 'quantity' attribute for relationships that can be quantified as a numeric ratio.

Design Comments: HL7: This role is identical to the Part role, except that it reverses the direction of traversal.

classCode [1..1] (M)
Role (CS) {CNE:V:RoleClassPart, root= "PART"}
id [0..1]
Role (II)

Design Comments: A unique identifier for the relationship between the playing the role of part and the scoping entity. Note that the scoper of the role will normally not be the issuer of the id.

code [0..1]
Role (CD) {CWE:D:PartRoleType}

Design Comments: A coded value that more precisely defines the type of part.

statusCode [0..1]
Role (CS) {CNE:V:RoleStatus}

Design Comments: A code indicating the operative state of the relationship e.g. normal, cancelled, terminated.

effectiveTime [0..1]
Role (IVL<TS>)

Design Comments: An interval of time specifying the period during which the relationship is in effect, if such time limit is applicable and known

quantity [0..1]
Role (RTO<PQ,PQ>)

Design Comments: For compositional relationships between (usually) material substances: a ratio (numerator : denominator) specifying the relative quantities of the subject relative to the related entity.

wholePublicHealthEntityChoice [0..1] (E_PublicHealthEntityUniversal)
 
LocatedPlacePartOf

Design Comments: An association of a place to other places that contain it. This supports a hierarchy of places, for example a bed location (playing entity) located within a room (scoping entity)

classCode [1..1] (M)
Role (CS) {CNE:V:RoleClassLocatedEntity, root= "LOCE"}
id [0..*]
Role (DSET<II>)

Design Comments: Identifier(s) for this hierarchical relationship of two places.

statusCode [0..1]
Role (CS) {CNE:V:RoleStatus}

Design Comments: This is the status of the association between the playing and scoping places. This becomes important for mobile locations.

effectiveTime [0..1]
Role (IVL<TS>)

Design Comments: This is the interval of time the places are associated.

location [0..1] (Place)
 
MemberOf

Design Comments: An entity may be a member of a group. Entities may be grouped together for a variety purposes ranging from formal groups (such as organizations) to informal groupings for a variety of purposes (such as all the pencils in a pencil holder). The member role is played by the entity and scoped by a group.

classCode [1..1] (M)
Role (CS) {CNE:V:RoleClassMember, root= "MBR"}
id [0..*]
Role (DSET<II>)

Design Comments: This is the id of the entity in the group. Note that the scoper of this role is not necessarily the issuer of the id (although it may be).

code [0..1]
Role (CD) {CWE:D:MemberRoleType}

Design Comments: A role type that is used to further qualify an entity playing the role of a member of a group.

statusCode [0..1]
Role (CS) {CNE:V:RoleStatus}

Design Comments: The administrative status of the entities membership in a group.

effectiveTime [0..1]
Role (IVL<TS>)

Design Comments: The interval of time during which the entity is/was a member of a group.

groupChoice [0..1] (GroupChoice)
 
GroupChoice
choice of E_PublicHealthOrganizationUniversal
          or EntityGroup

Design Comments: A group of entities. This may be a formal or ad-hoc grouping of entities. The appropriate class code should be used for the purpose of creating an entity group. If determinerCode is INSTANCE then this is an instance of a group. If determinerCode is KIND then this is a kind of group. The group may be composed of any type of entity, there is no requirement that the group be of all the same type of entity. The Member role is used to associate the members of a group with the group.

 
EntityGroup

Design Comments: A group of entities. This may be a formal or ad-hoc grouping of entities. The appropriate class code should be used for the purpose of creating an entity group. If determinerCode is INSTANCE then this is an instance of a group. If determinerCode is KIND then this is a kind of group. The group may be composed of any type of entity, there is no requirement that the group be of all the same type of entity. The Member role is used to associate the members of a group with the group.

classCode [1..1] (M)
Entity (CS) {CNE:V:EntityClassRoot, root= "ENT"}
determinerCode [1..1] (M)
Entity (CS) {CNE:V:EntityDeterminer}
code [0..1]
Entity (CD) {CWE:D:EntityCode}

Design Comments: A code further describing the type of entity group.

quantity [0..1]
Entity (INT)

Design Comments: A code further identifying the type of group.

name [0..1]
Entity (ST)

Design Comments: A non-unique textual identifier or moniker for the entity group.

desc [0..1]
Entity (ED)

Design Comments: A textual or multimedia depiction of the entity group.

statusCode [0..1]
Entity (CS) {CNE:V:EntityStatus}

Design Comments: A code indicating the status of the record of this entity group.

existenceTime [0..1]
Entity (IVL<TS>)

Design Comments: An interval of time specifying the period in which the entity group physically existed.

riskCode [0..*]
Entity (DSET<CD>) {CWE:D:EntityRisk}

Design Comments: A value representing the type of hazard or threat associated with the entity group. This attribute identifies the type of risk without specifying the level of risk.

handlingCode [0..*]
Entity (DSET<CD>) {CWE:D:EntityHandling}

Design Comments: A value representing special handling requirements for the entity group.

 
Observed

Design Comments: A public health entity may have additional characteristics that are describe via this role and its associated observations.

Design Comments: HL7: Observed is a role that associates an entity with a set of observations. The entity is the subject of the observations.

classCode [1..1] (M)
Role (CS) {CNE:V:RoleClassRoot, root= "ROL"}
subjectOf [1..*] (Subject2)

Design Comments: The public health entity is the subject of a set of observations.

 
Subject2

Design Comments: The public health entity is the subject of a set of observations.

typeCode [1..1] (M)
Participation (CS) {CNE:V:ParticipationTargetSubject, root= "SBJ"}
contextControlCode [0..1]
Participation (CS) {CNE:V:ContextControl, default= "AN"}

Design Comments: A code that specifies how this participation contributes to the context of the current Act, and whether it may be propagated to descendent Acts whose association allows such propagation (see ActRelationship.contextConductionInd). The default value of AN has been associated with this participation.

observationEvent [1..1] (ObservationEvent)

Design Comments: An observation on the associated entity to facilitate identification. This may be used to handle data like height, weight, hair color, eye color, etc.

Rationale: Use case: identification of John Doe individuals , either the investigative subject, or some related individual.

Use case: demographic data typically available from secondary sources, eg. from drivers license

Use case: forensic data. Use case: red cow with white blaze.

 
ObservationEvent

Design Comments: An observation on the associated entity to facilitate identification. This may be used to handle data like height, weight, hair color, eye color, etc.

Rationale: Use case: identification of John Doe individuals , either the investigative subject, or some related individual.

Use case: demographic data typically available from secondary sources, eg. from drivers license

Use case: forensic data. Use case: red cow with white blaze.

classCode [1..1] (M)
Observation (CS) {CNE:V:ActClassObservation, root= "OBS"}
moodCode [1..1] (M)
Observation (CS) {CNE:V:ActMoodEventOccurrence, root= "EVN"}
id [0..1]
Observation (II)

Design Comments: a unique identifier for the observation.

code [1..1]
Observation (CD) {CWE:D:ObservationType}

Design Comments: a code that specifies the type of observation being reported.

negationInd [0..1]
Observation (BL)

Design Comments: Used with an Observation event, it allows one to say "entity does not have blue eyes". RIM: An indicator specifying that the Act statement is a negation of the Act as described by the descriptive attributes.

title [0..1]
Observation (ED)

Design Comments: A word or phrase by which the Observation may be known among people. Example: name of a research study (e.g. "Scandinavian Simvastatin Study"

text [0..1]
Observation (ED)

Design Comments: a free-form text description of the observation.

statusCode [0..1]
Observation (CS) {CNE:V:ActStatus}

Design Comments: code indicating the operative status of the business process, which in this case is an Observation.

Rationale: may be required for appropriate interpretation of the Observation, which could be on-going.

effectiveTime [0..1]
Observation (QSET<TS>)

Design Comments: The time period in which the Observation report was started and, if a point in time or a closed interval of time, in which it ended. May not be the time of the observation itself.

confidentialityCode [0..*]
Observation (DSET<CD>) {CWE:D:Confidentiality}

Design Comments: A code that controls the disclosure of information about this observation event.

value [1..1]
Observation (ANY) {CWE:D:ObservationValue}

Design Comments: Information derived from the observation; the observation 'result' expressed as a value.

UsageNotes: The default ANY datatypes support any kind of information, from simple text to binary attachments (eg. an image file). Needs to be constrained for actual implementations and realistic limits set on the scope of its use.

interpretationCode [0..*]
Observation (DSET<CD>) {CWE:D:ObservationInterpretation}

Design Comments: One or more codes specifying a rough qualitative interpretation of the observation, such as "normal", "abnormal", "below normal", "change up", "resistant", "susceptible", etc.

methodCode [0..*]
Observation (DSET<CD>) {CWE:D:ObservationMethod}

Design Comments: A code that provides additional detail about the means or technique used to ascertain the observation. Examples: Blood pressure measurement method: arterial puncture vs. sphygmomanometer (Riva-Rocci), sitting vs. supine position, etc

targetSiteCode [0..*]
Observation (DSET<CD>) {CWE:D:ActSite}

Design Comments: The anatomical site or system that is the focus of the observation.

 
OtherIDs

Design Comments: An identifying relationship between the focal entity and a scoping organization. Note that this could be an identifier used by the primary scoping organization in a different context. The ids carried in this role are intended to be interoperable because they are associated with a specific Role class code.

classCode [1..1] (M)
Role (CS) {CNE:V:RoleClassRoot, root= "ROL"}

Design Comments: Structural attribute. This can be any specialization of "role" not otherwise present in the model. A specific role class code must be selected for each instance of this class.

id [1..*] (M)
Role (DSET<II>)

Design Comments: One or more identifiers issued to the focal subject by the associated assigningOrganization. Note, this is a mandatory attribute.

Rationale: The primary intent of this role description is to supply supporting identifiers for the entity.

code [0..1]
Role (CD) {CWE:D:RoleCode}

Design Comments: A code further defining the type of role.

statusCode [0..1]
Role (CS) {CNE:V:RoleStatus}

Design Comments: A value specifying the state of this identifying relationship (based on the RIM Role class state-machine), for example, active, terminated, nullified

effectiveTime [0..1]
Role (IVL<TS>)

Design Comments: An interval of time specifying the period during which this identifying relationship is in effect, if such time limit is applicable and known.

scopingOrganization [0..1] (E_OrganizationUniversal)
 
ManagingEntity

Design Comments: The ManagingEntity role class associates a playing entity which either owned by, hold by, maintained by or accessed through the scoping entity. This class is traversed from the player to the scoper. Depending upon jurisdiction or culture, there may be restrictions on what entities can act as owners, and what entities can be owned.

classCode [1..1] (M)
Role (CS) {CNE:V:RoleClassManagedEntity}
id [0..1]
Role (II)

Design Comments: The id is assumed to be issued by the manager of the managed entity. The owner is the scoper of this role.

statusCode [0..1]
Role (CS) {CNE:V:RoleStatus}

Design Comments: The status of the managed entity role.

effectiveTime [0..1]
Role (IVL<TS>)

Design Comments: The time of management of the entity.

scoper1 [0..1] (E_PublicHealthEntityUniversal)
 
ProductEntity

Design Comments: The ProductEntity class is used to associate a product (player) with the organization (scopes) that distributes, retails, manufactures, regulates or warrants the product.

classCode [1..1] (M)
Role (CS) {CNE:V:RoleClassProductRelated}
id [0..1]
Role (II)

Design Comments: A unique identifier for the relationship between the entity playing the role of product and the organization scoping the role. The scoping organization is assumed to be the issuer of the id.

code [0..1]
Role (CD) {CWE:D:ProductRelatedRoleType}

Design Comments: A code further identifying the type of product.

name [0..1]
Role (TN)

Design Comments: The name of the product.

statusCode [0..1]
Role (CS) {CNE:V:RoleStatus}

Design Comments: A code indicating the operative state of the relationship e.g. normal, cancelled, terminated.

effectiveTime [0..1]
Role (IVL<TS>)

Design Comments: An interval of time specifying the period during which the relationship is in effect, if such time limit is applicable and known.

scoper [0..1] (E_PublicHealthOrganizationUniversal)
 
ContactParty

Design Comments: Captures contact information for a person who can provide information regarding the public health entity.

classCode [1..1] (M)
Role (CS) {CNE:V:RoleClassContact, root= "CON"}
addr [0..*]
Role (COLL<AD>)

Design Comments: The mail and/or physical address associated with the person or organization playing the contact role.

telecom [0..*]
Role (COLL<TEL>)

Design Comments: The phone number(s) and email address(s) by which the person or organization playing the contact role can be contacted.

Rationale: needed for case followup and scheduling.

contactPerson [0..1] (E_PersonUniversal)
 
Part

Design Comments: An association between an entity (player) and another entity (scoper) where the playing entity is considered in a "part" of the other entity, e.g. body part. This role should be used only if other roles in the model such as MBR (member), INGR (ingredient), LOCE (located entity) or CONT (content) are not appropriate. Note the model includes a 'quantity' attribute for relationships that can be quantified as a numeric ratio.

Design Comments: HL7: This role is identical to the PartOfWhole role, except that it reverses the direction of traversal.

classCode [1..1] (M)
Role (CS) {CNE:V:RoleClassPart, root= "PART"}
id [0..1]
Role (II)

Design Comments: A unique identifier for the relationship between the playing the role of part and the scoping entity. Note that the scoper of the role will normally not be the issuer of the id.

code [0..1]
Role (CD) {CWE:D:PartRoleType}

Design Comments: A coded value that more precisely defines the type of part.

statusCode [0..1]
Role (CS) {CNE:V:RoleStatus}

Design Comments: A code indicating the operative state of the relationship e.g. normal, cancelled, terminated.

effectiveTime [0..1]
Role (IVL<TS>)

Design Comments: An interval of time specifying the period during which the relationship is in effect, if such time limit is applicable and known.

quantity [0..1]
Role (RTO<PQ,PQ>)

Design Comments: For compositional relationships between (usually) material substances: a ratio (numerator : denominator) specifying the relative quantities of the subject relative to the related entity.

partPublicHealthEntityChoice [0..1] (E_PublicHealthEntityUniversal)
 
LocatedEntity

Design Comments: Used to associate a place with a spatial coordinate

classCode [1..1] (M)
Role (CS) {CNE:V:RoleClassLocatedEntity, root= "LOCE"}
id [0..1]
Role (II)

Design Comments: Allows an id for the location of an entity to be conveyed. Note that the scoper of this role is probably not the issuer of this id.

code [0..1]
Role (CD) {CWE:D:LocatedEntityRoleType}

Design Comments: Identifies the type of entity location.

addr [0..*]
Role (COLL<AD>)

Design Comments: The address of the entities location.

telecom [0..*]
Role (COLL<TEL>)

Design Comments: The telecommunication or email address of the entities location.

subjectOf [0..*] (Subject3)

Design Comments: Used to associate spatial coordinates with an entities location. If multiple spatial coordinates are provided, they should identify the same location.

 
Subject3

Design Comments: Used to associate spatial coordinates with an entities location. If multiple spatial coordinates are provided, they should identify the same location.

typeCode [1..1] (M)
Participation (CS) {CNE:V:ParticipationTargetSubject, root= "SBJ"}
contextControlCode [0..1]
Participation (CS) {CNE:V:ContextControl, default= "AN"}

Design Comments: A code that specifies how this participation contributes to the context of the current Act, and whether it may be propagated to descendent Acts whose association allows such propagation (see ActRelationship.contextConductionInd). The default value of AN has been associated with this participation.

position [1..1] (A_SpatialCoordinateUniversal)
 
LocatedPlaceHasParts

Design Comments: An association of a place to other places contained within it. This supports a hierarchy of places, for example a building wing (scoping entity) contains rooms (playing entity).

classCode [1..1] (M)
Role (CS) {CNE:V:RoleClassLocatedEntity, root= "LOCE"}
id [0..1]
Role (II)

Design Comments: Identifier(s) for this hierarchical relationship of a place containing another place

statusCode [0..1]
Role (CS) {CNE:V:RoleStatus}

Design Comments: This is the status of the association between the playing and scoping places. This becomes important for mobile locations.

effectiveTime [0..1]
Role (IVL<TS>)

Design Comments: This is the interval of time the places are associated.

locatedPlace [0..1] (Place)