RSPK31 Dispense History Response (2.6)

This is the standard HL7 v2.6 spec, with 8 loops and 33 segment positions, as OpenEDI JSON, an ediFabric C# template and an ediFabric Native model. To change it for a trading partner, customize it in the EDI Spec Builder.

Loading the spec…
The spec as an OpenAPI 3 schema with x-openedi-* extensions, for ediFabric Native, ediFabric Cloud and the EDI Spec Builder. Download OpenEDI (183 KB) Generate classes
The ediFabric .NET template, class TSRSPK31. It needs the common segments, composites and codes of HL7 v2.6, one download for every transaction in the version. Download C# (1 KB) Common files (99 KB)
The intermediary model ediFabric Native loads with set_map. Native supports X12 today, and HL7 is coming. Download Native (1 KB)

Use the RSPK31 spec in your code

ediFabric .NET

Add the C# template and its common files to your project, or reference the template NuGet package, and read RSPK31 files into TSRSPK31 objects. See ediFabric .NET.

ediFabric Native

Native supports X12 today, and HL7 is coming. When it's available, map version 2.6 to this Native model with set_map to parse RSPK31 files to JSON from Python, Java, C or C#. See ediFabric Native.

OpenEDI

Select Customize in Spec Builder to copy the spec under your own name, change it for your partner, and parse files against it in EdiNation, ediFabric Native or ediFabric Cloud. Read about OpenEDI.

Generate RSPK31 classes in Python, Java, Node.js, Go, Rust or C

The OpenEDI file describes each RSPK31 as JSON. To work with RSPK31 data as typed objects, generate classes from the OpenEDI file in your language; the root class is TSRSPK31. The classes keep the loops, segments, lengths and code lists, but not the EDI data formats. Read more in Generate a class from OpenEDI.

Python: datamodel-code-generator. Node.js: openapi-typescript. Java, Go, Rust and C: OpenAPI Generator.

RSPK31 structure

Loops and segments of the standard RSPK31, with their usage and maximum repeats.

IDNameUsageMax use
MSHMessage HeaderMandatory1
MSAMessage AcknowledgmentMandatory1
ERRErrorOptional>1
SFTSoftware SegmentOptional>1
UACUser Authentication Credential SegmentOptional1
QAKQuery AcknowledgmentMandatory1
QPDQuery Parameter DefinitionMandatory1
RCPResponse Control ParameterMandatory1
Loop PIDPatient IdentificationOptional1
PIDPatient IdentificationMandatory1
PD1Patient Additional DemographicOptional1
NTENotes And CommentsOptional>1
AL1Patient Allergy InformationOptional>1
Loop PV1Patient VisitOptional1
PV1Patient VisitMandatory1
PV2Patient Visit Additional InformationOptional1
Loop ORCCommon OrderMandatory>1
ORCCommon OrderMandatory1
Loop TQ1Timing QuantityOptional>1
TQ1Timing QuantityMandatory1
TQ2Timing Quantity RelationshipOptional>1
Loop RXOPharmacy Treatment OrderOptional1
RXOPharmacy Treatment OrderMandatory1
NTENotes And CommentsOptional>1
RXRPharmacy Treatment RouteMandatory>1
Loop RXCPharmacy Treatment Component OrderOptional>1
RXCPharmacy Treatment Component OrderMandatory1
NTENotes And CommentsOptional>1
Loop RXEPharmacy Treatment Encoded OrderOptional1
RXEPharmacy Treatment Encoded OrderMandatory1
Loop TQ1Timing QuantityMandatory>1
TQ1Timing QuantityMandatory1
TQ2Timing Quantity RelationshipOptional>1
RXRPharmacy Treatment RouteMandatory>1
RXCPharmacy Treatment Component OrderOptional>1
RXDPharmacy Treatment DispenseMandatory1
RXRPharmacy Treatment RouteMandatory>1
RXCPharmacy Treatment Component OrderOptional>1
OBXObservation ResultOptional1
NTENotes And CommentsOptional>1
DSCContinuation PointerOptional1