API: snapshot tests for the KBV Condition Diagnosis pipeline#206
Merged
Conversation
Pins FHIR schema, TypeSchema (profile + resolved snapshot) and generated TypeScript for KBV_PR_Base_Condition_Diagnosis and its base Condition, mirroring the on-the-fly example (kbv.basis@1.9.0, open type-sliced onset[x]/abatement[x], profile reference target on subject).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
kbv-condition-diagnosison-the-fly example (kbv.basis@1.9.0from the simplifier registry, tree-shaken toKBV_PR_Base_Condition_Diagnosis), fully in-memory — no disk output.ConditionKBV_PR_Base_Condition_DiagnosisCondition.tsandCondition_KBV_PR_Base_Condition_Diagnosis.tsThe profile exercises open type-sliced choice elements (
onset[x]/abatement[x]) and a profile reference target onsubject(KBV_PR_Base_Patient). The snapshots pin current representations at each stage, so upcoming TypeSchema refactorings (e.g. #203) will surface their representation changes explicitly in these snapshot diffs.