FHIR / FHIR/sushi

Should normative status and version extensions be inherited on SD elements? (Probably not?)

Open
#1,407 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
188
Forks
65
Avg merge
8d 11h
Merged PRs (30d)
3

Description

When SUSHI creates a profile, it clones the parent SD and then performs a series of steps, including removing all top-level extensions that should not be inherited by a profile (such as the normative status and normative version extensions). SUSHI does not currently remove these extensions from elements in the SD, but it seems like perhaps it should. We should investigate and modify as necessary.

Zulip discussion: https://chat.fhir.org/#narrow/stream/215610-shorthand/topic/Deterministic.20Output/near/408648034

Contributor guide

Open the contributing guide

Research direction

Start by tracing the profile-generation steps where SUSHI clones the parent StructureDefinition and removes top-level extensions. Use the linked Zulip discussion to establish the expected inheritance behavior for extensions on elements, then inspect the relevant processing and tests. Done means the behavior is decided and the implementation and coverage match that decision.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
compilers
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.