Difference between revisions of "Integrity (MU3)"

From OpenEMR Project Wiki
Line 4: Line 4:
==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-516 (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 (note in above status that CCDA import may be bypassing this, which will research).
:*Message digest of imported documents/records are created via sha3-516 to ensure integrity of records (note in above status that CCDA import mechanism needs to have a hash stored).

Revision as of 07:39, 24 September 2020

Status

  • To complete this, need to ensure CCDA imports get hashed like other documents/imports.

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 ).
  • Message digest of imported documents/records are created via sha3-516 to ensure integrity of records (note in above status that CCDA import mechanism needs to have a hash stored).