Changes between Version 25 and Version 26 of Archtectural Overview Security


Ignore:
Timestamp:
Feb 29, 2008, 9:21:38 PM (16 years ago)
Author:
KOBAYASHI, Shinji
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Archtectural Overview Security

    v25 v26  
    175175Digital Signature
    176176
     177openEHRのEHRの内部ではバージョン管理されるオブジェクトの各バージョンにデジタル署名がつけられることがある(たとえば,処方薬リストや受付ノートなどの,全ての論理アイテムの各バージョン)。署名は秘密鍵により暗号(RSA-1など)
     178
    177179The possibility exists within an openEHR EHR to digitally sign each Version in a Versioned object (i.e. for each Version of any logical item, such as medications list, encounter note etc.). The signature is created as a private-key encryption (e.g. RSA-1) of a hash (e.g. MD5) of a canonical representation (such as in schema-based XML) of the Version being committed. A likely candidate for defining the signature and digest strings in openEHR is the openPGP message format (IETF RFC24402), due to being an open specification and self-describing. The use of RFC2440 for the format does not imply the use of the PGP distributed certificate infrastructure, or indeed any certification infrastructure; openEHR is agnostic on this point. If no public key or equivalent infrastructure is available, the encryption step might be omitted, resulting in a digest only of the content. The signature is stored within the Version object, allowing it to be conveniently carried within EHR Extracts. The process is shown in FIGURE 22.
    178180