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

Condition.extension:endocrinologicalDisorder doesn't seem needed #101

Open
jpriebe-epic opened this issue Apr 5, 2023 · 6 comments
Open

Comments

@jpriebe-epic
Copy link

endocrinologicalDisorder

This seems really specific to one concept case and I'm not sure it belongs in a specification. I don't see why it would need to be it's own extension.

Google turns up one specific diagnosis code that corresponds to endocrinological Disorder:

image

Something I'm missing here? Just looks like an example of something you could represent with Condition.

@jpriebe-epic jpriebe-epic changed the title Condition.extension:endocrinologicalDisorder Condition.extension:endocrinologicalDisorder doesn't seem needed Apr 5, 2023
@mikajylha
Copy link
Collaborator

mikajylha commented Apr 15, 2023

Finnish icd-10 version (specified by THL) has this specific case for codes that end with '&'. These are cancer diagnosis that may be supplemented with additional code starting with 'E' from ICD-10. Here I took the approach of embedding this additional e-code to the condition. Using a completely separate condition instance would be difficult because we have no condition-to-condition linking in FHIR and would be unable to maintain context (this cancer was caused by this disorder).

I'm not quite sure if this is Finnish only.

Some kind of condition-to-condition linking or "sub-condition":ing could potentially remove need for some other extensions defined in this profile too.

@jpriebe-epic
Copy link
Author

Maybe it's needed to stay it's own thing, but I'm also not sure how extending the single IDC-10 codeset couldn't accomplish this. Or including multiple related conditions.

Can you include an example of how one of these would be specified with the current specifications?

@jpriebe-epic
Copy link
Author

Still looking for an example - it might make sense as you say but I'd like to see what it looks like.

@mikajylha
Copy link
Collaborator

mikajylha commented Aug 10, 2023

I'll add an example.

@mrinnetmaki
Copy link
Collaborator

@mikajylha @jpriebe-epic can you please confirm whether this issue is resolved and can be closed?

@jpriebe-epic
Copy link
Author

Not a huge deal for us if this is left as-is. Would still be interested in seeing an example, though

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

3 participants