Per May 2024 Connectathon, implement Lisa Nelson's fancy UI as described at https://docs.google.com/document/d/1umIJgEo15msDLPmkX0ztdx5C-45LIys1ZEySdnleUDw/edit?pli=1#heading=h.sqoliyrvmnkc

Email from Lisa to Justin 2023-07-18 after final report out:

I noticed you were not picking up the revocation status of the document. This work was started two Connectathons ago (discussed). One Connectathon we attempted to support a revocation use case and ran into vocabulary problems and a major flaw in the DocumentReference.docStatus and Composition.status vocabulary which could not be easily fixed in FHIR R4.

Over the past few months we’ve been struggling to invent a workaround that is feasible, and offers a path to the future where this issue is addressed. In FHIR R5 and FHIR R6, they fixed the vocabulary problem for status DocumentReference.docStatus and Composition.status.

In the meantime, while we continue to focus on FHIR R4 implementation guidance. We have to use an extension for the revocation status of a document. So you need to check in a different structural spot to find the revocation status.

Documents that are not revoked don’t use this extension field, but documents that are revoked do, so you need to check for it, and reveal it if you find it. You should find this in the current MI AD document at the end of the story, after scene 5 or so.

{
  "resourceType": "DocumentReference",
  "id": "429a3d92-0491-49ae-97bb-1a21f78084ea",
  "meta": {
    "versionId": "2",
    "lastUpdated": "2024-07-18T15:48:17.000+00:00",
    "source": "#b0O94EGavVDKWKrI"
  },
  "extension": [ {
    "url": "http://hl7.org/fhir/us/ccda/StructureDefinition/VersionNumber",
    "valueInteger": 1711857600
  }, {
    "url": "http://hl7.org/fhir/us/pacio-adi/StructureDefinition/adi-document-revoke-status-extension",
    "valueCoding": {
      "system": "http://hl7.org/fhir/us/pacio-adi/CodeSystem/ADIRevokeStatusCS",
      "code": "cancelled"
    }
  } ],

I show you a couple possibilities for your UI. You could include the Revocation Status: after Document Status, or you could do something bolder and really Watermark the card in a more noticeable way.

Just a couple possible ideas.

Good luck.

Server will stay up in “final state” for our use case for at least a day or so while I focus on some other things. Let me know if you want to test anything. We don’t have to limit testing to the Connectathons only.

Regards,

Lisa

During testing for the ADI July '24 track I noticed that we're calling https://qa-rr-fhir.maxmddirect.com/Patient/$match - that's /Patient/$match against the AD Vault, and it's returning a 400. Lisa says that we shouldn't be doing that. I think there's no harm as-is, but we shouldn't be doing that.

https://qa-rr-fhir.maxmddirect.com/Patient/$match

Testing notes at https://docs.google.com/document/d/1EzdS8g_zOPXeqkm9kf-XoGaZKAafBMVjVJwsZDLL6Cg/edit#heading=h.8zb5qbshr7d

To support COVID-19 SMART Health Cards, Apple added a URL scheme for importing SHC content, as well as detection of QR codes containing SHC data. Whether the data included in the URL fits in a QR code or not, the content can be added to Apple Health. Given the SHC data does fit in a QR code, it will also automatically create a wallet entry with the SHC QR code.

SHL in Apple Wallet

Since SHL content is often too large for a QR code, using the same methods with the SHC contained in a SHL only imports the data to Apple Health and does not automatically create a Wallet entry. Ideally, a Wallet entry would include the SHL and metadata like its label, expiration, etc., but this would have to be custom-made (requires Apple Developer registration, card design, and wallet certification).

SHL in Apple Health

An SHL can't yet be added directly to Apple Health, but its SHC content can. To add an SHL's SHC record to Apple Health, add Apple's button w/url like https://redirect.health.apple.com/SMARTHealthCard/[encoded shc] where the encoded SHC is the output of

let str = shc_jws;
let numericEncodings = [];
for (let i=0; i<str.length; i++) {
  let c = str.charCodeAt(i) - 45;
  if (c < 10) {
    c = "0"+c;
  } else {
     c = c.toString();
  }
  numericEncodings.push(c);
}
let num = numericEncodings.join("");
return num;