The ABS (Abstract) segment carries the abstracted summary of a patient's clinical encounter or visit. An abstract is the condensed, attested record that coding, quality, and utilization-review staff produce after a visit closes: who discharged the patient, how severe the illness was, when the record was attested, and a set of perinatal indicators for obstetric and newborn cases. ABS is a low-frequency but information-dense segment that travels with the patient record when an abstract is exchanged between systems.
Because the abstract is a derived summary rather than a real-time clinical event, ABS typically appears after registration and visit data has already been established. It complements the demographic and visit context provided by PID and PV1 rather than replacing them.
Purpose
The ABS segment exists to transmit the clinical/visit abstract as a discrete, structured payload. Its job is to record the attestation and coding metadata that surrounds a completed encounter:
- Identify the care provider responsible for discharge and the clinician who attested to the abstract.
- Capture severity-of-illness and triage classifications used for case-mix and acuity analysis.
- Record the attestation and abstract-completion timestamps that anchor the record for audit.
- Convey perinatal data — gestation, newborn, caesarian, and stillborn indicators — for obstetric abstracts.
ABS does not carry diagnoses or procedures directly; those remain in their own segments. Instead it normalizes the surrounding abstract metadata so a receiving system can file the visit summary consistently.
Used in
ABS conveys a clinical or visit abstract and is used wherever a completed encounter summary is exchanged. It is most often seen in patient-abstract and transfer flows that ride on ADT message structures, where the abstract accompanies the demographic and visit segments after a visit has closed. Receiving systems use ABS to populate utilization-review, case-mix, and quality-reporting workflows.
Field-by-field reference
Source: HAPI HL7v2 v2.5.1 javadocs (ABS.html). Lengths are shown as —; Required and Table # values are taken from the HL7 v2.5.1 standard where well-established.
| Seq | Name | Data Type | Length | Req | Repeat | Table # | Description |
|---|---|---|---|---|---|---|---|
| ABS-1 | Discharge Care Provider | xcn | — | O | — | — | Clinician responsible for the patient's discharge |
| ABS-2 | Transfer Medical Service Code | ce | — | O | — | — | Medical service code at time of transfer |
| ABS-3 | Severity of Illness Code | ce | — | O | — | — | Coded severity-of-illness classification for the visit |
| ABS-4 | Date/Time of Attestation | ts | — | O | — | — | Timestamp the abstract was attested |
| ABS-5 | Attested By | xcn | — | O | — | — | Clinician who attested to the abstract |
| ABS-6 | Triage Code | ce | — | O | — | — | Coded triage classification assigned to the patient |
| ABS-7 | Abstract Completion Date/Time | ts | — | O | — | — | Timestamp the abstract was completed |
| ABS-8 | Abstracted By | xcn | — | O | — | — | Person who created the clinical abstract |
| ABS-9 | Case Category Code | ce | — | O | — | — | Coded category classifying the abstracted case |
| ABS-10 | Caesarian Section Indicator | id | — | O | — | HL70136 | Indicates whether delivery was by caesarian section |
| ABS-11 | Gestation Category Code | ce | — | O | — | — | Coded gestation category for the pregnancy |
| ABS-12 | Gestation Period - Weeks | nm | — | O | — | — | Gestation period expressed in weeks |
| ABS-13 | Newborn Code | ce | — | O | — | — | Coded classification describing a newborn |
| ABS-14 | Stillborn Indicator | id | — | O | — | HL70136 | Indicates whether the birth was stillborn |
Most-used fields
In practice, integrations lean on a small subset of ABS:
- ABS-1 Discharge Care Provider — anchors the abstract to the discharging clinician for accountability.
- ABS-3 Severity of Illness Code — drives case-mix, acuity, and risk-adjustment reporting.
- ABS-4 Date/Time of Attestation — the audit anchor that proves when the abstract was signed off.
- ABS-5 Attested By — identifies the attesting clinician, often required for compliance.
- ABS-7 Abstract Completion Date/Time — used to measure coding turnaround and completeness.
The perinatal fields (ABS-10 through ABS-14) are only populated for obstetric and newborn abstracts and are otherwise left empty.
Version differences (2.3 to 2.8.2)
- 2.3: The ABS segment was not yet part of the patient-administration domain in the same form; abstract-style data was handled informally in site-specific Z-segments.
- 2.4: The ABS segment was introduced to carry the visit abstract with the discharge, attestation, and severity fields that form its core.
- 2.5 / 2.5.1: Field set stabilized at fourteen elements as documented here, including the perinatal indicators (gestation, newborn, caesarian, stillborn). This is the structure reflected by the HAPI v2.5.1 model.
- 2.6 through 2.8.2: The segment definition remains essentially stable. Data-type underpinnings evolve at the type level (for example refinements to coded and timestamp types), but ABS field semantics and ordering are unchanged. Always validate the exact length and optionality against the target system's conformance profile.
Common mistakes
- Treating ABS as a clinical-coding segment: diagnoses and procedures do not belong here. ABS holds abstract metadata only.
- Populating perinatal fields (ABS-10 to ABS-14) on non-obstetric abstracts. Leave them empty unless the case is a delivery or newborn.
- Confusing ABS-4 Date/Time of Attestation with ABS-7 Abstract Completion Date/Time. Attestation is the clinician sign-off; completion is when coding finished.
- Sending ABS without the supporting PID and PV1 context, leaving the receiver unable to file the abstract against the correct visit.
- Assuming ABS-1 and ABS-5 are the same person. The discharge care provider and the attester are frequently different individuals.
Examples
Minimal ABS — only the discharge provider and attestation timestamp populated:
ABS|1004^Nguyen^Carla^^^^MD|||20260608143000|
Fully populated ABS — including severity, triage, completion, and perinatal data for an obstetric abstract:
ABS|1004^Nguyen^Carla^^^^MD|MED^Internal Medicine^L|2^Moderate^HL70421|20260608143000|2271^Okafor^David^^^^MD|3^Urgent^HL70411|20260608161500|5582^Reyes^Mona^^^^RN|OB^Obstetric^L|N|FT^Full Term^L|39|S^Single Live Birth^L|N
Annotated breakdown of the fully populated example:
ABS Segment ID (Abstract)
1004^Nguyen^Carla^^^^MD ABS-1 Discharge Care Provider (XCN)
MED^Internal Medicine^L ABS-2 Transfer Medical Service Code (CE)
2^Moderate^HL70421 ABS-3 Severity of Illness Code (CE)
20260608143000 ABS-4 Date/Time of Attestation (TS)
2271^Okafor^David^^^^MD ABS-5 Attested By (XCN)
3^Urgent^HL70411 ABS-6 Triage Code (CE)
20260608161500 ABS-7 Abstract Completion Date/Time (TS)
5582^Reyes^Mona^^^^RN ABS-8 Abstracted By (XCN)
OB^Obstetric^L ABS-9 Case Category Code (CE)
N ABS-10 Caesarian Section Indicator (ID)
FT^Full Term^L ABS-11 Gestation Category Code (CE)
39 ABS-12 Gestation Period - Weeks (NM)
S^Single Live Birth^L ABS-13 Newborn Code (CE)
N ABS-14 Stillborn Indicator (ID)
In-context excerpt — ABS following the demographic and visit segments in a patient-abstract exchange:
MSH|^~&|HIM|MERCY|ABSTRACT|REGIONAL|20260608161500||ADT^A08^ADT_A01|MSG00231|P|2.5.1
PID|1||MRN556677^^^MERCY^MR||Alvarez^Renata^J||19840312|F
PV1|1|I|3W^312^A^MERCY||||1004^Nguyen^Carla^^^^MD|||MED
ABS|1004^Nguyen^Carla^^^^MD|MED^Internal Medicine^L|2^Moderate^HL70421|20260608143000|2271^Okafor^David^^^^MD
In-context excerpt — ABS in a transfer context carrying the transfer medical service and severity:
MSH|^~&|HIM|MERCY|TRANSFER|EAST|20260609090000||ADT^A02^ADT_A02|MSG00232|P|2.5.1
PID|1||MRN556677^^^MERCY^MR||Alvarez^Renata^J||19840312|F
PV1|1|I|5E^501^B^EAST||||1004^Nguyen^Carla^^^^MD|||SURG
ABS|1004^Nguyen^Carla^^^^MD|SURG^Surgery^L|3^Severe^HL70421|20260609085500||1^Emergent^HL70411
FHIR mapping
ABS is not mapped at the segment level. No segment-level ConceptMap is published in the v2-to-FHIR IG for ABS.
Conceptually, an ABS abstract aligns with a visit-level Composition or an Encounter abstract in FHIR: the attestation fields (ABS-4, ABS-5) correspond to Composition.attester, the discharge provider (ABS-1) and abstractor (ABS-8) to participant roles, and severity (ABS-3) to an Encounter or Condition characteristic. Perinatal indicators map most naturally to Observation resources tied to the delivery or newborn record. Because no normalized field-level mapping is published, treat any ABS-to-FHIR translation as an integration-specific design decision and confirm it against the receiving FHIR profile.
Engine considerations
- ABS is optional in the structures that allow it; engines must not fail a message simply because ABS is absent.
- Most fields are coded (CE) and carry a local code, text, and coding-system triad. Engines should preserve all three components rather than collapsing to the code alone.
- ABS-1, ABS-5, and ABS-8 are XCN person fields. Map identifier, name, and degree components consistently with how the engine maps the same people elsewhere (for example PV1 attending provider).
- Distinguish the two timestamps (ABS-4 attestation, ABS-7 completion) explicitly in transforms; mislabeling them corrupts coding-turnaround metrics downstream.
- Treat the perinatal indicators as conditional: only emit them when the source case is obstetric, and validate the ID values against the receiving system's table.
How Vorro parses and produces ABS
When Vorro parses an inbound message containing ABS, it reads all fourteen fields positionally against the v2.5.1 definition, preserving every CE component (identifier, text, coding system) and every XCN component (ID, family/given name, degree, assigning authority) without lossy normalization. Empty trailing fields are retained as empty rather than dropped, so downstream consumers can distinguish "not sent" from "sent empty."
When producing ABS, Vorro emits fields only when mapped source data exists, leaves the perinatal block (ABS-10 through ABS-14) empty for non-obstetric cases, and normalizes timestamps to the configured precision for ABS-4 and ABS-7. Coded fields are populated from the integration's value-set configuration so that severity, triage, and case-category codes match the receiving system's expectations. The result is a clean, conformant abstract that files correctly alongside the PID and PV1 context.
