Skip to content

separate out general schema components from clinical components#16

Open
sierra-moxon wants to merge 2 commits intomainfrom
issue_3281
Open

separate out general schema components from clinical components#16
sierra-moxon wants to merge 2 commits intomainfrom
issue_3281

Conversation

@sierra-moxon
Copy link
Copy Markdown
Member

@sierra-moxon sierra-moxon commented Mar 16, 2026

fixes: #21
there are also a few small changes to get the tests to pass.

the point of this PR is to make it clearer how to reuse the microschemas that are generic, for non-clinical use cases. This was my "least disruptive" idea. e.g., I'm building a geochemical profile using the same patterns (and I want to instantiate QuantityValue but not explain BodyWeight...)

other ideas include:

  • remove clinical classes all together and make a new repo in monarch-initiative (or linkml) for this clinical "profile". there could be a registry of profiles.
  • or we could change the name of this repo to something like linkml-cde-profile and make a new linkml-microschema repo with just the generic model elements...

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 16, 2026

PR Preview Action v1.8.1

QR code for preview link

🚀 View preview at
https://linkml.github.io/linkml-microschema-profile/pr-preview/pr-16/

Built to branch gh-pages at 2026-03-16 22:27 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

…ing mixin, use linkml-validate instead of run-examples
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.

Move clinically specific subclasses out of linkml-microschema-profile

1 participant