T1Scope, method and evidentiary boundary

The focus is United States prescription-drug distribution involving manufacturers, wholesalers, dispensers and their delegated service providers. The account profile supports two existing contexts: required tracing and investigation workflows, and separately authorized commercial reporting. It does not establish a universal manufacturer right to downstream records.

Earlier project research, including an adversarial-tribunal draft, is treated as design input. Its assertions are not promoted to independent evidence because they recur in several documents. This package replaces the earlier conclusion that a unanimous review proves the design with an assurance register and explicit deployment gates. The account-binding and transfer-context separation is retained; the purpose and settlement rules are rewritten.

Evidence labels

Research discipline. Primary sources were used for load-bearing requirements and mechanism descriptions. Specification availability, implementation documentation and production adoption are different forms of evidence. This package does not assign calibrated probabilities to source quality or infer pharmaceutical results from advertising adoption. No confidential customer or account data was sent to public research services. No downloaded research code was executed.

Regulatory timing. FDA's August 6, 2026 letter provides specified relief through November 27, 2027 for qualifying small business dispensers and applicable trading-partner activities. Eligibility is defined at the owning corporate entity and includes the stated employee and date criteria. Pilot partners' actual obligations, exceptions and service arrangements must be established individually. [29, 30]

T2The documented problem

Multiple accounts are legitimate; inconsistent interpretation is the failure. Cencora's September 2024 guidance describes WAC, GPO and 340B accounts at the same physical location being associated with one GLN. That is a documented company configuration, not a universal rule that every street address has exactly one GLN. It illustrates why the destination identifier and the purchasing relationship must remain separate. [9]

Two denominator corrections that change the business case

The Cardinal Health pilot's 507 records were logged transmission and support samples, not a representative sample of shipments. Successful automated exchanges without the specified human interaction were excluded. The 364 exception records therefore do not establish a 72 percent industry failure rate. The timing and master-data categories are useful for designing test cases, not for estimating national incidence. [28]

The HDA and Rutgers paper cites a weighted 0.7 percent chargeback rejection rate from the 2017 HDA Factbook. Its 43 percent and 46 percent eligibility figures concern respondents in two trade-letter-information subgroups. They are not identity-error rates or shares of disputed dollars; the study did not derive an industry rejection cost. [6]

T3Preserve the pharmaceutical baseline

FDA recommends EPCIS for interoperable tracing-data exchange. Statutory TI includes product and transaction information and the business names and addresses of transfer parties; it is not legally defined as a list of GLNs alone. Routine Transaction History exchange effectively ended on November 27, 2023, but relevant tracing-information gathering continues under the applicable provisions. DSCSA does not establish a general manufacturer entitlement to every downstream TI record. [1, 2, 8, 31]

An actual route may include a 3PL, a drop shipment or another arrangement in which possession and ownership diverge. Do not draw every physical handler as a legal ownership hop. EPCIS and CBV already distinguish owning party, possessing party and location, and support business-transaction references, aggregation and corrections. [1, 3, 32]

Existing coverage is substantial

Residual opportunity: a shared way to expose and interpret an issuer's account relationship, its evidence and the exact version used. This is primarily a configuration and governance problem with a possible narrow interface-profile gap, not proof of a missing industry-wide identity standard.

T4Ad-tech mechanisms worth retaining

Reuse coordination behavior, not advertising semantics.

These sources establish published formats and operational interface patterns. They do not establish how much of a pharmaceutical rejection rate is addressable, or prove that a particular wholesaler would adopt the profile. The SupplyChain object contributes a useful issuer and account tuple, not a second custody graph. A declared path-complete flag cannot certify tracing completeness, and an existing seller or domain entry cannot prove drug authenticity.

T5Three more ad-tech patterns that close implementation gaps

A common adapter contract, learned from Prebid

Prebid Server requires explicit adapter schemas and provides request and response fixture-testing patterns; its guidance also restricts arbitrary endpoint behavior. The lesson is not to run a pharmaceutical workflow through an auction server. It is to isolate each partner's interface behind a small, tested contract. [24]

Proposed implementation. Each wholesaler or registry adapter declares its source owner, supported identifier types, schema versions, lookup capabilities, error mappings and authorized endpoints. Contract tests cover nulls, leading zeros, multiple matches, stale source status, missing permissions and unsupported history. No adapter can promote a candidate match or reinterpret an authorization decision.

Activity-specific controls, not a purpose entitlement string

Prebid activity controls separate component activities from a component's mere presence. That enforcement structure adapts to resolve_account, read_history, manage_endpoint and release_fields. Its advertising defaults and privacy predicates must not be imported; some documented defaults are permissive. [25]

Proposed implementation. An existing policy enforcement point checks the authenticated actor, represented organization, operation, resource, fields and authority evidence before an adapter is invoked and again before data is released. Supplemental data access is denied unless authorized. An established statutory tracing route is not disabled because an optional account-profile field is missing.

Configuration acknowledgment plus polling repair, learned from the Deals API

IAB Tech Lab's Deals API v1.0, released for public comment in December 2025, separates origin-provided configuration from receiver status, preserves the origin's ID and recommends polling to recover missed notifications. It explicitly excludes revisions, negotiation and deciding whether a deal applies. Public specification availability is not evidence of broad deployment. [26]

Proposed implementation. When a contract roster, account relationship or endpoint changes, the sender publishes an immutable version reference. The receiver acknowledges receipt and separately records whether it can apply that version. A periodic reconciliation detects missing updates. An acknowledgment means neither contract acceptance nor transaction eligibility.

T6Established non-IAB mechanisms where they fit better

Selection rule. Use the deployed identity provider, message bus, audit store and integration framework first. A standard is not a requirement to introduce another product or service. Add a mechanism only when its acceptance test cannot be satisfied cleanly by the existing stack.

Code reuse versus design reuse. No UID2, Prebid or Deals API code is required. Copying their wire schemas would carry unsuitable defaults and semantics. Use supported enterprise libraries for schema validation, OAuth and signatures; review licenses, maintenance and vulnerabilities before selecting packages. Where supported, token exchange can distinguish an acting service from the organization it represents; it does not authorize the service to read every record belonging to that organization. [50, 52, 54]

T7Target architecture and assertion authority

One thin integration profile; existing systems retain ownership.

GS1 and HIBCC integration means authorized reference and lookup, not a claim that either registry accepts this custom schema. Registry licensing, caching, archive and redistribution rights must be confirmed. HIBCC's existing collaboration with MediLedger cautions against claiming a previously empty market. [5, 10, 33, 55]

Who can assert what

The issuer is authoritative about its account assignment, not infallible about external facts. Conflicts require source-owner correction. Two agreeing assertions can still be wrong; bilateral corroboration is evidence, not certainty.

T8Access without invented disclosure rights

A request declares its workflow context, the idea the Transparency and Consent Framework applies when a purpose is declared at impression time. The declaration is logged and used to scope the response. It does not create a statutory obligation, a contractual entitlement or permission to disclose a complete account history. DSCSA information-gathering and verification obligations depend on the requester, role, transaction and applicable provision; protection of confidential commercial information remains relevant. A non-refusable purpose class at the resolver is therefore not adopted. [2, 31]

Implementation detail. Rich Authorization Requests can express requested actions, resources and data types where the authorization server supports them. They do not decide whether the asserted legal authority is valid. Separate authorization-detail entries are needed when different actions apply to different resources. A local policy decision object is sufficient where RAR is not deployed. [37, 38]

A regulator need not impersonate a commercial account holder. Conversely, a commercial requester cannot obtain investigation-level information by changing an operation code. The response references the verified authority decision and applied policy version; it does not store reusable credentials in an enduring product record.

NPI boundary. No NPI-to-staff or account requirement is introduced. Existing identifiers may be retained where legitimately used, but employment, representation and permission come from verified organizational access controls.

T9Minimal records and cardinality

The profile has two necessary logical artifacts: an account assertion and the transaction's resolution receipt. Lifecycle and delegation evidence may reuse existing source events and access records. They are not forced into one envelope.

Illustrative account assertion (fictional, unsigned, not an EPCIS document) Proposed profile 0.2

{
  "schema_version": "0.2",
  "record_kind": "account_binding",
  "binding_id": "urn:example:binding:gpo-001",
  "version": 1,
  "issuer_ref": "urn:example:org:wholesaler-a",
  "account": { "namespace": "urn:example:wholesaler-a:erp1:accounts", "id": "004921" },
  "relationships": [
    { "role": "purchaser", "subject_kind": "organization", "subject_ref": "urn:example:org:hospital", "identifier_refs": [] },
    { "role": "ship_to",   "subject_kind": "location",     "subject_ref": "urn:example:site:hospital-north", "identifier_refs": [] }
  ],
  "purchasing_context": [{ "system": "urn:example:codes:purchasing-program", "version": "1", "code": "GPO" }],
  "valid_time": { "from": "2026-01-01T00:00:00Z", "to": null },
  "recorded_at": "2026-01-02T10:00:00Z",
  "provenance": { "asserted_by": "urn:example:org:wholesaler-a", "matched_by": "urn:example:org:wholesaler-a",
                  "match_method": "issuer_record_confirmed", "evidence_refs": ["urn:example:evidence:crm-export-2026-01"],
                  "checked_at": "2026-01-02T10:00:00Z" },
  "assurance": "source_confirmed"
}

Illustrative resolution receipt (fictional, separate from eligibility)

{
  "record_kind": "resolution_receipt",
  "transaction_ref": "urn:example:edi:844:doc-77:line-3",
  "binding_refs": [{ "binding_id": "urn:example:binding:gpo-001", "version": 1 }],
  "effective_at": "2026-02-15T00:00:00Z",
  "knowledge_cutoff": "2026-02-20T10:00:00Z",
  "resolved_at": "2026-02-20T10:00:00Z",
  "resolver_ref": "urn:example:service:resolver-a",
  "resolution_outcome": "resolved",
  "authorization_decision_ref": "urn:example:authz:decision-83",
  "policy_version": "bilateral-profile-4",
  "workflow_declared": "chargeback_interpretation",
  "eligibility_decision_ref": null
}

eligibility_decision_ref: null means no eligibility decision is represented, not that eligibility passed. The receipt cannot itself grant access. A later reassessment creates another receipt and retains the original.

Referential integrity. A binding may have several locations; the transaction must select its actual destination under the agreed relationship rules. An array match must not fan records out to every location. A binding_ref points to one immutable version while the logical binding_id may have successors; these are different API operations. A new owner does not automatically acquire access to the old owner's commercial records.

Excluded from the binding: package serial, lot and expiry, EPCIS disposition, full TI and TS, contract prices, approval verdicts, private keys and patient data.

T10Time, corrections and lifecycle

Two times answer different questions. Effective time says when a relationship applied. Recorded time says when the issuer's system learned or recorded the assertion. Neither is the same as EPCIS event time or repository capture time. The relationship history complements existing HIN and GS1 predecessor information and EPCIS corrections; it does not replace them. [3, 5, 10]

The first assertion is not edited to conceal its existence. A projection may derive valid and recorded intervals from successor and correction events. The original record bytes, the later correction and the reason for change remain retained. Ambiguous or conflicting assertions are not resolved merely by taking the latest timestamp across unrelated issuers.

Keep three state axes separate

Assurance: candidate, reviewed or source-confirmed. This describes evidence quality under the pilot's rules; it is not a calibrated probability. Lifecycle: proposed, active, suspended, retired or withdrawn, expressed by authorized lifecycle events. A past assertion can remain readable even though it can no longer route new transactions. Access: allowed, denied, restricted or escalated for a specific authenticated request. A valid active binding does not make every requester authorized.

Successor discovery is not historical retrieval. An exact-version lookup either returns the named version or a controlled unavailable response. It never redirects to the latest owner or location. A separate successor query may return candidates and effective dates. Account reuse, merges, splits and retrospective corrections require explicit lineage.

T11Resolver and adapter contract

The paths below are proposed pilot interfaces, not existing GS1, UID2 or OCI endpoints. A partner's existing interface may implement equivalent behavior without these names.

Two levels of failure. Top-level authentication, authorization, malformed-request, capacity and availability failures use the selected HTTP semantics and RFC 9457 where appropriate. A valid batch can return HTTP 200 with explicit per-item application outcomes. [41]

Result vocabulary (proposed): resolved, unknown_account, needs_destination, ambiguous_binding, inactive_binding, evidence_stale, unsupported_history, not_accessible. These are new pharmaceutical-profile terms, not UID2's consumer outcomes. A caller outside an account's permitted scope receives a non-enumerating result rather than an existence or evidence report.

Adapter invariants. Every adapter preserves the source account string and its namespace. It reports unsupported functionality explicitly. It cannot invent missing valid-time history, treat a timeout as no match, merge distinct subjects on address similarity, or convert a probabilistic candidate into a verified route. All outgoing destinations come from approved configuration; caller-controlled URLs and untrusted evidence links are not fetched. [24]

Cache rule. Cache by issuer, account, time mode, source and version and disclosure scope. refresh_after is a profile recheck hint, not a promise that current authorization cannot change. Revalidate permission on access and apply bounded continuity rules when a source is unavailable. [20, 46]

T12Reliable updates and explicit acknowledgments

A notification is not the state of record. The account store and its update mechanism must not disagree silently. Use the existing enterprise event infrastructure where it already provides durable publication, deduplication and reconciliation; an additional bus is not a prerequisite.

CloudEvents can standardize the envelope if both systems support it; it supplies neither delivery guarantees nor pharmaceutical business meaning. The outbox pattern does not remove the need for idempotent receivers. EPCIS subscriptions and capture jobs remain bound to their defined queries, events and status semantics; they do not automatically carry arbitrary resolver errors. PDG's structured notification content can travel over an agreed API, service-provider integration or existing email bridge. [3, 13, 14, 15, 44, 45]

T13Integration with EPCIS, X12 and existing masters

EPCIS integration order. First use existing provider routing and audit metadata. Next consider a bilateral sidecar keyed to an existing document or event identifier. Add a namespaced event extension only when the deployed application profile and counterparties preserve it and it belongs at that event. EPCIS eventID is optional in the core model; when absent, define an agreed stable document or record locator rather than quietly minting an ID. [3]

X12 integration order. Default to an associated record keyed by issuer, document, line, business date and original identifiers, with the unaltered source retained. A reference inside 844 or 867 is an alternative only after the actual version, segment, loop, qualifier, length and partner implementation guide are verified. Nothing here asserts that a universal REF placement exists or that "no X12 change" is required. [7]

T14Vocabulary and semantic crosswalks

Use separate dimensions for organization role, account relationship, purchasing context, assurance, lifecycle, resolution outcome and operation. Reuse EPCIS, CBV and PDG meanings where they already apply. Do not place GPO and ship-to in the same mutually exclusive role list. [13, 14, 15, 32]

Each production vocabulary needs a named owner, namespace, version, definitions, effective dates, compatibility rules and a deprecation path. PDG, HDA and relevant GS1 and HIBCC participants are potential governance collaborators, not committed sponsors. Until governance is agreed, the vocabulary is a bilateral pilot profile.

SKOS supplies precise concept-mapping predicates, but exactMatch is transitive; assigning it loosely can spread an unjustified equivalence through a graph. Broader and narrower mappings do not establish that two parties or contracts are identical. PROV-O can connect each mapping to source records, transformation activity and responsible agents; the initial implementation can retain equivalent plain JSON fields. [42, 43]

T15Worked workflows, investigations and continuity

A. Order, tracing exchange and chargeback (one hospital site, three purchasing relationships; fictional)

1. Establish the account. The wholesaler records the GPO account's issuer namespace, purchaser and ship-to references. Existing GS1 and HIN records are checked under their access terms. The hospital's appropriate administrator confirms a new receiving-service delegation.
2. Publish evidence. The verified relationship becomes an immutable assertion with effective and recorded times. A contradictory location remains an exception rather than being resolved by a name or address score.
3. Process the order. The transaction resolves the specific GPO account and selected destination. The WAC and 340B account relationships are not merged into it. The resolver checks current authorization and records the exact binding version used.
4. Exchange records. Product tracing follows the existing channel. A sidecar or supported metadata extension links the transaction to its binding reference. The receiving organization separately matches product and electronic evidence.
5. Interpret the claim. The manufacturer's authorized 844 workflow receives the permitted account context. Its eligibility engine checks contract, membership or roster, product scope and effective dates. The calculation then applies price, quantity and duplicate controls. These are separate decisions with possibly different outcomes.
6. Resolve disagreement. A claim can have a correct account mapping but a wrong price or inapplicable contract. The record cites which evidence and rules produced each decision. An account-related correction creates a successor and a reassessment; it does not overwrite the submitted claim.

B. Drop shipment. The wholesaler may issue a PO to the manufacturer while the dispenser uses a different PO. Preserve both issuer-scoped references and the supported document and line relationship. A commercial account assertion explains the customer reference; it does not insert a fictitious wholesaler possession event. [3, 11, 32]

C. A late location correction. If a move is confirmed after a sale, keep the old processing receipt and the later corrected interpretation. Eligibility reassessment is explicitly authorized and separately logged; a successor identifier is not automatic proof of retroactive contract coverage.

Investigation: a scoped route, not a full-history switch

An investigator requests records for a specified product, transaction range or case. The service authenticates the requester and checks the applicable authority through the established process. It resolves only the necessary relationship context and releases the responsive fields. A request marked suspect_product cannot automatically retrieve every superseded customer account. A purpose mismatch produces a recorded policy decision or escalation, not a hidden denial of a valid legal obligation. [2, 31]

Optional manufacturer sourcing information

A machine-readable manufacturer distributor list may improve a voluntarily adopted sourcing or risk check. It must remain distinct from DSCSA ATP status and from product-specific authenticity. Presence is not proof of a legitimate package; absence is not automatic proof of illegal resale. The reviewed eCFR text of 21 CFR 203.50 includes written-list and public-on-request language. FDA's February 2022 proposal contemplated removal of that section after statutory changes. This package does not resolve its current operative applicability or present a signed list as a DSCSA mandate; the optional design requires counsel review. The 2023 Gilead opinion discusses allegedly forged pedigrees and licensed downstream wholesalers; it does not establish that every manufacturer-unauthorized resale is illegal. [23, 56, 57, 58]

Controls when a dependency fails

Signed resale chains, universal pharmacy tokens, ads.cert deployment and a paid Data Transparency audit program are not selected. PAIR and ADMaP remain deferred unless a measured confidential-roster use case establishes a need and valid shared matching material. No collective commercial-customer pool is proposed. A private delegated service may support more than one issuer only with tenant separation and explicit authority; federation does not make it the owner of those account facts.

T16Measure cause, not just lookup success

An unresolved mapping may coexist with a price error without causing the rejection. A resolved mapping may be confidently wrong. A report of resolved, unmapped and ambiguous outcomes is therefore a diagnostic, not the identity share of exceptions or disputed dollars.

Independent adjudication. Use representative records from both accepted transactions and exceptions, with known sampling probabilities where sampling is used. Retain product family, partner, workflow, period and case-mix information. Reconstruct the evidence available at the original decision, not just today's corrected master. Two qualified reviewers independently classify a bounded sample, with adjudication for disagreement. Reviewers must not accept the new resolver's output as evidence of correctness. Record missing evidence rather than force a category.

Retrospective replay can test historical reconstruction and mapping agreement. Reduced live rejection rates, staff effort and time to resolution require a prospective controlled phase or a separately instrumented work study. Neither a simulated tribunal nor a passing fixture suite supplies those outcomes.

T17Pilot gates, metrics and economic decision

Use one willing manufacturer, one wholesaler, one health system with the documented price-class account pattern, and their existing service providers. A second issuer or provider is a later interoperability test, not a prerequisite for discovering whether the first gap exists.

Required measures. Accuracy: agreement with independently adjudicated account and relationship truth, including wrong confident matches; coverage and unresolved cases reported separately. Operational benefit: manual touches, median and 95th-percentile resolution time, avoidable resubmissions, onboarding effort and partner correction latency. Economic effect: root-cause-reviewed counts and dollars with transaction volume and case mix; a rejected claim's face value is not automatically a recoverable loss. Safety and continuity: wrong-recipient tests, endpoint changes, unavailable-source behavior, historical reconstruction, product and data latency and added lookup cost; any unauthorized routing blocks release.

Targets and sampling thresholds must be set before evaluation. Zero observed errors is not proof of zero risk: under independent identical trials, a zero-error sample of size n has a one-sided 95 percent binomial upper bound of 1 minus 0.05 to the power 1/n; real claim clusters may violate those assumptions. Duration depends on access, data quality, staffing and partner testing. There is no unconditional "export plus a fortnight" estimate and no new automatic chargeback withholding rule.

T18Design-assurance register and acceptance contract

Analytical perspectives, not an independent expert tribunal. The table records revised design decisions. It does not claim that a real panel voted, that external reviewers endorsed the system, or that design agreement demonstrates operational effectiveness.

Ordered implementation increments

1. Existing-system baseline. Data owners inventory identifier history, update HIN and GLN records, classify accounts and correct partner routing. Finance and compliance agree on evidence and rights. The output is a measured baseline, not a new platform.
2. Issuer extension. Add immutable relationship versions and evidence references where absent. Preserve effective and recorded times, typed subjects and source account strings. Deploy one adapter and a read-only resolver using existing security.
3. Decision receipts. Connect selected transactions to their exact interpreted versions in existing audit storage. Keep contract and eligibility decisions separate. Introduce portable signatures only where authenticated lookup plus retained source evidence is insufficient for the agreed audit use case.
4. Reliability and narrow activation. Reuse existing notification channels; add durable change delivery and reconciliation where needed. Validate partner guides and current permissions. Activate only the reviewed use case, with a rollback to approved existing behavior.

Acceptance cases beyond the local fixture checks

The companion fixture suite's 24 passing checks cover only a narrow subset of schema, time and immutable-fixture behavior. They do not implement these end-to-end gates. Assign the data owner, integration owner, security owner, commercial process owner and compliance owner explicitly before any production change. [59]

T19Revision ledger and final conclusion

Final recommendation

A manufacturer does not need an advertising identity system for medicines. It needs reliable interpretation of the customer relationships in the records it is entitled to receive, at the time those relationships applied, and with evidence of how the interpretation was produced.

The strongest incremental solution is a verified account-binding profile hosted with the issuer, connected to existing identifier sources and existing transaction channels. Ad tech contributes disciplined namespaces, lookup, provenance, adapters, activity controls and synchronization patterns. Established IETF and W3C mechanisms provide more precise technical semantics for gaps that ad-tech analogies alone did not close.

The end state is concrete: a correct relationship can be resolved; an uncertain one is explicit; a past decision is reproducible; a changed endpoint requires real authority; and an eligibility dispute identifies the actual contract and roster evidence rather than assuming identity settles it. Product authenticity and required tracing procedures remain outside the account resolver.

T20References and source notes

Numbers are shared with the executive track. Titles open the source where a link is available. Proposed adaptations are not endorsements by the source organizations.

1. FDA · DSCSA standards for the interoperable exchange of information for tracing, final guidance (September 2023)
   EPCIS recommendation, exchange architecture and protection of confidential commercial information.
2. FDA · Enhanced drug distribution security at the package level, guidance (January 2024, procedural revision 1)
   Reconciliation, information gathering and protected exchange.
3. GS1 · EPCIS 2.0.1
   Event model, ErrorDeclaration, capture and query interfaces and extension mechanisms.
4. Open Credentialing Initiative · DSCSA interoperability profile, v3.4 series
   Identity and ATP credential profiles; deployment support must be confirmed.
5. HIBCC · The HIN system: a user guide
   Undated guide. Account-number bridge, audit fields and referback after a move; not a current API contract.
6. HDA Research Foundation and Rutgers University · Change management: best practices in contract and chargeback administration (2018)
   Weighted 0.7 percent rejection rate from the 2017 HDA Factbook; eligibility survey subgroups; industry cost not derived.
7. X12 · Transaction set descriptions
   844 and 849 product transfer account adjustment and response; 845, 852 and 867 per the X12 catalog. No segment-level validation claimed.
8. FDA · Exemptions from the enhanced drug distribution security requirements of section 582(g)(1) (October 9, 2024)
   States that section 582(k)(1) effectively ended routine Transaction History exchange on November 27, 2023; phased exemption dates by trading partner type.
9. Cencora · DSCSA: understanding GLN requirements (September 13, 2024)
   Company-specific WAC, GPO and 340B account example and the 2024 duplicate GLN cleanup.
10. GS1 US · Location data quality, Data Hub help
    Inactive and replacement GLN handling; registry data and access remain source-controlled.
11. PDG and FDA · 2025 dispenser town hall report (November 2025)
    Participant reports of portal growth, misrouted files, drop-ship references and 340B context; not a prevalence survey.
12. AmerisourceBergen · Exceptions pilot white paper (2018)
    Historical manufacturer-onboarding duration.
13. PDG · Interoperability blueprint, chapter 3 (v1.5, January 2026; v1.6, July 2026)
    TI and TS design, exception categories and near-term email notification.
14. PDG · Exception notification guideline v1.0.1
    Structured notification content; not a universal transport mandate.
15. PDG · Blueprint resources: exception notification JSON schema and connection template
    Confirm the partner-supported schema before implementation.
16. HIDA · Navigating healthcare identifiers: HIN assignments and updates
    Webinar resource on HIN assignment, location distinctions and updates.
17. Morningstar · Drug distribution industry trends (June 2025)
    Concentration by revenue, not shipment share.
18. IAB Tech Lab · sellers.json and the SupplyChain object
    Issuer-scoped seller identifiers and out-of-band participant metadata.
19. IAB Tech Lab · OpenRTB 2.x release history
    2.6-202409 adds the EID inserter, matcher and mm fields; latest tagged release observed is 2.6-202606.
20. Unified ID 2.0 · POST /v3/identity/map
    Batch results, refresh timestamp and temporary prior identifier; not archival versioning.
21. IAB Tech Lab · Taxonomies repository
    Independently versioned taxonomies and mappings; no pharmaceutical ownership implied.
22. IAB Tech Lab · Data Transparency Standard
    Data-label disclosure; does not certify the correctness of a mapping.
23. IAB Tech Lab · ads.txt: authorized digital sellers
    Authorized-seller publication mechanics.
24. Prebid.org · Prebid Server: new bid adapter (Go)
    Adapter JSON schemas, fixture tests and endpoint restrictions.
25. Prebid.org · Activity controls
    Per-activity permission rules; permissive defaults are not adopted.
26. IAB Tech Lab · Deals API v1.0 (released for public comment, December 4, 2025)
    Origin-scoped deal identity, receiver status and polling repair.
27. HDA · Exceptions handling guidelines for DSCSA (2023)
    Six named scenario sections in the edition reviewed.
28. Cardinal Health, hosted by FDA · Interoperability data exchange errors and exception handling DSCSA pilot project, final report
    Logged exception and support samples, May 2017 to January 2020; not a representative transaction sample.
29. FDA · Small business dispenser exemption extension (letter, August 6, 2026)
    Specified relief through November 27, 2027; size measured at the owning corporate entity as of November 27, 2026.
30. FDA · Exemptions under the Drug Supply Chain Security Act
    Current exemption status; page updated August 26, 2026.
31. U.S. Code · 21 U.S.C. 360eee and 360eee-1 (FD&C Act sections 581 and 582)
    Definitions, Transaction Information and Statements, verification and information-gathering provisions.
32. GS1 · Core Business Vocabulary 2.0
    Owning party, possessing party, location and business-transaction semantics.
33. GS1 US · Healthcare managed GLN subscription, Data Hub help
    Program-administrator and location-record workflow; not hosting approval for a custom profile.
34. Open Credentialing Initiative · Frequently asked questions
    Credential issuer, holder presentation and verification; a credential is not a TI signing key.
35. IAB Tech Lab · OpenRTB 2.6 specification, tag 2.6-202606
    SupplyChain, SupplyChain node, EID and UID objects.
36. IAB Tech Lab · OpenDirect
    Adjacent order-workflow specification; not selected.
37. IETF · RFC 9396: OAuth 2.0 Rich Authorization Requests
    Structured authorization_details; a request is not legal authority.
38. IETF · RFC 8707: Resource Indicators for OAuth 2.0
    Resource and audience scoping for OAuth requests.
39. IETF · RFC 8705: OAuth 2.0 mutual-TLS client authentication and certificate-bound access tokens
    Certificate-bound tokens where supported.
40. IETF · RFC 9700: OAuth 2.0 security best current practice
    Select a supported security profile rather than a new bearer scheme.
41. IETF · RFC 9457: Problem Details for HTTP APIs
    Top-level error representation; per-item batch outcomes remain application-specific.
42. W3C · PROV-O: the PROV ontology
    Entities, activities and agents for provenance; neither truth certification nor authorization.
43. W3C · SKOS reference
    Mapping relations; exactMatch is transitive and must not be assigned casually.
44. CloudEvents · CloudEvents specification v1.0.2
    Envelope attributes and source-scoped identity; not a delivery or ordering guarantee.
45. AWS Prescriptive Guidance · Transactional outbox pattern
    Atomic database and outbox write; duplicate delivery still requires idempotent consumers.
46. IETF · RFC 9111: HTTP caching
    Cache controls; current authorization remains separate from data freshness.
47. IETF · RFC 7515: JSON Web Signature
    Signature over specified bytes and protected metadata.
48. IETF · RFC 8785: JSON Canonicalization Scheme
    Deterministic JSON serialization when explicitly selected.
49. W3C · RDF dataset canonicalization
    A distinct canonicalization route; not interchangeable with JCS.
50. IETF · RFC 9421: HTTP Message Signatures
    Optional message-component protection; does not establish licensure or physical truth.
51. IETF · RFC 9530: Digest Fields
    Content-Digest and Repr-Digest; a bare digest does not authenticate its issuer.
52. OpenID Foundation · OpenID Shared Signals Framework 1.0 (final, 2025)
    Optional security-event integration; not account-master transport.
53. W3C · Trace Context
    Operational correlation only; sampled telemetry is not the decision audit record.
54. IETF · RFC 8693: OAuth 2.0 Token Exchange
    Optional subject and actor delegation where deployed; not authority to acquire a customer graph.
55. HIBCC · MediLedger and HIN collaboration
    Existing-industry integration announcement; not independent return-on-investment evidence.
56. U.S. District Court, E.D.N.Y. · Gilead Sciences v. Safe Chain Solutions, opinion (July 31, 2023)
    Allegations and findings in their procedural context.
57. eCFR · 21 CFR 203.50, requirements for wholesale distribution of prescription drugs
    Written authorized distributor list, available to the public on request; read with the 2022 proposed rule.
58. FDA, Federal Register · Certain requirements regarding prescription drug marketing, proposed rule (February 4, 2022)
    Proposes removing section 203.50 in its entirety; not treated here as a final repeal.
59. Centillion.ai · Reference fixture checks, profile 0.2 (internal, not published)
    24 authored synthetic checks; no live interoperation, signature, access-control or outcome validation.

v3.1, 27 September 2026. Proposed profile, not compliance certification. v3.1 re-maps every citation to one shared reference list and names the IAB Tech Lab Deals API correctly. Package unified from: Unified Narrative v2.0, DSCSA Commercial Identity White Paper v2.0, the v2.1 consensus amendment and the v2.1 solution board, with source re-checks on 27 September 2026.