FHIR Chat · This is not a valid FHIR ID · hapi

Stream: hapi

Topic: This is not a valid FHIR ID


view this post on Zulip Christian Nau (Jun 21 2021 at 06:27):

Hello!
I'm trying to install german-base-profile package, containing this value-set: https://simplifier.net/basisprofil-de-r4/valuesetvitalsigndebodyheightloinc
But during start-up I'm getting this error:

 Can not process entity with ID[ValueSetVitalSignDE_Body_Height_Loinc], this is not a valid FHIR ID

What can I do about this?

view this post on Zulip Grahame Grieve (Jun 21 2021 at 06:34):

ask the author of the valueset to use a valid id

view this post on Zulip Christian Nau (Jun 21 2021 at 06:51):

This is the "official" package. I don't know if I can make them change their ID.
Why is it invalid?

view this post on Zulip Grahame Grieve (Jun 21 2021 at 06:54):

underscores are invalid in resource ids.

view this post on Zulip Grahame Grieve (Jun 21 2021 at 06:54):

@Ward Weistra Simplifier shouldn't allow that. @Patrick Werner who should fix that?

view this post on Zulip Ward Weistra (Jun 21 2021 at 09:29):

Seems we haven't turned on every more expensive step of validation available in the .NET SDK in Simplifier. I'll look into improving that.

view this post on Zulip Patrick Werner (Jun 21 2021 at 15:23):

Grahame Grieve said:

Ward Weistra Simplifier shouldn't allow that. Patrick Werner who should fix that?

Will make sure that a fix is applied soon.

view this post on Zulip Patrick Werner (Jun 21 2021 at 15:23):

@Alexander Zautke @Simone Heckmann fyi

view this post on Zulip Patrick Werner (Jun 21 2021 at 15:23):

I can fix all the ids.

view this post on Zulip Simone Heckmann (Jun 21 2021 at 15:26):

Christian Nau said:

This is the "official" package. I don't know if I can make them change their ID.

You can make us do anything :wink:. Just go to the german stream and let us know... (we don't usually monitor all of the international discussions)

view this post on Zulip Ward Weistra (Jun 22 2021 at 12:28):

@Alexander Zautke noticed that the regex is not checked here, because StructureDefinition.id in R4 is typed as a string (fixed in R5). Therefore no validation of the id datatype is happening when running the validator.

We're looking whether we can manually work around this issue in the validator just for these cases: https://github.com/FirelyTeam/firely-net-sdk/issues/1773

view this post on Zulip Grahame Grieve (Jun 22 2021 at 12:48):

I think there's test cases for this in the validator tests

view this post on Zulip Ward Weistra (Jun 22 2021 at 16:14):

OK, will say why this wasn't found when implementing those then!


Last updated: Apr 12 2022 at 19:14 UTC