Skip to content

Non-deterministic profile generation for US Core example #98

@ryukzak

Description

@ryukzak

The test-typescript-us-core-example CI job produces different generated files than local execution. The root cause is non-deterministic canonical URL resolution when multiple StructureDefinitions share the same short name (e.g., assertedDate resolves to condition-assertedDate locally but allergyintolerance-assertedDate on CI).

This affects ~30 generated profile files in examples/typescript-us-core/. The git diff validation step is currently commented out as a workaround (generation, typecheck, and tests still run).

Example diff from CI:

-// CanonicalURL: http://hl7.org/fhir/StructureDefinition/condition-assertedDate
+// CanonicalURL: http://hl7.org/fhir/StructureDefinition/allergyintolerance-assertedDate

Likely cause: iteration order over FHIR package contents differs between cached and freshly downloaded packages. The profile file naming uses the SD's short name which can collide across packages — the first-seen SD wins, but "first" depends on package load order.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions