AD Revocation status fix per Lisa post- July '24 Connectathon
Closed this issue · 1 comments
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
