Terug naar index  <<  Terug naar terminologie

ref Waardelijst ActRelationshipType 2011‑07‑26

Id 2.16.840.1.113883.1.11.10317
ref
ad2bbr-
Geldigheid 2011‑07‑26
Status final Definitief Versielabel DEFN=UV=VO=1099-20110726
Naam ActRelationshipType Weergavenaam ActRelationshipType
Omschrijving
en-US description:

A code specifying the meaning and purpose of every ActRelationship instance. Each of its values implies specific constraints to what kinds of Act objects can be related and in which way.

Discussion: The types of act relationships fall under one of 5 categories:

1.) (De)-composition, with composite (source) and component (target)

2.) Sequel which includes follow-up, fulfillment, instantiation, replacement, transformation, etc. that all have in common that source and target are Acts of essentially the same kind but with variances in mood and other attributes, and where the target exists before the source and the source refers to the target that it links back to.

3.) Pre-condition, trigger, reason, contraindication, with the conditioned Act at the source and the condition or reason at the target.

4.) Post-condition, outcome, goal and risk, with the Act at the source having the outcome or goal at the target.

5.) A host of functional relationships including support, cause, derivation, etc. generalized under the notion of "pertinence".

Bron codesysteem
2.16.840.1.113883.5.1002 - Act Relationship Type
Niveau/ Type Code Weergavenaam Codesysteem
0‑S
ART
act relationship type
Act Relationship Type
1‑A
_ActRelationshipConditional
ActRelationshipConditional
Act Relationship Type
2‑L
CIND
has contra-indication
Act Relationship Type
2‑L
PRCN
has pre-condition
Act Relationship Type
2‑S
RSON
has reason
Act Relationship Type
3‑L
BLOCK
Blocks
Act Relationship Type
3‑L
CURE
curative indication
Act Relationship Type
3‑L
CURE.ADJ
adjunct curative indication
Act Relationship Type
3‑L
DIAG
diagnosis
Act Relationship Type
3‑S
MITGT
mitigates
Act Relationship Type
4‑L
RCVY
Recovery
Act Relationship Type
3‑L
MTGT.ADJ
adjunct mitigation
Act Relationship Type
3‑L
SYMP
symptomatic relief
Act Relationship Type
2‑L
TRIG
has trigger
Act Relationship Type
1‑S
COMP
has component
Act Relationship Type
2‑L
ARR
arrival
Act Relationship Type
2‑L
CTRLV
has control variable
Act Relationship Type
2‑L
DEP
departure
Act Relationship Type
1‑S
OUTC
has outcome
Act Relationship Type
2‑A
_ActRelationsipObjective
Act Relationsip Objective
Act Relationship Type
3‑L
OBJC
has continuing objective
Act Relationship Type
3‑L
OBJF
has final objective
Act Relationship Type
2‑L
GOAL
has goal
Act Relationship Type
2‑L
RISK
has risk
Act Relationship Type
1‑S
PERT
has pertinent information
Act Relationship Type
2‑A
_ActClassTemporallyPertains
ActClassTemporallyPertains
Act Relationship Type
3‑A
_ActRelationshipTemporallyPertainsEnd
ActRelationshipTemporallyPertainsEnd
Act Relationship Type
4‑L
EAE
ends after end of
Act Relationship Type
4‑S
EAS
ends after start of
Act Relationship Type
5‑L
EDU
ends during
Act Relationship Type
4‑L
EBS
ends before start of
Act Relationship Type
4‑S
ECW
ends concurrent with
Act Relationship Type
5‑L
CONCURRENT
concurrent with
Act Relationship Type
3‑A
_ActRelationshipTemporallyPertainsStart
ActRelationshipTemporallyPertainsStart
Act Relationship Type
4‑L
SAE
starts after end of
Act Relationship Type
4‑S
SAS
starts after start of
Act Relationship Type
5‑L
SDU
starts during
Act Relationship Type
4‑L
SBS
starts before start of
Act Relationship Type
4‑S
SCW
starts concurrent with
Act Relationship Type
5‑L
CONCURRENT
concurrent with
Act Relationship Type
3‑L
DURING
occurs during
Act Relationship Type
3‑L
OVERLAP
overlaps with
Act Relationship Type
2‑A
_ActRelationshipAccounting
ActRelationshipAccounting
Act Relationship Type
3‑A
_ActRelationshipCostTracking
ActRelationshipCostTracking
Act Relationship Type
4‑L
CHRG
has charge
Act Relationship Type
4‑L
COST
has cost
Act Relationship Type
3‑A
_ActRelationshipPosting
ActRelationshipPosting
Act Relationship Type
4‑L
CREDIT
has credit
Act Relationship Type
4‑L
DEBIT
has debit
Act Relationship Type
2‑L
AUTH
authorized by
Act Relationship Type
2‑L
CAUS
is etiology for
Act Relationship Type
2‑L
COVBY
covered by
Act Relationship Type
2‑L
DRIV
is derived from
Act Relationship Type
2‑L
ELNK
episodeLink
Act Relationship Type
2‑L
EVID
provides evidence for
Act Relationship Type
2‑L
EXACBY
exacerbated by
Act Relationship Type
2‑L
EXPL
has explanation
Act Relationship Type
2‑L
ITEMSLOC
items located
Act Relationship Type
2‑L
LIMIT
limited by
Act Relationship Type
2‑L
META
has metadata
Act Relationship Type
2‑L
MFST
is manifestation of
Act Relationship Type
2‑L
NAME
assigns name
Act Relationship Type
2‑L
PREV
has previous instance Previous instance
Act Relationship Type
2‑S
REFR
refers to
Act Relationship Type
3‑L
USE
uses
Act Relationship Type
2‑L
REFV
has reference values
Act Relationship Type
2‑L
RELVBY
relieved by
Act Relationship Type
2‑S
SPRT
has support
Act Relationship Type
3‑L
SPRTBND
has bounded support
Act Relationship Type
2‑L
SUBJ
has subject
Act Relationship Type
2‑L
SUMM
summarized by
Act Relationship Type
1‑S
SEQL
is sequel
Act Relationship Type
2‑L
APND
is appendage
Act Relationship Type
2‑L
BSLN
has baseline
Act Relationship Type
2‑L
COMPLY
complies with
Act Relationship Type
2‑L
DOC
documents
Act Relationship Type
2‑S
FLFS
fulfills
Act Relationship Type
3‑L
OCCR
occurrence is occurrence of
Act Relationship Type
3‑L
OREF
references order
Act Relationship Type
3‑L
SCH
schedules request schedules
Act Relationship Type
2‑L
GEN
has generalization
Act Relationship Type
2‑L
GEVL
evaluates (goal)
Act Relationship Type
2‑L
INST
instantiates (master)
Act Relationship Type
2‑L
MOD
modifies
Act Relationship Type
2‑L
MTCH
matches (trigger)
Act Relationship Type
2‑L
OPTN
has option
Act Relationship Type
2‑L
RCHAL
re-challenge
Act Relationship Type
2‑L
REV
reverses
Act Relationship Type
2‑L
RPLC
replaces
Act Relationship Type
2‑L
SUCC
succeeds
Act Relationship Type
2‑L
UPDT
updates (condition)
Act Relationship Type
2‑S
XCRPT
Excerpts
Act Relationship Type
3‑L
VRXCRPT
Excerpt verbatim
Act Relationship Type
2‑L
XFRM
transformation
Act Relationship Type

Legenda: Type L=leaf, S=specializable, A=abstract, D=deprecated. NullFlavors komen in het attribuut @nullFlavor in plaats van in @code.
download XML JSON CSV SQL SVS