-
Notifications
You must be signed in to change notification settings - Fork 1
Passport Validation Guidelines

-
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 (represented above with a green arrow).
-
The transaction hash must match the transaction hash in the passport (represented above with a purple arrow).
-
The transaction date and time from the passport must match with a maximum difference of 1-5 seconds with the transaction (represented above with a brown arrow).

- Using Etherscan 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 (represented in the example from above with the green arrows).

-
Assert that the link from the passport points to
https://ipfs.io/ipfs/+<content_hash>, as displayed above with a brown arrow. -
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.

-
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 (represented in the example from above with the green arrows).
-
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 (represented in the example from above with the blue arrows).
This wiki is under heavy development. Content is subject to change.