Difference between revisions of "Smart Health Card"

From MgmtWiki
Jump to: navigation, search
(Embedded in a QR codes)
(Embedded in a QR codes)
Line 44: Line 44:
 
   }
 
   }
 
  }
 
  }
===Embedded in a QR codes===
+
===Embedding in QR codes===
 
* The [[Smart Health Card]] is embedded in a JWS (JOSE) format with a header, payload and signature block for verification.
 
* The [[Smart Health Card]] is embedded in a JWS (JOSE) format with a header, payload and signature block for verification.
 
*Each JWS string that appears in the .verifiableCredential[] of a .smart-health-card file can be embedded in one or more QR codes. We aim to ensure that printed (or electronically displayed) codes are usable at physical dimensions of 40mmx40mm. This constraint allows us to use QR codes up to Version 22, at 105x105 modules. When embedding a JWS string in QR codes, the JWS string SHALL be encoded as Numerical Mode QR codes consisting of the digits 0-9 (see [https://spec.smarthealth.cards/#encoding-chunks-as-qr-codes Encoding Chunks as QR codes]).
 
*Each JWS string that appears in the .verifiableCredential[] of a .smart-health-card file can be embedded in one or more QR codes. We aim to ensure that printed (or electronically displayed) codes are usable at physical dimensions of 40mmx40mm. This constraint allows us to use QR codes up to Version 22, at 105x105 modules. When embedding a JWS string in QR codes, the JWS string SHALL be encoded as Numerical Mode QR codes consisting of the digits 0-9 (see [https://spec.smarthealth.cards/#encoding-chunks-as-qr-codes Encoding Chunks as QR codes]).

Revision as of 16:25, 27 October 2021

Full Title or Meme

A (usually virtual) Smart Card containing at least some Identity and some Health Information, typically vaccination data,

The Smart Health Card is one of a series of SMART health specifications initiated by Boston Children's Hospital often with Harvard and other Boston hospitals.

Context

Design Goals

  1. Support end-to-end workflow where users receive and present relevant healthcare data
  2. Enable workflow with open standards
  3. Support strong cryptographic signatures
  4. Enable privacy preserving data presentations for specific use cases

Use Cases

Technical Details

The overall JWS payload matches the following structure (before it is minified and compressed):

{
 "iss": "<<Issuer URL>>",
 "nbf": 1591037940,
 "vc": {
   "type": [
     "https://smarthealth.cards#health-card",
     "<<Additional Types>>",
   ],
   "credentialSubject": {
     "fhirVersion": "<<FHIR Version, e.g. '4.0.1'>>",
     "fhirBundle":{
       "resourceType": "Bundle",
       "type": "collection",
       "entry": ["<<FHIR Resource>>", "<<FHIR Resource>>", "..."]
     }
   }
 }
}

Embedding in QR codes

  • The Smart Health Card is embedded in a JWS (JOSE) format with a header, payload and signature block for verification.
  • Each JWS string that appears in the .verifiableCredential[] of a .smart-health-card file can be embedded in one or more QR codes. We aim to ensure that printed (or electronically displayed) codes are usable at physical dimensions of 40mmx40mm. This constraint allows us to use QR codes up to Version 22, at 105x105 modules. When embedding a JWS string in QR codes, the JWS string SHALL be encoded as Numerical Mode QR codes consisting of the digits 0-9 (see Encoding Chunks as QR codes).
  • WARNING the size recommended above can be scanned by modern (in 2021) smart phone with a high resolution camera, but cannot be resolved by most PC cameras or less expensive smart phones.

References