Configure Tasks

The certificate task helps you issue a certificate of completion to the partners who have successfully performed all the required tasks. The main goal of such a certificate is to provide proof that a certain partner went through a specific task, and completed all the required works, trainings, assignments, and so on, for example, validated their EDI transactions against a certain guideline, completed your policy acknowledgment, and so on.

You can configure and issue a certificate of completion for any task. Before you configure the certificate content, you should add and configure a task of the Certificate type first.

To configure a certificate content:

  1. On the Programs In Design page, click the program name.
  2. On that program's page, on the Program Setup tab, on the Tasks tile, click Manage Tasks.
  3. On the YourProgramName: Manage Tasks page, in the left pane with tasks, select Certificate.
  4. In the right pane, in Content Configuration, enter the following information:
    • An image with your organization seal
    • An image with your organization's logo
    • The certificate title
    • The certificate description about this certificate
    • Your organization name who issues this certificate
    • Validity (in days) for your certificate
    • The certificate key for authentication that can be system generated.
    • The authentication URL if you want to authenticate the certificate.
    • The name and designation of signatories of the certificate
  5. Click Save or Save & Close.

This task allows you to collect the data you require from your partners in the form you require. You can create multiple forms for different purposes to capture different kind of the data from your partners. Such forms should contain a combination of the allowed user interface components. To configure forms, define the schema in the JSON format in the designer area for your partners to enter data values in the configured fields.

Before you configure the form for the Data Collection task, you should add and configure a task of the Data Collection type first.

To configure a form:

  1. On the Programs In Design page, click the program name.
  2. On that program's page, on the Program Setup tab, on the Tasks tile, click Manage Tasks.
  3. On the YourProgramName: Manage Tasks page, in the left pane with tasks, select Data Collection.
  4. In the right pane, in Content Configuration, in the Data Collection Form JSON field, enter the JSON form. Click Show Form Preview to view how it looks on the user interface.
  5. Click Save or Save & Close.

Create your custom forms

You can compose your own forms with the user interface components you like. Below are the available components you can choose from, the properties they support, and the JSON code samples for you to quickly copy and customize.

Field declaration: "fieldType": "text"

Available properties:

  • Label: "title": "stringValue",
  • Watermark: "placeholder": "stringValue",
  • Remarks: "remarks": "stringValue",
  • Minimum length: "minLength": "numberValue",
  • Maximum length: "maxLength": "numberValue",
  • Pattern: "pattern": "stringValue",
  • Default value: "supported": "string/number/dateValue",
  • Mandatory: "required": "booleanValue",
  • Read-only: "readonly": "booleanValue",
  • Repetition: "repeat": {"min": "numberValue", "max": "numberValue"}.
Copy

Example

{
                                "Text": {
                                "fieldType": "text",
                                "title": "Label",
                                "placeholder": "Placeholder",
                                "remarks": "Some remark",
                                "minLength": "1",
                                "maxLength": "9",
                                "required": "true",
                                "readonly": "false",
                                "repeat": {"min": "1", "max": "9"}
                                }
                                }
                            

How it looks on the user interface:

Field declaration: "fieldType": "number"

Available properties:

  • Label: "title": "stringValue",
  • Watermark: "placeholder": "stringValue",
  • Remarks: "remarks": "stringValue",
  • Minimum value: "minValue": "number/dateValue",
  • Maximum value: "maxValue": "number/dateValue",
  • Pattern: "pattern": "stringValue",
  • Default value: "supported": "string/number/dateValue",
  • Mandatory: "required": "booleanValue",
  • Read-only: "readonly": "booleanValue",
  • Repetition: "repeat": {"min": "numberValue", "max": "numberValue"}.
Copy

Example

{
                                "Number": {
                                "fieldType": "number",
                                "title": "Label",
                                "placeholder": "Placeholder",
                                "minValue": "0",
                                "maxValue": "5",
                                "required": "false",
                                "readonly": "false"   
                                }
                                }
                            

How it looks on the user interface:

Field declaration: "fieldType": "date"

Available properties:

  • Label: "title": "stringValue",
  • Remarks: "remarks": "stringValue",
  • Minimum value: "minValue": "number/dateValue",
  • Maximum value: "maxValue": "number/dateValue",
  • Default value: "supported": "string/number/dateValue",
  • Mandatory: "required": "booleanValue",
  • Read-only: "readonly": "booleanValue",
  • Repetition: "repeat": {"min": "numberValue", "max": "numberValue"}.

Example

{
                                "Date": {
                                "fieldType": "date",
                                "title": "Label",
                                "minValue": "01/01/1900", 
                                "maxValue": "01/01/2022" 
                                }
                                }
                            

How it looks on the user interface:

Field declaration: "fieldType": "textarea"

Available properties:

  • Label: "title": "stringValue",
  • Watermark: "placeholder": "stringValue",
  • Remarks: "remarks": "stringValue",
  • Minimum length: "minLength": "numberValue",
  • Maximum length: "maxLength": "numberValue",
  • Default value: "supported": "string/number/dateValue",
  • Mandatory: "required": "booleanValue",
  • Read-only: "readonly": "booleanValue",
  • Repetition: "repeat": {"min": "numberValue", "max": "numberValue"},

Example

{
                                "TextArea": {
                                "fieldType": "textarea",
                                "title": "Purpose",
                                "placeholder": "Enter a short description",
                                "minLength": "0",
                                "maxLength": "255"
                                }
                                }
                            

How it looks on the user interface:

Field declaration: "fieldType": "dropdown"

Available properties:

  • Label: "title": "stringValue",
  • Watermark: "placeholder": "stringValue",
  • Remarks: "remarks": "stringValue",
  • Default value: "supported": "string/number/dateValue",
  • Mandatory: "required": "booleanValue",
  • Read-only: "readonly": "booleanValue",
  • Repetition: "repeat": {"min": "numberValue", "max": "numberValue"},
  • Options: "options": [{"value": "string/numberValue", "title": "stringValue"}].

Example

{
                                "Dropdown": {
                                "fieldType": "dropdown",
                                "title": "Label",
                                "placeholder": "Select an option",
                                "options": [{"value": "1", "title": "Option 1"},{"value": "2", "title": "Option 2"},{"value": "3", "title": "Option 3"}]
                                } 
                                }
                            

How it looks on the user interface:

Field declaration: "fieldType": "radiobutton"

Available properties:

  • Label: "title": "stringValue",
  • Remarks: "remarks": "stringValue",
  • Default value: "supported": "string/number/dateValue",
  • Mandatory: "required": "booleanValue",
  • Read-only: "readonly": "booleanValue",
  • Repetition: "repeat": {"min": "numberValue", "max": "numberValue"},
  • Options: "options": [{"value": "string/numberValue", "title": "stringValue"}].

Example

{
                                "Radiobutton": {
                                "fieldType": "radiobutton",
                                "title": "Label",
                                "options": [{"value": "1", "title": "Option 1"},{"value": "2", "title": "Option 2"},{"value": "3", "title": "Option 3"}]
                                } 
                                }
                            

How it looks on the user interface:

Field declaration: "fieldType": "checkbox"

Available properties:

  • Label: "title": "stringValue",
  • Remarks: "remarks": "stringValue",
  • Default value: "supported": "string/number/dateValue",
  • Mandatory: "required": "booleanValue",
  • Read-only: "readonly": "booleanValue",
  • Repetition: "repeat": {"min": "numberValue", "max": "numberValue"},
  • Options: "options": [{"value": "string/numberValue", "title": "stringValue"}].

Example

{
                                "Checkbox": {
                                "fieldType": "checkbox",
                                "title": "Label",
                                "options": [{"value": "1", "title": "Option 1"},{"value": "2", "title": "Option 2"},{"value": "3", "title": "Option 3"}]
                                }
                                }
                            

How it looks on the user interface:

Field declaration: "fieldType": "password"

Available properties:

  • Label: "title": "stringValue",
  • Watermark: "placeholder": "stringValue",
  • Remarks: "remarks": "stringValue",
  • Mandatory: "required": "booleanValue",
  • Read-only: "readonly": "booleanValue",
  • Repetition: "repeat": {"min": "numberValue", "max": "numberValue"}.

Example

{
                                "Password": {
                                "fieldType": "password",
                                "title": "Password",
                                "placeholder": "Enter a password",
                                "required": "true"
                                }
                                }
                            

How it looks on the user interface:

Field declaration: "fieldType": "embeddedfile"

Available properties:

  • Label: "title": "stringValue",
  • Remarks: "remarks": "stringValue",
  • Default value: "supported": "string/number/dateValue",
  • Mandatory: "required": "booleanValue",
  • Read-only: "readonly": "booleanValue",
  • Repetition: "repeat": {"min": "numberValue", "max": "numberValue"}.

Example

{
                                "EmbeddedFile": {
                                "fieldType": "embeddedfile",
                                "title": "Some file name"
                                }
                                }
                            

How it looks on the user interface:

Field declaration: "fieldType": "section"

Available properties:

  • Label: "title": "stringValue",
  • Remarks: "remarks": "stringValue",
  • Mandatory: "required": "booleanValue",
  • Read-only: "readonly": "booleanValue",
  • Repetition: "repeat": {"min": "numberValue", "max": "numberValue"}.

Example

{
                                "Section": {
                                "title": "Section",
                                "fieldType": "section",
                                "fields": {
                                "Text": {
                                "fieldType": "text",
                                "title": "Label",
                                "placeholder": "Placeholder",
                                "remarks": "Some remark",
                                "minLength": "1",
                                "maxLength": "9",
                                "required": "true",
                                "readonly": "false",
                                "repeat": {"min": "1", "max": "9"}
                                },
                                "SubSection": {
                                "title": "Sub-section",
                                "fieldType": "section",
                                "fields": {
                                "Number": {
                                "fieldType": "number",
                                "title": "Label",
                                "placeholder": "Placeholder",
                                "minValue": "0",
                                "maxValue": "5",
                                "required": "false",
                                "readonly": "false"   
                                }
                                }
                                }
    
                                }
                                }
                                }
                            

How it looks on the user interface:

Copy
Example
{
"clinicName": {
                             "title": "Clinic Name",
                             "required": true,
                             "fieldType": "text",
                             "placeholder": "Enter Clinic Name"
              },
              "billingProvider": {
                             "title": "Billing Provider",
                             "required": true,
                             "fieldType": "text",
                             "placeholder": "Enter Billing Provider Name"
              },
              "npi": {
                             "title": "NPI",
                             "required": true,
                             "fieldType": "number",
                             "placeholder": "Enter Billing Provider NPI",
                             "minValue": "1000000000",
                             "maxValue": "9999999999"
 
              },
              "subscriberID": {
                             "title": "Subscriber ID (Health Plan Number)",
                             "required": true,
                             "fieldType": "text",
                             "placeholder": "Enter Subscriber ID"
              },
              "mpi": {
                             "title": "MPI (medicare only, if available)",
                             "required": false,
                             "fieldType": "text"
              },
              "lastName": {
                             "title": "Last Name",
                             "required": true,
                             "fieldType": "text"
              },
              "firstName": {
                             "title": "First Name",
                             "required": true,
                             "fieldType": "text"
              },
              "dob": {
                             "title": "Date of Birth",
                             "required": true,
                             "fieldType": "date"
              },
              "dos": {
                             "title": "Date of Service",
                             "required": true,
                             "fieldType": "date"
              },
              "claimNumber": {
                             "title": "Claim Number",
                             "required": false,
                             "fieldType": "text"
              },
              "dxCode": {
                             "title": "ICD-10 Diagnosis Code",
                             "remark": "(must be supported in medical record)",
                             "required": true,
                             "fieldType": "text"
              }
}

How it looks on the user interface:

The share information task enables you to share any kind of data with your partners. You can share information and documents with your partner.

The testing task enables you to set up self-testing steps that your partners can follow to ensure that every task has been performed correctly.

The API Collection task enables you to add APIs to your program.

System Variables

You, as a health plan administrator or a program owner, can use the system variables to configure the APIs. These system variables can be used to fetch a logged-in user token or the account ID of the logged-in user who executes the API task.

  • ${system.loggedInUserToken}: a macro to get a user token of the user who executes the task.
  • ${system.loggedInAccountId}: a macro to get the Account ID of the user who executes the task.

The branching task enables you to configure branching task in a program, so that a user can design various workflows within the program based on the answers provided by a certain partner to a particular question in a certain task.

Based on the partner’s answer, the sequence of the tasks that follow can change – where the partner sees only the tasks that are relevant to a particular workflow. For each answer choice, you, as an administrator, can select the applicable/not-applicable tasks within a branching workflow.

The validation task enables you to allow your partners to validate their EDI transactions against set standards and guidelines. When a certain partner submits a data file for validation, Onboarding and Testing Cloud Service adds a property file with metadata to that file. Thus, allowing you to search for and track the required data in Transaction Management. The property file is submitted with the following fields:

  • PartnershipID: the unique identifier for the established partnership between a certain partner and an organization.
  • PartnerName: the name of the partner who has submitted a data for validation.
  • PrimaryContactName: the name of a first person responsible for all communication with other organizations.
  • PrimaryContactEmail: the email address of a first person responsible for all communication with other organizations.
  • ProgramID: the unique identifier for the specific program.
  • EnrollmentID: the unique identifier for the specific enrollment.
  • EnrollmentPurpose: the reason for the putting a certain partner onto a certain program.
  • TaskID: the unique identifier for the specific task.
  • ExecutionRunID: the unique identifier for the specific execution run.
  • UserEmailID: the unique email address of a certain user when the user signs in to Smart Trading Cloud services.

For the Validation task, you, as a program owner, can view the summary of all the execution runs performed across all the partners and view the execution runs' details of each partner.

If you partner's data contains protected health information (PHI), the partner can remove such data by deleting certain execution runs. Only the validation result of this execution run will remain.