Difference between revisions of "Smart Health Card"

From MgmtWiki
Jump to: navigation, search
(References)
(Context)
Line 7: Line 7:
 
* [https://smarthealth.cards/index.html What are SMART Health Cards?] The (SHC) Web Site from Boston Children's Hospital.
 
* [https://smarthealth.cards/index.html What are SMART Health Cards?] The (SHC) Web Site from Boston Children's Hospital.
 
* The primary context is the [https://wiki.idesg.org/wiki/index.php/Health_Care_Profile Kantara Health Care Profile].
 
* The primary context is the [https://wiki.idesg.org/wiki/index.php/Health_Care_Profile Kantara Health Care Profile].
* There is a half-baked [https://www.youtube.com/watch?v=UdlmRoJK1Yg&t=26s effort in Microsoft] as part of VCI to take ownership of this term [https://bitly.com/fhir20-did for Microsoft or the VCI] that they belong to using DIDs. The SHC is structure like a [[Verifiable Credential]] using FHIR formatted data from HL7 EHRs, but there is no ability to give patients control of the data that is released from the SHC.
+
* There is a commercial [https://www.youtube.com/watch?v=UdlmRoJK1Yg&t=26s effort in Microsoft] as part of VCI to take ownership of this term [https://bitly.com/fhir20-did for the VCI] that they belong to using DIDs. The SHC is structure like a [[Verifiable Credential]] using FHIR formatted data from HL7 EHRs, but there is no ability to give patients control of the data that is released from the SHC.
  
 
===Design Goals===
 
===Design Goals===

Revision as of 17:15, 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>>", "..."]
     }
   }
 }
}

References