hl7.cda.uv.core 2.0.2-sd

package/ValueSet-CDAActClass.json

@@ -0,0 +1 @@
+{"resourceType":"ValueSet","id":"CDAActClass","text":{"status":"extensions","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet CDAActClass</b></p><a name=\"CDAActClass\"> </a><a name=\"hcCDAActClass\"> </a><ul><li>Include these codes as defined in <a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ActClass</code></a><span title=\"Version is not explicitly stated, which means it is fixed to 3.1.1, the version found through the package references\"> version &#x1F4E6;3.1.1</span><table class=\"none\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-FCNTRCT\">FCNTRCT</a></td><td style=\"color: #cccccc\">financial contract</td><td>A contract whose value is measured in monetary terms.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-COV\">COV</a></td><td style=\"color: #cccccc\">coverage</td><td>When used in the EVN mood, this concept means with respect to a covered party:<br/><br/>1.  A health care insurance policy or plan that is contractually binding between two or more parties; or<br/>2.  A health care program, usually administered by government entities, that provides coverage to persons determined eligible under the terms of the program.<br/><br/> *  When used in the definition (DEF) mood, COV means potential coverage for a patient who may or may not be a covered party.<br/> *  The concept's meaning is fully specified by the choice of ActCoverageTypeCode (abstract) ActProgramCode or ActInsurancePolicyCode.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-CNTRCT\">CNTRCT</a></td><td style=\"color: #cccccc\">contract</td><td>An agreement of obligation between two or more parties that is subject to contractual law and enforcement.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-CACT\">CACT</a></td><td style=\"color: #cccccc\">control act</td><td>An act representing a system action such as the change of state of another act or the initiation of a query. All control acts represent trigger events in the HL7 context. ControlActs may occur in different moods.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-ACTN\">ACTN</a></td><td style=\"color: #cccccc\">action</td><td>Sender asks addressee to do something depending on the focal Act of the payload. An example is &quot;fulfill this order&quot;. Addressee has responsibilities to either reject the message or to act on it in an appropriate way (specified by the specific receiver responsibilities for the interaction).</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-INFO\">INFO</a></td><td style=\"color: #cccccc\">information</td><td>Sender sends payload to addressee as information. Addressee does not have responsibilities beyond serving addressee's own interest (i.e., read and memorize if you see fit). This is equivalent to an FYI on a memo.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-STC\">STC</a></td><td style=\"color: #cccccc\">state transition control</td><td>**Description:** Sender transmits a status change pertaining to the focal act of the payload. This status of the focal act is the final state of the state transition. This can be either a request or an event, according to the mood of the control act.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-CASE\">CASE</a></td><td style=\"color: #cccccc\">public health case</td><td>A public health case is an Observation representing a condition or event that has a specific significance for public health. Typically it involves an instance or instances of a reportable infectious disease or other condition. The public health case can include a health-related event concerning a single individual or it may refer to multiple health-related events that are occurrences of the same disease or condition of interest to public health. An outbreak involving multiple individuals may be considered as a type of public health case. A public health case definition (Act.moodCode = &quot;definition&quot;) includes the description of the clinical, laboratory, and epidemiologic indicators associated with a disease or condition of interest to public health. There are case definitions for conditions that are reportable, as well as for those that are not. There are also case definitions for outbreaks. A public health case definition is a construct used by public health for the purpose of counting cases, and should not be used as clinical indications for treatment. Examples include AIDS, toxic-shock syndrome, and salmonellosis and their associated indicators that are used to define a case.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-OUTB\">OUTB</a></td><td style=\"color: #cccccc\">outbreak</td><td>An outbreak represents a series of public health cases. The date on which an outbreak starts is the earliest date of onset among the cases assigned to the outbreak, and its ending date is the last date of onset among the cases assigned to the outbreak.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-COND\">COND</a></td><td style=\"color: #cccccc\">Condition</td><td>An observable finding or state that persists over time and tends to require intervention or management, and, therefore, distinguished from an Observation made at a point in time; may exist before an Observation of the Condition is made or after interventions to manage the Condition are undertaken. Examples: equipment repair status, device recall status, a health risk, a financial risk, public health risk, pregnancy, health maintenance, chronic illness</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-OBSSER\">OBSSER</a></td><td style=\"color: #cccccc\">observation series</td><td>Container for Correlated Observation Sequences sharing a common frame of reference. All Observations of the same cd must be comparable and relative to the common frame of reference. For example, a 3-channel ECG device records a 12-lead ECG in 4 steps (3 leads at a time). Each of the separate 3-channel recordings would be in their own &quot;OBSCOR&quot;. And, all 4 OBSCOR would be contained in one OBSSER because all the times are relative to the same origin (beginning of the recording) and all the ECG signals were from a fixed set of electrodes.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-OBSCOR\">OBSCOR</a></td><td style=\"color: #cccccc\">correlated observation sequences</td><td>Container for Observation Sequences (Observations whose values are contained in LIST&lt;&gt;'s) having values correlated with each other. Each contained Observation Sequence LIST&lt;&gt; must be the same length. Values in the LIST&lt;&gt;'s are correlated based on index. E.g. the values in position 2 in all the LIST&lt;&gt;'s are correlated. This is analogous to a table where each column is an Observation Sequence with a LIST&lt;&gt; of values, and each row in the table is a correlation between the columns. For example, a 12-lead ECG would contain 13 sequences: one sequence for time, and a sequence for each of the 12 leads.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-ROIBND\">ROIBND</a></td><td style=\"color: #cccccc\">bounded ROI</td><td>A Region of Interest (ROI) specified for a multidimensional observation, such as an Observation Series (OBSSER). The ROI is specified using a set of observation criteria, each delineating the boundary of the region in one of the dimensions in the multidimensional observation. The relationship between a ROI and its referenced Act is specified through an ActRelationship of type subject (SUBJ), which must always be present. Each of the boundary criteria observations is connected with the ROI using ActRelationships of type &quot;has component&quot; (COMP). In each boundary criterion, the Act.code names the dimension and the Observation.value specifies the range of values inside the region. Typically the bounded dimension is continuous, and so the Observation.value will be an interval (IVL) data type. The Observation.value need not be specified if the respective dimension is only named but not constrained. For example, an ROI for the QT interval of a certain beat in ECG Lead II would contain 2 boundary criteria, one naming the interval in time (constrained), and the other naming the interval in ECG Lead II (only named, but not constrained).</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-ROIOVL\">ROIOVL</a></td><td style=\"color: #cccccc\">overlay ROI</td><td>A Region of Interest (ROI) specified for an image using an overlay shape. Typically used to make reference to specific regions in images, e.g., to specify the location of a radiologic finding in an image or to specify the site of a physical finding by &quot;circling&quot; a region in a schematic picture of a human body. The units of the coordinate values are in pixels. The origin is in the upper left hand corner, with positive X values going to the right and positive Y values going down. The relationship between a ROI and its referenced Act is specified through an ActRelationship of type &quot;subject&quot; (SUBJ), which must always be present.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-OBS\">OBS</a></td><td style=\"color: #cccccc\">observation</td><td>**Description:**An act that is intended to result in new information about a subject. The main difference between Observations and other Acts is that Observations have a value attribute. The **code** attribute of Observation and the **value** attribute of Observation must be considered in combination to determine the semantics of the observation.<br/><br/>**Discussion:**<br/><br/>Structurally, many observations are name-value-pairs, where the Observation.code (inherited from Act) is the name and the Observation.value is the value of the property. Such a construct is also known as a variable (a named feature that can assume a value) hence, the Observation class is always used to hold generic name-value-pairs or variables, even though the variable valuation may not be the result of an elaborate observation method. It may be a simple answer to a question or it may be an assertion or setting of a parameter.<br/><br/>As with all Act statements, Observation statements describe what was done, and in the case of Observations, this includes a description of what was actually observed (results or answers); and those results or answers are part of the observation and not split off into other objects.<br/><br/>The method of action is asserted by the Observation classCode or its subclasses at the least granular level, by the Observation.code attribute value at the medium level of granularity, and by the attribute value of observation.methodCode when a finer level of granularity is required. The method in whole or in part may also appear in the attribute value of Observation.value when using coded data types to express the value of the attribute. Relevant aspects of methodology may also be restated in value when the results themselves imply or state a methodology.<br/><br/>An observation may consist of component observations each having their own Observation.code and Observation.value. In this case, the composite observation may not have an Observation.value for itself. For instance, a white blood cell count consists of the sub-observations for the counts of the various granulocytes, lymphocytes and other normal or abnormal blood cells (e.g., blasts). The overall white blood cell count Observation itself may therefore not have a value by itself (even though it could have one, e.g., the sum total of white blood cells). Thus, as long as an Act is essentially an Act of recognizing and noting information about a subject, it is an Observation, regardless of whether it has a simple value by itself or whether it has sub-observations.<br/><br/>Even though observations are professional acts (see Act) and as such are intentional actions, this does not require that every possible outcome of an observation be pondered in advance of it being actually made. For instance, differential white blood cell counts (WBC) rarely show blasts, but if they do, this is part of the WBC observation even though blasts might not be predefined in the structure of a normal WBC.<br/><br/>Clinical documents commonly have Subjective and Objective findings, both of which are kinds of Observations. In addition, clinical documents commonly contain Assessments, which are also kinds of Observations. Thus, the establishment of a diagnosis is an Observation.<br/><br/>**Examples:**<br/><br/> *  Recording the results of a Family History Assessment<br/> *  Laboratory test and associated result<br/> *  Physical exam test and associated result<br/> *  Device temperature<br/> *  Soil lead level</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-ALRT\">ALRT</a></td><td style=\"color: #cccccc\">detected issue</td><td>An observation identifying a potential adverse outcome as a result of an Act or combination of Acts.<br/><br/>*Examples:* Detection of a drug-drug interaction; Identification of a late-submission for an invoice; Requesting discharge for a patient who does not meet hospital-defined discharge criteria.<br/><br/>*Discussion:* This class is commonly used for identifying 'business rule' or 'process' problems that may result in a refusal to carry out a particular request. In some circumstances it may be possible to 'bypass' a problem by modifying the request to acknowledge the issue and/or by providing some form of mitigation.<br/><br/>*Constraints:* the Act or Acts that may cause the the adverse outcome are the target of a subject ActRelationship. The subbtypes of this concept indicate the type of problem being detected (e.g. drug-drug interaction) while the Observation.value is used to repesent a specific problem code (e.g. specific drug-drug interaction id).</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-CLNTRL\">CLNTRL</a></td><td style=\"color: #cccccc\">clinical trial</td><td>The set of actions that define an experiment to assess the effectiveness and/or safety of a biopharmaceutical product (food, drug, device, etc.). In definition mood, this set of actions is often embodied in a clinical trial protocol; in event mood, this designates the aggregate act of applying the actions to one or more subjects.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-CNOD\">CNOD</a></td><td style=\"color: #cccccc\">Condition Node</td><td>An instance of Observation of a Condition at a point in time that includes any Observations or Procedures associated with that Condition as well as links to previous instances of Condition Node for the same Condition<br/><br/>***Deprecation Comment:*** This concept has been deprecated because an alternative structure for tracking the evolution of a problem has been presented and adopted by the Care Provision Work Group.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-DGIMG\">DGIMG</a></td><td style=\"color: #cccccc\">diagnostic image</td><td>Class for holding attributes unique to diagnostic images.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-INVSTG\">INVSTG</a></td><td style=\"color: #cccccc\">investigation</td><td>An formalized inquiry into the circumstances surrounding a particular unplanned event or potential event for the purposes of identifying possible causes and contributing factors for the event. This investigation could be conducted at a local institutional level or at the level of a local or national government.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-SPCOBS\">SPCOBS</a></td><td style=\"color: #cccccc\">specimen observation</td><td>An observation on a specimen in a laboratory environment that may affect processing, analysis or result interpretation</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-SPLY\">SPLY</a></td><td style=\"color: #cccccc\">supply</td><td>Supply orders and deliveries are simple Acts that focus on the delivered product. The product is associated with the Supply Act via Participation.typeCode=&quot;product&quot;. With general Supply Acts, the precise identification of the Material (manufacturer, serial numbers, etc.) is important. Most of the detailed information about the Supply should be represented using the Material class. If delivery needs to be scheduled, tracked, and billed separately, one can associate a Transportation Act with the Supply Act. Pharmacy dispense services are represented as Supply Acts, associated with a SubstanceAdministration Act. The SubstanceAdministration class represents the administration of medication, while dispensing is supply.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-DIET\">DIET</a></td><td style=\"color: #cccccc\">diet</td><td>Diet services are supply services, with some aspects resembling Medication services: the detail of the diet is given as a description of the Material associated via Participation.typeCode=&quot;product&quot;. Medically relevant diet types may be communicated in the Diet.code attribute using domain ActDietCode, however, the detail of the food supplied and the various combinations of dishes should be communicated as Material instances.<br/><br/>**Deprecation Note**<br/><br/>**Class:** Use either the Supply class (if dealing with what should be given to the patient) or SubstanceAdministration class (if dealing with what the patient should consume)<br/><br/>**energyQuantity:** This quantity can be conveyed by using a Content relationship with a quantity attribute expressing the calories<br/><br/>**carbohydrateQuantity:**This quantity can be conveyed using a Content relationship to an Entity with a code of carbohydrate and a quantity attribute on the content relationship.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-DOCCLIN\">DOCCLIN</a></td><td style=\"color: #cccccc\">clinical document</td><td>A clinical document is a documentation of clinical observations and services, with the following characteristics:<br/><br/>1.  Persistence - A clinical document continues to exist in an unaltered state, for a time period defined by local and regulatory requirements;<br/>2.  Stewardship - A clinical document is maintained by a person or organization entrusted with its care;<br/>3.  Potential for authentication - A clinical document is an assemblage of information that is intended to be legally authenticated;<br/>4.  Wholeness - Authentication of a clinical document applies to the whole and does not apply to portions of the document without the full context of the document;<br/>5.  Human readability - A clinical document is human readable.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-CDALVLONE\">CDALVLONE</a></td><td style=\"color: #cccccc\">CDA Level One clinical document</td><td>A clinical document that conforms to Level One of the HL7 Clinical Document Architecture (CDA)</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-DOC\">DOC</a></td><td style=\"color: #cccccc\">document</td><td>The notion of a document comes particularly from the paper world, where it corresponds to the contents recorded on discrete pieces of paper. In the electronic world, a document is a kind of composition that bears resemblance to their paper world counter-parts. Documents typically are meant to be human-readable.<br/><br/>HL7's notion of document differs from that described in the W3C XML Recommendation, in which a document refers specifically to the contents that fall between the root element's start-tag and end-tag. Not all XML documents are HL7 documents.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-COMPOSITION\">COMPOSITION</a></td><td style=\"color: #cccccc\">composition</td><td>A context representing a grouped commitment of information to the EHR. It is considered the unit of modification of the record, the unit of transmission in record extracts, and the unit of attestation by authorizing clinicians.<br/><br/>A composition represents part of a patient record originating from a single interaction between an authenticator and the record.<br/><br/>Unless otherwise stated all statements within a composition have the same authenticator, apply to the same patient and were recorded in a single session of use of a single application.<br/><br/>A composition contains organizers and entries.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-ENTRY\">ENTRY</a></td><td style=\"color: #cccccc\">entry</td><td>This context represents the information acquired and recorded for an observation, a clinical statement such as a portion of the patient's history or an inference or assertion, or an action that might be intended or has actually been performed. This class may represent both the actual data describing the observation, inference, or action, and optionally the details supporting the clinical reasoning process such as a reference to an electronic guideline, decision support system, or other knowledge reference.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-BATTERY\">BATTERY</a></td><td style=\"color: #cccccc\">battery</td><td>**Definition:** An observation that is composed of a set of observations. These observations typically have a logical or practical grouping for generally accepted clinical or functional purposes, such as observations that are run together because of automation. A battery can define required and optional component observations and, in some cases, will define complex rules that determine whether or not a particular observation is made. BATTERY is a constraint on the Observation class in that it is understood to always be composed of component observations.<br/><br/>**UsageNotes:** The focus in a BATTERY is that it is composed of individual observations. In request (RQO) mood, a battery is a request to perform the component observations. In event (EVN) mood a battery is a reporting of associated set of observation events. In definition mood a battery is the definition of the associated set of observations.<br/><br/>**Examples:** Vital signs, Full blood count, Chemistry panel.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-CLUSTER\">CLUSTER</a></td><td style=\"color: #cccccc\">Cluster</td><td>**Description:**An ACT that organizes a set of component acts into a semantic grouping that have a shared subject. The subject may be either a subject participation (SBJ), subject act relationship (SUBJ), or child participation/act relationship types.<br/><br/>**Discussion:** The focus in a CLUSTER act is the grouping of the contained acts. For example &quot;a request to cluster&quot; (RQO), &quot;a type of cluster that is allowed to occur&quot; (DEF), etc.<br/><br/>**Examples:** <br/><br/> *  Radiologic investigations that might include administration of a dye, followed by radiographic observations;<br/> *  &quot;Isolate cluster&quot; which includes all testing and specimen processing performed on a specific isolate;<br/> *  a set of actions to perform at a particular stage in a clinical trial.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-EXTRACT\">EXTRACT</a></td><td style=\"color: #cccccc\">extract</td><td>This context represents the part of a patient record conveyed in a single communication. It is drawn from a providing system for the purposes of communication to a requesting process (which might be another repository, a client application or a middleware service such as an electronic guideline engine), and supporting the faithful inclusion of the communicated data in the receiving system.<br/><br/>An extract may be the entirety of the patient record as held by the sender or it may be a part of that record (e.g. changes since a specified date).<br/><br/>An extract contains folders or compositions.<br/><br/>An extract cannot contain another extract.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-EHR\">EHR</a></td><td style=\"color: #cccccc\">electronic health record</td><td>A context that comprises all compositions. The EHR is an extract that includes the entire chart.<br/><br/>**NOTE:** In an exchange scenario, an EHR is a specialization of an extract.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-ORGANIZER\">ORGANIZER</a></td><td style=\"color: #cccccc\">organizer</td><td>Organizer of entries. Navigational. No semantic content. Knowledge of the section code is not required to interpret contained observations. Represents a heading in a heading structure, or &quot;organizer tree&quot;.<br/><br/>The record entries relating to a single clinical session are usually grouped under headings that represent phases of the encounter, or assist with layout and navigation. Clinical headings usually reflect the clinical workflow during a care session, and might also reflect the main author's reasoning processes. Much research has demonstrated that headings are used differently by different professional groups and specialties, and that headings are not used consistently enough to support safe automatic processing of the E H R.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-CATEGORY\">CATEGORY</a></td><td style=\"color: #cccccc\">category</td><td>A group of entries within a composition or topic that have a common characteristic - for example, Examination, Diagnosis, Management OR Subjective, Objective, Analysis, Plan.<br/><br/>The distinction from Topic relates to value sets. For Category there is a bounded list of things like &quot;Examination&quot;, &quot;Diagnosis&quot; or SOAP categories. For Topic the list is wide open to any clinical condition or reason for a part of an encounter.<br/><br/>A CATEGORY MAY CONTAIN ENTRIES.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-DOCBODY\">DOCBODY</a></td><td style=\"color: #cccccc\">document body</td><td>A context that distinguishes the body of a document from the document header. This is seen, for instance, in HTML documents, which have discrete &lt;head&gt; and &lt;body&gt; elements.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-DOCSECT\">DOCSECT</a></td><td style=\"color: #cccccc\">document section</td><td>A context that subdivides the body of a document. Document sections are typically used for human navigation, to give a reader a clue as to the expected content. Document sections are used to organize and provide consistency to the contents of a document body. Document sections can contain document sections and can contain entries.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-TOPIC\">TOPIC</a></td><td style=\"color: #cccccc\">topic</td><td>A group of entries within a composition that are related to a common clinical theme - such as a specific disorder or problem, prevention, screening and provision of contraceptive services.<br/><br/>A topic may contain categories and entries.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-FOLDER\">FOLDER</a></td><td style=\"color: #cccccc\">folder</td><td>A context representing the high-level organization of an extract e.g. to group parts of the record by episode, care team, clinical specialty, clinical condition, or source application. Internationally, this kind of organizing structure is used variably: in some centers and systems the folder is treated as an informal compartmentalization of the overall health record; in others it might represent a significant legal portion of the EHR relating to the originating enterprise or team.<br/><br/>A folder contains compositions.<br/><br/>Folders may be nested within folders.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-ACT\">ACT</a></td><td style=\"color: #cccccc\">act</td><td>A record of something that is being done, has been done, can be done, or is intended or requested to be done.<br/><br/>*Examples:*The kinds of acts that are common in health care are (1) a clinical observation, (2) an assessment of health condition (such as problems and diagnoses), (3) healthcare goals, (4) treatment services (such as medication, surgery, physical and psychological therapy), (5) assisting, monitoring or attending, (6) training and education services to patients and their next of kin, (7) and notary services (such as advanced directives or living will), (8) editing and maintaining documents, and many others.<br/><br/>*Discussion and Rationale:* Acts are the pivot of the RIM; all domain information and processes are represented primarily in Acts. Any profession or business, including healthcare, is primarily constituted of intentional and occasionally non-intentional actions, performed and recorded by responsible actors. An Act-instance is a record of such an action.<br/><br/>Acts connect to Entities in their Roles through Participations and connect to other Acts through ActRelationships. Participations are the authors, performers and other responsible parties as well as subjects and beneficiaries (which includes tools and material used in the performance of the act, which are also subjects). The moodCode distinguishes between Acts that are meant as factual records, vs. records of intended or ordered services, and the other modalities in which act can appear.<br/><br/>One of the Participations that all acts have (at least implicitly) is a primary author, who is responsible of the Act and who &quot;owns&quot; the act. Responsibility for the act means responsibility for what is being stated in the Act and as what it is stated. Ownership of the act is assumed in the sense of who may operationally modify the same act. Ownership and responsibility of the Act is not the same as ownership or responsibility of what the Act-object refers to in the real world. The same real world activity can be described by two people, each being the author of their Act, describing the same real world activity. Yet one can be a witness while the other can be a principal performer. The performer has responsibilities for the physical actions; the witness only has responsibility for making a true statement to the best of his or her ability. The two Act-instances may even disagree, but because each is properly attributed to its author, such disagreements can exist side by side and left to arbitration by a recipient of these Act-instances.<br/><br/>In this sense, an Act-instance represents a &quot;statement&quot; according to Rector and Nowlan (1991) \\[Foundations for an electronic medical record. Methods Inf Med. 30.\\] Rector and Nowlan have emphasized the importance of understanding the medical record not as a collection of facts, but &quot;a faithful record of what clinicians have heard, seen, thought, and done.&quot; Rector and Nowlan go on saying that &quot;the other requirements for a medical record, e.g., that it be attributable and permanent, follow naturally from this view.&quot; Indeed the Act class is this attributable statement, and the rules of updating acts (discussed in the state-transition model, see Act.statusCode) versus generating new Act-instances are designed according to this principle of permanent attributable statements.<br/><br/>Rector and Nolan focus on the electronic medical record as a collection of statements, while attributed statements, these are still mostly factual statements. However, the Act class goes beyond this limitation to attributed factual statements, representing what is known as &quot;speech-acts&quot; in linguistics and philosophy. The notion of speech-act includes that there is pragmatic meaning in language utterances, aside from just factual statements; and that these utterances interact with the real world to change the state of affairs, even directly cause physical activities to happen. For example, an order is a speech act that (provided it is issued adequately) will cause the ordered action to be physically performed. The speech act theory has culminated in the seminal work by Austin (1962) \\[How to do things with words. Oxford University Press\\].<br/><br/>An activity in the real world may progress from defined, through planned and ordered to executed, which is represented as the mood of the Act. Even though one might think of a single activity as progressing from planned to executed, this progression is reflected by multiple Act-instances, each having one and only one mood that will not change along the Act-instance life cycle. This is because the attribution and content of speech acts along this progression of an activity may be different, and it is often critical that a permanent and faithful record be maintained of this progression. The specification of orders or promises or plans must not be overwritten by the specification of what was actually done, so as to allow comparing actions with their earlier specifications. Act-instances that describe this progression of the same real world activity are linked through the ActRelationships (of the relationship category &quot;sequel&quot;).<br/><br/>Act as statements or speech-acts are the only representation of real world facts or processes in the HL7 RIM. The truth about the real world is constructed through a combination (and arbitration) of such attributed statements only, and there is no class in the RIM whose objects represent &quot;objective state of affairs&quot; or &quot;real processes&quot; independent from attributed statements. As such, there is no distinction between an activity and its documentation. Every Act includes both to varying degrees. For example, a factual statement made about recent (but past) activities, authored (and signed) by the performer of such activities, is commonly known as a procedure report or original documentation (e.g., surgical procedure report, clinic note etc.). Conversely, a status update on an activity that is presently in progress, authored by the performer (or a close observer) is considered to capture that activity (and is later superceded by a full procedure report). However, both status update and procedure report are acts of the same kind, only distinguished by mood and state (see statusCode) and completeness of the information.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-ACCM\">ACCM</a></td><td style=\"color: #cccccc\">accommodation</td><td>An accommodation is a service provided for a Person or other LivingSubject in which a place is provided for the subject to reside for a period of time. Commonly used to track the provision of ward, private and semi-private accommodations for a patient.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-CONS\">CONS</a></td><td style=\"color: #cccccc\">consent</td><td>The Consent class represents informed consents and all similar medico-legal transactions between the patient (or his legal guardian) and the provider. Examples are informed consent for surgical procedures, informed consent for clinical trials, advanced beneficiary notice, against medical advice decline from service, release of information agreement, etc.<br/><br/>The details of consents vary. Often an institution has a number of different consent forms for various purposes, including reminding the physician about the topics to mention. Such forms also include patient education material. In electronic medical record communication, consents thus are information-generating acts on their own and need to be managed similar to medical activities. Thus, Consent is modeled as a special class of Act.<br/><br/>The &quot;signatures&quot; to the consent document are represented electronically through Participation instances to the consent object. Typically an informed consent has Participation.typeCode of &quot;performer&quot;, the healthcare provider informing the patient, and &quot;consenter&quot;, the patient or legal guardian. Some consent may associate a witness or a notary public (e.g., living wills, advanced directives). In consents where a healthcare provider is not required (e.g. living will), the performer may be the patient himself or a notary public.<br/><br/>Some consent has a minimum required delay between the consent and the service, so as to allow the patient to rethink his decisions. This minimum delay can be expressed in the act definition by the ActRelationship.pauseQuantity attribute that delays the service until the pause time has elapsed after the consent has been completed.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-CTTEVENT\">CTTEVENT</a></td><td style=\"color: #cccccc\">clinical trial timepoint event</td><td>An identified point during a clinical trial at which one or more actions are scheduled to be performed (definition mood), or are actually performed (event mood). The actions may or may not involve an encounter between the subject and a healthcare professional.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-INC\">INC</a></td><td style=\"color: #cccccc\">incident</td><td>An event that occurred outside of the control of one or more of the parties involved. Includes the concept of an accident.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-INFRM\">INFRM</a></td><td style=\"color: #cccccc\">inform</td><td>The act of transmitting information and understanding about a topic to a subject where the participation association must be SBJ.<br/><br/>**Discussion:** This act may be used to request that a patient or provider be informed about an Act, or to indicate that a person was informed about a particular act.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-PCPR\">PCPR</a></td><td style=\"color: #cccccc\">care provision</td><td>An **Act** that of taking on whole or partial responsibility for, or attention to, safety and well-being of a subject of care.<br/><br/>*Discussion:* A **care provision** event may exist without any other care actions taking place. For example, when a patient is assigned to the care of a particular health professional.<br/><br/>In **request** (RQO) mood **care provision** communicates a referral, which is a request:<br/><br/> *  from one party (linked as a **participant** of type **author** (AUT)),<br/> *  to another party (linked as a **participant** of type **performer** (PRF),<br/> *  to take responsibility for a scope specified by the code attribute,<br/> *  for an entity (linked as a **participant** of type **subject** (SBJ)).<br/><br/>The scope of the care for which responsibility is taken is identified by *code* attribute.<br/><br/>In **event** (EVN) mood **care provision** indicates the effective time interval of a specified scope of responsibility by a **performer** (PRF) or set of **performers** (PRF) for a **subject** (SBJ).<br/><br/>*Examples:*<br/><br/>1.  Referral from GP to a specialist.<br/>2.  Assignment of a patient or group of patients to the case list of a health professional.<br/>3.  Assignment of inpatients to the care of particular nurses for a working shift.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-REG\">REG</a></td><td style=\"color: #cccccc\">registration</td><td>Represents the act of maintaining information about the registration of its associated registered subject. The subject can be either an Act or a Role, and includes subjects such as lab exam definitions, drug protocol definitions, prescriptions, persons, patients, practitioners, and equipment.<br/><br/>The registration may have a unique identifier - separate from the unique identification of the subject - as well as a core set of related participations and act relationships that characterize the registration event and aid in the disposition of the subject information by a receiving system.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-SPCTRT\">SPCTRT</a></td><td style=\"color: #cccccc\">specimen treatment</td><td>A procedure or treatment performed on a specimen to prepare it for analysis</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-ACCT\">ACCT</a></td><td style=\"color: #cccccc\">account</td><td>A financial account established to track the net result of financial acts.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-ACSN\">ACSN</a></td><td style=\"color: #cccccc\">accession</td><td>A unit of work, a grouper of work items as defined by the system performing that work. Typically some laboratory order fulfillers communicate references to accessions in their communications regarding laboratory orders. Often one or more specimens are related to an accession such that in some environments the accession number is taken as an identifier for a specimen (group).</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-ADJUD\">ADJUD</a></td><td style=\"color: #cccccc\">financial adjudication</td><td>A transformation process where a requested invoice is transformed into an agreed invoice. Represents the adjudication processing of an invoice (claim). Adjudication results can be adjudicated as submitted, with adjustments or refused.<br/><br/>Adjudication results comprise 2 components: the adjudication processing results and a restated (or adjudicated) invoice or claim</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-CONTREG\">CONTREG</a></td><td style=\"color: #cccccc\">container registration</td><td>An Act where a container is registered either via an automated sensor, such as a barcode reader, or by manual receipt</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-DISPACT\">DISPACT</a></td><td style=\"color: #cccccc\">disciplinary action</td><td>An action taken with respect to a subject Entity by a regulatory or authoritative body with supervisory capacity over that entity. The action is taken in response to behavior by the subject Entity that body finds to be undesirable.<br/><br/>Suspension, license restrictions, monetary fine, letter of reprimand, mandated training, mandated supervision, etc.*Examples:*</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-ENC\">ENC</a></td><td style=\"color: #cccccc\">encounter</td><td>An interaction between a patient and healthcare participant(s) for the purpose of providing patient service(s) or assessing the health status of a patient. For example, outpatient visit to multiple departments, home health support (including physical therapy), inpatient hospital stay, emergency room visit, field visit (e.g., traffic accident), office visit, occupational therapy, telephone call.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-INVE\">INVE</a></td><td style=\"color: #cccccc\">invoice element</td><td>Represents concepts related to invoice processing in health care</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-LIST\">LIST</a></td><td style=\"color: #cccccc\">working list</td><td>Working list collects a dynamic list of individual instances of Act via ActRelationship which reflects the need of an individual worker, team of workers, or an organization to manage lists of acts for many different clinical and administrative reasons. Examples of working lists include problem lists, goal lists, allergy lists, and to-do lists.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-MPROT\">MPROT</a></td><td style=\"color: #cccccc\">monitoring program</td><td>An officially or unofficially instituted program to track acts of a particular type or categorization.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-PROC\">PROC</a></td><td style=\"color: #cccccc\">procedure</td><td>An Act whose immediate and primary outcome (post-condition) is the alteration of the physical condition of the subject.<br/><br/>*Examples:* : Procedures may involve the disruption of some body surface (e.g. an incision in a surgical procedure), but they also include conservative procedures such as reduction of a luxated join, chiropractic treatment, massage, balneotherapy, acupuncture, shiatsu, etc. Outside of clinical medicine, procedures may be such things as alteration of environments (e.g. straightening rivers, draining swamps, building dams) or the repair or change of machinery etc.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-REV\">REV</a></td><td style=\"color: #cccccc\">review</td><td>The act of examining and evaluating the subject, usually another act. For example, &quot;This prescription needs to be reviewed in 2 months.&quot;</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-SBADM\">SBADM</a></td><td style=\"color: #cccccc\">substance administration</td><td>The act of introducing or otherwise applying a substance to the subject.<br/><br/>*Discussion:* The effect of the substance is typically established on a biochemical basis, however, that is not a requirement. For example, radiotherapy can largely be described in the same way, especially if it is a systemic therapy such as radio-iodine. This class also includes the application of chemical treatments to an area.<br/><br/>*Examples:* Chemotherapy protocol; Drug prescription; Vaccination record</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-SUBST\">SUBST</a></td><td style=\"color: #cccccc\">Substitution</td><td>Definition: Indicates that the subject Act has undergone or should undergo substitution of a type indicated by Act.code.<br/><br/>Rationale: Used to specify &quot;allowed&quot; substitution when creating orders, &quot;actual&quot; susbstitution when sending events, as well as the reason for the substitution and who was responsible for it.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-TRNS\">TRNS</a></td><td style=\"color: #cccccc\">transportation</td><td>Transportation is the moving of a payload (people or material) from a location of origin to a destination location. Thus, any transport service has the three target instances of type payload, origin, and destination, besides the targets that are generally used for any service (i.e., performer, device, etc.)</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-VERIF\">VERIF</a></td><td style=\"color: #cccccc\">Verification</td><td>An act which describes the process whereby a 'verifying party' validates either the existence of the Role attested to by some Credential or the actual Vetting act and its details.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-XACT\">XACT</a></td><td style=\"color: #cccccc\">financial transaction</td><td>A sub-class of Act representing any transaction between two accounts whose value is measured in monetary terms.<br/><br/>In the &quot;intent&quot; mood, communicates a request for a transaction to be initiated, or communicates a transfer of value between two accounts.<br/><br/>In the &quot;event&quot; mood, communicates the posting of a transaction to an account.</td></tr></table></li></ul></div>"},"url":"http://hl7.org/cda/stds/core/ValueSet/CDAActClass","version":"2.0.2-sd","name":"CDAActClass","title":"CDAActClass","status":"draft","experimental":false,"date":"2025-12-12T15:26:32+11:00","publisher":"Health Level 7","contact":[{"name":"HL7 International - Structured Documents","telecom":[{"system":"url","value":"http://www.hl7.org/Special/committees/structure"},{"system":"email","value":"structdog@lists.HL7.org"}]}],"description":"A code specifying the major type of Act that this Act-instance represents.","compose":{"include":[{"system":"http://terminology.hl7.org/CodeSystem/v3-ActClass","concept":[{"code":"FCNTRCT"},{"code":"COV"},{"code":"CNTRCT"},{"code":"CACT"},{"code":"ACTN"},{"code":"INFO"},{"code":"STC"},{"code":"CASE"},{"code":"OUTB"},{"code":"COND"},{"code":"OBSSER"},{"code":"OBSCOR"},{"code":"ROIBND"},{"code":"ROIOVL"},{"code":"OBS"},{"code":"ALRT"},{"code":"CLNTRL"},{"code":"CNOD"},{"code":"DGIMG"},{"code":"INVSTG"},{"code":"SPCOBS"},{"code":"SPLY"},{"code":"DIET"},{"code":"DOCCLIN"},{"code":"CDALVLONE"},{"code":"DOC"},{"code":"COMPOSITION"},{"code":"ENTRY"},{"code":"BATTERY"},{"code":"CLUSTER"},{"code":"EXTRACT"},{"code":"EHR"},{"code":"ORGANIZER"},{"code":"CATEGORY"},{"code":"DOCBODY"},{"code":"DOCSECT"},{"code":"TOPIC"},{"code":"FOLDER"},{"code":"ACT"},{"code":"ACCM"},{"code":"CONS"},{"code":"CTTEVENT"},{"code":"INC"},{"code":"INFRM"},{"code":"PCPR"},{"code":"REG"},{"code":"SPCTRT"},{"code":"ACCT"},{"code":"ACSN"},{"code":"ADJUD"},{"code":"CONTREG"},{"code":"DISPACT"},{"code":"ENC"},{"code":"INVE"},{"code":"LIST"},{"code":"MPROT"},{"code":"PROC"},{"code":"REV"},{"code":"SBADM"},{"code":"SUBST"},{"code":"TRNS"},{"code":"VERIF"},{"code":"XACT"}]}]}}

package/ValueSet-CDAActClassObservation.json

@@ -0,0 +1 @@
+{"resourceType":"ValueSet","id":"CDAActClassObservation","text":{"status":"extensions","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet CDAActClassObservation</b></p><a name=\"CDAActClassObservation\"> </a><a name=\"hcCDAActClassObservation\"> </a><ul><li>Include these codes as defined in <a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ActClass</code></a><span title=\"Version is not explicitly stated, which means it is fixed to 3.1.1, the version found through the package references\"> version &#x1F4E6;3.1.1</span><table class=\"none\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-CASE\">CASE</a></td><td style=\"color: #cccccc\">public health case</td><td>A public health case is an Observation representing a condition or event that has a specific significance for public health. Typically it involves an instance or instances of a reportable infectious disease or other condition. The public health case can include a health-related event concerning a single individual or it may refer to multiple health-related events that are occurrences of the same disease or condition of interest to public health. An outbreak involving multiple individuals may be considered as a type of public health case. A public health case definition (Act.moodCode = &quot;definition&quot;) includes the description of the clinical, laboratory, and epidemiologic indicators associated with a disease or condition of interest to public health. There are case definitions for conditions that are reportable, as well as for those that are not. There are also case definitions for outbreaks. A public health case definition is a construct used by public health for the purpose of counting cases, and should not be used as clinical indications for treatment. Examples include AIDS, toxic-shock syndrome, and salmonellosis and their associated indicators that are used to define a case.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-OUTB\">OUTB</a></td><td style=\"color: #cccccc\">outbreak</td><td>An outbreak represents a series of public health cases. The date on which an outbreak starts is the earliest date of onset among the cases assigned to the outbreak, and its ending date is the last date of onset among the cases assigned to the outbreak.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-COND\">COND</a></td><td style=\"color: #cccccc\">Condition</td><td>An observable finding or state that persists over time and tends to require intervention or management, and, therefore, distinguished from an Observation made at a point in time; may exist before an Observation of the Condition is made or after interventions to manage the Condition are undertaken. Examples: equipment repair status, device recall status, a health risk, a financial risk, public health risk, pregnancy, health maintenance, chronic illness</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-OBSSER\">OBSSER</a></td><td style=\"color: #cccccc\">observation series</td><td>Container for Correlated Observation Sequences sharing a common frame of reference. All Observations of the same cd must be comparable and relative to the common frame of reference. For example, a 3-channel ECG device records a 12-lead ECG in 4 steps (3 leads at a time). Each of the separate 3-channel recordings would be in their own &quot;OBSCOR&quot;. And, all 4 OBSCOR would be contained in one OBSSER because all the times are relative to the same origin (beginning of the recording) and all the ECG signals were from a fixed set of electrodes.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-OBSCOR\">OBSCOR</a></td><td style=\"color: #cccccc\">correlated observation sequences</td><td>Container for Observation Sequences (Observations whose values are contained in LIST&lt;&gt;'s) having values correlated with each other. Each contained Observation Sequence LIST&lt;&gt; must be the same length. Values in the LIST&lt;&gt;'s are correlated based on index. E.g. the values in position 2 in all the LIST&lt;&gt;'s are correlated. This is analogous to a table where each column is an Observation Sequence with a LIST&lt;&gt; of values, and each row in the table is a correlation between the columns. For example, a 12-lead ECG would contain 13 sequences: one sequence for time, and a sequence for each of the 12 leads.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-ROIBND\">ROIBND</a></td><td style=\"color: #cccccc\">bounded ROI</td><td>A Region of Interest (ROI) specified for a multidimensional observation, such as an Observation Series (OBSSER). The ROI is specified using a set of observation criteria, each delineating the boundary of the region in one of the dimensions in the multidimensional observation. The relationship between a ROI and its referenced Act is specified through an ActRelationship of type subject (SUBJ), which must always be present. Each of the boundary criteria observations is connected with the ROI using ActRelationships of type &quot;has component&quot; (COMP). In each boundary criterion, the Act.code names the dimension and the Observation.value specifies the range of values inside the region. Typically the bounded dimension is continuous, and so the Observation.value will be an interval (IVL) data type. The Observation.value need not be specified if the respective dimension is only named but not constrained. For example, an ROI for the QT interval of a certain beat in ECG Lead II would contain 2 boundary criteria, one naming the interval in time (constrained), and the other naming the interval in ECG Lead II (only named, but not constrained).</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-ROIOVL\">ROIOVL</a></td><td style=\"color: #cccccc\">overlay ROI</td><td>A Region of Interest (ROI) specified for an image using an overlay shape. Typically used to make reference to specific regions in images, e.g., to specify the location of a radiologic finding in an image or to specify the site of a physical finding by &quot;circling&quot; a region in a schematic picture of a human body. The units of the coordinate values are in pixels. The origin is in the upper left hand corner, with positive X values going to the right and positive Y values going down. The relationship between a ROI and its referenced Act is specified through an ActRelationship of type &quot;subject&quot; (SUBJ), which must always be present.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-OBS\">OBS</a></td><td style=\"color: #cccccc\">observation</td><td>**Description:**An act that is intended to result in new information about a subject. The main difference between Observations and other Acts is that Observations have a value attribute. The **code** attribute of Observation and the **value** attribute of Observation must be considered in combination to determine the semantics of the observation.<br/><br/>**Discussion:**<br/><br/>Structurally, many observations are name-value-pairs, where the Observation.code (inherited from Act) is the name and the Observation.value is the value of the property. Such a construct is also known as a variable (a named feature that can assume a value) hence, the Observation class is always used to hold generic name-value-pairs or variables, even though the variable valuation may not be the result of an elaborate observation method. It may be a simple answer to a question or it may be an assertion or setting of a parameter.<br/><br/>As with all Act statements, Observation statements describe what was done, and in the case of Observations, this includes a description of what was actually observed (results or answers); and those results or answers are part of the observation and not split off into other objects.<br/><br/>The method of action is asserted by the Observation classCode or its subclasses at the least granular level, by the Observation.code attribute value at the medium level of granularity, and by the attribute value of observation.methodCode when a finer level of granularity is required. The method in whole or in part may also appear in the attribute value of Observation.value when using coded data types to express the value of the attribute. Relevant aspects of methodology may also be restated in value when the results themselves imply or state a methodology.<br/><br/>An observation may consist of component observations each having their own Observation.code and Observation.value. In this case, the composite observation may not have an Observation.value for itself. For instance, a white blood cell count consists of the sub-observations for the counts of the various granulocytes, lymphocytes and other normal or abnormal blood cells (e.g., blasts). The overall white blood cell count Observation itself may therefore not have a value by itself (even though it could have one, e.g., the sum total of white blood cells). Thus, as long as an Act is essentially an Act of recognizing and noting information about a subject, it is an Observation, regardless of whether it has a simple value by itself or whether it has sub-observations.<br/><br/>Even though observations are professional acts (see Act) and as such are intentional actions, this does not require that every possible outcome of an observation be pondered in advance of it being actually made. For instance, differential white blood cell counts (WBC) rarely show blasts, but if they do, this is part of the WBC observation even though blasts might not be predefined in the structure of a normal WBC.<br/><br/>Clinical documents commonly have Subjective and Objective findings, both of which are kinds of Observations. In addition, clinical documents commonly contain Assessments, which are also kinds of Observations. Thus, the establishment of a diagnosis is an Observation.<br/><br/>**Examples:**<br/><br/> *  Recording the results of a Family History Assessment<br/> *  Laboratory test and associated result<br/> *  Physical exam test and associated result<br/> *  Device temperature<br/> *  Soil lead level</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-ALRT\">ALRT</a></td><td style=\"color: #cccccc\">detected issue</td><td>An observation identifying a potential adverse outcome as a result of an Act or combination of Acts.<br/><br/>*Examples:* Detection of a drug-drug interaction; Identification of a late-submission for an invoice; Requesting discharge for a patient who does not meet hospital-defined discharge criteria.<br/><br/>*Discussion:* This class is commonly used for identifying 'business rule' or 'process' problems that may result in a refusal to carry out a particular request. In some circumstances it may be possible to 'bypass' a problem by modifying the request to acknowledge the issue and/or by providing some form of mitigation.<br/><br/>*Constraints:* the Act or Acts that may cause the the adverse outcome are the target of a subject ActRelationship. The subbtypes of this concept indicate the type of problem being detected (e.g. drug-drug interaction) while the Observation.value is used to repesent a specific problem code (e.g. specific drug-drug interaction id).</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-CLNTRL\">CLNTRL</a></td><td style=\"color: #cccccc\">clinical trial</td><td>The set of actions that define an experiment to assess the effectiveness and/or safety of a biopharmaceutical product (food, drug, device, etc.). In definition mood, this set of actions is often embodied in a clinical trial protocol; in event mood, this designates the aggregate act of applying the actions to one or more subjects.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-CNOD\">CNOD</a></td><td style=\"color: #cccccc\">Condition Node</td><td>An instance of Observation of a Condition at a point in time that includes any Observations or Procedures associated with that Condition as well as links to previous instances of Condition Node for the same Condition<br/><br/>***Deprecation Comment:*** This concept has been deprecated because an alternative structure for tracking the evolution of a problem has been presented and adopted by the Care Provision Work Group.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-DGIMG\">DGIMG</a></td><td style=\"color: #cccccc\">diagnostic image</td><td>Class for holding attributes unique to diagnostic images.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-INVSTG\">INVSTG</a></td><td style=\"color: #cccccc\">investigation</td><td>An formalized inquiry into the circumstances surrounding a particular unplanned event or potential event for the purposes of identifying possible causes and contributing factors for the event. This investigation could be conducted at a local institutional level or at the level of a local or national government.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActClass.html#v3-ActClass-SPCOBS\">SPCOBS</a></td><td style=\"color: #cccccc\">specimen observation</td><td>An observation on a specimen in a laboratory environment that may affect processing, analysis or result interpretation</td></tr></table></li></ul></div>"},"url":"http://hl7.org/cda/stds/core/ValueSet/CDAActClassObservation","version":"2.0.2-sd","name":"CDAActClassObservation","title":"CDAActClassObservation","status":"draft","experimental":false,"date":"2025-12-12T15:26:32+11:00","publisher":"Health Level 7","contact":[{"name":"HL7 International - Structured Documents","telecom":[{"system":"url","value":"http://www.hl7.org/Special/committees/structure"},{"system":"email","value":"structdog@lists.HL7.org"}]}],"description":"An act that is intended to result in new information about a subject. The main difference between Observations and other Acts is that Observations have a value attribute.","compose":{"include":[{"system":"http://terminology.hl7.org/CodeSystem/v3-ActClass","concept":[{"code":"CASE"},{"code":"OUTB"},{"code":"COND"},{"code":"OBSSER"},{"code":"OBSCOR"},{"code":"ROIBND"},{"code":"ROIOVL"},{"code":"OBS"},{"code":"ALRT"},{"code":"CLNTRL"},{"code":"CNOD"},{"code":"DGIMG"},{"code":"INVSTG"},{"code":"SPCOBS"}]}]}}

package/ValueSet-CDAActMood.json

@@ -0,0 +1 @@
+{"resourceType":"ValueSet","id":"CDAActMood","text":{"status":"extensions","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet CDAActMood</b></p><a name=\"CDAActMood\"> </a><a name=\"hcCDAActMood\"> </a><ul><li>Include these codes as defined in <a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ActMood</code></a><span title=\"Version is not explicitly stated, which means it is fixed to 2.1.1, the version found through the package references\"> version &#x1F4E6;2.1.1</span><table class=\"none\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-INT\">INT</a></td><td style=\"color: #cccccc\">intent</td><td>**Definition:** An intention or plan for an act.<br/><br/>**&gt;UsageNotes:** The final outcome of the intent, the act that is intended to occur, is always an event. However the final outcome may be reached indirectly via steps through other intents, such as promise, permission request, or an appointment that may lead to an actual event to occur. Alternatively, the intended act may never occur.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-APT\">APT</a></td><td style=\"color: #cccccc\">appointment</td><td>**Definition:** An act that has been scheduled to be performed at a specific place and time.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-ARQ\">ARQ</a></td><td style=\"color: #cccccc\">appointment request</td><td>**Definition:** A request act that is specialized for the appointment scheduling request/fulfillment cycle. An appointment request is fulfilled only and completely by an appointment (APT), i.e., all that the appointment request intends is to create an appointment *(the actual act may well not happen if that is the professional decision during the appointment)*.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-PRMS\">PRMS</a></td><td style=\"color: #cccccc\">promise</td><td>**Definition:** A commitment to perform an act (may be either solicited or unsolicited). The committer becomes responsible to the other party for executing the act, and, as a consequence, the other party may rely on the first party to perform or cause to perform the act.<br/><br/>**UsageNotes:** Commitments may be retracted or cancelled.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-PRP\">PRP</a></td><td style=\"color: #cccccc\">proposal</td><td>**Definition:** A suggestion that an act might be performed. Not an explicit request, and professional responsibility may or may not be present.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-RQO\">RQO</a></td><td style=\"color: #cccccc\">request</td><td>**Definition:** A request act that is specialized for an event request/fulfillment cycle.<br/><br/>**UsageNotes:** The fulfillment cycle may involve intermediary fulfilling acts in moods such as PRMS, APT, or even another RQO before being fulfilled by the final event.<br/><br/>**UsageNotes:** The concepts of a &quot;request&quot; and an &quot;order&quot; are viewed as different, because there is an implication of a mandate associated with order. In practice, however, this distinction has no general functional value in the inter-operation of health care computing. &quot;Orders&quot; are commonly refused for a variety of clinical and business reasons, and the notion of a &quot;request&quot; obligates the recipient (the fulfiller) to respond to the sender (the author). Indeed, in many regions, including Australia and Europe, the common term used is &quot;request.&quot;<br/><br/>Thus, the concept embodies both notions, as there is no useful distinction to be made. If a mandate is to be associated with a request, this will be embodied in the &quot;local&quot; business rules applied to the transactions. Should HL7 desire to provide a distinction between these in the future, the individual concepts could be added as specializations of this concept.<br/><br/>The critical distinction here, is the difference between this concept and an &quot;intent&quot;, of which it is a specialization. An intent involves decisions by a single party, the author. A request, however, involves decisions by two parties, the author and the fulfiller, with an obligation on the part of the fulfiller to respond to the request indicating that the fulfiller will indeed fulfill the request.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-SLOT\">SLOT</a></td><td style=\"color: #cccccc\">resource slot</td><td>**Definition:** A kind of act that may occur during the specified time period.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-DEF\">DEF</a></td><td style=\"color: #cccccc\">definition</td><td>**Definition:** A definition of a kind of act that can occur .<br/><br/>**OpenIssue:** The semantic constructs embodied in DEF and CRT moods seem indistinguishable, and their uses can readily be determined by the context in which these are used. Therefore, this OpenIssue has been created to declare that it is likely that ActMood.DEF will be &quot;retired&quot; in the future in favor of the more general ActMood.CRT.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-EVN\">EVN</a></td><td style=\"color: #cccccc\">event (occurrence)</td><td>**Definition:** An act that actually happens (may be an ongoing act or a documentation of a past act).</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-EVN.46CRT\">EVN.CRT</a></td><td style=\"color: #cccccc\">event criterion</td><td>***Deprecation Comment:*** This concept This codes should no longer be used. Instead, set attribute Act.isCriterionInd to &quot;true&quot; and use the desired mood for your criterion.<br/><br/>**Definition:** A criterion (CRT) that has\\_match = an event (EVN).</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-GOL\">GOL</a></td><td style=\"color: #cccccc\">Goal</td><td>**Definition:** An expectation that is considered to be desirable to occur in the future<br/><br/>**Examples:**Target weight below 80Kg, Stop smoking, Regain ability to walk, goal is to administer thrombolytics to candidate patients presenting with acute myocardial infarction.<br/><br/>**UsageNotes:** INT (intent) reflects a plan for the future, which is a declaration to do something. This contrasts with goal which doesn't represent an intention to act, merely a hope for an eventual result. A goal is distinct from the intended actions to reach that goal. &quot;I will reduce the dose of drug x to 20mg&quot; is an intent. &quot;I hope to be able to get the patient to the point where I can reduce the dose of drug x to 20mg&quot; is a goal. EXPEC (expectation) reflects a prediction rather than a hope. RSK (risk) reflects a potential negative event rather than a hope.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-OPT\">OPT</a></td><td style=\"color: #cccccc\">option</td><td>**Definition:** One of a set of acts that specify an option for the property values that the parent act may have. Typically used in definitions or orders to describe alternatives. An option can only be used as a group, that is, all assigned values must be used together. The actual mood of the act is the same as the parent act, and they must be linked by an actrelationship with type = OPTN.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-PERM\">PERM</a></td><td style=\"color: #cccccc\">permission</td><td>**Definition:** A kind of act that defines a permission that has been granted.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-PERMRQ\">PERMRQ</a></td><td style=\"color: #cccccc\">permission request</td><td>**Definition:** A request for a permission to perform the act. Typically a payer (or possibly a supervisor) is being requested to give permission to perform the act. As opposed to the RQO, the requestee is not asked to perform or cause to perform the act but only to give the permission.</td></tr></table></li></ul></div>"},"url":"http://hl7.org/cda/stds/core/ValueSet/CDAActMood","version":"2.0.2-sd","name":"CDAActMood","title":"CDAActMood","status":"draft","experimental":false,"date":"2025-12-12T15:26:32+11:00","publisher":"Health Level 7","contact":[{"name":"HL7 International - Structured Documents","telecom":[{"system":"url","value":"http://www.hl7.org/Special/committees/structure"},{"system":"email","value":"structdog@lists.HL7.org"}]}],"description":"A code distinguishing whether an Act is conceived of as a factual statement or in some other manner as a command, possibility, goal, etc.","compose":{"include":[{"system":"http://terminology.hl7.org/CodeSystem/v3-ActMood","concept":[{"code":"INT"},{"code":"APT"},{"code":"ARQ"},{"code":"PRMS"},{"code":"PRP"},{"code":"RQO"},{"code":"SLOT"},{"code":"DEF"},{"code":"EVN"},{"code":"EVN.CRT"},{"code":"GOL"},{"code":"OPT"},{"code":"PERM"},{"code":"PERMRQ"}]}]}}

package/ValueSet-CDAActMoodIntent.json

@@ -0,0 +1 @@
+{"resourceType":"ValueSet","id":"CDAActMoodIntent","text":{"status":"extensions","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet CDAActMoodIntent</b></p><a name=\"CDAActMoodIntent\"> </a><a name=\"hcCDAActMoodIntent\"> </a><ul><li>Include these codes as defined in <a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ActMood</code></a><span title=\"Version is not explicitly stated, which means it is fixed to 2.1.1, the version found through the package references\"> version &#x1F4E6;2.1.1</span><table class=\"none\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-INT\">INT</a></td><td style=\"color: #cccccc\">intent</td><td>**Definition:** An intention or plan for an act.<br/><br/>**&gt;UsageNotes:** The final outcome of the intent, the act that is intended to occur, is always an event. However the final outcome may be reached indirectly via steps through other intents, such as promise, permission request, or an appointment that may lead to an actual event to occur. Alternatively, the intended act may never occur.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-APT\">APT</a></td><td style=\"color: #cccccc\">appointment</td><td>**Definition:** An act that has been scheduled to be performed at a specific place and time.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-ARQ\">ARQ</a></td><td style=\"color: #cccccc\">appointment request</td><td>**Definition:** A request act that is specialized for the appointment scheduling request/fulfillment cycle. An appointment request is fulfilled only and completely by an appointment (APT), i.e., all that the appointment request intends is to create an appointment *(the actual act may well not happen if that is the professional decision during the appointment)*.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-PRMS\">PRMS</a></td><td style=\"color: #cccccc\">promise</td><td>**Definition:** A commitment to perform an act (may be either solicited or unsolicited). The committer becomes responsible to the other party for executing the act, and, as a consequence, the other party may rely on the first party to perform or cause to perform the act.<br/><br/>**UsageNotes:** Commitments may be retracted or cancelled.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-PRP\">PRP</a></td><td style=\"color: #cccccc\">proposal</td><td>**Definition:** A suggestion that an act might be performed. Not an explicit request, and professional responsibility may or may not be present.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-RQO\">RQO</a></td><td style=\"color: #cccccc\">request</td><td>**Definition:** A request act that is specialized for an event request/fulfillment cycle.<br/><br/>**UsageNotes:** The fulfillment cycle may involve intermediary fulfilling acts in moods such as PRMS, APT, or even another RQO before being fulfilled by the final event.<br/><br/>**UsageNotes:** The concepts of a &quot;request&quot; and an &quot;order&quot; are viewed as different, because there is an implication of a mandate associated with order. In practice, however, this distinction has no general functional value in the inter-operation of health care computing. &quot;Orders&quot; are commonly refused for a variety of clinical and business reasons, and the notion of a &quot;request&quot; obligates the recipient (the fulfiller) to respond to the sender (the author). Indeed, in many regions, including Australia and Europe, the common term used is &quot;request.&quot;<br/><br/>Thus, the concept embodies both notions, as there is no useful distinction to be made. If a mandate is to be associated with a request, this will be embodied in the &quot;local&quot; business rules applied to the transactions. Should HL7 desire to provide a distinction between these in the future, the individual concepts could be added as specializations of this concept.<br/><br/>The critical distinction here, is the difference between this concept and an &quot;intent&quot;, of which it is a specialization. An intent involves decisions by a single party, the author. A request, however, involves decisions by two parties, the author and the fulfiller, with an obligation on the part of the fulfiller to respond to the request indicating that the fulfiller will indeed fulfill the request.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActMood.html#v3-ActMood-SLOT\">SLOT</a></td><td style=\"color: #cccccc\">resource slot</td><td>**Definition:** A kind of act that may occur during the specified time period.</td></tr></table></li></ul></div>"},"url":"http://hl7.org/cda/stds/core/ValueSet/CDAActMoodIntent","version":"2.0.2-sd","name":"CDAActMoodIntent","title":"CDAActMoodIntent","status":"draft","experimental":false,"date":"2025-12-12T15:26:32+11:00","publisher":"Health Level 7","contact":[{"name":"HL7 International - Structured Documents","telecom":[{"system":"url","value":"http://www.hl7.org/Special/committees/structure"},{"system":"email","value":"structdog@lists.HL7.org"}]}],"description":"An intention or plan to perform a service.","compose":{"include":[{"system":"http://terminology.hl7.org/CodeSystem/v3-ActMood","concept":[{"code":"INT"},{"code":"APT"},{"code":"ARQ"},{"code":"PRMS"},{"code":"PRP"},{"code":"RQO"},{"code":"SLOT"}]}]}}

package/ValueSet-CDAActRelationshipType.json

@@ -0,0 +1 @@
+{"resourceType":"ValueSet","id":"CDAActRelationshipType","text":{"status":"extensions","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet CDAActRelationshipType</b></p><a name=\"CDAActRelationshipType\"> </a><a name=\"hcCDAActRelationshipType\"> </a><ul><li>Include these codes as defined in <a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType</code></a><span title=\"Version is not explicitly stated, which means it is fixed to 3.1.0, the version found through the package references\"> version &#x1F4E6;3.1.0</span><table class=\"none\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-RSON\">RSON</a></td><td style=\"color: #cccccc\">has reason</td><td>**Description:** The reason or rationale for a service. A reason link is weaker than a trigger, it only suggests that some service may be or might have been a reason for some action, but not that this reason requires/required the action to be taken. Also, as opposed to the trigger, there is no strong timely relation between the reason and the action. As well as providing various types of information about the rationale for a service, the RSON act relationship is routinely used between a SBADM act and an OBS act to describe the indication for use of a medication. Child concepts may be used to describe types of indication.<br/><br/>*Discussion:* In prior releases, the code &quot;SUGG&quot; (suggests) was expressed as &quot;an inversion of the reason link.&quot; That code has been retired in favor of the inversion indicator that is an attribute of ActRelationship.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-MITGT\">MITGT</a></td><td style=\"color: #cccccc\">mitigates</td><td>The source act removes or lessens the occurrence or effect of the target act.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-CIND\">CIND</a></td><td style=\"color: #cccccc\">has contra-indication</td><td>A contraindication is just a negation of a reason, i.e. it gives a condition under which the action is not to be done. Both, source and target can be any kind of service; target service is in criterion mood. How the strength of a contraindication is expressed (e.g., relative, absolute) is left as an open issue. The priorityNumber attribute could be used.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-PRCN\">PRCN</a></td><td style=\"color: #cccccc\">has pre-condition</td><td>A requirement to be true before a service is performed. The target can be any service in criterion mood. For multiple pre-conditions a conjunction attribute (AND, OR, XOR) is applicable.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-TRIG\">TRIG</a></td><td style=\"color: #cccccc\">has trigger</td><td>A pre-condition that if true should result in the source Act being executed. The target is in typically in criterion mood. When reported after the fact (i.e. the criterion has been met) it may be in Event mood. A delay between the trigger and the triggered action can be specified.<br/><br/>*Discussion:* This includes the concept of a required act for a service or financial instrument such as an insurance plan or policy. In such cases, the trigger is the occurrence of a specific condition such as coverage limits being exceeded.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-COMP\">COMP</a></td><td style=\"color: #cccccc\">has component</td><td>The target act is a component of the source act, with no semantics regarding composition or aggregation implied.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-ARR\">ARR</a></td><td style=\"color: #cccccc\">arrival</td><td>The relationship that links to a Transportation Act (target) from another Act (source) indicating that the subject of the source Act entered into the source Act by means of the target Transportation act.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-CTRLV\">CTRLV</a></td><td style=\"color: #cccccc\">has control variable</td><td>A relationship from an Act to a Control Variable. For example, if a Device makes an Observation, this relates the Observation to its Control Variables documenting the device's settings that influenced the observation.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-DEP\">DEP</a></td><td style=\"color: #cccccc\">departure</td><td>The relationship that links to a Transportation Act (target) from another Act (source) indicating that the subject of the source Act departed from the source Act by means of the target Transportation act.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-OBJC\">OBJC</a></td><td style=\"color: #cccccc\">has continuing objective</td><td>A desired state that a service action aims to maintain. E.g., keep systolic blood pressure between 90 and 110 mm Hg. Source is an intervention service. Target must be an observation in criterion mood.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-OBJF\">OBJF</a></td><td style=\"color: #cccccc\">has final objective</td><td>A desired outcome that a service action aims to meet finally. Source is any service (typically an intervention). Target must be an observation in criterion mood.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-OUTC\">OUTC</a></td><td style=\"color: #cccccc\">has outcome</td><td>An observation that should follow or does actually follow as a result or consequence of a condition or action (sometimes called &quot;post-conditional&quot;.) Target must be an observation as a goal, risk or any criterion. For complex outcomes a conjunction attribute (AND, OR, XOR) can be used. An outcome link is often inverted to describe an outcome assessment.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-GOAL\">GOAL</a></td><td style=\"color: #cccccc\">has goal</td><td>A goal that one defines given a patient's health condition. Subsequently planned actions aim to meet that goal. Source is an observation or condition node, target must be an observation in goal mood.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-RISK\">RISK</a></td><td style=\"color: #cccccc\">has risk</td><td>A noteworthy undesired outcome of a patient's condition that is either likely enough to become an issue or is less likely but dangerous enough to be addressed.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-CHRG\">CHRG</a></td><td style=\"color: #cccccc\">has charge</td><td>A relationship that provides an ability to associate a financial transaction (target) as a charge to a clinical act (source). A clinical act may have a charge associated with the execution or delivery of the service.<br/><br/>The financial transaction will define the charge (bill) for delivery or performance of the service.<br/><br/>Charges and costs are distinct terms. A charge defines what is charged or billed to another organization or entity within an organization. The cost defines what it costs an organization to perform or deliver a service or product.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-COST\">COST</a></td><td style=\"color: #cccccc\">has cost</td><td>A relationship that provides an ability to associate a financial transaction (target) as a cost to a clinical act (source). A clinical act may have an inherit cost associated with the execution or delivery of the service.<br/><br/>The financial transaction will define the cost of delivery or performance of the service.<br/><br/>Charges and costs are distinct terms. A charge defines what is charged or billed to another organization or entity within an organization. The cost defines what it costs an organization to perform or deliver a service or product.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-CREDIT\">CREDIT</a></td><td style=\"color: #cccccc\">has credit</td><td>A credit relationship ties a financial transaction (target) to an account (source). A credit, once applied (posted), may have either a positive or negative effect on the account balance, depending on the type of account. An asset account credit will decrease the account balance. A non-asset account credit will decrease the account balance.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-DEBIT\">DEBIT</a></td><td style=\"color: #cccccc\">has debit</td><td>A debit relationship ties a financial transaction (target) to an account (source). A debit, once applied (posted), may have either a positive or negative effect on the account balance, depending on the type of account. An asset account debit will increase the account balance. A non-asset account debit will decrease the account balance.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-SAS\">SAS</a></td><td style=\"color: #cccccc\">starts after start of</td><td>The source Act starts after the start of the target Act (i.e. if we say &quot;ActOne SAS ActTwo&quot;, it means that ActOne starts after the start of ActTwo, therefore ActOne is the source and ActTwo is the target).<br/><br/>*UsageNote:* Inverse code is **SBS**</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-SPRT\">SPRT</a></td><td style=\"color: #cccccc\">has support</td><td>Used to indicate that an existing service is suggesting evidence for a new observation. The assumption of support is attributed to the same actor who asserts the observation. Source must be an observation, target may be any service (e.g., to indicate a status post).</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-SPRTBND\">SPRTBND</a></td><td style=\"color: #cccccc\">has bounded support</td><td>A specialization of &quot;has support&quot; (SPRT), used to relate a secondary observation to a Region of Interest on a multidimensional observation, if the ROI specifies the true boundaries of the secondary observation as opposed to only marking the approximate area. For example, if the start and end of an ST elevation episode is visible in an EKG, this relation would indicate the ROI bounds the &quot;ST elevation&quot; observation -- the ROI defines the true beginning and ending of the episode. Conversely, if a ROI simply contains ST elevation, but it does not define the bounds (start and end) of the episode, the more general &quot;has support&quot; relation is used. Likewise, if a ROI on an image defines the true bounds of a &quot;1st degree burn&quot;, the relation &quot;has bounded support&quot; is used; but if the ROI only points to the approximate area of the burn, the general &quot;has support&quot; relation is used.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-PERT\">PERT</a></td><td style=\"color: #cccccc\">has pertinent information</td><td>This is a very unspecific relationship from one item of clinical information to another. It does not judge about the role the pertinent information plays.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-AUTH\">AUTH</a></td><td style=\"color: #cccccc\">authorized by</td><td>A relationship in which the target act authorizes or certifies the source act.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-CAUS\">CAUS</a></td><td style=\"color: #cccccc\">is etiology for</td><td>**Description:** An assertion that an act was the cause of another act.This is stronger and more specific than the support link. The source (cause) is typically an observation, but may be any act, while the target may be any act.<br/><br/>**Examples:**<br/><br/> *  a growth of Staphylococcus aureus may be considered the cause of an abscess<br/> *  contamination of the infusion bag was deemed to be the cause of the infection that the patient experienced<br/> *  lack of staff on the shift was deemed to be a supporting factor (proximal factor) causing the patient safety incident where the patient fell out of bed because the bed-sides had not been put up which caused the night patient to fall out of bed</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-COVBY\">COVBY</a></td><td style=\"color: #cccccc\">covered by</td><td>A relationship in which the source act is covered by or is under the authority of a target act. A financial instrument such as an Invoice Element is covered by one or more specific instances of an Insurance Policy.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-DRIV\">DRIV</a></td><td style=\"color: #cccccc\">is derived from</td><td>Associates a derived Act with its input parameters. E.G., an anion-gap observation can be associated as being derived from given sodium-, (potassium-,), chloride-, and bicarbonate-observations. The narrative content (Act.text) of a source act is wholly machine-derived from the collection of target acts.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-EXPL\">EXPL</a></td><td style=\"color: #cccccc\">has explanation</td><td>This is the inversion of support. Used to indicate that a given observation is explained by another observation or condition.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-ITEMSLOC\">ITEMSLOC</a></td><td style=\"color: #cccccc\">items located</td><td>Items located</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-LIMIT\">LIMIT</a></td><td style=\"color: #cccccc\">limited by</td><td>A relationship that limits or restricts the source act by the elements of the target act. For example, an authorization may be limited by a financial amount (up to $500). Target Act must be in EVN.CRIT mood.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-MFST\">MFST</a></td><td style=\"color: #cccccc\">is manifestation of</td><td>An assertion that a new observation may be the manifestation of another existing observation or action. This assumption is attributed to the same actor who asserts the manifestation. This is stronger and more specific than an inverted support link. For example, an agitated appearance can be asserted to be the manifestation (effect) of a known hyperthyroxia. This expresses that one might not have realized a symptom if it would not be a common manifestation of a known condition. The target (cause) may be any service, while the source (manifestation) must be an observation.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-NAME\">NAME</a></td><td style=\"color: #cccccc\">assigns name</td><td>Used to assign a &quot;name&quot; to a condition thread. Source is a condition node, target can be any service.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-PREV\">PREV</a></td><td style=\"color: #cccccc\">has previous instance</td><td>A relationship in which the target act is a predecessor instance to the source act. Generally each of these instances is similar, but no identical. In healthcare coverage it is used to link a claim item to a previous claim item that might have claimed for the same set of services.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-REFR\">REFR</a></td><td style=\"color: #cccccc\">refers to</td><td>A relationship in which the target act is referred to by the source act. This permits a simple reference relationship that distinguishes between the referent and the referee.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-REFV\">REFV</a></td><td style=\"color: #cccccc\">has reference values</td><td>Reference ranges are essentially descriptors of a class of result values assumed to be &quot;normal&quot;, &quot;abnormal&quot;, or &quot;critical.&quot; Those can vary by sex, age, or any other criterion. Source and target are observations, the target is in criterion mood. This link type can act as a trigger in case of alarms being triggered by critical results.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-SUBJ\">SUBJ</a></td><td style=\"color: #cccccc\">has subject</td><td>Relates an Act to its subject Act that the first Act is primarily concerned with.<br/><br/>Examples<br/><br/>1.  The first Act may be a ControlAct manipulating the subject Act<br/>2.  The first act is a region of interest (ROI) that defines a region within the subject Act.<br/>3.  The first act is a reporting or notification Act, that echos the subject Act for a specific new purpose.<br/><br/>Constraints<br/><br/>An Act may have multiple subject acts.<br/><br/>Rationale<br/><br/>The ActRelationshipType &quot;has subject&quot; is similar to the ParticipationType &quot;subject&quot;, Acts that primarily operate on physical subjects use the Participation, those Acts that primarily operate on other Acts (other information) use the ActRelationship.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-SUMM\">SUMM</a></td><td style=\"color: #cccccc\">summarized by</td><td>An act that contains summary values for a list or set of subordinate acts. For example, a summary of transactions for a particular accounting period.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-XCRPT\">XCRPT</a></td><td style=\"color: #cccccc\">Excerpts</td><td>The source is an excerpt from the target.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-VRXCRPT\">VRXCRPT</a></td><td style=\"color: #cccccc\">Excerpt verbatim</td><td>The source is a direct quote from the target.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-FLFS\">FLFS</a></td><td style=\"color: #cccccc\">fulfills</td><td>The source act fulfills (in whole or in part) the target act. Source act must be in a mood equal or more actual than the target act.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-OCCR\">OCCR</a></td><td style=\"color: #cccccc\">occurrence</td><td>The source act is a single occurrence of a repeatable target act. The source and target act can be in any mood on the &quot;completion track&quot; but the source act must be as far as or further along the track than the target act (i.e., the occurrence of an intent can be an event but not vice versa).</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-OREF\">OREF</a></td><td style=\"color: #cccccc\">references order</td><td>Relates either an appointment request or an appointment to the order for the service being scheduled.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-SCH\">SCH</a></td><td style=\"color: #cccccc\">schedules request</td><td>Associates a specific time (and associated resources) with a scheduling request or other intent.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-RPLC\">RPLC</a></td><td style=\"color: #cccccc\">replaces</td><td>A replacement source act replaces an existing target act. The state of the target act being replaced becomes obselete, but the act is typically still retained in the system for historical reference. The source and target must be of the same type.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-SUCC\">SUCC</a></td><td style=\"color: #cccccc\">succeeds</td><td>**Definition:** A new act that carries forward the intention of the original act, but does not completely replace it. The status of the predecessor act must be 'completed'. The original act is the target act and the successor is the source act.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-SEQL\">SEQL</a></td><td style=\"color: #cccccc\">is sequel</td><td>An act relationship indicating that the source act follows the target act. The source act should in principle represent the same kind of act as the target. Source and target need not have the same mood code (mood will often differ). The target of a sequel is called antecedent. Examples for sequel relationships are: revision, transformation, derivation from a prototype (as a specialization is a derivation of a generalization), followup, realization, instantiation.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-APND\">APND</a></td><td style=\"color: #cccccc\">is appendage</td><td>An addendum (source) to an existing service object (target), containing supplemental information. The addendum is itself an original service object linked to the supplemented service object. The supplemented service object remains in place and its content and status are unaltered.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-DOC\">DOC</a></td><td style=\"color: #cccccc\">documents</td><td>The source act documents the target act.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-ELNK\">ELNK</a></td><td style=\"color: #cccccc\">episodeLink</td><td>Expresses an association that links two instances of the same act over time, indicating that the instance are part of the same episode, e.g. linking two condition nodes for episode of illness; linking two encounters for episode of encounter.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-GEN\">GEN</a></td><td style=\"color: #cccccc\">has generalization</td><td>The generalization relationship can be used to express categorical knowledge about services (e.g., amilorid, triamterene, and spironolactone have the common generalization potassium sparing diuretic).</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-GEVL\">GEVL</a></td><td style=\"color: #cccccc\">evaluates (goal)</td><td>A goal-evaluation links an observation (intent or actual) to a goal to indicate that the observation evaluates the goal. Given the goal and the observation, a &quot;goal distance&quot; (e.g., goal to observation) can be &quot;calculated&quot; and need not be sent explicitly.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-INST\">INST</a></td><td style=\"color: #cccccc\">instantiates (master)</td><td>Used to capture the link between a potential service (&quot;master&quot; or plan) and an actual service, where the actual service instantiates the potential service. The instantiation may override the master's defaults.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-MTCH\">MTCH</a></td><td style=\"color: #cccccc\">matches (trigger)</td><td>A trigger-match links an actual service (e.g., an observation or procedure that took place) with a service in criterion mood. For example if the trigger is &quot;observation of pain&quot; and pain is actually observed, and if that pain-observation caused the trigger to fire, that pain-observation can be linked with the trigger.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-OPTN\">OPTN</a></td><td style=\"color: #cccccc\">has option</td><td>A relationship between a source Act that provides more detailed properties to the target Act.<br/><br/>The source act thus is a specialization of the target act, but instead of mentioning all the inherited properties it only mentions new property bindings or refinements.<br/><br/>The typical use case is to specify certain alternative variants of one kind of Act. The priorityNumber attribute is used to weigh refinements as preferred over other alternative refinements.<br/><br/>Example: several routing options for a drug are specified as one SubstanceAdministration for the general treatment with attached refinements for the various routing options.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-REV\">REV</a></td><td style=\"color: #cccccc\">reverses</td><td>A relationship between a source Act that seeks to reverse or undo the action of the prior target Act.<br/><br/>Example: A posted financial transaction (e.g., a debit transaction) was applied in error and must be reversed (e.g., by a credit transaction) the credit transaction is identified as an undo (or reversal) of the prior target transaction.<br/><br/>Constraints: the &quot;completion track&quot; mood of the target Act must be equally or more &quot;actual&quot; than the source act. I.e., when the target act is EVN the source act can be EVN, or any INT. If the target act is INT, the source act can be INT.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-UPDT\">UPDT</a></td><td style=\"color: #cccccc\">updates (condition)</td><td>A condition thread relationship specifically links condition nodes together to form a condition thread. The source is the new condition node and the target links to the most recent node of the existing condition thread.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-XFRM\">XFRM</a></td><td style=\"color: #cccccc\">transformation</td><td>Used when the target Act is a transformation of the source Act. (For instance, used to show that a CDA document is a transformation of a DICOM SR document.)</td></tr></table></li></ul></div>"},"url":"http://hl7.org/cda/stds/core/ValueSet/CDAActRelationshipType","version":"2.0.2-sd","name":"CDAActRelationshipType","title":"CDAActRelationshipType","status":"draft","experimental":false,"date":"2025-12-12T15:26:32+11:00","publisher":"Health Level 7","contact":[{"name":"HL7 International - Structured Documents","telecom":[{"system":"url","value":"http://www.hl7.org/Special/committees/structure"},{"system":"email","value":"structdog@lists.HL7.org"}]}],"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.","compose":{"include":[{"system":"http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType","concept":[{"code":"RSON"},{"code":"MITGT"},{"code":"CIND"},{"code":"PRCN"},{"code":"TRIG"},{"code":"COMP"},{"code":"ARR"},{"code":"CTRLV"},{"code":"DEP"},{"code":"OBJC"},{"code":"OBJF"},{"code":"OUTC"},{"code":"GOAL"},{"code":"RISK"},{"code":"CHRG"},{"code":"COST"},{"code":"CREDIT"},{"code":"DEBIT"},{"code":"SAS"},{"code":"SPRT"},{"code":"SPRTBND"},{"code":"PERT"},{"code":"AUTH"},{"code":"CAUS"},{"code":"COVBY"},{"code":"DRIV"},{"code":"EXPL"},{"code":"ITEMSLOC"},{"code":"LIMIT"},{"code":"MFST"},{"code":"NAME"},{"code":"PREV"},{"code":"REFR"},{"code":"REFV"},{"code":"SUBJ"},{"code":"SUMM"},{"code":"XCRPT"},{"code":"VRXCRPT"},{"code":"FLFS"},{"code":"OCCR"},{"code":"OREF"},{"code":"SCH"},{"code":"RPLC"},{"code":"SUCC"},{"code":"SEQL"},{"code":"APND"},{"code":"DOC"},{"code":"ELNK"},{"code":"GEN"},{"code":"GEVL"},{"code":"INST"},{"code":"MTCH"},{"code":"OPTN"},{"code":"REV"},{"code":"UPDT"},{"code":"XFRM"}]}]}}

package/ValueSet-CDAActSubstanceAdministrationCode.json

@@ -0,0 +1 @@
+{"resourceType":"ValueSet","id":"CDAActSubstanceAdministrationCode","text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet CDAActSubstanceAdministrationCode</b></p><a name=\"CDAActSubstanceAdministrationCode\"> </a><a name=\"hcCDAActSubstanceAdministrationCode\"> </a><ul><li>Include these codes as defined in <a href=\"http://tx.fhir.org/r5\"><code>http://terminology.hl7.org/CodeSystem/v3-ActCode</code></a><span title=\"Version is explicitly stated to be 7.0.0\"> version &#x1F4CD;9.0.0</span><table class=\"none\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td></tr><tr><td>DRUG</td><td/></tr><tr><td>FD</td><td/></tr><tr><td>IMMUNIZ</td><td/></tr><tr><td>BOOSTER</td><td/></tr><tr><td>INITIMMUNIZ</td><td/></tr></table></li></ul></div>"},"url":"http://hl7.org/cda/stds/core/ValueSet/CDAActSubstanceAdministrationCode","version":"2.0.2-sd","name":"CDAActSubstanceAdministrationCode","title":"CDAActSubstanceAdministrationCode","status":"draft","experimental":false,"date":"2025-12-12T15:26:32+11:00","publisher":"Health Level 7","contact":[{"name":"HL7 International - Structured Documents","telecom":[{"system":"url","value":"http://www.hl7.org/Special/committees/structure"},{"system":"email","value":"structdog@lists.HL7.org"}]}],"description":"Describes the type of substance administration being performed.","compose":{"include":[{"system":"http://terminology.hl7.org/CodeSystem/v3-ActCode","version":"7.0.0","concept":[{"code":"DRUG"},{"code":"FD"},{"code":"IMMUNIZ"},{"code":"BOOSTER"},{"code":"INITIMMUNIZ"}]}]}}

package/ValueSet-CDACompressionAlgorithm.json

@@ -0,0 +1 @@
+{"resourceType":"ValueSet","id":"CDACompressionAlgorithm","text":{"status":"extensions","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet CDACompressionAlgorithm</b></p><a name=\"CDACompressionAlgorithm\"> </a><a name=\"hcCDACompressionAlgorithm\"> </a><ul><li>Include these codes as defined in <a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-CompressionAlgorithm.html\"><code>http://terminology.hl7.org/CodeSystem/v3-CompressionAlgorithm</code></a><span title=\"Version is explicitly stated to be 2.1.1\"> version &#x1F4CD;2.1.1</span><table class=\"none\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-CompressionAlgorithm.html#v3-CompressionAlgorithm-DF\">DF</a></td><td style=\"color: #cccccc\">deflate</td><td>The deflate compressed data format as specified in RFC 1951 \\[http://www.ietf.org/rfc/rfc1951.txt\\].</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-CompressionAlgorithm.html#v3-CompressionAlgorithm-GZ\">GZ</a></td><td style=\"color: #cccccc\">gzip</td><td>A compressed data format that is compatible with the widely used GZIP utility as specified in RFC 1952 \\[http://www.ietf.org/rfc/rfc1952.txt\\] (uses the deflate algorithm).</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-CompressionAlgorithm.html#v3-CompressionAlgorithm-ZL\">ZL</a></td><td style=\"color: #cccccc\">zlib</td><td>A compressed data format that also uses the deflate algorithm. Specified as RFC 1950 \\[http://www.ietf.org/rfc/rfc1952.txt\\]</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-CompressionAlgorithm.html#v3-CompressionAlgorithm-Z\">Z</a></td><td style=\"color: #cccccc\">compress</td><td>Original UNIX compress algorithm and file format using the LZC algorithm (a variant of LZW). Patent encumbered and less efficient than deflate.</td></tr></table></li></ul></div>"},"url":"http://hl7.org/cda/stds/core/ValueSet/CDACompressionAlgorithm","version":"2.0.2-sd","name":"CDACompressionAlgorithm","title":"CDACompressionAlgorithm","status":"draft","experimental":false,"date":"2025-12-12T15:26:32+11:00","publisher":"Health Level 7","contact":[{"name":"HL7 International - Structured Documents","telecom":[{"system":"url","value":"http://www.hl7.org/Special/committees/structure"},{"system":"email","value":"structdog@lists.HL7.org"}]}],"description":"Type of compression algorithm used - limited to 4 concepts from original CDA definition","compose":{"include":[{"system":"http://terminology.hl7.org/CodeSystem/v3-CompressionAlgorithm","version":"2.1.1","concept":[{"code":"DF"},{"code":"GZ"},{"code":"ZL"},{"code":"Z"}]}]}}

package/ValueSet-CDAContextControl.json

@@ -0,0 +1 @@
+{"resourceType":"ValueSet","id":"CDAContextControl","text":{"status":"extensions","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet CDAContextControl</b></p><a name=\"CDAContextControl\"> </a><a name=\"hcCDAContextControl\"> </a><ul><li>Include these codes as defined in <a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ContextControl.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ContextControl</code></a><span title=\"Version is not explicitly stated, which means it is fixed to 2.1.0, the version found through the package references\"> version &#x1F4E6;2.1.0</span><table class=\"none\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ContextControl.html#v3-ContextControl-AN\">AN</a></td><td style=\"color: #cccccc\">additive, non-propagating</td><td>The association adds to the existing context associated with the Act, but will not propagate to any descendant Acts reached by conducting ActRelationships (see contextControlCode). Examples: If an 'Author' Participation were marked as &quot;Additive, Non-Propagating&quot; it means that the author will be added to the set of author participations that have propagated from ancestor Acts for the purpose of this Act. However only the previously propagated authors will propagate to any child Acts that allow context to be propagated.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ContextControl.html#v3-ContextControl-AP\">AP</a></td><td style=\"color: #cccccc\">additive, propagating</td><td>The association adds to the existing context associated with the Act, and will propagate to any descendant Acts reached by conducting ActRelationships (see contextControlCode). Examples: If an 'Author' Participation were marked as &quot;Additive, Propagating&quot; it means that the author will be added to the set of author participations that have propagated from ancestor Acts, and will itself propagate with the other authors to any child Acts that allow context to be propagated.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ContextControl.html#v3-ContextControl-ON\">ON</a></td><td style=\"color: #cccccc\">overriding, non-propagating</td><td>The association is added to the existing context associated with the Act, but overrides an association with the same typeCode. However, this overriding association will not propagate to any descendant Acts reached by conducting ActRelationships (see contextControlCode). Examples: If an 'Author' Participation were marked as &quot;Overriding, Non-Propagating&quot; it means that the author will replace the set of author participations that have propagated from ancestor Acts. Furthermore, no author participations whatsoever will propagate to any child Acts that allow context to be propagated.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-ContextControl.html#v3-ContextControl-OP\">OP</a></td><td style=\"color: #cccccc\">overriding, propagating</td><td>The association is added to the existing context associated with the Act, but overrides an association with the same typeCode. This overriding association will propagate to any descendant Acts reached by conducting ActRelationships (see contextControlCode). Examples: If an 'Author' Participation were marked as &quot;Overriding, Propagating&quot; it means that the author will replace the set of author participations that have propagated from ancestor Acts, and will itself be the only author to propagate to any child Acts that allow context to be propagated.</td></tr></table></li></ul></div>"},"url":"http://hl7.org/cda/stds/core/ValueSet/CDAContextControl","version":"2.0.2-sd","name":"CDAContextControl","title":"CDAContextControl","status":"draft","experimental":false,"date":"2025-12-12T15:26:32+11:00","publisher":"Health Level 7","contact":[{"name":"HL7 International - Structured Documents","telecom":[{"system":"url","value":"http://www.hl7.org/Special/committees/structure"},{"system":"email","value":"structdog@lists.HL7.org"}]}],"description":"A code that specifies how an ActRelationship or Participation contributes to the context of an Act, and whether it may be propagated to descendent Acts whose association allows such propagation.","compose":{"include":[{"system":"http://terminology.hl7.org/CodeSystem/v3-ContextControl","concept":[{"code":"AN"},{"code":"AP"},{"code":"ON"},{"code":"OP"}]}]}}

package/ValueSet-CDAEntityCode.json

@@ -0,0 +1 @@
+{"resourceType":"ValueSet","id":"CDAEntityCode","text":{"status":"extensions","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet CDAEntityCode</b></p><a name=\"CDAEntityCode\"> </a><a name=\"hcCDAEntityCode\"> </a><p>This value set includes codes based on the following rules:</p><ul><li>Import all the codes that are contained in <a href=\"ValueSet-CDAMaterialEntityClassType.html\">CDAMaterialEntityClassType</a></li><li>Include these codes as defined in <a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityCode.html\"><code>http://terminology.hl7.org/CodeSystem/v3-EntityCode</code></a><span title=\"Version is not explicitly stated, which means it is fixed to 2.1.0, the version found through the package references\"> version &#x1F4E6;2.1.0</span><table class=\"none\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityCode.html#v3-EntityCode-BED\">BED</a></td><td style=\"color: #cccccc\">Bed Location</td><td>The location of a bed</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityCode.html#v3-EntityCode-BLDG\">BLDG</a></td><td style=\"color: #cccccc\">Building Location</td><td>The location of a building</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityCode.html#v3-EntityCode-FLOOR\">FLOOR</a></td><td style=\"color: #cccccc\">Floor Location</td><td>The location of a floor of a building</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityCode.html#v3-EntityCode-ROOM\">ROOM</a></td><td style=\"color: #cccccc\">Room Location</td><td>The location of a room</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityCode.html#v3-EntityCode-WING\">WING</a></td><td style=\"color: #cccccc\">Wing Location</td><td>The location of a wing of a building (e.g. East Wing). The same room number for the same floor number can be distinguished by wing number in some situations</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityCode.html#v3-EntityCode-HHOLD\">HHOLD</a></td><td style=\"color: #cccccc\">household</td><td>The group of persons who occupy a single housing unit.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityCode.html#v3-EntityCode-NAT\">NAT</a></td><td style=\"color: #cccccc\">NationEntityType</td><td>Codes identifying nation states. Allows for finer grained specification of Entity with classcode &lt;= NAT<br/><br/>*Example:*ISO3166 country codes.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityCode.html#v3-EntityCode-RELIG\">RELIG</a></td><td style=\"color: #cccccc\">religious institution</td><td>An organization that provides religious rites of worship.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityCode.html#v3-EntityCode-PRAC\">PRAC</a></td><td style=\"color: #cccccc\">PractitionerGroup</td><td/></tr></table></li></ul></div>"},"url":"http://hl7.org/cda/stds/core/ValueSet/CDAEntityCode","version":"2.0.2-sd","name":"CDAEntityCode","title":"CDAEntityCode","status":"draft","experimental":false,"date":"2025-12-12T15:26:32+11:00","publisher":"Health Level 7","contact":[{"name":"HL7 International - Structured Documents","telecom":[{"system":"url","value":"http://www.hl7.org/Special/committees/structure"},{"system":"email","value":"structdog@lists.HL7.org"}]}],"description":"A value representing the specific kind of Entity the instance represents.","compose":{"include":[{"valueSet":["http://hl7.org/cda/stds/core/ValueSet/CDAMaterialEntityClassType"]},{"system":"http://terminology.hl7.org/CodeSystem/v3-EntityCode","concept":[{"code":"BED"},{"code":"BLDG"},{"code":"FLOOR"},{"code":"ROOM"},{"code":"WING"},{"code":"HHOLD"},{"code":"NAT"},{"code":"RELIG"},{"code":"PRAC"}]}]}}

package/ValueSet-CDAEntityNamePartQualifier.json

@@ -0,0 +1 @@
+{"resourceType":"ValueSet","id":"CDAEntityNamePartQualifier","text":{"status":"extensions","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet CDAEntityNamePartQualifier</b></p><a name=\"CDAEntityNamePartQualifier\"> </a><a name=\"hcCDAEntityNamePartQualifier\"> </a><ul><li>Include these codes as defined in <a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNamePartQualifier.html\"><code>http://terminology.hl7.org/CodeSystem/v3-EntityNamePartQualifier</code></a><span title=\"Version is not explicitly stated, which means it is fixed to 2.1.0, the version found through the package references\"> version &#x1F4E6;2.1.0</span><table class=\"none\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNamePartQualifier.html#v3-EntityNamePartQualifier-LS\">LS</a></td><td style=\"color: #cccccc\">Legal status</td><td>For organizations a suffix indicating the legal status, e.g., &quot;Inc.&quot;, &quot;Co.&quot;, &quot;AG&quot;, &quot;GmbH&quot;, &quot;B.V.&quot; &quot;S.A.&quot;, &quot;Ltd.&quot; etc.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNamePartQualifier.html#v3-EntityNamePartQualifier-AC\">AC</a></td><td style=\"color: #cccccc\">academic</td><td>Indicates that a prefix like &quot;Dr.&quot; or a suffix like &quot;M.D.&quot; or &quot;Ph.D.&quot; is an academic title.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNamePartQualifier.html#v3-EntityNamePartQualifier-NB\">NB</a></td><td style=\"color: #cccccc\">nobility</td><td>In Europe and Asia, there are still people with nobility titles (aristocrats). German &quot;von&quot; is generally a nobility title, not a mere voorvoegsel. Others are &quot;Earl of&quot; or &quot;His Majesty King of...&quot; etc. Rarely used nowadays, but some systems do keep track of this.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNamePartQualifier.html#v3-EntityNamePartQualifier-PR\">PR</a></td><td style=\"color: #cccccc\">professional</td><td>Primarily in the British Imperial culture people tend to have an abbreviation of their professional organization as part of their credential suffices.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNamePartQualifier.html#v3-EntityNamePartQualifier-VV\">VV</a></td><td style=\"color: #cccccc\">voorvoegsel</td><td>A Dutch &quot;voorvoegsel&quot; is something like &quot;van&quot; or &quot;de&quot; that might have indicated nobility in the past but no longer so. Similar prefixes exist in other languages such as Spanish, French or Portugese.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNamePartQualifier.html#v3-EntityNamePartQualifier-AD\">AD</a></td><td style=\"color: #cccccc\">adopted</td><td>The name the person was given at the time of adoption.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNamePartQualifier.html#v3-EntityNamePartQualifier-BR\">BR</a></td><td style=\"color: #cccccc\">birth</td><td>A name that a person had shortly after being born. Usually for family names but may be used to mark given names at birth that may have changed later.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNamePartQualifier.html#v3-EntityNamePartQualifier-SP\">SP</a></td><td style=\"color: #cccccc\">spouse</td><td>The name assumed from the partner in a marital relationship (hence the &quot;SP&quot;). Usually the spouse's family name. Note that no inference about gender can be made from the existence of spouse names.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNamePartQualifier.html#v3-EntityNamePartQualifier-CL\">CL</a></td><td style=\"color: #cccccc\">callme</td><td>A callme name is (usually a given name) that is preferred when a person is directly addressed.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNamePartQualifier.html#v3-EntityNamePartQualifier-IN\">IN</a></td><td style=\"color: #cccccc\">initial</td><td>Indicates that a name part is just an initial. Initials do not imply a trailing period since this would not work with non-Latin scripts. Initials may consist of more than one letter, e.g., &quot;Ph.&quot; could stand for &quot;Philippe&quot; or &quot;Th.&quot; for &quot;Thomas&quot;.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNamePartQualifier.html#v3-EntityNamePartQualifier-TITLE\">TITLE</a></td><td style=\"color: #cccccc\">title</td><td>Indicates that a prefix or a suffix is a title that applies to the whole name, not just the adjacent name part.</td></tr></table></li></ul></div>"},"url":"http://hl7.org/cda/stds/core/ValueSet/CDAEntityNamePartQualifier","version":"2.0.2-sd","name":"CDAEntityNamePartQualifier","title":"CDAEntityNamePartQualifier","status":"draft","experimental":false,"date":"2025-12-12T15:26:32+11:00","publisher":"Health Level 7","contact":[{"name":"HL7 International - Structured Documents","telecom":[{"system":"url","value":"http://www.hl7.org/Special/committees/structure"},{"system":"email","value":"structdog@lists.HL7.org"}]}],"description":"Qualifies parts of names","compose":{"include":[{"system":"http://terminology.hl7.org/CodeSystem/v3-EntityNamePartQualifier","concept":[{"code":"LS"},{"code":"AC"},{"code":"NB"},{"code":"PR"},{"code":"VV"},{"code":"AD"},{"code":"BR"},{"code":"SP"},{"code":"CL"},{"code":"IN"},{"code":"TITLE"}]}]}}

package/ValueSet-CDAEntityNameUse.json

@@ -0,0 +1 @@
+{"resourceType":"ValueSet","id":"CDAEntityNameUse","text":{"status":"extensions","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet CDAEntityNameUse</b></p><a name=\"CDAEntityNameUse\"> </a><a name=\"hcCDAEntityNameUse\"> </a><ul><li>Include these codes as defined in <a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNameUse.html\"><code>http://terminology.hl7.org/CodeSystem/v3-EntityNameUse</code></a><span title=\"Version is explicitly stated to be 2.1.0\"> version &#x1F4CD;2.1.0</span><table class=\"none\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNameUse.html#v3-EntityNameUse-C\">C</a></td><td style=\"color: #cccccc\">License</td><td>As recorded on a license, record, certificate, etc. (only if different from legal name)</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNameUse.html#v3-EntityNameUse-L\">L</a></td><td style=\"color: #cccccc\">Legal</td><td>Known as/conventional/the one you use</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNameUse.html#v3-EntityNameUse-I\">I</a></td><td style=\"color: #cccccc\">Indigenous/Tribal</td><td>e.g. Chief Red Cloud</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNameUse.html#v3-EntityNameUse-P\">P</a></td><td style=\"color: #cccccc\">pseudonym</td><td>A self asserted name that the person is using or has used.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNameUse.html#v3-EntityNameUse-A\">A</a></td><td style=\"color: #cccccc\">Artist/Stage</td><td>Includes writer's pseudonym, stage name, etc</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNameUse.html#v3-EntityNameUse-R\">R</a></td><td style=\"color: #cccccc\">Religious</td><td>e.g. Sister Mary Francis, Brother John</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNameUse.html#v3-EntityNameUse-SRCH\">SRCH</a></td><td style=\"color: #cccccc\">search</td><td>A name intended for use in searching or matching.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNameUse.html#v3-EntityNameUse-PHON\">PHON</a></td><td style=\"color: #cccccc\">phonetic</td><td>A name spelled phonetically.<br/><br/>There are a variety of phonetic spelling algorithms. This code value does not distinguish between these.*Discussion:*</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNameUse.html#v3-EntityNameUse-SNDX\">SNDX</a></td><td style=\"color: #cccccc\">Soundex</td><td>A name spelled according to the SoundEx algorithm.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNameUse.html#v3-EntityNameUse-ASGN\">ASGN</a></td><td style=\"color: #cccccc\">assigned</td><td>A name assigned to a person. Reasons some organizations assign alternate names may include not knowing the person's name, or to maintain anonymity. Some, but not necessarily all, of the name types that people call &quot;alias&quot; may fit into this category.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNameUse.html#v3-EntityNameUse-ABC\">ABC</a></td><td style=\"color: #cccccc\">Alphabetic</td><td>Alphabetic transcription of name (Japanese: romaji)</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNameUse.html#v3-EntityNameUse-SYL\">SYL</a></td><td style=\"color: #cccccc\">Syllabic</td><td>Syllabic transcription of name (e.g., Japanese kana, Korean hangul)</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-EntityNameUse.html#v3-EntityNameUse-IDE\">IDE</a></td><td style=\"color: #cccccc\">Ideographic</td><td>Ideographic representation of name (e.g., Japanese kanji, Chinese characters)</td></tr></table></li></ul></div>"},"url":"http://hl7.org/cda/stds/core/ValueSet/CDAEntityNameUse","version":"2.0.2-sd","name":"CDAEntityNameUse","title":"CDAEntityNameUse","status":"draft","experimental":false,"date":"2025-12-12T15:26:32+11:00","publisher":"Health Level 7","contact":[{"name":"HL7 International - Structured Documents","telecom":[{"system":"url","value":"http://www.hl7.org/Special/committees/structure"},{"system":"email","value":"structdog@lists.HL7.org"}]}],"description":"A set of codes advising a system or user which name in a set of names to select for a given purpose - limited to values allowed in original CDA definition","compose":{"include":[{"system":"http://terminology.hl7.org/CodeSystem/v3-EntityNameUse","version":"2.1.0","concept":[{"code":"C"},{"code":"L"},{"code":"I"},{"code":"P"},{"code":"A"},{"code":"R"},{"code":"SRCH"},{"code":"PHON"},{"code":"SNDX"},{"code":"ASGN"},{"code":"ABC"},{"code":"SYL"},{"code":"IDE"}]}]}}

package/ValueSet-CDAInformationRecipientRole.json

@@ -0,0 +1 @@
+{"resourceType":"ValueSet","id":"CDAInformationRecipientRole","text":{"status":"extensions","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet CDAInformationRecipientRole</b></p><a name=\"CDAInformationRecipientRole\"> </a><a name=\"hcCDAInformationRecipientRole\"> </a><ul><li>Include these codes as defined in <a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-RoleClass.html\"><code>http://terminology.hl7.org/CodeSystem/v3-RoleClass</code></a><span title=\"Version is explicitly stated to be 3.1.0\"> version &#x1F4CD;3.1.0</span><table class=\"none\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-RoleClass.html#v3-RoleClass-ASSIGNED\">ASSIGNED</a></td><td style=\"color: #cccccc\">assigned entity</td><td>An agent role in which the agent is an Entity acting in the employ of an organization. The focus is on functional role on behalf of the organization, unlike the Employee role where the focus is on the 'Human Resources' relationship between the employee and the organization.</td></tr><tr><td><a href=\"http://terminology.hl7.org/5.2.0/CodeSystem-v3-RoleClass.html#v3-RoleClass-HLTHCHRT\">HLTHCHRT</a></td><td style=\"color: #cccccc\">health chart</td><td>The role of a material (player) that is the physical health chart belonging to an organization (scoper).</td></tr></table></li></ul></div>"},"url":"http://hl7.org/cda/stds/core/ValueSet/CDAInformationRecipientRole","version":"2.0.2-sd","name":"CDAInformationRecipientRole","title":"CDAInformationRecipientRole","status":"draft","experimental":false,"date":"2025-12-12T15:26:32+11:00","publisher":"Health Level 7","contact":[{"name":"HL7 International - Structured Documents","telecom":[{"system":"url","value":"http://www.hl7.org/Special/committees/structure"},{"system":"email","value":"structdog@lists.HL7.org"}]}],"description":"Used to represent the role(s) of those who should receive a copy of a document - limited to values allowed in original CDA definition","compose":{"include":[{"system":"http://terminology.hl7.org/CodeSystem/v3-RoleClass","version":"3.1.0","concept":[{"code":"ASSIGNED"},{"code":"HLTHCHRT"}]}]}}