-
Notifications
You must be signed in to change notification settings - Fork 2
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
Preferred tooling for profile definition #3
Comments
yes by far the best choice. We should consider rewriting UK core in FSH. |
I am already creating FSH versions of the UK Core content, more as a use-case for other discussions I am having with options for developing profiles. In my opinion, it is definitely the way to go when creating profiles. |
As far as scope goes this project is about the API IG, not the profiles so need to be mindful that it keeps focus. |
Sushi project committed for review at first meeting |
Two options for publishing IG when finished.
At this stage, no need to commit as we can generate FHIR conformance resources. These can be loaded to Simplifier as FHIR resources for consistency with UK Core. Need to consider whether implementers who wish to derive product-specific capability statement are able to do this without using Simplifier. Documentation (e.g. for search parameters) can be provided as markdown files within this repository. |
FSH and Sushi agreed as preferred tooling for profile definition. Separate issue created for IG publication: #6 |
What tooling do we use for profile definition?
Propose:
https://build.fhir.org/ig/HL7/fhir-shorthand/
https://github.com/FHIR/sushi
The text was updated successfully, but these errors were encountered: