Credentials PSV Primary Source IG
1.0.0 - ci-build
Credentials PSV Primary Source IG, published by . This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/alpivonka/Credentialing-PrimarySource-FHIR-IG/ and changes regularly. See the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
These define constraints on FHIR resources for systems conforming to this implementation guide.
| PSV ActivityDefinition (Verification Activity) |
Defines a concrete verification activity to be performed by a worker/system. |
| PSV AuditEvent |
System-level audit of verification operations. |
| PSV Endpoint (US Core derived) |
Endpoints for boards/registries/verifiers. |
| PSV Evidence Binary |
Raw binary artifact (hashable). |
| PSV Evidence Document |
Stores document artifacts (PDF, CSV, screenshots) used as evidence. |
| PSV Measure |
Aggregates verification coverage or SLA metrics. |
| PSV MeasureReport |
Reports metrics for verification coverage/SLA. |
| PSV Organization (US Core derived) |
Represents employers, boards (validators), certifying bodies, accreditors. |
| PSV OrganizationAffiliation |
Privileges and affiliations between organizations and practitioners. |
| PSV PlanDefinition (Policy) |
Defines policy (frequency, method, failure action) for verification types. |
| PSV Practitioner with Qualification Slices (Common Pattern + Rules) |
Practitioner profile with typed qualification slices and shared invariants for credentialing. |
| PSV PractitionerRole (US Core derived) |
PractitionerRole for roles/specialties linked to organizations. |
| PSV Provenance (US Core derived) |
Audits VerificationResult with evidence entities (CSV snapshot, API receipt, PDF). |
| PSV Verification Task |
Requests execution of a verification (e.g., LEIE monthly, license quarterly). |
| PSV VerificationResult |
Standard verification evidence linking validators to verified targets. |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| Action | |
| Flag Evidence (VerificationResult link) |
Carries a reference to the VerificationResult that justifies this Flag. |
| Flag Target Location (element path) |
Optional element path (e.g., qualification[license][0]) for UI deep-linking. |
| Qualification Restriction | |
| Qualification Specialty | |
| Qualification Status |
Status of a credential/qualification entry (e.g., active, expired, suspended). |
| Training Completion Status | |
| Training Type |
These define sets of codes used by systems conforming to this implementation guide.
| PSV Action | |
| PSV Verification Type | |
| VS - Qualification Status | |
| VS — Board/Training Specialty |
Allowed specialties used for training/board examples. |
| VS — DEA Controlled Substance Schedules (II–V) |
Allowed DEA schedules for clinician prescribing context. |
| VS — DEA Registrant Type |
Allowed DEA registrant categories for practitioner credentialing. |
| VS — Training Completion Status |
Allowed values for training completion status. |
| VS — Training Type |
Allowed training types for practitioner qualifications. |
These define new code systems used by systems conforming to this implementation guide.
| Board/Training Specialty (Minimal) |
Minimal specialty codes used in examples. Replace/expand with your authoritative list. |
| DEA Controlled Substance Schedules (II–V) |
Subset of U.S. controlled substance schedules commonly applicable to prescribers. Schedule I excluded. |
| DEA Registrant Type |
DEA registrant categories relevant to care delivery and dispensing. |
| PSV Action CodeSystem | |
| PSV Verification Type CodeSystem | |
| Qualification Status | |
| Training Completion Status |
Completion state for a training program. |
| Training Type |
Types of postgraduate clinical training programs. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.