BFD-4295: Mappings for C4DIC Operation - #2806
Merged
Merged
Conversation
alex-dzeda
marked this pull request as ready for review
September 16, 2025 17:40
alex-dzeda
requested review from
aschey-forpeople,
malessi and
mjburling
as code owners
September 16, 2025 17:40
aschey-forpeople
approved these changes
Sep 18, 2025
mjburling
approved these changes
Sep 23, 2025
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.
JIRA Ticket:
BFD-4295
What Does This PR Do?
Adds a FHIR Mapping Language specification for generating a bundle of C4DIC resources.
Update CMS to have an & instead of an "and Medicaid Services"
What Should Reviewers Watch For?
If you're reviewing this PR, please check for these things in particular:
There's a few tangentially-related updates in here, and one thing to be aware of:
The uuid() function doesn't work for whatever reason when passing R4 to the validator in the version parameter. So I've hardcoded uuids. An AC on the implementation ticket will make note of this and what to do. Once there's further direction on the additional fields to add to the digital insurance card bundle, I'll take another stab at using a the R5 validator, but pass in the R4 profiles, to attempt to take advantage of the UUID functionality.
As part of testing out the R5 version, I adjusted the internal concept maps to use the R5-onwards equivalency, ==
What Security Implications Does This PR Have?
Please indicate if this PR does any of the following:
Adds any new software dependencies
Modifies any security controls
Adds new transmission or storage of data
Any other changes that could possibly affect security?
I have considered the above security implications as it relates to this PR. (If one or more of the above apply, it cannot be merged without the ISSO or team security engineer's (
@sb-benohe) approval.)I have created tests to sufficiently ensure the reliability of my code, if applicable. If this is a modification to an existing piece of code, I have audited the associated tests to ensure everything works as expected.
Validation
Have you fully verified and tested these changes? Is the acceptance criteria met? Please provide reproducible testing instructions, code snippets, or screenshots as applicable.
Validator passes the resulting bundle resource with no errors.