
![]()
I submitted a USCDI data element to ONC's Interoperability Standards Platform: Patient Digital Identity Credential, filed under the Provenance data class at Level 0. It is a public record with a submitter, a rationale, two use cases, an assessment against ONC priorities and the four ONC evaluation criteria, and a comment thread anyone can join. The submission is at https://isp.healthit.gov/taxonomy/term/7980/level-0.
The argument it makes is narrow: a patient-issued credential that names who authorised an exchange is a provenance question, not an identity-provider question, and USCDI currently has nowhere to put it. If a record is shared on a patient's instruction, the receiving system needs to know which instruction, issued when, by whom, and revocable — and that is data, not a policy statement.
USCDI decides what a certified system must be able to exchange. Provenance in USCDI covers author, organisation and time, which answers "who wrote this" but not "who allowed this to travel". Consent and authorisation are recorded today in each organisation's own system, in its own shape, and never travel with the record. A credential element gives the exchange something portable to carry.
It is an artefact, not a certification. It shows a specific position taken in a public federal process, with the reasoning attached — which is more useful to a buyer than a logo. If your programme is deciding where consent and provenance live in an exchange, the submission is a worked argument you can agree or disagree with. The comment thread on the ISP page is open to anyone with an account.
Is a USCDI submission a certification? No. It is a proposal and a public record. Certification is a separate process run against certified health IT criteria.
Can the element be adopted? That is ONC's decision, taken through USCDI version cycles with public comment. The submission is an input to that process, not a claim on the outcome.
Where else does the standards work show up? In the interfaces themselves: FHIR patient access, consent and revocation design, X12 claims, and the HIPAA controls around all of it.