Contact Support

How can we help you?

Explore info by product

Credentialing

Licensing

Monitoring

PDM

Payer Enrollment

Roster Management

Help Desk

Skip to content
English - United States
  • There are no suggestions because the search field is empty.

Product Features

Provider Portal: Product Specification


1. Form Structure & Configuration

1.1 Form Pages & Sections
  • Forms are structured into pages and sections.

  • Each question must be assigned to a specific page/section.

  • While organizations can suggest page layouts, Certify retains the right to reassign sections for functional or logic-based needs.


2. Question Definition Parameters

When creating a form, organizations must define the following for each question:

2.1 Core Parameters
  • Question Text (Mandatory): The main text shown to the provider.

  • Sub-Text / Helper Text (Optional): Additional information or context to guide the user.

2.2 Response Types (Mandatory Field)

Supported input formats include:

  • Single-Line Text Field (with optional hint text)

  • Multi-Line Text Field Group (e.g., Address Line 1, Address Line 2, City, State, ZIP)

  • Button-Based Single Select (e.g., Yes / No / Unknown)

  • Date Picker

  • Single-Select Dropdown

  • Multi-Select Dropdown

  • File Upload (PDF only, max 10MB)

2.3 Required Flag (Mandatory)
  • Indicates whether a question must be answered before the form can be submitted.

  • If "No", the question is optional.

2.4 Field-Level Requirements for Grouped Inputs
  • In multi-line grouped inputs (e.g., address), each field can be set as required or optional independently.


3. Input Validations

Built-in validations ensure accurate and clean data collection:

  • Character Limits: Customizable per field.

  • Phone Number: This should follow standard phone number formatting, no alpha characters

  • Fax Number: This should follow standard phone number formatting, no alpha characters

  • Federal Tax ID Number (TIN): This should only allow a 9 digit number

  • NPI Number: This should only allow a 10 digit number. Validates format using checksum logic (does not verify against NPPES)

  • Email Address: Fail - Valid email format should be required


4. Intelligent Pre-Fill & Dynamic Behavior

4.1 Pre-Filled Forms (Q3)
  • Forms can be configured to pre-fill with:

    • Previously submitted data

    • Organization-provided information

    • External system data (if integrated on Platform)

4.2 Dynamic Input Population
  • Fields can be auto-filled based on earlier responses.

    • E.g., Entering a ZIP Code can populate City/State.

4.3 Conditional Select Filtering
  • Dropdown/select options can be filtered in real time based on values selected in previous fields.

    • E.g., Specialty list changes based on selected Provider Type.

4.4 Conditional Visibility
  • Fields and sections can be configured to appear only when specific conditions are met.

    • E.g., Show “Hospital Affiliation” section only if user answers “Yes” to a practice-related question.

4.5 Conditional Question Logic
  • Questions can appear dynamically based on previous selections.

    • E.g.,

      • If Question A = X → Show Question B

      • If Question A = Y → Show Question C

      • If no selection → Show Question D

  • Follow-up questions appear immediately once the triggering response is selected.


5. Hard Stop Logic (Q2)

Organizations can configure disqualification logic to prevent submission under certain conditions:

5.1 Ineligibility Rules
  • Based on user responses, specific selections can block form progression.

5.2 Custom Messaging
  • Organizations can define the exact text to display when a hard stop is triggered.

5.3 User Options Upon Hard Stop
  • Exit the application

  • Return to previous question to modify response

Note: The hard stop is triggered only after clicking “Next,” ensuring context and confirmation.


6. Form Submission Capabilities (Q3)

6.1 Webhooks
  • Form submission can trigger outbound webhooks to external systems for real-time integration.

6.2 API Access
  • All submitted form data is accessible via secure, authenticated API endpoints for use in downstream systems.

6.3 Dynamic Access Provisioning
  • Based on form inputs, users can be granted access to additional forms post-submission.

    • E.g., Selecting a specific region unlocks a region-specific compliance form.

6.4 PDF Output Generation
  • Each submitted form automatically generates a PDF version for download, archival, or distribution.


7. Summary of Benefits

  • Seamless provider experience with intelligent field logic

  • Accurate, validated data entry ensuring credentialing compliance

  • Custom workflows without requiring engineering intervention

  • Real-time integration with organizational systems

  • Scalable configuration for enterprise-level credentialing operations

Videos

Credentialing with Certify

Introduction to Certify Credentialing Solutions

Certify: The Future of Provider Data Management

×

Still need help?

Submit your question and we’ll get back to you.