Passport Validation Guidelines

Validate source authenticity

Open Picture in full screen

1. The content hash from the Hippocrates passport must be the same as the hash inside the data of the decoded smart contract input identified by the transaction hash. As represented above with a green arrow.

2. The transaction hash must match the transaction hash in the passport. As represented above with a purple arrow.

3. The transaction date and time from the passport must match with a maximum difference of 1-5 seconds with the transaction. As represented above with a brown arrow.

Validate signature authenticity

1. Using Etherscan verify that passport emitter wallet address (identity) signed the message body represented in the section Passport emitter Declaration by copying and pasting such fields in the etherscan page, as represented above in the screenshot.

Validate medical record authenticity

1. Assert that the link from the passport points to https://ipfs.io/ipfs/ + <content_hash>, as displayed above with a brown arrow.

2. Verify that the medical record from the location https://ipfs.io/ipfs/ + <content_hash> is identical to the medical record from the Hippocrates passport, as represented above.

Validate Smart Contract authenticity

1. Verify the same wallet address from (a) the Passport Emitter section and (b) the transaction hash, match identically to the Hippocrates staff page, which can be found in the digital platform. As represented in the example from above with the green arrows.

2. Verify that the smart contract utilised to store the content hash of the patient data is the same smart contract to the one located on the staff page, which can be found in the digital platform. As represented in the example from above with the blue arrows.