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

Invalid Search parameter definition #2567

Open
brianpos opened this issue Aug 8, 2023 · 5 comments
Open

Invalid Search parameter definition #2567

brianpos opened this issue Aug 8, 2023 · 5 comments
Labels

Comments

@brianpos
Copy link
Collaborator

brianpos commented Aug 8, 2023

Invalid search parameter definition in http://hl7.org/fhir/SearchParameter/Observation-value-date in R4B:
value.as(DateTime) | value.as(Period)
should be
value.as(DateTime) | value.as(Period)
(admitedly this is how it is defined in the spec itself)
https://hl7.org/fhir/r4b/observation.html#search

https://github.com/FirelyTeam/firely-net-sdk/blob/168747b66d1bbd1733913436950fdb0a79fac984/src/Hl7.Fhir.R4B/Model/Generated/Template-ModelInfo.cs#L1757

@brianpos
Copy link
Collaborator Author

brianpos commented Aug 8, 2023

@mmsmits
Copy link
Member

mmsmits commented Aug 8, 2023

You mean it's currently
value.as(DateTime) | value.as(Period)
and it should be
value.​ofType(dateTime) | value.​ofType(Period)

or the other way around?

@brianpos
Copy link
Collaborator Author

the fhirpath typename for datetime is dateTime

@Kasdejong Kasdejong self-assigned this Mar 27, 2024
@Kasdejong Kasdejong removed their assignment Mar 27, 2024
@mmsmits
Copy link
Member

mmsmits commented Mar 28, 2024

Refinement:

  • First check with FS team if there is a list they use. @eugene-blokhin ?
  • Alter the codegen to correct these issues.
  • Check if these issues need to be corrected for all FHIR version
  • Unit test in the SDK to check if the generator stays consistent after this change.

@alexzautke
Copy link
Member

In R5 we only fixed invalid Composite search parameter definitions. We din't stumble yet over this. At least in R4 no SearchParameter that is relevant for US compliancy is affected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Todo
Development

No branches or pull requests

4 participants