Nippin information

Nippin information

Dernière mise à jour: 2024-02-14 13:07

The different statuses of a Nippin message in the database

StatusDescription
ARCHIVEDMessages are set to ARCHIVED, only if the NippinCleanup table has 0 records. These messages will not be processed and won't receive any attention afterwards.
INVALIDXML payload is invalid, a ticket can be created at our Servicedesk
BUFFEREDnot used
ERRORHD4DP2.0 was not able to send the message to MyCarenet or SFTP folder
SENTHD4DP.20 was able to send the message to MyCarenet or SFTP folder

Queries

You can run several queries on the data in the Nippin database. Examples:

Count records grouped by the type and status:

nippin=# select interface_type, status, count(id) from nippin_message group by interface_type,status;
 interface_type | status  | count
----------------+---------+-------
 FILE_SYSTEM    | SENT    |   117
 FILE_SYSTEM    | INVALID |   352
 FILE_SYSTEM    | TO_SEND |  9238
(3 rows)

Get all error and invalid information:

select id, message_id, project_id, dcd_id, payload_after_validation from nippin_message where status in ('INVALID', 'ERROR');

Get previous and current registration code:

select id, message_id, project_id, dcd_id, previous_registrationcode, current_registrationcode from nippin_message;

MyCareNet integration-specific queries

You can run queries that are specific for the integration of MyCareNet on the data

Count records with status SENT and group them based on the reference ID received from Mycarenet.

 select postresponse_tack_result_major, postresponse_tack_reference, count(*)  from nippin_message where status = 'SENT' group by status, postresponse_tack_result_major, postresponse_tack_reference;
  postresponse_tack_result_major   |     postresponse_tack_reference      | count
-----------------------------------+--------------------------------------+-------
 urn:nip:tack:result:major:success | ***** |   2
 urn:nip:tack:result:major:success | ***** |   88