Stability data

nutrab2b.quality.stability_reported.v2 · Quality & compliance

Purpose: Time-point results under ICH conditions supporting shelf life and label claims.
When to send: Each stability pull.
Sender → receiver: Manufacturer / lab → Brand
Expected responses: ACK
Equivalent standards: -
Scenarios using it: -

Fields and mappings

Field	Type	Req	Description	Code list / format
study_id	string	yes	Study
lot_number	string	yes	Lot
condition	string	yes	Condition	stability_condition
month	integer	yes	Time point (months)
results	array<object>	yes	Results
analyte	string	yes	Analyte	analyte
value	number	yes	Value
uom	string	yes	Unit	uom
status	string	yes	Status	result_status

Business rules

None beyond schema and code lists.

Example

{
  "specversion": "2.0",
  "id": "evt-stability-ASH-26-118-1",
  "type": "nutrab2b.quality.stability_reported.v2",
  "source": "urn:gln:4012345000009:erp",
  "subject": "ASH-26-118",
  "time": "2026-11-02T09:00:00Z",
  "datacontenttype": "application/json",
  "dataschema": "https://nutrab2b.org/schemas/2.0/STABILITY.json",
  "sender": {
    "gln": "4012345000009"
  },
  "receiver": {
    "gln": "0614141000012"
  },
  "correlationid": "CONV-RFQ-1001",
  "idempotencykey": "STABILITY:ASH-26-118:1",
  "sequence": 1,
  "env": "test",
  "data": {
    "study_id": "STB-ASH-01",
    "lot_number": "ASH-26-118",
    "condition": "LT_25_60",
    "month": 12,
    "results": [
      {
        "analyte": "ASSAY",
        "value": 5.1,
        "uom": "P1",
        "status": "PASS"
      }
    ]
  }
}

Mapping checklist

Every required field populated from your system of record
Coded fields mapped to the Bodylia OpenB2B code lists
GLN, GTIN and SSCC check digits validated
Rules above pass in the validator
Idempotency key and per-subject sequence generated
Expected responses, including rejections, handled