Difference between revisions of "Integrity (MU3)"

From OpenEMR Project Wiki
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Status==
==Status==
:*'''VERIFIED COMPLETE'''
:*'''VERIFIED COMPLETE'''
:*This item is ready to self-attest.
:*Ready to sign self-declaration.


==Notes==
==Notes==
:*All message digest hashing is using sha3-516 (able to use sha3 because of this: https://csrc.nist.gov/publications/detail/fips/180/4/final ).
:*All message digest hashing is using sha3-512 (able to use sha3 because of this: https://csrc.nist.gov/publications/detail/fips/180/4/final ).
:*Message digest of imported documents/records are created via sha3-516 to ensure integrity of records (as an example, CCDA import is stored and hashed).
:*Message digest of imported documents/records are created via sha3-512 to ensure integrity of records (as an example, CCDA import is stored and hashed via sha3-512).

Latest revision as of 18:03, 9 March 2022

Status

  • VERIFIED COMPLETE
  • Ready to sign self-declaration.

Notes

  • All message digest hashing is using sha3-512 (able to use sha3 because of this: https://csrc.nist.gov/publications/detail/fips/180/4/final ).
  • Message digest of imported documents/records are created via sha3-512 to ensure integrity of records (as an example, CCDA import is stored and hashed via sha3-512).