In accordance with DoH circular DG/62/17, from 1-Jan-2018 in relation to the implementation of Value Added Tax, several data elements were added to the following transactions schema:
Practice showed that many users systems were not ready to support these changes. A new feature is designed in Greenrain messenger that consists in updating the file with missed fields on uploading to the Post Office. This logic is applied for Shafafiya severs only and if the corresponding settings are selected in Settings.
Step 1. Click Settings at the top of the app.
Step 2. In the dialog appeared click VAT Support tab and check the necessary VAT settings:
Step 3. Click OK.
Step 4. On Upload tab, click Select Files to Upload and select a transaction file.
Step 5. Click Upload Transactions or Validate Only.
Greenrain Messenger adds absent fields to the file, verifies the numbers, then uploads the file to the Post Office/validates on the Post office without uploading.
Add missing VAT for Claim.Submission
Restrictions
Calculation
Add missing VAT for Person.Register
Restrictions
Calculation
Often happens that users validate/upload big batches, and too many errors are returned by the Post Office. It takes time to find those errors and resolve them one by one which leads to exceeding the allowed submission period. The purpose of the feature is to exclude failed records from the original file and let user upload successful records first, then correct failed records in a separate file. This logic is applied only if the corresponding setting is switched on in Settings.
General workflow looks as follows.
Step 1. Click Settings at the top of the app.
Step 2. In the dialog appeared on General tab check the setting Split successful and failed records to separate transactions.
Step 3. Click OK.
Step 4. On Upload tab, click Select Files to Upload and select a transaction file.
Transactions details load to the grid below.
Step 5. Click Upload Transactions or Validate Only.
Each record in the file starts validating against the specific Health Authority rules set. Progress bar at the bottom of the tab shows uploading/validating progress. When the process is finished, a dialog appears saying that the file uploading/validating is finished either successfully or not.
Scenario | Upload Transactions | Validate Only |
---|---|---|
All records are successful | The file is not updated and uploaded to the Post Office as is, then moved to _Sent folder. | The file is not updated and validated on the Post Office as is, then stayed in the select folder. |
All records failed | The file is not updated and not uploaded to the Post Office. Validation errors report is returned. | The file is not updated and not uploaded to the Post Office. Validation errors report is returned. |
Some records are successful, some failed | The file splits into two batches.
| The file splits into the said two batches, and both they stay in the select folder. |
Greenrain Messenger shows both split files. User may open the _Failed file and correct errors, then try uploading/validating again.
Split rules
When the user selects any of the split files after corrections again, Greenrain Messenger loads both of them to the grid (if exist) since they are related, and uploads/validates them together.
If the original transaction contains duplicated records by Claim.ID / Member.ID, all the copies of the claim / person are placed into _Failed file no matter that each separate data entry doesn't throw errors. It's up to user to decide which of the copies should be deleted from the transaction. |
DoH Personal Profile web service provides true details about a particular member so that Person.Register transaction contains correct information. This change was introduced on Shafafiya on March 10, 2018.
When user uploads or validates Person.Register file, Greenrain Messenger calls DoH Personal Profile Service in order to retrieve this information and update the file before uploading. The logic described is applied only if the corresponding setting is switched on in Settings.
Step 1. Click Settings at the top of the app.
Step 2. In the dialog appeared click Person.Register tab and check the setting Automatically update Person.Register transactions.
Step 3. Click OK.
Greerain Messenger calls DoH Personal Profile Service with the following parameters from the transaction for each person:
If personal information is available, then the fields below are added to Person.Register transaction with corresponding values returned by the service.
Field Name | Description |
---|---|
Person.UnifiedNumber | Unified Number to uniquely identify a person. This number is issued by the Ministry of Interior (MOI). |
Person.FirstNameEn | Person First Name in English. This value equals to the first word in a person's full name. Info |
Person.MiddleNameEn | Person Middle Name in English. This value contains everything left between the first and the last words in a person's full name. |
Person.LastNameEn | Person Last Name in English. This value equals to the last word in a person's full name. |
Person.FirstNameAr | Person First Name in Arabic. This value equals to the first word in a person's full name. Make sure that Arabic names are written from right to left. |
Person.MiddleNameAr | Person Middle Name in Arabic. This value contains everything left between the first and the last words in person's full name. |
Person.LastNameAr | Person Last Name in Arabic. This value equals to the last word in a person's full name. |
Person.NationalityCode | Person Nationality code. |
Person.CityCode | Code of residence city for the person. However, DoH service contains the city of birth only. |
In case some fields already exist in the transaction but have values that are not matched with those returned by the service, Greenrain Messenger replaces this incorrect information too.
Greenrain Messenger cannot call the service (and make the necessary updates) in the following cases:
Greenrain Messenger performs the search with Person.EmiratesIDNumber first. In case there are no results or Person.EmiratesIDNumber has one of the default values, the search if performed with Person.UnifiedNumber. If a person still cannot be found for some reason, DoH Personal Profile returns a corresponding error. Examples:
Condition | Error Message Example |
---|---|
Passport Number is wrong | Passport number 'ABC12345' is incorrect. Original error description: INVALID PASSPORT NUMBER. Original error code: 1. Reference: Person.UnifiedNumber = 12345466 and Person.EmiratesIDNumber = 000-0000-0000000-0. Source: DoH Personal Profile Service. |
Birth Date is wrong | Birth Date 10-Jan-2001 is incorrect. Original error description: INVALID BIRTH DATE. Original error code: 1. Reference: Person.UnifiedNumber = 12345466 and Person.EmiratesIDNumber = 784-1983-5146079-9. Source: DoH Personal Profile Service. |
Any other unexpected error | DoH Personal Profile Service returned an error. Original error description: CANNOT PROCESS THE REQUEST. Original error code: 1. Reference: Person.UnifiedNumber = 12345466 and Person.EmiratesIDNumber = 000-0000-0000000-0. Source: DoH Personal Profile Service. |
DoH sent a notification email on January 9, 2019 requesting that DoH Personal Profile Service must be called with Emirates ID Number of UAE residents and Unified Number for anybody else. In order to be compliant with DoH rules to call the service, please make sure that in your transaction:
Default values for Emirates ID Number:
|
In accordance with DoH circular US/12/19 issued on March 14, 2019, providers must send a copy of e-claims to the patients by email or SMS (so-called Electronic Medical Invoice). The effective date is June 1, 2019. To cover this requirement, Greenrain Messenger uses personal contact data gathered with the means of Greenrain Submission to send a medical invoice to the patient. An email is sent once a Claim.Submission transaction is uploaded to Shafafiya. An email contains the claim details attached as a pdf file. Electronic medical invoice is sent if the following conditions are met:
The medical invoice looks as follows: