Skip to content

Test cases for strict identifier system validation#245

Open
lmckenzi wants to merge 2 commits into
masterfrom
StrictIdentifierSystems
Open

Test cases for strict identifier system validation#245
lmckenzi wants to merge 2 commits into
masterfrom
StrictIdentifierSystems

Conversation

@lmckenzi
Copy link
Copy Markdown
Contributor

@lmckenzi lmckenzi commented Oct 9, 2025

Provides tests for checking hapifhir/org.hl7.fhir.core#2202

"severity" : "information",
"code" : "business-rule",
"details" : {
"text" : "Identifier.system is not based on example.org or example.com and is not a preferred URI of any identifier system NamingSystems. Ensure that the Identifier.system value is a properly defined system value"
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I think this language is a problem. It should be 'chcek' not 'ensure' - it's not wrong to use something for which there's no NamingSystem. Or maybe it should say 'best practice is to declare the system in a NamingSystem resource'

Comment thread validator/manifest.json
{
"name": "identifier-systems",
"file": "patient-identifiers.xml",
"description": "Check that identifier systems are valid",
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

it's not valid, it's 'declared'

Copy link
Copy Markdown
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.

per comments - language is too strong

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