ReportHTML

Entity [Form Received]

Description

This entity will capture the information of all official forms defined (required/optional) in the DDP package.

This entity will also optinally save the related digital version of the forms if they are submitted from digital channel.

This entity will also used to identify the completion of submission if all mandatory forms are submitted.

List of attributes

Form Received ID

The primary key as GUID.

Char (32)

Package ID

Reference to Package entity.

Char (32)

Form ID

The Form ID reference to a lookup table.

Suggestion and Usage:
1 = ADLI
2 = HSR
4 = Client Consent
8 = Self-Report

If the sum of all received Form ID =15, then this package submission is complete.

Integer

Status Code

The status code for this form:
Received
OPSDoc Integrated
Adjudication process status(e.g.):
Reviewed
Supporting document required
... ...

Varchar (20)

Receive Date

The datetime this form is received.

Date & Time

OPSDoc Integration Date

The datetime when saving to repository is complete.

Date & Time

Receive Channel ID

The channel ID reference to a lookup table. E.g.,
SADIE
MyBenefits
Nimble
Other in future......

Integer

Submission Channel User Key

The external User Key from the submission channel.

E.g.:
If the form is submitted from SADIE, this will be the HCP user ID in SADIE. This user key is mainly for future communication purpose other than capturing the HCP profile,
If the form is submitted from MyBenefits, this key could be the Member ID or user key for the trustee of that member (who submitted this form on behalf of the Member ID).

Varchar (50)

Format Type Code

The format type code of the form:
PDF
Image (user consent form)
JSON/PDF
......

Varchar (20)

Checksum

The checksum of the file content. This is to ensure system can always check whether the form has been manipulated after first received.

Varchar (100)

OPSDoc Object ID

Repository created document key.

Varchar (100)

OPSDoc Name

File name saved in the repository.

Varchar (100)

Digital Content

If the form is received from digital channels in digital format, this attribute is to store the BOLB of the digital form content. For SADIE, it will be JSON BLOB.

Long binary

JSON OPSDoc

The digital format confirmation received from the OPSDoc repository.

Long binary

Date Created

The data and time this record was created.

Date & Time

Date Updated

The data and time this record was last updated. For the full update history should be captured with an audit table.

Date & Time

Created By

The ID/Code of the user/system component who created this record.

Varchar (20)

Updated By

The ID/Code of the user/system component who last updated this record.

Varchar (20)

Home