Terminology| Vocabulary Work Group | Maturity Level: N/A | Standards Status: Informative |
Raw XML (canonical form + also see XML Format Specification)
**** MISSING DEFINITIONS ****
<?xml version="1.0" encoding="UTF-8"?> <CodeSystem xmlns="http://hl7.org/fhir"> <id value="v3-ActClass"/> <meta> <lastUpdated value="2018-08-12T00:00:00.000+00:00"/> </meta> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <p> Release Date: 2018-08-12</p> <table class="grid"> <tr> <td> <b> Level</b> </td> <td> <b> Code</b> </td> <td> <b> Display</b> </td> <td> <b> Definition</b> </td> </tr> <tr> <td> 1</td> <td> ACT <a name="v3-ActClass-ACT"> </a> </td> <td> 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/> 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/> 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/> 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/> One of the Participations that all acts have (at least implicitly) is a primary author, who is responsible of the Act and who "owns" 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/> In this sense, an Act-instance represents a "statement" 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 "a faithful record of what clinicians have heard, seen, thought, and done." Rector and Nowlan go on saying that "the other requirements for a medical record, e.g., that it be attributable and permanent, follow naturally from this view." 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/> 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 "speech-acts" 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/> 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 "sequel"). <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 "objective state of affairs" or "real processes" 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. <br/> </td> </tr> <tr> <td> 2</td> <td> <span style="color: grey"> <i> (_ActClassRecordOrganizer)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActClass-_ActClassRecordOrganizer"> </a> </td> <td> Used to group a set of acts sharing a common context. Organizer structures can nest within other context structures - such as where a document is contained within a folder, or a folder is contained within an EHR extract. <br/> </td> </tr> <tr> <td> 3</td> <td> COMPOSITION <a name="v3-ActClass-COMPOSITION"> </a> </td> <td> 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/> A composition represents part of a patient record originating from a single interaction between an authenticator and the record. <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/> A composition contains organizers and entries. <br/> </td> </tr> <tr> <td> 4</td> <td> DOC <a name="v3-ActClass-DOC"> </a> </td> <td> 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/> 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. <br/> </td> </tr> <tr> <td> 5</td> <td> DOCCLIN <a name="v3-ActClass-DOCCLIN"> </a> </td> <td> clinical document</td> <td> A clinical document is a documentation of clinical observations and services, with the following characteristics: <br/> Persistence - A clinical document continues to exist in an unaltered state, for a time period defined by local and regulatory requirements; <br/> Stewardship - A clinical document is maintained by a person or organization entrusted with its care; <br/> Potential for authentication - A clinical document is an assemblage of information that is intended to be legally authenticated; <br/> 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/> Human readability - A clinical document is human readable. <br/> </td> </tr> <tr> <td> 6</td> <td> CDALVLONE <a name="v3-ActClass-CDALVLONE"> </a> </td> <td> CDA Level One clinical document</td> <td> A clinical document that conforms to Level One of the HL7 Clinical Document Architecture (CDA) <br/> </td> </tr> <tr> <td> 3</td> <td> CONTAINER <a name="v3-ActClass-CONTAINER"> </a> </td> <td> record container</td> <td> Description: Container of clinical statements. Navigational. No semantic content. Knowledge of the section code is not required to interpret contained observations. Represents a heading in a heading structure, or "container tree". <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. <br/> </td> </tr> <tr> <td> 4</td> <td> CATEGORY <a name="v3-ActClass-CATEGORY"> </a> </td> <td> 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/> The distinction from Topic relates to value sets. For Category there is a bounded list of things like "Examination", "Diagnosis" or SOAP categories. For Topic the list is wide open to any clinical condition or reason for a part of an encounter. <br/> A CATEGORY MAY CONTAIN ENTRIES. <br/> </td> </tr> <tr> <td> 4</td> <td> DOCBODY <a name="v3-ActClass-DOCBODY"> </a> </td> <td> 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 <head> and <body> elements. <br/> </td> </tr> <tr> <td> 4</td> <td> DOCSECT <a name="v3-ActClass-DOCSECT"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td> 4</td> <td> TOPIC <a name="v3-ActClass-TOPIC"> </a> </td> <td> 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/> A topic may contain categories and entries. <br/> </td> </tr> <tr> <td> 3</td> <td> EXTRACT <a name="v3-ActClass-EXTRACT"> </a> </td> <td> 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/> 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/> An extract contains folders or compositions. <br/> An extract cannot contain another extract. <br/> </td> </tr> <tr> <td> 4</td> <td> EHR <a name="v3-ActClass-EHR"> </a> </td> <td> electronic health record</td> <td> A context that comprises all compositions. The EHR is an extract that includes the entire chart. <br/> NOTE: In an exchange scenario, an EHR is a specialization of an extract. <br/> </td> </tr> <tr> <td> 3</td> <td> FOLDER <a name="v3-ActClass-FOLDER"> </a> </td> <td> 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/> A folder contains compositions. <br/> Folders may be nested within folders. <br/> </td> </tr> <tr> <td> 3</td> <td> GROUPER <a name="v3-ActClass-GROUPER"> </a> </td> <td> grouper</td> <td> Definition: An ACT that organizes a set of component acts into a semantic grouping that share a particular context such as timeframe, patient, etc. <br/> UsageNotes: The focus in a GROUPER act is the grouping of the contained acts. For example "a request to group" (RQO), "a type of grouping that is allowed to occur" (DEF), etc. <br/> Unlike WorkingList, which represents a dynamic, shared, continuously updated collection to provide a "view" of a set of objects, GROUPER collections tend to be static and simply indicate a shared set of semantics. Note that sharing of semantics can be achieved using ACT as well. However, with GROUPER, the sole semantic is of grouping. <br/> </td> </tr> <tr> <td> 4</td> <td> CLUSTER <a name="v3-ActClass-CLUSTER"> </a> </td> <td> 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/> Discussion: The focus in a CLUSTER act is the grouping of the contained acts. For example "a request to cluster" (RQO), "a type of cluster that is allowed to occur" (DEF), etc. <br/> Examples: <br/> Radiologic investigations that might include administration of a dye, followed by radiographic observations; <br/> "Isolate cluster" 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. <br/> </td> </tr> <tr> <td> 2</td> <td> ACCM <a name="v3-ActClass-ACCM"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> ACCT <a name="v3-ActClass-ACCT"> </a> </td> <td> account</td> <td> A financial account established to track the net result of financial acts. <br/> </td> </tr> <tr> <td> 2</td> <td> ACSN <a name="v3-ActClass-ACSN"> </a> </td> <td> 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). <br/> </td> </tr> <tr> <td> 2</td> <td> ADJUD <a name="v3-ActClass-ADJUD"> </a> </td> <td> 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/> Adjudication results comprise 2 components: the adjudication processing results and a restated (or adjudicated) invoice or claim <br/> </td> </tr> <tr> <td> 2</td> <td> CACT <a name="v3-ActClass-CACT"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td> 3</td> <td> ACTN <a name="v3-ActClass-ACTN"> </a> </td> <td> action</td> <td> Sender asks addressee to do something depending on the focal Act of the payload. An example is "fulfill this order". 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). <br/> </td> </tr> <tr> <td> 3</td> <td> INFO <a name="v3-ActClass-INFO"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td> 3</td> <td> STC <a name="v3-ActClass-STC"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> CNTRCT <a name="v3-ActClass-CNTRCT"> </a> </td> <td> contract</td> <td> An agreement of obligation between two or more parties that is subject to contractual law and enforcement. <br/> </td> </tr> <tr> <td> 3</td> <td> FCNTRCT <a name="v3-ActClass-FCNTRCT"> </a> </td> <td> financial contract</td> <td> A contract whose value is measured in monetary terms. <br/> </td> </tr> <tr> <td> 4</td> <td> COV <a name="v3-ActClass-COV"> </a> </td> <td> coverage</td> <td> When used in the EVN mood, this concept means with respect to a covered party: <br/> A health care insurance policy or plan that is contractually binding between two or more parties; or <br/> A health care program, usually administered by government entities, that provides coverage to persons determined eligible under the terms of the program. <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. <br/> </td> </tr> <tr> <td> 2</td> <td> CONC <a name="v3-ActClass-CONC"> </a> </td> <td> concern</td> <td> Definition: A worry that tends to persist over time and has as its subject a state or process. The subject of the worry has the potential to require intervention or management. <br/> Examples: an observation result, procedure, substance administration, equipment repair status, device recall status, a health risk, a financial risk, public health risk, pregnancy, health maintenance, allergy, and acute or chronic illness. <br/> </td> </tr> <tr> <td> 3</td> <td> HCASE <a name="v3-ActClass-HCASE"> </a> </td> <td> public health case</td> <td> A public health case is a Concern about an observation or event that has a specific significance for public health. The creation of a PublicHealthCase initiates the tracking of the object of concern. The decision to track is related to but somewhat independent of the underlying event or observation. <br/> UsageNotes: Typically a Public Health Case 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. <br/> A public health case definition (Act.moodCode = "definition") 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. 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. <br/> </td> </tr> <tr> <td> 3</td> <td> OUTBR <a name="v3-ActClass-OUTBR"> </a> </td> <td> outbreak</td> <td> An Outbreak is a concern resulting from a series of public health cases. <br/> UsageNotes: 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. The effectiveTime attribute is used to convey the relevant dates for the case. An outbreak definition (Act.moodCode = "definition" includes the criteria for the number, types and occurrence pattern of cases necessary to declare an outbreak and to judge the severity of an outbreak. <br/> </td> </tr> <tr> <td> 2</td> <td> CONS <a name="v3-ActClass-CONS"> </a> </td> <td> 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/> 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/> The "signatures" to the consent document are represented electronically through Participation instances to the consent object. Typically an informed consent has Participation.typeCode of "performer", the healthcare provider informing the patient, and "consenter", 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/> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> CONTREG <a name="v3-ActClass-CONTREG"> </a> </td> <td> 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 <br/> </td> </tr> <tr> <td> 2</td> <td> CTTEVENT <a name="v3-ActClass-CTTEVENT"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> DISPACT <a name="v3-ActClass-DISPACT"> </a> </td> <td> 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/> Suspension, license restrictions, monetary fine, letter of reprimand, mandated training, mandated supervision, etc.Examples: <br/> </td> </tr> <tr> <td> 2</td> <td> EXPOS <a name="v3-ActClass-EXPOS"> </a> </td> <td> exposure</td> <td> An interaction between entities that provides opportunity for transmission of a physical, chemical, or biological agent from an exposure source entity to an exposure target entity. <br/> Examples: The following examples are provided to indicate what interactions are considered exposures rather than other types of Acts: <br/> A patient accidentally receives three times the recommended dose of their medication due to a dosing error. <br/> This is a substance administration. Public health and/or safety authorities may also be interested in documenting this with an associated exposure. <br/> A patient accidentally is dispensed an incorrect medicine (e.g., clomiphene instead of clomipramine). They have taken several doses before the mistake is detected. They are therefore "exposed" to a medicine that there was no therapeutic indication for them to receive. <br/> There are several substance administrations in this example. Public health and/or safety authorities may also be interested in documenting this with associated exposures. <br/> In a busy medical ward, a patient is receiving chemotherapy for a lymphoma. Unfortunately, the IV infusion bag containing the medicine splits, spraying cytotoxic medication over the patient being treated and the patient in the adjacent bed. <br/> There are three substance administrations in this example. The first is the intended one (IV infusion) with its associated (implicit) exposure. There is an incident with an associated substance administration to the same patient involving the medication sprayed over the patient as well as an associated exposure. Additionally, the incident includes a substance administration involving the spraying of medication on the adjacent patient, also with an associated exposure. <br/> A patient who is a refugee from a war-torn African nation arrives in a busy inner city A&E department suffering from a cough with bloody sputum. Not understanding the registration and triage process, they sit in the waiting room for several hours before it is noticed that they have not booked in. As soon as they are being processed, it is suspected that they are suffering from TB. Vulnerable (immunosuppressed) patients who were sharing the waiting room with this patient may have been exposed to the tubercule bacillus, and must be traced for investigation. <br/> This is an exposure (or possibly multiple exposures) in the waiting room involving the refugee and everyone else in the waiting room during the period. There might also be a number of known or presumed substance administrations (coughing) via several possible routes. The substance administrations are only hypotheses until confirmed by further testing. <br/> A patient who has received an elective total hip replacement procedure suffers a prolonged stay in hospital, due to contracting an MRSA infection in the surgical wound site after the surgery. <br/> This is an exposure to MRSA. Although there was some sort of substance administration, it's possible the exact mechanism for introduction of the MRSA into the wound will not be identified. <br/> Routine maintenance of the X-ray machines at a local hospital reveals a serious breach of the shielding on one of the machines. Patients who have undergone investigations using that machine in the last month are likely to have been exposed to significantly higher doses of X-rays than was intended, and must be tracked for possible adverse effects. <br/> There has been an exposure of each patient who used the machine in the past 30 days. Some patients may have had substance administrations. <br/> A new member of staff is employed in the laundry processing room of a small cottage hospital, and a misreading of the instructions for adding detergents results in fifty times the usual concentration of cleaning materials being added to a batch of hospital bedding. As a result, several patients have been exposed to very high levels of detergents still present in the "clean" bedding, and have experienced dermatological reactions to this. <br/> There has been an incident with multiple exposures to several patients. Although there are substance administrations involving the application of the detergent to the skin of the patients, it is expected that the substance administrations would not be directly documented. <br/> Seven patients who are residents in a health care facility for the elderly mentally ill have developed respiratory problems. After several months of various tests having been performed and various medications prescribed to these patients, the problem is traced to their being "sensitive" to a new fungicide used in the wall plaster of the ward where these patients reside. <br/> The patients have been continuously exposed to the fungicide. Although there have been continuous substance administrations (via breathing) this would not normally be documented as a substance administration. <br/> A patient with osteoarthritis of the knees is treated symptomatically using analgesia, paracetamol (acetaminophen) 1g up to four times a day for pain relief. His GP does not realize that the patient has, 20 years previously (while at college) had severe alcohol addiction problems, and now, although this is completely under control, his liver has suffered significantly, leaving him more sensitive to hepatic toxicity from paracetamol use. Later that year, the patient returns with a noticeable level of jaundice. Paracetamol is immediately withdrawn and alternative solutions for the knee pain are sought. The jaundice gradually subsides with conservative management, but referral to the gastroenterologist is required for advice and monitoring. <br/> There is a substance administration with an associated exposure. The exposure component is based on the relative toxic level of the substance to a patient with a compromised liver function. <br/> A patient goes to their GP complaining of abdominal pain, having been discharged from the local hospital ten days' previously after an emergency appendectomy. The GP can find nothing particularly amiss, and presumes it is post operative surgical pain that will resolve. The patient returns a fortnight later, when the GP prescribes further analgesia, but does decide to request an outpatient surgical follow-up appointment. At this post-surgical outpatient review, the registrar decides to order an ultrasound, which, when performed three weeks later, shows a small faint inexplicable mass. A laparoscopy is then performed, as a day case procedure, and a piece of a surgical swab is removed from the patient's abdominal cavity. Thankfully, a full recovery then takes place. <br/> This is a procedural sequelae. There may be an Incident recorded for this also. <br/> A patient is slightly late for a regular pacemaker battery check in the Cardiology department of the local hospital. They are hurrying down the second floor corridor. A sudden summer squall has recently passed over the area, and rain has come in through an open corridor window leaving a small puddle on the corridor floor. In their haste, the patient slips in the puddle and falls so badly that they have to be taken to the A&E department, where it is discovered on investigation they have slightly torn the cruciate ligament in their left knee. <br/> This is not an exposure. There has been an incident. <br/> Usage Notes: This class deals only with opportunity and not the outcome of the exposure; i.e. not all exposed parties will necessarily experience actual harm or benefit. <br/> Exposure differs from Substance Administration by the absence of the participation of a performer in the act. <br/> The following participations SHOULD be used with the following participations to distinguish the specific entities: <br/> The exposed entity participates via the "exposure target" (EXPTRGT) participation. <br/> An entity that has carried the agent transmitted in the exposure participates via the "exposure source" (EXSRC) participation. For example: <br/> a person or animal who carried an infectious disease and interacts (EXSRC) with another person or animal (EXPTRGT) transmitting the disease agent; <br/> a place or other environment (EXSRC) and a person or animal (EXPTRGT) who is exposed in the presence of this environment. <br/> When it is unknown whether a participating entity is the source of the agent (EXSRC) or the target of the transmission (EXPTRGT), the "exposure participant" (EXPART) is used. <br/> The physical (including energy), chemical or biological substance which is participating in the exposure uses the "exposure agent" (EXPAGNT) participation. There are at least three scenarios: <br/> the player of the Role that participates as EXPAGNT is the chemical or biological substance mixed or carried by the scoper-entity of the Role (e.g., ingredient role); or <br/> the player of the Role that participates as EXPAGNT is a mixture known to contain the chemical, radiological or biological substance of interest; or <br/> the player of the Role that participates as a EXPAGNT is known to carry the agent (i.e., the player is a fomite, vector, etc.). <br/> The Exposure.statusCode attribute should be interpreted as the state of the Exposure business object (e.g., active, aborted, completed) and not the clinical status of the exposure (e.g., probable, confirmed). The clinical status of the exposure should be associated with the exposure via a subject observation. <br/> Design Comment: The usage notes require a clear criterion for determining whether an act is an exposure or substance administration-deleterious potential, uncertainty of actual transmission, or otherwise. SBADM states that the criterion is the presence of a performer-but there are examples above that call this criterion into question (e.g., the first one, concerning a dosing error). <br/> </td> </tr> <tr> <td> 3</td> <td> AEXPOS <a name="v3-ActClass-AEXPOS"> </a> </td> <td> acquisition exposure</td> <td> Description: <br/> An acquisition exposure act describes the proximity (location and time) through which the participating entity was potentially exposed to a physical (including energy), chemical or biological agent from another entity. The acquisition exposure act is used in conjunction with transmission exposure acts as part of an analysis technique for contact tracing. Although an exposure can be decomposed into transmission and acquisition exposures, there is no requirement that all exposures be treated in this fashion. <br/> Constraints: The Acquisition Exposure inherits the participation constraints that apply to Exposure with the following exception. The EXPSRC (exposure source) participation must never be associated with the Transmission Exposure either directly or via context conduction. <br/> </td> </tr> <tr> <td> 3</td> <td> TEXPOS <a name="v3-ActClass-TEXPOS"> </a> </td> <td> transmission exposure</td> <td> Description: <br/> A transmission exposure act describes the proximity (time and location) over which the participating source entity was capable of transmitting a physical (including energy), chemical or biological substance agent to another entity. The transmission exposure act is used in conjunction with acquisition exposure acts as part of an analysis technique for contact tracing. Although an exposure can be decomposed into transmission and acquisition exposures, there is no requirement that all exposures be treated in this fashion. <br/> Constraints: The Transmission Exposure inherits the participation constraints that apply to Exposure with the following exception. The EXPTRGT (exposure target) participation must never be associated with the Transmission Exposure either directly or via context conduction. <br/> </td> </tr> <tr> <td> 2</td> <td> INC <a name="v3-ActClass-INC"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> INFRM <a name="v3-ActClass-INFRM"> </a> </td> <td> inform</td> <td> The act of transmitting information and understanding about a topic to a subject where the participation association must be SBJ. <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. <br/> </td> </tr> <tr> <td> 2</td> <td> INVE <a name="v3-ActClass-INVE"> </a> </td> <td> invoice element</td> <td> Represents concepts related to invoice processing in health care <br/> </td> </tr> <tr> <td> 2</td> <td> LIST <a name="v3-ActClass-LIST"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> MPROT <a name="v3-ActClass-MPROT"> </a> </td> <td> monitoring program</td> <td> An officially or unofficially instituted program to track acts of a particular type or categorization. <br/> </td> </tr> <tr> <td> 2</td> <td> OBS <a name="v3-ActClass-OBS"> </a> </td> <td> 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/> Discussion: <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/> 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/> 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/> 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/> 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/> 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/> Examples: <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 <br/> </td> </tr> <tr> <td> 3</td> <td> <span style="color: grey"> <i> (_ActClassROI)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActClass-_ActClassROI"> </a> </td> <td> Regions of Interest (ROI) within a subject Act. Primarily used for making secondary observations on a subset of a subject observation. The relationship between a ROI and its referenced Act is specified through an ActRelationship of type "subject&q uot; (SUBJ), which must always be present. <br/> </td> </tr> <tr> <td> 4</td> <td> ROIBND <a name="v3-ActClass-ROIBND"> </a> </td> <td> 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 "has component" (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). <br/> </td> </tr> <tr> <td> 4</td> <td> ROIOVL <a name="v3-ActClass-ROIOVL"> </a> </td> <td> 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 "circling" 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 "subject&q uot; (SUBJ), which must always be present. <br/> </td> </tr> <tr> <td> 3</td> <td> <span style="color: grey"> <i> (_SubjectPhysicalPosition)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActClass-_SubjectPhysicalPosition"> </a> </td> <td> The spatial relationship of a subject whether human, other animal, or plant, to a frame of reference such as gravity or a collection device. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td> 4</td> <td> <span style="color: grey"> <i> (_SubjectBodyPosition)</i> </span> <b> <i> Abstract</i> </b> <b> <i> Deprecated</i> </b> </td> <td> <a name="v3-ActClass-_SubjectBodyPosition"> </a> </td> <td> Contains codes for defining the observed, physical position of a subject, such as during an observation, assessment, collection of a specimen, etc. ECG waveforms and vital signs, such as blood pressure, are two examples where a general, observed position typically needs to be noted. <br/> Deprecation Comment: This concept has been deprecated because it does not describe a type of Act (as it should in the ActClass code system), but rather encodes the result or value of an observation. The same code has been added to the ObservationValue code system. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td> 5</td> <td> LLD <a name="v3-ActClass-LLD"> </a> <b> <i> Deprecated</i> </b> </td> <td> left lateral decubitus</td> <td> Lying on the left side. <br/> Deprecation Comment: This concept has been deprecated because it does not describe a type of Act (as it should in the ActClass code system), but rather encodes the result or value of an observation. The same code has been added to the ObservationValue code system. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td> 5</td> <td> PRN <a name="v3-ActClass-PRN"> </a> <b> <i> Deprecated</i> </b> </td> <td> prone</td> <td> Lying with the front or ventral surface downward; lying face down. <br/> Deprecation Comment: This concept has been deprecated because it does not describe a type of Act (as it should in the ActClass code system), but rather encodes the result or value of an observation. The same code has been added to the ObservationValue code system. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td> 5</td> <td> RLD <a name="v3-ActClass-RLD"> </a> <b> <i> Deprecated</i> </b> </td> <td> right lateral decubitus</td> <td> Lying on the right side. <br/> Deprecation Comment: This concept has been deprecated because it does not describe a type of Act (as it should in the ActClass code system), but rather encodes the result or value of an observation. The same code has been added to the ObservationValue code system. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td> 5</td> <td> SFWL <a name="v3-ActClass-SFWL"> </a> <b> <i> Deprecated</i> </b> </td> <td> Semi-Fowler's</td> <td> A semi-sitting position in bed with the head of the bed elevated approximately 45 degrees. <br/> Deprecation Comment: This concept has been deprecated because it does not describe a type of Act (as it should in the ActClass code system), but rather encodes the result or value of an observation. The same code has been added to the ObservationValue code system. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td> 5</td> <td> SIT <a name="v3-ActClass-SIT"> </a> <b> <i> Deprecated</i> </b> </td> <td> sitting</td> <td> Resting the body on the buttocks, typically with upper torso erect or semi erect. <br/> Deprecation Comment: This concept has been deprecated because it does not describe a type of Act (as it should in the ActClass code system), but rather encodes the result or value of an observation. The same code has been added to the ObservationValue code system. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td> 5</td> <td> STN <a name="v3-ActClass-STN"> </a> <b> <i> Deprecated</i> </b> </td> <td> standing</td> <td> To be stationary, upright, vertical, on one's legs. <br/> Deprecation Comment: This concept has been deprecated because it does not describe a type of Act (as it should in the ActClass code system), but rather encodes the result or value of an observation. The same code has been added to the ObservationValue code system. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td> 5</td> <td> SUP <a name="v3-ActClass-SUP"> </a> <b> <i> Deprecated</i> </b> </td> <td> supine</td> <td> Deprecation Comment: This concept has been deprecated because it does not describe a type of Act (as it should in the ActClass code system), but rather encodes the result or value of an observation. The same code has been added to the ObservationValue code system. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td> 6</td> <td> RTRD <a name="v3-ActClass-RTRD"> </a> <b> <i> Deprecated</i> </b> </td> <td> reverse trendelenburg</td> <td> Lying on the back, on an inclined plane, typically about 30-45 degrees with head raised and feet lowered. <br/> Deprecation Comment: This concept has been deprecated because it does not describe a type of Act (as it should in the ActClass code system), but rather encodes the result or value of an observation. The same code has been added to the ObservationValue code system. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td> 6</td> <td> TRD <a name="v3-ActClass-TRD"> </a> <b> <i> Deprecated</i> </b> </td> <td> trendelenburg</td> <td> Lying on the back, on an inclined plane, typically about 30-45 degrees, with head lowered and feet raised. <br/> Deprecation Comment: This concept has been deprecated because it does not describe a type of Act (as it should in the ActClass code system), but rather encodes the result or value of an observation. The same code has been added to the ObservationValue code system. <br/> </td> </tr> <tr> <td> 3</td> <td> ALRT <a name="v3-ActClass-ALRT"> </a> </td> <td> detected issue</td> <td> An observation identifying a potential adverse outcome as a result of an Act or combination of Acts. <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/> 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/> 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). <br/> </td> </tr> <tr> <td> 3</td> <td> BATTERY <a name="v3-ActClass-BATTERY"> </a> </td> <td> 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/> 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/> Examples: Vital signs, Full blood count, Chemistry panel. <br/> </td> </tr> <tr> <td> 3</td> <td> CLNTRL <a name="v3-ActClass-CLNTRL"> </a> </td> <td> 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. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td> 3</td> <td> CNOD <a name="v3-ActClass-CNOD"> </a> <b> <i> Deprecated</i> </b> </td> <td> 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/> 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. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td> 3</td> <td> COND <a name="v3-ActClass-COND"> </a> <b> <i> Deprecated</i> </b> </td> <td> 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 <br/> </td> </tr> <tr style="background: #EFEFEF"> <td> 4</td> <td> CASE <a name="v3-ActClass-CASE"> </a> <b> <i> Deprecated</i> </b> </td> <td> 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 = "definition&qu ot;) 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. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td> 5</td> <td> OUTB <a name="v3-ActClass-OUTB"> </a> <b> <i> Deprecated</i> </b> </td> <td> 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. <br/> </td> </tr> <tr> <td> 3</td> <td> DGIMG <a name="v3-ActClass-DGIMG"> </a> </td> <td> diagnostic image</td> <td> Class for holding attributes unique to diagnostic images. <br/> </td> </tr> <tr> <td> 3</td> <td> GEN <a name="v3-ActClass-GEN"> </a> </td> <td> genomic observation</td> <td> Description:An observation of genomic phenomena. <br/> </td> </tr> <tr> <td> 4</td> <td> DETPOL <a name="v3-ActClass-DETPOL"> </a> </td> <td> determinant peptide</td> <td> Description:A determinant peptide in a polypeptide as described by polypeptide. <br/> </td> </tr> <tr> <td> 4</td> <td> EXP <a name="v3-ActClass-EXP"> </a> </td> <td> expression level</td> <td> Description:An expression level of genes/proteins or other expressed genomic entities. <br/> </td> </tr> <tr> <td> 4</td> <td> LOC <a name="v3-ActClass-LOC"> </a> </td> <td> locus</td> <td> Description:The position of a gene (or other significant sequence) on the genome. <br/> </td> </tr> <tr> <td> 4</td> <td> PHN <a name="v3-ActClass-PHN"> </a> </td> <td> phenotype</td> <td> Description:A genomic phenomenon that is expressed externally in the organism. <br/> </td> </tr> <tr> <td> 4</td> <td> POL <a name="v3-ActClass-POL"> </a> </td> <td> polypeptide</td> <td> Description:A polypeptide resulting from the translation of a gene. <br/> </td> </tr> <tr> <td> 4</td> <td> SEQ <a name="v3-ActClass-SEQ"> </a> </td> <td> bio sequence</td> <td> Description:A sequence of biomolecule like the DNA, RNA, protein and the like. <br/> </td> </tr> <tr> <td> 4</td> <td> SEQVAR <a name="v3-ActClass-SEQVAR"> </a> </td> <td> bio sequence variation</td> <td> Description:A variation in a sequence as described by BioSequence. <br/> </td> </tr> <tr> <td> 3</td> <td> INVSTG <a name="v3-ActClass-INVSTG"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td> 3</td> <td> OBSSER <a name="v3-ActClass-OBSSER"> </a> </td> <td> 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 "OBSCOR". 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. <br/> </td> </tr> <tr> <td> 4</td> <td> OBSCOR <a name="v3-ActClass-OBSCOR"> </a> </td> <td> correlated observation sequences</td> <td> Container for Observation Sequences (Observations whose values are contained in LIST<>'s) having values correlated with each other. Each contained Observation Sequence LIST<> must be the same length. Values in the LIST<>'s are correlated based on index. E.g. the values in position 2 in all the LIST<>'s are correlated. This is analogous to a table where each column is an Observation Sequence with a LIST<> 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. <br/> </td> </tr> <tr> <td> 3</td> <td> POS <a name="v3-ActClass-POS"> </a> </td> <td> position</td> <td> An observation denoting the physical location of a person or thing based on a reference coordinate system. <br/> </td> </tr> <tr> <td> 4</td> <td> POSACC <a name="v3-ActClass-POSACC"> </a> </td> <td> position accuracy</td> <td> Description:An observation representing the degree to which the assignment of the spatial coordinates, based on a matching algorithm by a geocoding engine against a reference spatial database, matches true or accepted values. <br/> </td> </tr> <tr> <td> 4</td> <td> POSCOORD <a name="v3-ActClass-POSCOORD"> </a> </td> <td> position coordinate</td> <td> Description:An observation representing one of a set of numerical values used to determine the position of a place. The name of the coordinate value is determined by the reference coordinate system. <br/> </td> </tr> <tr> <td> 3</td> <td> SPCOBS <a name="v3-ActClass-SPCOBS"> </a> </td> <td> specimen observation</td> <td> An observation on a specimen in a laboratory environment that may affect processing, analysis or result interpretation <br/> </td> </tr> <tr> <td> 3</td> <td> VERIF <a name="v3-ActClass-VERIF"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> PCPR <a name="v3-ActClass-PCPR"> </a> </td> <td> 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/> 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/> In request (RQO) mood care provision communicates a referral, which is a request: <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/> The scope of the care for which responsibility is taken is identified by code attribute. <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/> Examples: <br/> Referral from GP to a specialist. <br/> Assignment of a patient or group of patients to the case list of a health professional. <br/> Assignment of inpatients to the care of particular nurses for a working shift. <br/> </td> </tr> <tr> <td> 3</td> <td> ENC <a name="v3-ActClass-ENC"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> POLICY <a name="v3-ActClass-POLICY"> </a> </td> <td> policy</td> <td> Description:A mandate, regulation, obligation, requirement, rule, or expectation unilaterally imposed by one party on: <br/> The activity of another party <br/> The behavior of another party <br/> The manner in which an act is executed <br/> </td> </tr> <tr> <td> 3</td> <td> JURISPOL <a name="v3-ActClass-JURISPOL"> </a> </td> <td> jurisdictional policy</td> <td> Description:A mandate, regulation, obligation, requirement, rule, or expectation unilaterally imposed by a jurisdiction on: <br/> The activity of another party <br/> The behavior of another party <br/> The manner in which an act is executed <br/> Examples:A jurisdictional mandate regarding the prescribing and dispensing of a particular medication. A jurisdictional privacy or security regulation dictating the manner in which personal health information is disclosed. A jurisdictional requirement that certain services or health conditions are reported to a monitoring program, e.g., immunizations, methadone treatment, or cancer registries. <br/> </td> </tr> <tr> <td> 3</td> <td> ORGPOL <a name="v3-ActClass-ORGPOL"> </a> </td> <td> organizational policy</td> <td> Description:A mandate, obligation, requirement, rule, or expectation unilaterally imposed by an organization on: <br/> The activity of another party <br/> The behavior of another party <br/> The manner in which an act is executed <br/> Examples:A clinical or research protocols imposed by a payer, a malpractice insurer, or an institution to which a provider must adhere. A mandate imposed by a denominational institution for a provider to provide or withhold certain information from the patient about treatment options. <br/> </td> </tr> <tr> <td> 3</td> <td> SCOPOL <a name="v3-ActClass-SCOPOL"> </a> </td> <td> scope of practice policy</td> <td> Description:An ethical or clinical obligation, requirement, rule, or expectation imposed or strongly encouraged by organizations that oversee particular clinical domains or provider certification which define the boundaries within which a provider may practice and which may have legal basis or ramifications on: <br/> The activity of another party <br/> The behavior of another party <br/> The manner in which an act is executed <br/> Examples:An ethical obligation for a provider to fully inform a patient about all treatment options. An ethical obligation for a provider not to disclose personal health information that meets certain criteria, e.g., where disclosure might result in harm to the patient or another person. The set of health care services which a provider is credentialed or privileged to provide. <br/> </td> </tr> <tr> <td> 3</td> <td> STDPOL <a name="v3-ActClass-STDPOL"> </a> </td> <td> standard of practice policy</td> <td> Description:A requirement, rule, or expectation typically documented as guidelines, protocols, or formularies imposed or strongly encouraged by an organization that oversees or has authority over the practices within a domain, and which may have legal basis or ramifications on: <br/> The activity of another party <br/> The behavior of another party <br/> The manner in which an act is executed <br/> Examples:A payer may require a prescribing provider to adhere to formulary guidelines. An institution may adopt clinical guidelines and protocols and implement these within its electronic health record and decision support systems. <br/> </td> </tr> <tr> <td> 2</td> <td> PROC <a name="v3-ActClass-PROC"> </a> </td> <td> procedure</td> <td> An Act whose immediate and primary outcome (post-condition) is the alteration of the physical condition of the subject. <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. <br/> </td> </tr> <tr> <td> 3</td> <td> SBADM <a name="v3-ActClass-SBADM"> </a> </td> <td> substance administration</td> <td> The act of introducing or otherwise applying a substance to the subject. <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/> Examples: Chemotherapy protocol; Drug prescription; Vaccination record <br/> </td> </tr> <tr> <td> 3</td> <td> SBEXT <a name="v3-ActClass-SBEXT"> </a> </td> <td> Substance Extraction</td> <td> Description: The act of removing a substance from the subject. <br/> </td> </tr> <tr> <td> 4</td> <td> SPECCOLLECT <a name="v3-ActClass-SPECCOLLECT"> </a> </td> <td> Specimen Collection</td> <td> A procedure for obtaining a specimen from a source entity. <br/> </td> </tr> <tr> <td> 2</td> <td> REG <a name="v3-ActClass-REG"> </a> </td> <td> 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/> 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. <br/> </td> </tr> <tr> <td> 2</td> <td> REV <a name="v3-ActClass-REV"> </a> </td> <td> review</td> <td> The act of examining and evaluating the subject, usually another act. For example, "This prescription needs to be reviewed in 2 months." <br/> </td> </tr> <tr> <td> 2</td> <td> SPCTRT <a name="v3-ActClass-SPCTRT"> </a> </td> <td> specimen treatment</td> <td> A procedure or treatment performed on a specimen to prepare it for analysis <br/> </td> </tr> <tr> <td> 2</td> <td> SPLY <a name="v3-ActClass-SPLY"> </a> </td> <td> 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="pr oduct". 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. <br/> </td> </tr> <tr style="background: #EFEFEF"> <td> 3</td> <td> DIET <a name="v3-ActClass-DIET"> </a> <b> <i> Deprecated</i> </b> </td> <td> 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="product". 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/> Deprecation Note <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/> energyQuantity: This quantity can be conveyed by using a Content relationship with a quantity attribute expressing the calories <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. <br/> </td> </tr> <tr> <td> 2</td> <td> STORE <a name="v3-ActClass-STORE"> </a> </td> <td> storage</td> <td> The act of putting something away for safe keeping. The "something" ; may be physical object such as a specimen, or information, such as observations regarding a specimen. <br/> </td> </tr> <tr> <td> 2</td> <td> SUBST <a name="v3-ActClass-SUBST"> </a> </td> <td> Substitution</td> <td> Definition: Indicates that the subject Act has undergone or should undergo substitution of a type indicated by Act.code. <br/> Rationale: Used to specify "allowed" substitution when creating orders, "actual" susbstitution when sending events, as well as the reason for the substitution and who was responsible for it. <br/> </td> </tr> <tr> <td> 2</td> <td> TRFR <a name="v3-ActClass-TRFR"> </a> </td> <td> transfer</td> <td> Definition: The act of transferring information without the intent of imparting understanding about a topic to the subject that is the recipient or holder of the transferred information where the participation association must be RCV or HLD. <br/> </td> </tr> <tr> <td> 2</td> <td> TRNS <a name="v3-ActClass-TRNS"> </a> </td> <td> 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.) <br/> </td> </tr> <tr> <td> 2</td> <td> XACT <a name="v3-ActClass-XACT"> </a> </td> <td> financial transaction</td> <td> A sub-class of Act representing any transaction between two accounts whose value is measured in monetary terms. <br/> In the "intent" mood, communicates a request for a transaction to be initiated, or communicates a transfer of value between two accounts. <br/> In the "event" mood, communicates the posting of a transaction to an account. <br/> </td> </tr> <tr> <td> 2</td> <td> <span style="color: grey"> <i> (_ActClassContainer)</i> </span> <b> <i> Abstract</i> </b> </td> <td> <a name="v3-ActClass-_ActClassContainer"> </a> </td> <td/> </tr> <tr> <td> 3</td> <td> ENTRY <a name="v3-ActClass-ENTRY"> </a> </td> <td> 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. <br/> </td> </tr> <tr> <td> 3</td> <td> ORGANIZER <a name="v3-ActClass-ORGANIZER"> </a> </td> <td> 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 "organizer tree". <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. <br/> </td> </tr> <tr> <td> 1</td> <td> DOCCNTNT <a name="v3-ActClass-DOCCNTNT"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> DOCLIST <a name="v3-ActClass-DOCLIST"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> DOCLSTITM <a name="v3-ActClass-DOCLSTITM"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> DOCPARA <a name="v3-ActClass-DOCPARA"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> DOCTBL <a name="v3-ActClass-DOCTBL"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> LINKHTML <a name="v3-ActClass-LINKHTML"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> LOCALATTR <a name="v3-ActClass-LOCALATTR"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> LOCALMRKP <a name="v3-ActClass-LOCALMRKP"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> ordered <a name="v3-ActClass-ordered"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> REFR <a name="v3-ActClass-REFR"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> TBLCOL <a name="v3-ActClass-TBLCOL"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> TBLCOLGP <a name="v3-ActClass-TBLCOLGP"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> TBLDATA <a name="v3-ActClass-TBLDATA"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> TBLHDR <a name="v3-ActClass-TBLHDR"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> TBLROW <a name="v3-ActClass-TBLROW"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> tbody <a name="v3-ActClass-tbody"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> tfoot <a name="v3-ActClass-tfoot"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> thead <a name="v3-ActClass-thead"> </a> </td> <td/> <td/> </tr> <tr> <td> 1</td> <td> unordered <a name="v3-ActClass-unordered"> </a> </td> <td/> <td/> </tr> </table> </div> </text> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status"> <valueCode value="external"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm"> <valueInteger value="0"/> </extension> <url value="http://terminology.hl7.org/CodeSystem/v3-ActClass"/> <identifier> <system value="urn:ietf:rfc:3986"/> <value value="urn:oid:2.16.840.1.113883.5.6"/> </identifier> <version value="2018-08-12"/> <name value="v3.ActClass"/> <title value="v3 Code System ActClass"/> <status value="active"/> <experimental value="false"/> <date value="2018-08-12T00:00:00+00:00"/> <publisher value="HL7, Inc"/> <contact> <telecom> <system value="url"/> <value value="http://hl7.org"/> </telecom> </contact> <description value="**** MISSING DEFINITIONS ****"/> <caseSensitive value="true"/> <valueSet value="http://terminology.hl7.org/ValueSet/v3-ActClass"/> <hierarchyMeaning value="is-a"/> <content value="complete"/> <property> <code value="notSelectable"/> <uri value="http://hl7.org/fhir/concept-properties#notSelectable"/> <description value="Indicates that the code is abstract - only intended to be used as a selector for other concepts"/> <type value="boolean"/> </property> <property> <code value="status"/> <uri value="http://hl7.org/fhir/concept-properties#status"/> <description value="A property that indicates the status of the concept. One of active, experimental, deprecated, retired"/> <type value="code"/> </property> <property> <code value="deprecationDate"/> <uri value="http://hl7.org/fhir/concept-properties#deprecationDate"/> <description value="The date at which a concept was deprecated. Concepts that are deprecated but not inactive can still be used, but their use is discouraged"/> <type value="dateTime"/> </property> <concept> <code value="ACT"/> <display value="act"/> <definition value="A record of something that is being done, has been done, can be done, or is intended or requested to be done. 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. 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. 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. One of the Participations that all acts have (at least implicitly) is a primary author, who is responsible of the Act and who "owns" 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. In this sense, an Act-instance represents a "statement" 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 "a faithful record of what clinicians have heard, seen, thought, and done." Rector and Nowlan go on saying that "the other requirements for a medical record, e.g., that it be attributable and permanent, follow naturally from this view." 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. 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 "speech-acts" 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]. 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 "sequel"). 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 "objective state of affairs" or "real processes" 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."/> <concept> <code value="_ActClassRecordOrganizer"/> <display value="record organizer"/> <definition value="Used to group a set of acts sharing a common context. Organizer structures can nest within other context structures - such as where a document is contained within a folder, or a folder is contained within an EHR extract."/> <property> <code value="notSelectable"/> <valueBoolean value="true"/> </property> <concept> <code value="COMPOSITION"/> <display value="composition"/> <definition value="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. A composition represents part of a patient record originating from a single interaction between an authenticator and the record. 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. A composition contains organizers and entries."/> <concept> <code value="DOC"/> <display value="document"/> <definition value="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. 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."/> <concept> <code value="DOCCLIN"/> <display value="clinical document"/> <definition value="A clinical document is a documentation of clinical observations and services, with the following characteristics: Persistence - A clinical document continues to exist in an unaltered state, for a time period defined by local and regulatory requirements; Stewardship - A clinical document is maintained by a person or organization entrusted with its care; Potential for authentication - A clinical document is an assemblage of information that is intended to be legally authenticated; 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; Human readability - A clinical document is human readable."/> <concept> <code value="CDALVLONE"/> <display value="CDA Level One clinical document"/> <definition value="A clinical document that conforms to Level One of the HL7 Clinical Document Architecture (CDA)"/> </concept> </concept> </concept> </concept> <concept> <code value="CONTAINER"/> <display value="record container"/> <definition value="Description: Container of clinical statements. Navigational. No semantic content. Knowledge of the section code is not required to interpret contained observations. Represents a heading in a heading structure, or "container tree". 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."/> <concept> <code value="CATEGORY"/> <display value="category"/> <definition value="A group of entries within a composition or topic that have a common characteristic - for example, Examination, Diagnosis, Management OR Subjective, Objective, Analysis, Plan. The distinction from Topic relates to value sets. For Category there is a bounded list of things like "Examination", "Diagnosis" or SOAP categories. For Topic the list is wide open to any clinical condition or reason for a part of an encounter. A CATEGORY MAY CONTAIN ENTRIES."/> </concept> <concept> <code value="DOCBODY"/> <display value="document body"/> <definition value="A context that distinguishes the body of a document from the document header. This is seen, for instance, in HTML documents, which have discrete <head> and <body> elements."/> </concept> <concept> <code value="DOCSECT"/> <display value="document section"/> <definition value="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."/> </concept> <concept> <code value="TOPIC"/> <display value="topic"/> <definition value="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. A topic may contain categories and entries."/> </concept> </concept> <concept> <code value="EXTRACT"/> <display value="extract"/> <definition value="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. 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). An extract contains folders or compositions. An extract cannot contain another extract."/> <concept> <code value="EHR"/> <display value="electronic health record"/> <definition value="A context that comprises all compositions. The EHR is an extract that includes the entire chart. NOTE: In an exchange scenario, an EHR is a specialization of an extract."/> </concept> </concept> <concept> <code value="FOLDER"/> <display value="folder"/> <definition value="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. A folder contains compositions. Folders may be nested within folders."/> </concept> <concept> <code value="GROUPER"/> <display value="grouper"/> <definition value="Definition: An ACT that organizes a set of component acts into a semantic grouping that share a particular context such as timeframe, patient, etc. UsageNotes: The focus in a GROUPER act is the grouping of the contained acts. For example "a request to group" (RQO), "a type of grouping that is allowed to occur" (DEF), etc. Unlike WorkingList, which represents a dynamic, shared, continuously updated collection to provide a "view" of a set of objects, GROUPER collections tend to be static and simply indicate a shared set of semantics. Note that sharing of semantics can be achieved using ACT as well. However, with GROUPER, the sole semantic is of grouping."/> <concept> <code value="CLUSTER"/> <display value="Cluster"/> <definition value="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. Discussion: The focus in a CLUSTER act is the grouping of the contained acts. For example "a request to cluster" (RQO), "a type of cluster that is allowed to occur" (DEF), etc. Examples: Radiologic investigations that might include administration of a dye, followed by radiographic observations; "Isolate cluster" which includes all testing and specimen processing performed on a specific isolate; a set of actions to perform at a particular stage in a clinical trial."/> </concept> </concept> </concept> <concept> <code value="ACCM"/> <display value="accommodation"/> <definition value="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."/> </concept> <concept> <code value="ACCT"/> <display value="account"/> <definition value="A financial account established to track the net result of financial acts."/> </concept> <concept> <code value="ACSN"/> <display value="accession"/> <definition value="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)."/> </concept> <concept> <code value="ADJUD"/> <display value="financial adjudication"/> <definition value="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. Adjudication results comprise 2 components: the adjudication processing results and a restated (or adjudicated) invoice or claim"/> </concept> <concept> <code value="CACT"/> <display value="control act"/> <definition value="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."/> <concept> <code value="ACTN"/> <display value="action"/> <definition value="Sender asks addressee to do something depending on the focal Act of the payload. An example is "fulfill this order". 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)."/> </concept> <concept> <code value="INFO"/> <display value="information"/> <definition value="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."/> </concept> <concept> <code value="STC"/> <display value="state transition control"/> <definition value="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."/> </concept> </concept> <concept> <code value="CNTRCT"/> <display value="contract"/> <definition value="An agreement of obligation between two or more parties that is subject to contractual law and enforcement."/> <concept> <code value="FCNTRCT"/> <display value="financial contract"/> <definition value="A contract whose value is measured in monetary terms."/> <concept> <code value="COV"/> <display value="coverage"/> <definition value="When used in the EVN mood, this concept means with respect to a covered party: A health care insurance policy or plan that is contractually binding between two or more parties; or A health care program, usually administered by government entities, that provides coverage to persons determined eligible under the terms of the program. When used in the definition (DEF) mood, COV means potential coverage for a patient who may or may not be a covered party. The concept's meaning is fully specified by the choice of ActCoverageTypeCode (abstract) ActProgramCode or ActInsurancePolicyCode."/> </concept> </concept> </concept> <concept> <code value="CONC"/> <display value="concern"/> <definition value="Definition: A worry that tends to persist over time and has as its subject a state or process. The subject of the worry has the potential to require intervention or management. Examples: an observation result, procedure, substance administration, equipment repair status, device recall status, a health risk, a financial risk, public health risk, pregnancy, health maintenance, allergy, and acute or chronic illness."/> <concept> <code value="HCASE"/> <display value="public health case"/> <definition value="A public health case is a Concern about an observation or event that has a specific significance for public health. The creation of a PublicHealthCase initiates the tracking of the object of concern. The decision to track is related to but somewhat independent of the underlying event or observation. UsageNotes: Typically a Public Health Case 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. A public health case definition (Act.moodCode = "definition") 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. 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."/> </concept> <concept> <code value="OUTBR"/> <display value="outbreak"/> <definition value="An Outbreak is a concern resulting from a series of public health cases. UsageNotes: 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. The effectiveTime attribute is used to convey the relevant dates for the case. An outbreak definition (Act.moodCode = "definition" includes the criteria for the number, types and occurrence pattern of cases necessary to declare an outbreak and to judge the severity of an outbreak."/> </concept> </concept> <concept> <code value="CONS"/> <display value="consent"/> <definition value="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. 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. The "signatures" to the consent document are represented electronically through Participation instances to the consent object. Typically an informed consent has Participation.typeCode of "performer", the healthcare provider informing the patient, and "consenter", 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. 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."/> </concept> <concept> <code value="CONTREG"/> <display value="container registration"/> <definition value="An Act where a container is registered either via an automated sensor, such as a barcode reader, or by manual receipt"/> </concept> <concept> <code value="CTTEVENT"/> <display value="clinical trial timepoint event"/> <definition value="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."/> </concept> <concept> <code value="DISPACT"/> <display value="disciplinary action"/> <definition value="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. Suspension, license restrictions, monetary fine, letter of reprimand, mandated training, mandated supervision, etc.Examples:"/> </concept> <concept> <code value="EXPOS"/> <display value="exposure"/> <definition value="An interaction between entities that provides opportunity for transmission of a physical, chemical, or biological agent from an exposure source entity to an exposure target entity. Examples: The following examples are provided to indicate what interactions are considered exposures rather than other types of Acts: A patient accidentally receives three times the recommended dose of their medication due to a dosing error. This is a substance administration. Public health and/or safety authorities may also be interested in documenting this with an associated exposure. A patient accidentally is dispensed an incorrect medicine (e.g., clomiphene instead of clomipramine). They have taken several doses before the mistake is detected. They are therefore "exposed" to a medicine that there was no therapeutic indication for them to receive. There are several substance administrations in this example. Public health and/or safety authorities may also be interested in documenting this with associated exposures. In a busy medical ward, a patient is receiving chemotherapy for a lymphoma. Unfortunately, the IV infusion bag containing the medicine splits, spraying cytotoxic medication over the patient being treated and the patient in the adjacent bed. There are three substance administrations in this example. The first is the intended one (IV infusion) with its associated (implicit) exposure. There is an incident with an associated substance administration to the same patient involving the medication sprayed over the patient as well as an associated exposure. Additionally, the incident includes a substance administration involving the spraying of medication on the adjacent patient, also with an associated exposure. A patient who is a refugee from a war-torn African nation arrives in a busy inner city A&E department suffering from a cough with bloody sputum. Not understanding the registration and triage process, they sit in the waiting room for several hours before it is noticed that they have not booked in. As soon as they are being processed, it is suspected that they are suffering from TB. Vulnerable (immunosuppressed) patients who were sharing the waiting room with this patient may have been exposed to the tubercule bacillus, and must be traced for investigation. This is an exposure (or possibly multiple exposures) in the waiting room involving the refugee and everyone else in the waiting room during the period. There might also be a number of known or presumed substance administrations (coughing) via several possible routes. The substance administrations are only hypotheses until confirmed by further testing. A patient who has received an elective total hip replacement procedure suffers a prolonged stay in hospital, due to contracting an MRSA infection in the surgical wound site after the surgery. This is an exposure to MRSA. Although there was some sort of substance administration, it's possible the exact mechanism for introduction of the MRSA into the wound will not be identified. Routine maintenance of the X-ray machines at a local hospital reveals a serious breach of the shielding on one of the machines. Patients who have undergone investigations using that machine in the last month are likely to have been exposed to significantly higher doses of X-rays than was intended, and must be tracked for possible adverse effects. There has been an exposure of each patient who used the machine in the past 30 days. Some patients may have had substance administrations. A new member of staff is employed in the laundry processing room of a small cottage hospital, and a misreading of the instructions for adding detergents results in fifty times the usual concentration of cleaning materials being added to a batch of hospital bedding. As a result, several patients have been exposed to very high levels of detergents still present in the "clean" bedding, and have experienced dermatological reactions to this. There has been an incident with multiple exposures to several patients. Although there are substance administrations involving the application of the detergent to the skin of the patients, it is expected that the substance administrations would not be directly documented. Seven patients who are residents in a health care facility for the elderly mentally ill have developed respiratory problems. After several months of various tests having been performed and various medications prescribed to these patients, the problem is traced to their being "sensitive" to a new fungicide used in the wall plaster of the ward where these patients reside. The patients have been continuously exposed to the fungicide. Although there have been continuous substance administrations (via breathing) this would not normally be documented as a substance administration. A patient with osteoarthritis of the knees is treated symptomatically using analgesia, paracetamol (acetaminophen) 1g up to four times a day for pain relief. His GP does not realize that the patient has, 20 years previously (while at college) had severe alcohol addiction problems, and now, although this is completely under control, his liver has suffered significantly, leaving him more sensitive to hepatic toxicity from paracetamol use. Later that year, the patient returns with a noticeable level of jaundice. Paracetamol is immediately withdrawn and alternative solutions for the knee pain are sought. The jaundice gradually subsides with conservative management, but referral to the gastroenterologist is required for advice and monitoring. There is a substance administration with an associated exposure. The exposure component is based on the relative toxic level of the substance to a patient with a compromised liver function. A patient goes to their GP complaining of abdominal pain, having been discharged from the local hospital ten days' previously after an emergency appendectomy. The GP can find nothing particularly amiss, and presumes it is post operative surgical pain that will resolve. The patient returns a fortnight later, when the GP prescribes further analgesia, but does decide to request an outpatient surgical follow-up appointment. At this post-surgical outpatient review, the registrar decides to order an ultrasound, which, when performed three weeks later, shows a small faint inexplicable mass. A laparoscopy is then performed, as a day case procedure, and a piece of a surgical swab is removed from the patient's abdominal cavity. Thankfully, a full recovery then takes place. This is a procedural sequelae. There may be an Incident recorded for this also. A patient is slightly late for a regular pacemaker battery check in the Cardiology department of the local hospital. They are hurrying down the second floor corridor. A sudden summer squall has recently passed over the area, and rain has come in through an open corridor window leaving a small puddle on the corridor floor. In their haste, the patient slips in the puddle and falls so badly that they have to be taken to the A&E department, where it is discovered on investigation they have slightly torn the cruciate ligament in their left knee. This is not an exposure. There has been an incident. Usage Notes: This class deals only with opportunity and not the outcome of the exposure; i.e. not all exposed parties will necessarily experience actual harm or benefit. Exposure differs from Substance Administration by the absence of the participation of a performer in the act. The following participations SHOULD be used with the following participations to distinguish the specific entities: The exposed entity participates via the "exposure target" (EXPTRGT) participation. An entity that has carried the agent transmitted in the exposure participates via the "exposure source" (EXSRC) participation. For example: a person or animal who carried an infectious disease and interacts (EXSRC) with another person or animal (EXPTRGT) transmitting the disease agent; a place or other environment (EXSRC) and a person or animal (EXPTRGT) who is exposed in the presence of this environment. When it is unknown whether a participating entity is the source of the agent (EXSRC) or the target of the transmission (EXPTRGT), the "exposure participant" (EXPART) is used. The physical (including energy), chemical or biological substance which is participating in the exposure uses the "exposure agent" (EXPAGNT) participation. There are at least three scenarios: the player of the Role that participates as EXPAGNT is the chemical or biological substance mixed or carried by the scoper-entity of the Role (e.g., ingredient role); or the player of the Role that participates as EXPAGNT is a mixture known to contain the chemical, radiological or biological substance of interest; or the player of the Role that participates as a EXPAGNT is known to carry the agent (i.e., the player is a fomite, vector, etc.). The Exposure.statusCode attribute should be interpreted as the state of the Exposure business object (e.g., active, aborted, completed) and not the clinical status of the exposure (e.g., probable, confirmed). The clinical status of the exposure should be associated with the exposure via a subject observation. Design Comment: The usage notes require a clear criterion for determining whether an act is an exposure or substance administration-deleterious potential, uncertainty of actual transmission, or otherwise. SBADM states that the criterion is the presence of a performer-but there are examples above that call this criterion into question (e.g., the first one, concerning a dosing error)."/> <concept> <code value="AEXPOS"/> <display value="acquisition exposure"/> <definition value="Description: An acquisition exposure act describes the proximity (location and time) through which the participating entity was potentially exposed to a physical (including energy), chemical or biological agent from another entity. The acquisition exposure act is used in conjunction with transmission exposure acts as part of an analysis technique for contact tracing. Although an exposure can be decomposed into transmission and acquisition exposures, there is no requirement that all exposures be treated in this fashion. Constraints: The Acquisition Exposure inherits the participation constraints that apply to Exposure with the following exception. The EXPSRC (exposure source) participation must never be associated with the Transmission Exposure either directly or via context conduction."/> </concept> <concept> <code value="TEXPOS"/> <display value="transmission exposure"/> <definition value="Description: A transmission exposure act describes the proximity (time and location) over which the participating source entity was capable of transmitting a physical (including energy), chemical or biological substance agent to another entity. The transmission exposure act is used in conjunction with acquisition exposure acts as part of an analysis technique for contact tracing. Although an exposure can be decomposed into transmission and acquisition exposures, there is no requirement that all exposures be treated in this fashion. Constraints: The Transmission Exposure inherits the participation constraints that apply to Exposure with the following exception. The EXPTRGT (exposure target) participation must never be associated with the Transmission Exposure either directly or via context conduction."/> </concept> </concept> <concept> <code value="INC"/> <display value="incident"/> <definition value="An event that occurred outside of the control of one or more of the parties involved. Includes the concept of an accident."/> </concept> <concept> <code value="INFRM"/> <display value="inform"/> <definition value="The act of transmitting information and understanding about a topic to a subject where the participation association must be SBJ. 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."/> </concept> <concept> <code value="INVE"/> <display value="invoice element"/> <definition value="Represents concepts related to invoice processing in health care"/> </concept> <concept> <code value="LIST"/> <display value="working list"/> <definition value="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."/> </concept> <concept> <code value="MPROT"/> <display value="monitoring program"/> <definition value="An officially or unofficially instituted program to track acts of a particular type or categorization."/> </concept> <concept> <code value="OBS"/> <display value="observation"/> <definition value="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. Discussion: 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. 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. 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. 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. 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. 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. Examples: Recording the results of a Family History Assessment Laboratory test and associated result Physical exam test and associated result Device temperature Soil lead level"/> <concept> <code value="_ActClassROI"/> <display value="ActClassROI"/> <definition value="Regions of Interest (ROI) within a subject Act. Primarily used for making secondary observations on a subset of a subject observation. The relationship between a ROI and its referenced Act is specified through an ActRelationship of type "subject" (SUBJ), which must always be present."/> <property> <code value="notSelectable"/> <valueBoolean value="true"/> </property> <concept> <code value="ROIBND"/> <display value="bounded ROI"/> <definition value="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 "has component" (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)."/> </concept> <concept> <code value="ROIOVL"/> <display value="overlay ROI"/> <definition value="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 "circling" 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 "subject" (SUBJ), which must always be present."/> </concept> </concept> <concept> <code value="_SubjectPhysicalPosition"/> <display value="subject physical position"/> <definition value="The spatial relationship of a subject whether human, other animal, or plant, to a frame of reference such as gravity or a collection device."/> <property> <code value="notSelectable"/> <valueBoolean value="true"/> </property> <concept> <code value="_SubjectBodyPosition"/> <display value="subject body position"/> <definition value="Contains codes for defining the observed, physical position of a subject, such as during an observation, assessment, collection of a specimen, etc. ECG waveforms and vital signs, such as blood pressure, are two examples where a general, observed position typically needs to be noted. Deprecation Comment: This concept has been deprecated because it does not describe a type of Act (as it should in the ActClass code system), but rather encodes the result or value of an observation. The same code has been added to the ObservationValue code system."/> <property> <code value="notSelectable"/> <valueBoolean value="true"/> </property> <property> <code value="status"/> <valueCode value="deprecated"/> </property> <property> <code value="deprecationDate"/> <valueDateTime value="2009-07-12"/> </property> <concept> <code value="LLD"/> <display value="left lateral decubitus"/> <definition value="Lying on the left side. Deprecation Comment: This concept has been deprecated because it does not describe a type of Act (as it should in the ActClass code system), but rather encodes the result or value of an observation. The same code has been added to the ObservationValue code system."/> <property> <code value="status"/> <valueCode value="deprecated"/> </property> <property> <code value="deprecationDate"/> <valueDateTime value="2009-07-12"/> </property> </concept> <concept> <code value="PRN"/> <display value="prone"/> <definition value="Lying with the front or ventral surface downward; lying face down. Deprecation Comment: This concept has been deprecated because it does not describe a type of Act (as it should in the ActClass code system), but rather encodes the result or value of an observation. The same code has been added to the ObservationValue code system."/> <property> <code value="status"/> <valueCode value="deprecated"/> </property> <property> <code value="deprecationDate"/> <valueDateTime value="2009-07-12"/> </property> </concept> <concept> <code value="RLD"/> <display value="right lateral decubitus"/> <definition value="Lying on the right side. Deprecation Comment: This concept has been deprecated because it does not describe a type of Act (as it should in the ActClass code system), but rather encodes the result or value of an observation. The same code has been added to the ObservationValue code system."/> <property> <code value="status"/> <valueCode value="deprecated"/> </property> <property> <code value="deprecationDate"/> <valueDateTime value="2009-07-12"/> </property> </concept> <concept> <code value="SFWL"/> <display value="Semi-Fowler's"/> <definition value="A semi-sitting position in bed with the head of the bed elevated approximately 45 degrees. Deprecation Comment: This concept has been deprecated because it does not describe a type of Act (as it should in the ActClass code system), but rather encodes the result or value of an observation. The same code has been added to the ObservationValue code system."/> <property> <code value="status"/> <valueCode value="deprecated"/> </property> <property> <code value="deprecationDate"/> <valueDateTime value="2009-07-12"/> </property> </concept> <concept> <code value="SIT"/> <display value="sitting"/> <definition value="Resting the body on the buttocks, typically with upper torso erect or semi erect. Deprecation Comment: This concept has been deprecated because it does not describe a type of Act (as it should in the ActClass code system), but rather encodes the result or value of an observation. The same code has been added to the ObservationValue code system."/> <property> <code value="status"/> <valueCode value="deprecated"/> </property> <property> <code value="deprecationDate"/> <valueDateTime value="2009-07-12"/> </property> </concept> <concept> <code value="STN"/> <display value="standing"/> <definition value="To be stationary, upright, vertical, on one's legs. Deprecation Comment: This concept has been deprecated because it does not describe a type of Act (as it should in the ActClass code system), but rather encodes the result or value of an observation. The same code has been added to the ObservationValue code system."/> <property> <code value="status"/> <valueCode value="deprecated"/> </property> <property> <code value="deprecationDate"/> <valueDateTime value="2009-07-12"/> </property> </concept> <concept> <code value="SUP"/> <display value="supine"/> <definition value="Deprecation Comment: This concept has been deprecated because it does not describe a type of Act (as it should in the ActClass code system), but rather encodes the result or value of an observation. The same code has been added to the ObservationValue code system."/> <property> <code value="status"/> <valueCode value="deprecated"/> </property> <property> <code value="deprecationDate"/> <valueDateTime value="2009-07-12"/> </property> <concept> <code value="RTRD"/> <display value="reverse trendelenburg"/> <definition value="Lying on the back, on an inclined plane, typically about 30-45 degrees with head raised and feet lowered. Deprecation Comment: This concept has been deprecated because it does not describe a type of Act (as it should in the ActClass code system), but rather encodes the result or value of an observation. The same code has been added to the ObservationValue code system."/> <property> <code value="status"/> <valueCode value="deprecated"/> </property> <property> <code value="deprecationDate"/> <valueDateTime value="2009-07-12"/> </property> </concept> <concept> <code value="TRD"/> <display value="trendelenburg"/> <definition value="Lying on the back, on an inclined plane, typically about 30-45 degrees, with head lowered and feet raised. Deprecation Comment: This concept has been deprecated because it does not describe a type of Act (as it should in the ActClass code system), but rather encodes the result or value of an observation. The same code has been added to the ObservationValue code system."/> <property> <code value="status"/> <valueCode value="deprecated"/> </property> <property> <code value="deprecationDate"/> <valueDateTime value="2009-07-12"/> </property> </concept> </concept> </concept> </concept> <concept> <code value="ALRT"/> <display value="detected issue"/> <definition value="An observation identifying a potential adverse outcome as a result of an Act or combination of Acts. 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. 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. 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)."/> </concept> <concept> <code value="BATTERY"/> <display value="battery"/> <definition value="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. 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. Examples: Vital signs, Full blood count, Chemistry panel."/> </concept> <concept> <code value="CLNTRL"/> <display value="clinical trial"/> <definition value="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."/> </concept> <concept> <code value="CNOD"/> <display value="Condition Node"/> <definition value="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 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."/> <property> <code value="status"/> <valueCode value="deprecated"/> </property> <property> <code value="deprecationDate"/> <valueDateTime value="2009-07-12"/> </property> </concept> <concept> <code value="COND"/> <display value="Condition"/> <definition value="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"/> <property> <code value="status"/> <valueCode value="deprecated"/> </property> <property> <code value="deprecationDate"/> <valueDateTime value="2012-11-09"/> </property> <concept> <code value="CASE"/> <display value="public health case"/> <definition value="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 = "definition") 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."/> <property> <code value="status"/> <valueCode value="deprecated"/> </property> <property> <code value="deprecationDate"/> <valueDateTime value="2012-11-09"/> </property> <concept> <code value="OUTB"/> <display value="outbreak"/> <definition value="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."/> <property> <code value="status"/> <valueCode value="deprecated"/> </property> <property> <code value="deprecationDate"/> <valueDateTime value="2012-11-09"/> </property> </concept> </concept> </concept> <concept> <code value="DGIMG"/> <display value="diagnostic image"/> <definition value="Class for holding attributes unique to diagnostic images."/> </concept> <concept> <code value="GEN"/> <display value="genomic observation"/> <definition value="Description:An observation of genomic phenomena."/> <concept> <code value="DETPOL"/> <display value="determinant peptide"/> <definition value="Description:A determinant peptide in a polypeptide as described by polypeptide."/> </concept> <concept> <code value="EXP"/> <display value="expression level"/> <definition value="Description:An expression level of genes/proteins or other expressed genomic entities."/> </concept> <concept> <code value="LOC"/> <display value="locus"/> <definition value="Description:The position of a gene (or other significant sequence) on the genome."/> </concept> <concept> <code value="PHN"/> <display value="phenotype"/> <definition value="Description:A genomic phenomenon that is expressed externally in the organism."/> </concept> <concept> <code value="POL"/> <display value="polypeptide"/> <definition value="Description:A polypeptide resulting from the translation of a gene."/> </concept> <concept> <code value="SEQ"/> <display value="bio sequence"/> <definition value="Description:A sequence of biomolecule like the DNA, RNA, protein and the like."/> </concept> <concept> <code value="SEQVAR"/> <display value="bio sequence variation"/> <definition value="Description:A variation in a sequence as described by BioSequence."/> </concept> </concept> <concept> <code value="INVSTG"/> <display value="investigation"/> <definition value="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."/> </concept> <concept> <code value="OBSSER"/> <display value="observation series"/> <definition value="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 "OBSCOR". 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."/> <concept> <code value="OBSCOR"/> <display value="correlated observation sequences"/> <definition value="Container for Observation Sequences (Observations whose values are contained in LIST<>'s) having values correlated with each other. Each contained Observation Sequence LIST<> must be the same length. Values in the LIST<>'s are correlated based on index. E.g. the values in position 2 in all the LIST<>'s are correlated. This is analogous to a table where each column is an Observation Sequence with a LIST<> 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."/> </concept> </concept> <concept> <code value="POS"/> <display value="position"/> <definition value="An observation denoting the physical location of a person or thing based on a reference coordinate system."/> <concept> <code value="POSACC"/> <display value="position accuracy"/> <definition value="Description:An observation representing the degree to which the assignment of the spatial coordinates, based on a matching algorithm by a geocoding engine against a reference spatial database, matches true or accepted values."/> </concept> <concept> <code value="POSCOORD"/> <display value="position coordinate"/> <definition value="Description:An observation representing one of a set of numerical values used to determine the position of a place. The name of the coordinate value is determined by the reference coordinate system."/> </concept> </concept> <concept> <code value="SPCOBS"/> <display value="specimen observation"/> <definition value="An observation on a specimen in a laboratory environment that may affect processing, analysis or result interpretation"/> </concept> <concept> <code value="VERIF"/> <display value="Verification"/> <definition value="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."/> </concept> </concept> <concept> <code value="PCPR"/> <display value="care provision"/> <definition value="An Act that of taking on whole or partial responsibility for, or attention to, safety and well-being of a subject of care. 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. In request (RQO) mood care provision communicates a referral, which is a request: from one party (linked as a participant of type author (AUT)), to another party (linked as a participant of type performer (PRF), to take responsibility for a scope specified by the code attribute, for an entity (linked as a participant of type subject (SBJ)). The scope of the care for which responsibility is taken is identified by code attribute. 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). Examples: Referral from GP to a specialist. Assignment of a patient or group of patients to the case list of a health professional. Assignment of inpatients to the care of particular nurses for a working shift."/> <concept> <code value="ENC"/> <display value="encounter"/> <definition value="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."/> </concept> </concept> <concept> <code value="POLICY"/> <display value="policy"/> <definition value="Description:A mandate, regulation, obligation, requirement, rule, or expectation unilaterally imposed by one party on: The activity of another party The behavior of another party The manner in which an act is executed"/> <concept> <code value="JURISPOL"/> <display value="jurisdictional policy"/> <definition value="Description:A mandate, regulation, obligation, requirement, rule, or expectation unilaterally imposed by a jurisdiction on: The activity of another party The behavior of another party The manner in which an act is executed Examples:A jurisdictional mandate regarding the prescribing and dispensing of a particular medication. A jurisdictional privacy or security regulation dictating the manner in which personal health information is disclosed. A jurisdictional requirement that certain services or health conditions are reported to a monitoring program, e.g., immunizations, methadone treatment, or cancer registries."/> </concept> <concept> <code value="ORGPOL"/> <display value="organizational policy"/> <definition value="Description:A mandate, obligation, requirement, rule, or expectation unilaterally imposed by an organization on: The activity of another party The behavior of another party The manner in which an act is executed Examples:A clinical or research protocols imposed by a payer, a malpractice insurer, or an institution to which a provider must adhere. A mandate imposed by a denominational institution for a provider to provide or withhold certain information from the patient about treatment options."/> </concept> <concept> <code value="SCOPOL"/> <display value="scope of practice policy"/> <definition value="Description:An ethical or clinical obligation, requirement, rule, or expectation imposed or strongly encouraged by organizations that oversee particular clinical domains or provider certification which define the boundaries within which a provider may practice and which may have legal basis or ramifications on: The activity of another party The behavior of another party The manner in which an act is executed Examples:An ethical obligation for a provider to fully inform a patient about all treatment options. An ethical obligation for a provider not to disclose personal health information that meets certain criteria, e.g., where disclosure might result in harm to the patient or another person. The set of health care services which a provider is credentialed or privileged to provide."/> </concept> <concept> <code value="STDPOL"/> <display value="standard of practice policy"/> <definition value="Description:A requirement, rule, or expectation typically documented as guidelines, protocols, or formularies imposed or strongly encouraged by an organization that oversees or has authority over the practices within a domain, and which may have legal basis or ramifications on: The activity of another party The behavior of another party The manner in which an act is executed Examples:A payer may require a prescribing provider to adhere to formulary guidelines. An institution may adopt clinical guidelines and protocols and implement these within its electronic health record and decision support systems."/> </concept> </concept> <concept> <code value="PROC"/> <display value="procedure"/> <definition value="An Act whose immediate and primary outcome (post-condition) is the alteration of the physical condition of the subject. 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."/> <concept> <code value="SBADM"/> <display value="substance administration"/> <definition value="The act of introducing or otherwise applying a substance to the subject. 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. Examples: Chemotherapy protocol; Drug prescription; Vaccination record"/> </concept> <concept> <code value="SBEXT"/> <display value="Substance Extraction"/> <definition value="Description: The act of removing a substance from the subject."/> <concept> <code value="SPECCOLLECT"/> <display value="Specimen Collection"/> <definition value="A procedure for obtaining a specimen from a source entity."/> </concept> </concept> </concept> <concept> <code value="REG"/> <display value="registration"/> <definition value="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. 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."/> </concept> <concept> <code value="REV"/> <display value="review"/> <definition value="The act of examining and evaluating the subject, usually another act. For example, "This prescription needs to be reviewed in 2 months.""/> </concept> <concept> <code value="SPCTRT"/> <display value="specimen treatment"/> <definition value="A procedure or treatment performed on a specimen to prepare it for analysis"/> </concept> <concept> <code value="SPLY"/> <display value="supply"/> <definition value="Supply orders and deliveries are simple Acts that focus on the delivered product. The product is associated with the Supply Act via Participation.typeCode="product". 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."/> <concept> <code value="DIET"/> <display value="diet"/> <definition value="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". 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. Deprecation Note 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) energyQuantity: This quantity can be conveyed by using a Content relationship with a quantity attribute expressing the calories 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."/> <property> <code value="status"/> <valueCode value="deprecated"/> </property> <property> <code value="deprecationDate"/> <valueDateTime value="2009-08-20"/> </property> </concept> </concept> <concept> <code value="STORE"/> <display value="storage"/> <definition value="The act of putting something away for safe keeping. The "something" may be physical object such as a specimen, or information, such as observations regarding a specimen."/> </concept> <concept> <code value="SUBST"/> <display value="Substitution"/> <definition value="Definition: Indicates that the subject Act has undergone or should undergo substitution of a type indicated by Act.code. Rationale: Used to specify "allowed" substitution when creating orders, "actual" susbstitution when sending events, as well as the reason for the substitution and who was responsible for it."/> </concept> <concept> <code value="TRFR"/> <display value="transfer"/> <definition value="Definition: The act of transferring information without the intent of imparting understanding about a topic to the subject that is the recipient or holder of the transferred information where the participation association must be RCV or HLD."/> </concept> <concept> <code value="TRNS"/> <display value="transportation"/> <definition value="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.)"/> </concept> <concept> <code value="XACT"/> <display value="financial transaction"/> <definition value="A sub-class of Act representing any transaction between two accounts whose value is measured in monetary terms. In the "intent" mood, communicates a request for a transaction to be initiated, or communicates a transfer of value between two accounts. In the "event" mood, communicates the posting of a transaction to an account."/> </concept> <concept> <code value="_ActClassContainer"/> <display value="ActClassContainer"/> <definition value="ActClassContainer"/> <property> <code value="notSelectable"/> <valueBoolean value="true"/> </property> <property> <code value="status"/> <valueCode value="retired"/> </property> <concept> <code value="ENTRY"/> <display value="entry"/> <definition value="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."/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> <concept> <code value="ORGANIZER"/> <display value="organizer"/> <definition value="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 "organizer tree". 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."/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> </concept> </concept> <concept> <code value="DOCCNTNT"/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> <concept> <code value="DOCLIST"/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> <concept> <code value="DOCLSTITM"/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> <concept> <code value="DOCPARA"/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> <concept> <code value="DOCTBL"/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> <concept> <code value="LINKHTML"/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> <concept> <code value="LOCALATTR"/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> <concept> <code value="LOCALMRKP"/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> <concept> <code value="ordered"/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> <concept> <code value="REFR"/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> <concept> <code value="TBLCOL"/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> <concept> <code value="TBLCOLGP"/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> <concept> <code value="TBLDATA"/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> <concept> <code value="TBLHDR"/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> <concept> <code value="TBLROW"/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> <concept> <code value="tbody"/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> <concept> <code value="tfoot"/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> <concept> <code value="thead"/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> <concept> <code value="unordered"/> <property> <code value="status"/> <valueCode value="retired"/> </property> </concept> </CodeSystem>
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.
®© HL7.org 2011+. FHIR Release 4 (Technical Correction #1) (v4.0.1) generated on Thu, Jan 21, 2021 15:39+0000. QA Page
Links: Search |
Version History |
Table of Contents |
Credits |
Compare to R3 |
|
Propose a change
