Difference between revisions of "Integrity (MU3)"
From OpenEMR Project Wiki
Bradymiller (talk | contribs) |
Bradymiller (talk | contribs) (→Status) |
||
| Line 1: | Line 1: | ||
==Status== | ==Status== | ||
:*To complete this, need to ensure CCDA imports | :*To complete this, need to ensure CCDA imports get hashed like other documents/imports. | ||
==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 may be bypassing this, which will research). | ||
Revision as of 07:02, 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 may be bypassing this, which will research).
