Antitrust Statement

Professional Associations, such as HL7, which bring together competing entities are subject to strict 
scrutiny under applicable antitrust laws. HL7 recognizes that the antitrust laws were enacted to promote 
fairness in competition and, as such, supports laws against monopoly and restraints of trade and their 
enforcement. Each individual participating in HL7 meetings and conferences, regardless of venue, is 
responsible for knowing the contents of and adhering to the HL7 Antitrust Policy as stated in §05.01 of 
the Governance and Operations Manual (GOM).

Agenda

• Approve FHIR Infrastructure Minutes CC 2023-08-14
• Withdrawn IGs Grahame Grieve 
• Request from gender harmony to resolve the question around backporting CodeableReference extensions to R4 Grahame Grieve 
• FHIR-41808 - Getting issue details... STATUS Gino Canessa 
• Jurisdiction ValueSet Grahame Grieve 
• Obligation ticket

Attendees

Minutes Approval

• Motion to approve FHIR Infrastructure Minutes CC 2023-08-14 
  • Gino Canessa / Yunwei Wang: 11-0-1

Withdrawn IGs

• FMG: How withdrawn IG could be handled
• Grahame: creates a new entry in the package-list.json file saying that the previous publication has been withdrawn
  replaces all the html files in the root copy of the specification with a redirect to withdrawal-notice.html
  withdrawal-notice.html says why it's been withdrawn, and maybe directs users to an alternate specification
  all the publish boxes get updated to note that the spec is withdrawn, with a reference to the withdrawl-notice.html file
• Problem: historical packages are still available
• This is theoretical discussion since no IG requests withdrawn yet
• Alexander: Simplifier has functionality to unlist packages 
  • https://docs.fire.ly/projects/Simplifier/data_governance_and_quality_control/simplifierPackages.html#unlist-packages
• We will further investigate what happening in package registry
• Grahame Grieve  will document this one zulip so that people can continue discussion 
• https://chat.fhir.org/#narrow/stream/179280-fhir.2Finfrastructure-wg/topic/Withdrawn.20IGs

Backporting CodeableReference extensions to R4

• Vocab have a couple of extensions using CR data type
• Ease backporting of CR to R4
• To port to R4, we can say it is choice between CodeableConcept and Reference but not both
• Bas: The version page already stated how extension works in such situation. https://build.fhir.org/versions.html#extensions
• Such extension is translated/converted to complex extension
• Grahame, we could add a explanation in the extension IG how the CR extension works in R4
• Rob M: So there is a pattern for using complex extensions for data types or extensions defined in R5 to be used in R4
• Lloyd: This what would look like:

{
  "resourceType" : "ValueSet",
  "extenion" : [
    {
      "url" = "http://hl7.org/fhir/StructureDefinition/patient-sexParameterForClinicalUse",
      "extension" : [
        {
          "url" : "value",
          "valueCodeableConcept": ...
        },
        {
          "url" : "period",
          "valuePeriod": ...
        },
        {
          "url" : "comment",
          "valueString": ...
        },
        {
          "url" : "supportingInfo",
          "extension" : [   
            {
              "url": "_datatype",
              "valueString": "CodeableReference",
            },    
            {
              "url" = "http://hl7.org/fhir/5.0/StructureDefinition/extension-Extension.valueCodeableReference",
              "extension" : [
                {
                  "url" : "concept",
                  "valueCodeableConcept": ...
                },
                {
                  "url" : "reference",
                  "valueReference": ...
                }
              ]
            }
          ]
        }
      ]
    }
  }

• Lloyd: though the StructureDefinition of extension says that supportInfo  shall not have extension but the validator should recognize that the data type CodeableReference  is not defined in R4 and automatically accept the complex extension as replacement of value[x]
• there are two options for representing this complex extenion

          "extension" : [   
            {
              "url" = "http://hl7.org/fhir/5.0/StructureDefinition/extension-Extension.valueCodeableReference",
              "extension" : [
                {
                  "url" : "concept",
                  "valueCodeableConcept": ...
                },
                {
                  "url" : "reference",
                  "valueReference": ...
                }
              ]
            }
          ]

         "extension" : [   
            {
              "url": "_datatype",
              "valueString": "CodeableReference",
            },    
            {
              "url" : "concept",
              "valueCodeableConcept": ...
            },
            {
              "url" : "reference",
              "valueReference": ...
            }
          ]

• Item parked. Will continue discussion either on zulip or next week

Jurisdiction ValueSet

https://chat.fhir.org/#narrow/stream/179280-fhir.2Finfrastructure-wg/topic/Jurisdiction

• Reopen  FHIR-36933 - Getting issue details... STATUS
  • Grahame Grieve / Rick Geimer: 8-0-0
• Approve  FHIR-36933 - Getting issue details... STATUS
  • Grahame Grieve / Yunwei Wang: 8-0-0

Tracker

FHIR-41808 - Getting issue details... STATUS

• Gino, would like to move these to extension IG
• Lloyd, some description need to be updated before moving to extension IG
• Gino will update descriptions and come back next week

FHIR-41738 - Getting issue details... STATUS

• Lloyd applied changes from last Monday's discussion
• Grahame found some rending issues and will investigate
• Lloyd will continue working on this one.

Adjournment

Adjourned at 17:00 ET

Action Items

• Type your task here, using "@" to assign to a user and "//" to select a due date