The different statuses of a Nippin message in the database
Status
Description
TO_SEND
HD4DP v2 ready to be sent to MyCareNet or SFTP folder
ARCHIVED
Messages 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.
INVALID
XML payload is invalid, a ticket can be created at our service portal, including the payload of the invalid message.
BUFFERED
not used
ERROR
HD4DP v2 was not able to send the message to MyCareNet or SFTP folder
SENT
HD4DP v2 was able to send the message to MyCareNet or SFTP folder
Column Name
Data Type
Description
id
bigserial
Primary Key
message_id
varchar(255)
Identifier for the message
identification_value
text
Identification value of the organization that is sending the message
name
text
Name of the organization that is sending the message
payload
text
Payload of the message
payload_after_validation
text
Payload after (xsd-)validation
response
text
Response to the message (received from myCarenet)
valid
boolean
Whether the message is valid or not
interface_type
varchar(25)
Type of interface used for the message (e.g. FILE_SYSTEM or REST)
status
varchar(25)
Current status of the message (possible states : INVALID (validation against xsd-scheme failed), TO_SEND (ready for sending to myCarenet), SENT (sent to myCarenet), ERROR (something went wrong during sending, e.g. unable to reach myCarenet))
created_on
timestamp
Timestamp of when the message was created
input_reference
varchar(255)
Reference for the input message (this is a unique identifier that can be used for debugging/tracing with myCarenet)
issuer
text
Issuer of the message
postresponse_tack_applies_to
text
Applies-to value for the TACK post-response (received from myCarenet)
postresponse_tack_id
text
ID of the TACK post-response (received from myCarenet)
postresponse_tack_reference
text
Reference for the TACK post-response (received from myCarenet)
postresponse_tack_resultMajor
text
Result major for the TACK post-response (received from myCarenet)
postresponse_tack_resultMinor
text
Result minor for the TACK post-response (received from myCarenet)
postresponse_tack_resultMessage
text
Result message for the TACK post-response (received from myCarenet)
previous_registrationcode
varchar(255)
Previous registration code for the message (obsolete)
current_registrationcode
varchar(255)
Current registration code for the message (value will be identical to previous_registrationcode)
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
This documentation is being updated regularly. We try to provide as correct, complete and clear as possible information on these pages. Nevertheless, if you see anything in the documentation that is not correct, does not match your experience or requires further clarification, please create a request (type : request for information) via our portal (https://sciensano.service-now.com/sp) or send us an e-mail via support.healthdata@sciensano.be to report this documentation issue. Please, do not forget to mention the URL or web address of the page with the documentation issue. We will then adjust the documentation as soon as possible. Thank you!
Did not find what you were looking for? Contact us.