Difference between revisions of "Integrity (MU3)"
From OpenEMR Project Wiki
Bradymiller (talk | contribs) (→Notes) |
Bradymiller (talk | contribs) (→Status) |
||
| Line 1: | Line 1: | ||
==Status== | ==Status== | ||
:*'''VERIFIED COMPLETE''' | :*'''VERIFIED COMPLETE''' | ||
:* | :*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-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 (as an example, CCDA import is stored and hashed via sha3-516). | :*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 via sha3-516). | ||
Revision as of 23:12, 26 September 2020
Status
- VERIFIED COMPLETE
- Ready to sign self-declaration.
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 (as an example, CCDA import is stored and hashed via sha3-516).
