# EPCIS 2.0 JSON-LD Supply Chain Event Parser & Validator
> Next-generation EPCIS 2.0 JSON-LD parser and schema compliance validator for modern pharmaceutical supply chain architectures.

- **Canonical URL:** https://stanzaapi.com/tools/pharma-dscsa/compliance/epcis-2-0-json-ld
- **Governing Standard:** 21 U.S. Code § 360eee / GS1 EPCIS (U.S. Food & Drug Administration (FDA) DSCSA)
- **Latency:** <3ms Edge
- **Privacy:** In-memory execution only (zero data stored or logged)

## Technical Overview & Governing Rules
EPCIS 2.0 introduces JSON and JSON-LD serialization for IoT supply chain visibility, REST bindings, and native support for GS1 Digital Link URIs.

Captures environmental sensor telemetry (sensorElementList) such as cold-chain temperature alerts, relative humidity, and real-time geolocation coordinates.

Full compatibility with Core Business Vocabulary (CBV 2.0) standardizing business steps, dispositions, and error reasons.

## Specification Matrix
| Property | Type | Description | Standard |
| --- | --- | --- | --- |
| @context | String / Array | JSON-LD Schema Context | https://ref.gs1.org/standards/epcis/2.0.1/epcis-context.jsonld |
| type | String | Event Type | ObjectEvent, AggregationEvent, TransformationEvent, AssociationEvent |
| sensorElementList | Array | IoT Sensor Data | Temperature, humidity, geolocation |
| bizStep | URI String | Business Process Step | https://ref.gs1.org/cbv/bizstep/shipping |
| ObjectEvent | Event Type | Observe or commission objects | epcList, bizStep, readPoint |
| AggregationEvent | Event Type | Pack or unpack objects into a parent | parentID, childEPCs |
| TransformationEvent | Event Type | Consume inputs into outputs | inputEPCList, outputEPCList |
| AssociationEvent | Event Type | Bind objects to a parent (e.g. device) | parentID, childEPCs, bizStep |

## Standard JSON Response Model
```json
{
  "@context": [
    "https://ref.gs1.org/standards/epcis/2.0.1/epcis-context.jsonld"
  ],
  "type": "ObjectEvent",
  "eventTime": "2026-08-30T11:00:00Z",
  "action": "OBSERVE",
  "bizStep": "transporting",
  "epcList": [
    "https://id.example.com/01/00301234567896/21/123456789012"
  ]
}
```

## Frequently Asked Questions & Edge Cases
### Q: Is EPCIS 2.0 backward-compatible with 1.2 data models?
**A:** Yes, core business steps and event topologies map directly between EPCIS 1.2 and 2.0, with JSON-LD providing native web and API interoperability.

### Q: Does EPCIS 2.0 support real-time IoT sensor telemetry?
**A:** Yes, EPCIS 2.0 natively standardizes sensor reports (sensorReport) including temperature ranges, timestamps, and sensor device IDs for cold-chain pharmaceutical monitoring.

### Q: What is the current EPCIS 2.0 JSON-LD @context URL?
**A:** The current GS1 EPCIS 2.0 JSON-LD context is https://ref.gs1.org/standards/epcis/2.0.1/epcis-context.jsonld (EPCIS/CBV 2.0.1). Pin the versioned URL in your payloads so validation stays deterministic as GS1 publishes patch releases.