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.
Summary
I wanted a quick look at adding better extensions to fhir-fr.
At the moment we're not even recognising extension properties - because of how they're encoded they're just ignored.
This PR improves things a little, but doesn't have any intelligence. Really, we need to:
Patient Example
The example is acutally quite complex because for some reason, birth-place and identifty-status are mapped very differently.
I need to better study the defintions and work out the mapping rules.
In fhir-ndr-et, we used the mappings file to manually map the extension key. But I really want to do better than that here.
This probably needs a good day's work to figure out.
AI Usage
Please disclose how you've used AI in this work (it's cool, we just want to know!):
You can read more details in our Responsible AI Policy