CSCR-019 contextControlCode

Back to Clinical Statement Change Requests page.

Submitted by: Charlie Bishop	Revision date: ?
Submitted date: 08 March 2005	Change request ID: CSCR-019

(Copied from HL7 Website Meeting Minutes and original Change Request)

Name

contextControlCode

Issue

This attribute is not included in all the necessary classes and where it is included its use is inconsistent and the specified vocabulary domain is overly restrictive.

Recommendation

Standardize usage to be:

• cardinality [1..1]
• conformance Mandatory
• vocabulary domain ContextControl

Update usage in the following Act Relationships:

• ActChoice.sourceOf2/targetOf
• ActChoice.conditions
• ActChoice.definition
• Observation.referenceRange
• ObservationRange.precondition
• Criterion.precondition

Update usage in the following Participations:

• ActChoice.informant
• ActChoice.performer
• ActChoice.author
• ActChoice.dataEnterer
• ActChoice.verifier
• ActChoice.subject
• ActChoice.recordTarget

Add contextControlCode to the following Act Relationships:

• Organizer.component
• ActChoice.sourceOf1

Add contextControlCode to the following Participations:

• ActChoice.participant
• ActChoice.location
• SubstanceAdministration.consumable
• Supply.product

Rationale

Attribute needs to be included in the pattern so that it is available for domains that make use of the pattern. Vocabulary should be as general as possible in a pattern to avoid imposing unnecessary constraints on domains wishing to make use of the model.

Discussion

23 March 2006

• Discussed usage of ActRelationship ContextConductionIndictor and ContextControlCode
• Charlie will provide notes on the usage of ActRelationship ContextConductionIndictor and ContextControlCode to help the group understand the next set of change requests

Resolution

Motion (First, second): Motion Against: 0; Abstain: X; In Favor: Z