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

Observation.effectiveDateTime (Sexual Orientation) is not truncated #69

Open
anthonygalba opened this issue May 31, 2024 · 4 comments
Open

Comments

@anthonygalba
Copy link

Effective DateTime is not listed among the dates that need to be truncated to year on the UDS+ Sexual Orientation Resource IG page (https://fhir.org/guides/hrsa/uds-plus/StructureDefinition-uds-plus-sexual-orientation-observation.html). It looks like the other Observation-based resources do call this out as needing truncation, so I'm guessing this one was just missed.

Inferno does not validate this date is truncated, however the UDS+ testing sandbox does.
Please update the IG to call out that this date needs to be truncated as well.

@anthonygalba
Copy link
Author

I also noticed Observation.issued on lab observation and clinical result observation is not called out as needing to be truncated. However, the UDS+ sandbox does not throw any errors when we don't truncate that. So I'm not clear if those should be truncated or it's fine to send the full instant.

@nbashyam
Copy link
Contributor

The updates being done for 1.0.2 will be pushed to include these date truncation requirements as constraints and will be incorporated into INFERNO also and can be validated before submitting data to HRSA.

@nbashyam
Copy link
Contributor

Also, since the instant data type has a constraint in the FHIR Spec and does not allow the truncated date, we are planning to create an extension of "issuedDateTime" which is of dateTime data type and allows for the truncation. Let us know if there are any concerns on this approach.

@anthonygalba
Copy link
Author

As discussed at office hours today, that seems like a reasonable solution

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

No branches or pull requests

2 participants