ActClass (Oracle Healthcare Data Repository v8.0 API)

java.lang.Object
- oracle.hsgbu.hdr.hl7.rim.domain.ActClass

```
public class ActClass
extends Object
```
Controls values for structural elements of the HL7 Reference Information Model. Therefore, it is part of the Normative Ballot for the RIM.This table controls values for structural elements of the HL7 Reference Information Model.

Field Summary

Fields
Modifier and Type	Field and Description
`static CS`	`ACCM` 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.
`static CS`	`ACCT` A financial account established to track the net result of financial acts.
`static CS`	`ACSN` A unit of work, a grouper of work items as defined by the system performing that work.
`static CS`	`ACT` An action of interest that has happened, can happen, is happening, is intended to happen, or is requested/demanded to happen.
`static CS`	`ACTN` Sender asks addressee to do something depending on the focal Act of the payload.
`static CS`	`ADJUD` A transformation process where a requested invoice is transformed into an agreed invoice.
`static CS`	`AEXPOS` 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.
`static Set`	`ALL_VALUES` All values defined by this class.
`static CS`	`ALRT` An `Observation` identifying a potential adverse outcome as a result of an `Act` or combination of acts.
`static CS`	`BATTERY` A battery specifies a set of `Observation`s.
`static CS`	`CACT` An `Act` representing a system action such as the change of state of another act or the initiation of a query.
`static CS`	`CASE` A `PublicHealthCase` is an `Observation` representing a condition or event that has a specific significance for public health.
`static CS`	`CATEGORY` A group of entries within a composition or topic that have a common characteristic - for example, examination, diagnosis, management OR subjective, objective, analysis, and plan.
`static CS`	`CDALVLONE` A clinical document that conforms to Level One of the HL7 Clinical Document Architecture (CDA)
`static CS`	`CLNTRL` The set of actions that define an experiment to assess the effectiveness and/or safety of a biopharmaceutical product (food, drug, device, etc.).
`static CS`	`CLUSTER` A group of entries within a composition, topic or category that have a logical association with one another.
`static CS`	`CNOD` An instance of `Observation` of a condition at a point in time that includes any observations or `Procedure`s associated with that condition as well as links to previous instances of condition node for the same condition
`static CS`	`CNTRCT` An agreement of obligation between two or more parties that is subject to contractual law and enforcement.
`static CS`	`COMPOSITION` A context representing a grouped commitment of information to the EHR.
`static CS`	`CONC` A worry that tends to persist over time and has as its subject a state or process.
`static CS`	`COND` 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.
`static CS`	`CONS` Informed consent for surgical procedures, informed consent for clinical trials, advanced beneficiary notice, against medical advice decline from service, release of information agreement, etc.
`static CS`	`CONTAINER` Container of clinical statements.
`static CS`	`CONTREG` An `Act` where a container is registered either by an automated sensor, such as a barcode reader, or by manual receipt
`static CS`	`COV` A healthcare insurance policy or plan that is contractually binding between two or more parties.
`static CS`	`CTTEVENT` 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).
`static CS`	`DETPOL` A determinant peptide in a polypeptide as described by polypeptide.
`static CS`	`DGIMG` Class for holding attributes unique to diagnostic images.
`static CS`	`DIET` `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 by `Participation.typeCode="product"`.
`static CS`	`DISPACT` An action taken with respect to a subject Entity by a regulatory or authoritative body with supervisory capacity over that entity.
`static CS`	`DOC` The notion of a document comes particularly from the paper world, where it corresponds to the contents recorded on discrete pieces of paper.
`static CS`	`DOCBODY` A context that distinguishes the body of a document from the document header.
`static CS`	`DOCCLIN` A clinical document is a documentation of clinical observations and services, with the following characteristics:
`static CS`	`DOCSECT` A context that subdivides the body of a document.
`static CS`	`EHR` A context that comprises all compositions.
`static CS`	`ENC` 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.
`static CS`	`ENTRY` 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.
`static CS`	`EXP` An expression level of genes/proteins or other expressed genomic entities.
`static CS`	`EXPOS` 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.
`static CS`	`EXTRACT` This context represents the part of a patient record conveyed in a single communication.
`static CS`	`FCNTRCT` A contract whose value is measured in monetary terms.
`static CS`	`FOLDER` A context representing the high-level organization of an extract, for example, to group parts of the record by episode, care team, clinical specialty, clinical condition, or source application.
`static CS`	`GEN` An observation of genomic phenomena.
`static CS`	`GROUPER` An ACT that organizes a set of component acts into a semantic grouping that share a particular context such as timeframe, patient, etc.
`static CS`	`HCASE` A public health case is a Concern about an observation or event that has a specific significance for public health.
`static CS`	`INC` An event that occurred outside of the control of one or more of the parties involved.
`static CS`	`INFO` Sender sends payload to addressee as information.
`static CS`	`INFRM` The act of transmitting information and understanding about a topic to a subject.
`static CS`	`INVE` Represents concepts related to invoice processing in healthcare
`static CS`	`INVSTG` An official 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.
`static CS`	`JURISPOL` A mandate, regulation, obligation, requirement, rule, or expectation unilaterally imposed by a jurisdiction.
`static CS`	`LIST` A {link oracle.hsgbu.hdr.hl7.rim.WorkingList} collects a dynamic list of individual instances of `Act` through `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.
`static CS`	`LOC` The position of a gene (or other significant sequence) on the genome.
`static CS`	`MPROT` An officially or unofficially instituted program to track acts of a particular type or categorization.
`static CS`	`OBS` An `Observation` is an action that is performed to determine an answer or result value.
`static CS`	`OBSCOR` `Container` for observation sequences (observations whose values are contained in LIST<>'s) having values correlated with each other.
`static CS`	`OBSSER` `Container` for Correlated Observation Sequences sharing a common frame of reference.
`static CS`	`ORGANIZER` Organizer of entries.
`static CS`	`ORGPOL` A mandate, obligation, requirement, rule, or expectation unilaterally imposed by an organization.
`static CS`	`OUTB` An outbreak represents a series of public health cases.
`static CS`	`OUTBR` An Outbreak is a concern resulting from a series of public health cases.
`static CS`	`PCPR` A `PatientCareProvision` is the taking on of the responsibility by a performer for the healthcare of a patient or group of patients.
`static CS`	`PHN` A genomic phenomenon that is expressed externally in the organism.
`static CS`	`POL` A polypeptide resulting from the translation of a gene.
`static CS`	`POLICY` A mandate, regulation, obligation, requirement, rule, or expectation unilaterally imposed by one party.
`static CS`	`POS` An observation representing the physical location of a place based on a reference coordinate system
`static CS`	`POSACC` 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.
`static CS`	`POSCOORD` An observation representing one of a set of numerical values used to determine the position of a place.
`static CS`	`PROC` An `Act` whose immediate and primary outcome (post-condition) is the alteration of the physical condition of the subject.
`static CS`	`REG` Represents the act of maintaining information about an entity or role in a registry.
`static CS`	`REV` The act of examining and evaluating the subject, usually another act.
`static CS`	`ROIBND` A Region of Interest (ROI) specified for a multidimensional `Observation`, such as an Observation Series (OBSSER).
`static CS`	`ROIOVL` A Region of Interest (ROI) specified for an image using an overlay shape.
`static CS`	`SBADM` The act of introducing or otherwise applying a substance to the subject.
`static CS`	`SBEXT` The act of removing a substance from the subject.
`static CS`	`SCOPOL` 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.
`static CS`	`SEQ` A sequence of biomolecule like the DNA, RNA, protein and the like.
`static CS`	`SEQVAR` A variation in a sequence as described by BioSequence.
`static CS`	`SPCOBS` An `Observation` on a specimen in a laboratory environment that may affect processing, analysis or result interpretation
`static CS`	`SPCTRT` A procedure or treatment performed on a specimen to prepare it for analysis
`static CS`	`SPECCOLLECT` A procedure for obtaining a specimen from a source entity.
`static CS`	`SPLY` Supply orders and deliveries are simple acts that focus on the delivered product.
`static CS`	`STC` Sender transmits a status change pertaining to the focal act of the payload.
`static CS`	`STDPOL` 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.
`static CS`	`STORE` The act of putting something away for safe keeping.
`static CS`	`SUBST` Indicates that the subject Act has undergone or should undergo substitution of a type indicated by Act.code.
`static CS`	`TEXPOS` 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.
`static CS`	`TOPIC` 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.
`static CS`	`TRFR` 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.
`static CS`	`TRNS` Transportation is the moving of a payload (people or material) from a location of origin to a destination location.
`static CS`	`VERIF` An act which describes the process whereby a 'verifying party' validates either the existence of a Role and its associated classes, or of an Act and its participations.
`static CS`	`XACT` A subclass of `Act` representing any transaction between two accounts whose value is measured in monetary terms.

Constructor Summary

Constructors
Constructor and Description

ActClass()

Constructors
Constructor and Description
`ActClass()`

Method Summary
- Methods inherited from class java.lang.Object
  clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

- Field Detail
  - OBS
```
public static CS OBS
```
    An Observation is an action that is performed to determine an answer or result value. Observation result values (Observation.value) include specific information about the observed object. The type and constraints of result values depend on the kind of action performed. 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 a type of observation. Therefore, the establishment of a diagnosis is an observation.
  - ACCT
```
public static CS ACCT
```
    A financial account established to track the net result of financial acts.
  - SPCOBS
```
public static CS SPCOBS
```
    An Observation on a specimen in a laboratory environment that may affect processing, analysis or result interpretation
  - CONTREG
```
public static CS CONTREG
```
    An Act where a container is registered either by an automated sensor, such as a barcode reader, or by manual receipt
  - OBSSER
```
public static CS OBSSER
```
    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 four steps, three leads at a time. Each of the separate 3-channel recordings would be in their own "OBSCOR". And, all four OBSCORs 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.
  - BATTERY
```
public static CS BATTERY
```
    A battery specifies 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 grouped together because of automation. A battery can define mandatory and optional components and, in some cases, will define complex rules that determine whether or not a particular observation is made. Examples include "Blood pressure", "Full blood count", "Chemistry panel".
  - LIST
```
public static CS LIST
```
    A {link oracle.hsgbu.hdr.hl7.rim.WorkingList} collects a dynamic list of individual instances of Act through 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.
  - ENTRY
```
public static CS ENTRY
```
    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.
  - INC
```
public static CS INC
```
    An event that occurred outside of the control of one or more of the parties involved. Includes the concept of an accident.
  - DIET
```
public static CS DIET
```
    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 by 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.
  - CNTRCT
```
public static CS CNTRCT
```
    An agreement of obligation between two or more parties that is subject to contractual law and enforcement.
  - SBADM
```
public static CS SBADM
```
    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 be largely 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 include chemotherapy protocol, drug prescription, vaccination record
  - INFRM
```
public static CS INFRM
```
    The act of transmitting information and understanding about a topic to a subject.
    
    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.
  - DOCBODY
```
public static CS DOCBODY
```
    A context that distinguishes the body of a document from the document header. This is seen, for instance, in HTML documents, which have discrete and elements.
  - CONS
```
public static CS CONS
```
    Informed consent for surgical procedures, informed consent for clinical trials, advanced beneficiary notice, against medical advice decline from service, release of information agreement, etc. are few examples of Consent
    
    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 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 consents may associate a witness or a notary public (examples include living wills, advanced directives). In consents where a healthcare provider is not required (example, 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.
  - DOC
```
public static CS DOC
```
    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.
  - ALRT
```
public static CS ALRT
```
    An Observation identifying a potential adverse outcome as a result of an Act or combination of acts.
    
    Examples include 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 adverse outcome are the target of a subject ActRelationship. The subtypes of this concept indicate the type of problem being detected (e.g. drug-drug interaction) while the Observation.value is used to represent a specific problem code (examples include specific drug-drug interaction id).
  - TOPIC
```
public static CS TOPIC
```
    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.
  - CTTEVENT
```
public static CS CTTEVENT
```
    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.
  - ROIOVL
```
public static CS ROIOVL
```
    A Region of Interest (ROI) specified for an image using an overlay shape. Typically used to make reference to specific regions in images, for example, 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.
  - CACT
```
public static CS CACT
```
    An Act representing a system action such as the change of state of another act or the initiation of a query. All ControlActs represent trigger events in the HL7 context. ControlActs may occur in different moods.
  - EHR
```
public static CS EHR
```
    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.
  - ENC
```
public static CS ENC
```
    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 (example, traffic accident), office visit, occupational therapy, telephone call.
  - OBSCOR
```
public static CS OBSCOR
```
    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. Example, 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.
  - COV
```
public static CS COV
```
    A healthcare insurance policy or plan that is contractually binding between two or more parties.
  - PROC
```
public static CS PROC
```
    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 (example, an incision in a surgical procedure) conservative procedures such as reduction of a luxated join, including physiotherapy such as chiropractic treatment, massage, balneotherapy, acupuncture, and shiatsu. Outside of clinical medicine, procedures may be such things as alteration of environments (example, straightening rivers, draining swamps, building dams) or the repair or change of machinery.
    
    Discussion:
    
    Applied to clinical medicine, procedure is but one among several types of clinical activities, such as observation, substance-administrations, and communicative interactions (Example, teaching, advice, psychotherapy, represented simply as Act objects without special attributes). A Procedure does not subsume those other activities nor is procedure subsumed by them. Notably, a procedure does not consist of all acts of whose intent is intervention or treatment. Whether the bodily alteration is appreciated or intended as beneficial to the subject is likewise irrelevant, what counts is that the act is essentially an alteration of the physical condition of the subject.
    
    The choice between representations for a real activities is based on whether the specific properties of procedure are applicable and whether the activity or activity steps necessary post-condition is the physical alteration. For example, taking an x-ray image may sometimes be called procedure, but it is not a procedure in the RIM sense because an x-ray image is not done to alter the physical condition of the body.
    
    Many clinical activities combine acts of observation and procedure nature into one composite. For instance, interventional radiology (example, catheter directed thrombolysis) does both observing and treating, and most surgical procedures include conscious and documented observation steps. These clinical activities therefore are best represented by multiple component acts each of the appropriate type.
  - ORGANIZER
```
public static CS ORGANIZER
```
    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.
  - COMPOSITION
```
public static CS COMPOSITION
```
    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.
  - ACCM
```
public static CS ACCM
```
    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.
  - COND
```
public static CS COND
```
    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 include equipment repair status, device recall status, a health risk, a financial risk, public health risk, pregnancy, health maintenance, and chronic illness
  - OUTB
```
public static CS OUTB
```
    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.
  - CLUSTER
```
public static CS CLUSTER
```
    A group of entries within a composition, topic or category that have a logical association with one another. The representation of a single Observation or action might itself be multi-part. The data might need to be represented as a nested set of values, as a table, list, or as a time series. The cluster class permits such aggregation within an entry for such compound data. Examples include Haematology investigations, which might include two or more distinct batteries. A cluster may contain batteries and/or individual entries
  - INFO
```
public static CS INFO
```
    Sender sends payload to addressee as information. Addressee does not have responsibilities beyond serving addressee's own interest (read and memorize if you see fit). This is equivalent to an FYI on a memo.
  - ROIBND
```
public static CS ROIBND
```
    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 to be 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 EKG 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).
  - ADJUD
```
public static CS ADJUD
```
    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 consists of two components: the adjudication processing results and a restated (or adjudicated) invoice or claim
  - CLNTRL
```
public static CS CLNTRL
```
    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.
  - STC
```
public static CS STC
```
    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 a command, according to the mood of the control act.
  - DGIMG
```
public static CS DGIMG
```
    Class for holding attributes unique to diagnostic images.
  - FOLDER
```
public static CS FOLDER
```
    A context representing the high-level organization of an extract, for example, 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.
  - CATEGORY
```
public static CS CATEGORY
```
    A group of entries within a composition or topic that have a common characteristic - for example, examination, diagnosis, management OR subjective, objective, analysis, and plan. The distinction from topic relates to value sets. For category, there is a bounded list of things such as "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.
  - ACSN
```
public static CS ACSN
```
    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).
  - XACT
```
public static CS XACT
```
    A subclass 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.
  - MPROT
```
public static CS MPROT
```
    An officially or unofficially instituted program to track acts of a particular type or categorization.
  - CASE
```
public static CS CASE
```
    A PublicHealthCase 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.
  - TRNS
```
public static CS TRNS
```
    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.)
  - SPCTRT
```
public static CS SPCTRT
```
    A procedure or treatment performed on a specimen to prepare it for analysis
  - DOCSECT
```
public static CS DOCSECT
```
    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.
  - ACT
```
public static CS ACT
```
    An action of interest that has happened, can happen, is happening, is intended to happen, or is requested/demanded to happen. An act is an intentional action in the business domain of HL7. Healthcare (and any profession or business) is constituted of intentional actions. An Act instance is a record of such an intentional action.
    
    Any intentional action can exist in different moods. Moods describe activities as they progress in the business cycle, from defined, through planned and ordered to complete.
    
    Any instance of an Act assumes one and only one mood and will not change its mood along its life cycle. The moods - definition, intent, order, event - seem to specify a life cycle of an activity. However, the participants in the activity in these different moods are different, as is the data. Therefore, the mood of an Act instance is static. The progression actualization (the progression from defined, through planned and ordered, to being performed) is called the business cycle to distinguish it from the lifecycle of a single Act instance. Related Act instances that form such a business cycle are linked through the ActRelationship class.
    
    Examples for acts in healthcare are: a clinical test, an assessment of health condition (such as problems and diagnoses), the setting of healthcare goals, the performance of treatment services (such as medication, surgery, physical and psychological therapy), assisting, monitoring or attending, training and education services to patients and their next of kin, and notary services (such as advanced directives or living will).
    
    Acts have participants, which can be actors or targets. Examples of actors are nurses, doctors, family members, notary publics, and service organizations - every person or organization that is capable of independent decisions and can thus is responsible (and liable) for the actions performed.
    
    Target participants in an act may include the patient, the patient's spouse, family, or community, a specimen drawn from the patient or from any object of interest. As patients do play active roles in their own healthcare, the patient can be both an active participant and a target participant at the same time (self-administered or reflexive services).
    
    An act can have multiple active participants and multiple target participants, their specific role being distinguished in the typeCode of the respective instance of the Participation class. In particular, an act involving coordination of care may involve two or more active participants - playing different roles - who interact on behalf of a patient, family, or aggregate in the role of target participant. For example, a nurse (active participant) calls Meals on Wheels (active participant) on behalf of the patient (target participant).
    
    An act includes the results, answers, or informational procedure products gained during the act. In this model, "results" do not exist without an act, and every clinical result, including those results gained accidentally, is gleaned by an act. In other moods, such as definition or intent, the results are the possible results, the expected or aimed-for results, or the tested-for results.
  - INVE
```
public static CS INVE
```
    Represents concepts related to invoice processing in healthcare
  - EXTRACT
```
public static CS EXTRACT
```
    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 (Example, changes since a specified date). An extract contains folders or compositions. An extract cannot contain another extract.
  - FCNTRCT
```
public static CS FCNTRCT
```
    A contract whose value is measured in monetary terms.
  - ACTN
```
public static CS ACTN
```
    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).
  - DOCCLIN
```
public static CS DOCCLIN
```
    A clinical document is a documentation of clinical observations and services, with the following characteristics:
    
    (1) Persistence - A clinical document continues to exist in an unaltered state, for a time period defined by local and regulatory requirements.
    
    (2) Stewardship - A clinical document is maintained by a person or organization entrusted with its care.
    
    (3) Potential for authentication - A clinical document is an assemblage of information that is intended to be legally authenticated.
    
    (4) Wholeness - Authentication of a clinical document applies to the whole and does not apply to portions of the document without the full context of the document.
    
    (5) Human readability - A clinical document is human readable.
  - INVSTG
```
public static CS INVSTG
```
    An official 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.
  - CDALVLONE
```
public static CS CDALVLONE
```
    A clinical document that conforms to Level One of the HL7 Clinical Document Architecture (CDA)
  - CNOD
```
public static CS CNOD
```
    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
  - REG
```
public static CS REG
```
    Represents the act of maintaining information about an entity or role in a registry. The class is most general, designed to support a variety of registries for persons, patients, practitioners, and equipment. If required, specific registry types will be treated as specializations of this class.
  - PCPR
```
public static CS PCPR
```
    A PatientCareProvision is the taking on of the responsibility by a performer for the healthcare of a patient or group of patients. Discussion: The patient care event can exist without any care actions having taken place. The scope of the care is identified by Act.code. Examples: (1) preferred primary care provision: the primary care physician being the primary performer participation, author being the patient (2) referral from general practitioner to specialist (a PCPR in request mood, where the author participant is the GP, and the primary performer participation is the specialist) (3) a case manager to a patient or group of patients (4) assigning nurses to patients each shift
  - SPLY
```
public static CS SPLY
```
    Supply orders and deliveries are simple acts that focus on the delivered product. The product is associated with the Supply by using Participation.typeCode="product". With general SupplyActs, 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 SupplyAct. Pharmacy dispense services are represented as Supply Acts, associated with a substance administration act. The SubstanceAdministration class represents the administration of medication, while dispensing is supply.
  - SUBST
```
public static CS SUBST
```
    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.
  - SPECCOLLECT
```
public static CS SPECCOLLECT
```
    A procedure for obtaining a specimen from a source entity.
  - DISPACT
```
public static CS DISPACT
```
    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
  - REV
```
public static CS REV
```
    The act of examining and evaluating the subject, usually another act. For example, "This prescription needs to be reviewed in 2 months
  - STORE
```
public static CS STORE
```
    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.
  - VERIF
```
public static CS VERIF
```
    An act which describes the process whereby a 'verifying party' validates either the existence of a Role and its associated classes, or of an Act and its participations.
  - POS
```
public static CS POS
```
    An observation representing the physical location of a place based on a reference coordinate system
  - POSACC
```
public static CS POSACC
```
    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.
  - POSCOORD
```
public static CS POSCOORD
```
    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.
  - AEXPOS
```
public static CS AEXPOS
```
    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.
  - CONC
```
public static CS CONC
```
    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.
  - CONTAINER
```
public static CS CONTAINER
```
    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".
  - DETPOL
```
public static CS DETPOL
```
    A determinant peptide in a polypeptide as described by polypeptide.
  - EXP
```
public static CS EXP
```
    An expression level of genes/proteins or other expressed genomic entities.
  - EXPOS
```
public static CS EXPOS
```
    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.
  - GEN
```
public static CS GEN
```
    An observation of genomic phenomena.
  - GROUPER
```
public static CS GROUPER
```
    An ACT that organizes a set of component acts into a semantic grouping that share a particular context such as timeframe, patient, etc.
  - HCASE
```
public static CS HCASE
```
    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.
  - JURISPOL
```
public static CS JURISPOL
```
    A mandate, regulation, obligation, requirement, rule, or expectation unilaterally imposed by a jurisdiction.
  - LOC
```
public static CS LOC
```
    The position of a gene (or other significant sequence) on the genome.
  - ORGPOL
```
public static CS ORGPOL
```
    A mandate, obligation, requirement, rule, or expectation unilaterally imposed by an organization.
  - OUTBR
```
public static CS OUTBR
```
    An Outbreak is a concern resulting from a series of public health cases.
  - PHN
```
public static CS PHN
```
    A genomic phenomenon that is expressed externally in the organism.
  - POL
```
public static CS POL
```
    A polypeptide resulting from the translation of a gene.
  - POLICY
```
public static CS POLICY
```
    A mandate, regulation, obligation, requirement, rule, or expectation unilaterally imposed by one party.
  - SBEXT
```
public static CS SBEXT
```
    The act of removing a substance from the subject.
  - SCOPOL
```
public static CS SCOPOL
```
    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.
  - SEQ
```
public static CS SEQ
```
    A sequence of biomolecule like the DNA, RNA, protein and the like.
  - SEQVAR
```
public static CS SEQVAR
```
    A variation in a sequence as described by BioSequence.
  - STDPOL
```
public static CS STDPOL
```
    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.
  - TEXPOS
```
public static CS TEXPOS
```
    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.
  - TRFR
```
public static CS TRFR
```
    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.
  - ALL_VALUES
```
public static final Set ALL_VALUES
```
    All values defined by this class.
- Constructor Detail
  - ActClass
```
public ActClass()
```

Class ActClass

Field Summary

Constructor Summary

Method Summary

Methods inherited from class java.lang.Object

Field Detail

OBS

ACCT

SPCOBS

CONTREG

OBSSER

BATTERY

LIST

ENTRY

INC

DIET

CNTRCT

SBADM

INFRM

DOCBODY

CONS

DOC

ALRT

TOPIC

CTTEVENT

ROIOVL

CACT

EHR

ENC

OBSCOR

COV

PROC

ORGANIZER

COMPOSITION

ACCM

COND

OUTB

CLUSTER

INFO

ROIBND

ADJUD

CLNTRL

STC

DGIMG

FOLDER

CATEGORY

ACSN

XACT

MPROT

CASE

TRNS

SPCTRT

DOCSECT

ACT

INVE

EXTRACT

FCNTRCT

ACTN

DOCCLIN

INVSTG

CDALVLONE

CNOD

REG

PCPR

SPLY

SUBST

SPECCOLLECT

DISPACT

REV

STORE

VERIF

POS

POSACC

POSCOORD

AEXPOS

CONC

CONTAINER

DETPOL

EXP

EXPOS