Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update validate-inactive-3a-response-parameters.json #153

Merged
merged 2 commits into from
Nov 30, 2023

Conversation

lawley
Copy link
Contributor

@lawley lawley commented Nov 28, 2023

Support optional code and system values and more precise issue location

Support optional `code` and `system` values and more precise issue location
@grahamegrieve
Copy link
Collaborator

Why these changes?

@lawley
Copy link
Contributor Author

lawley commented Nov 28, 2023

Aligned with this from requirements.md

  • The server SHALL return system, code and display for the code that it considered valid, along with the version if this is known

Ontoservers implements

  • The server SHOULD return system, code and display for the code that it considered invalid, along with the version if these are known

Also, it is specifically the Coding.code that is at issue here rather than, for example, the Coding.display

@grahamegrieve
Copy link
Collaborator

but it's not valid. And the problem is the concept, not the code

Copy link
Collaborator

@grahamegrieve grahamegrieve left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@grahamegrieve grahamegrieve merged commit 07b0ac9 into FHIR:master Nov 30, 2023
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants