Stream: EBMonFHIR
Topic: cited-artifact-status-type value set
Yunwei Wang (Nov 23 2021 at 20:14):
I noticed that Citation.citedArtifact.currentState binds to cited-artifact-status-type value set instead of publication-status value set. I would like to know if it is possible to also include codes from publication-status value set into the cited-artifact-status-type value set, which mean the value set take codes from both PublicationStatus and CitedArtifactStatusType code systems.
@Brian Alper
Brian Alper (Nov 25 2021 at 10:53):
@Yunwei Wang publication-status includes 4 codes (draft, active, retired, unknown). The first two (draft, active) are included in cited-artifact-status-type at http://build.fhir.org/valueset-cited-artifact-status-type.html and the "retired" publication-status could be represented with any of withdrawn, rejected, archived or retracted -- so there are more specific codes in cited-artifact-status-type so it seems incorrect to have a less specific code that overlaps with existing codes. If really needed the binding is Extensible. (Having said that, if you have a strong case to add the "retired" code to cited-artifact-status-type please let us know and we can still consider it.) Not sure there is a strong case to add "unknown" for a status marker that is an optional element. Seems like a must-have for publication-status because the element is required and cannot be left missing when unknown.
Yunwei Wang (Nov 26 2021 at 14:34):
The artifact we imported from CDS-Connect has "unknown" status
Brian Alper (Nov 26 2021 at 16:48):
You could simply leave Citation.citedArtifact.currentState empty or missing to reflect no information about the current state of the cited artifact. If you desire to affirmatively state the current state is "unknown" you could add a currentState value and based on Extensible binding strength "If there is no applicable concept in value set (based on human review), an alternate concept (either system/code pair, or text) may be used instead." so you could use the publication-status code system with the code for "unknown".
Yunwei Wang (Nov 26 2021 at 18:58):
I think it makes sense to define the value as taking codes from both code systems. A use case is the citedArtifact is another Citation (or another FHIR resource). In such scenario, the value citedArtifact.currentState would be the status of the cited Citation. So including values from PublicationStatus could avoid create a mapping between these two code systems.
To be clear, I don't want to add "unknown" to CitedArtifactStatusType code systems. Instead I want to change the definition of cited-artifact-status-type value set so that it takes values from both code systems.
Brian Alper (Nov 26 2021 at 22:09):
A value set can include codes from more than one code system. We will have to learn how to apply that change in the FHIR build but that sounds like a reasonable way to apply the concept. You can suggest the change to the value set with a FHIR Tracker/Jira request and it can be discussed in one of the HL7 CDS WG meetings.
Last updated: Apr 12 2022 at 19:14 UTC
