Patient Care has JIRAs for adding "escape" value codes (e.g. unknown, other), but Patient Care resource elements often bind to FHIR-I pattern value sets / code systems (such as Request.intent). Is it appropriate for PC to transfer ownership to FHIR-I and just defer to what the pattern does? Or, should PC open a new JIRA for FHIR-I to define the pattern first? We don't want to add new/duplicate codes if FHIR-I plans to do the same in their code system / value set. Example: J#55322

It would be best if someone created tracker item for the 'request' pattern (and tag it as grouping 'workflow' - that'll get it dealt with sooner).

This is an issue OO has run into as well. I think they commented on a recommended action and transferred ownership of the ticket.

If you know the ticket #, can you add it to the 'workflow' grouping?

I don’t recall it.

There are several related to Request.intent J#55322 (CommunicationRequest) J#55275 (ServiceRequest) J#55262 (DeviceRequest) J#55267 (NutritionOrder) All of these JIRAs seem to bind their intent element to the same value set, such that if FHIR-I resolves a single JIRA, it would resolve all of these with that one change to https://build.fhir.org/valueset-request-intent.html I'll log the FHIR-I JIRA....

Here is the new FHIR-I JIRA - https://jira.hl7.org/browse/FHIR-56142