slug: credentially
provider: Credentially
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Healthcare Providers
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 5
edges:
- tag: Subscriptions
  spec_file: credentially-subscriptions-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.9
  evidence: GET /subscriptions "Get all webhook subscriptions for this org"; POST /subscriptions "Create
    a new webhook subscription"; DELETE /subscriptions/{id} "Delete a webhook subscription"
  reason: Despite the commercial-sounding tag, the operations manage outbound webhook subscriptions —
    event subscription lifecycle on a developer API surface, not customer subscriptions.
  recovered_from: healthcare-vertical-edges.json
- tag: Compliance-packages
  spec_file: credentially-compliance-packages-api-openapi.yml
  capability_id: BC-2890.10
  capability_id_l1: BC-2890
  capability_name: Practitioner Credentialing
  confidence: 0.7
  evidence: POST /api/compliance-packages/{profileId}  assign  Assign compliance packages to profile
  reason: Assigns and tracks bundles of compliance/document requirements against healthcare staff profiles
    (schemas EmployeeComplianceRequirementDto, CheckIntegrationDto) on a healthcare credentialing platform
    — practitioner credentialing and continuous compliance monitoring.
- tag: DBS
  spec_file: credentially-dbs-api-openapi.yml
  capability_id: BC-2890.10
  capability_id_l1: BC-2890
  capability_name: Practitioner Credentialing
  confidence: 0.7
  evidence: getProfileDbsChecks "Get Profile DBS Checks"; updateProfileDbsCheck "Create Or Refresh Profile
    DBS Check"
  reason: DBS criminal-record checks on practitioner profiles are a background/verification element of
    credentialing on this healthcare-only credentialing platform ("DBS and right-to-work validation").
    Some overlap with pre-employment screening in talent acquisition, hence 0.7.
  recovered_from: healthcare-vertical-edges.json
- tag: Documents
  spec_file: credentially-documents-api-openapi.yml
  capability_id: BC-2890.10
  capability_id_l1: BC-2890
  capability_name: Practitioner Credentialing
  confidence: 0.7
  evidence: 'PATCH /api/documents/approve  approve_1  Approve document of file; schemas: VerificationDto,
    DocumentTypeDto, VerificationStatusDto, OrganisationDocumentTypeDto'
  reason: Operations upload, approve/reject and verify compliance documents against organisation document
    types, with verification status objects. In a healthcare-only credentialing/compliance platform this
    is the document-verification leg of practitioner credentialing rather than generic file storage; some
    residual chance it is better read as generic HR document handling, hence 0.7.
- tag: Profiles
  spec_file: credentially-profiles-api-openapi.yml
  capability_id: BC-2890.10
  capability_id_l1: BC-2890
  capability_name: Practitioner Credentialing
  confidence: 0.7
  evidence: 'schemas: GmcRegistrationDetailsDto, HcpcRegistrationDetailsDto, NmcQualificationDto, ChecklistStepStatusApprovalDto,
    GradeDto, JobPositionDto'
  reason: Profile records carry UK practitioner regulator registration and qualification details (GMC/NMC/HCPC)
    plus onboarding checklist approval status, i.e. the practitioner credentialing record. Overlaps with
    HR employee records, so not maximal confidence.