Feedback and review comments must be submitted as a Simplifier issue. Issues should be logged at the level of the FHIR Simplifier resource. This is done in the project view in Simplifier.
This documentation pack contains links to the Simplifier project and the implementation guide. The project holds all the source files, and the guide is a human readable html view of the project. It is acknowledged that not everyone will have enough knowledge of FHIR Implementation Guides or Simplifier to log an issue to the correct Simplifier resource (see note below) and therefore logging at the project level is allowable if this is the case.
Note: Simplifier refers to everything as a resource whether it’s an image, example or FHIR profile
The UK Core uses Simplifier for issue tracking and maintenance. Although the UK Core is in the public domain, you will need to create an account and login to raise issues. Creating a Simplifier account is done by going to https://simplifier.net/ and using the sign up option on the top right of the page. An email address and a chosen password are the only details needed to set up an account.
Logging in to your Simplifier account is required to raise issues. Browse to https://simplifier.net/ and use the login option on the top right of the page, then enter the chosen credentials.
The UK Core Implementation Guide 0.2.0 - STU1 project is derived from the UK Core Implementation Guide 0.1.0 - STU1 Release with the content required for the Sprint 4 of Clinical and Technical Assurance added.
Further information about the Clinical and Technical Assurance Sprint in the context of the UK Core release approach is available in the UK Core Release Cycle section.
When the change request is for a change to an existing UK Core FHIR asset, the preferred approach is to raise the issue at the level of the relevant asset.
It is acknowledged that not everyone will have enough knowledge of FHIR Implementation Guides or Simplifier to log an issue to the correct Simplifier resource, therefore logging at the project level is allowable, if this is the case. However, issue logging at asset level is the preferred approach, as it makes triage of issues easier.
Note: Simplifier refers to everything as a resource whether it’s an image, example or FHIR profile and provides a mechanism to filter on type.
To search for a particular asset, for example to find the Patient profile, filter by resource category "Profiles" (tick the box alongside Profiles), add the word "Patient" in the search box and hit return. This will bring up a link to the Patient profile which will take you to a page with a view of the Patient profile.
Once the required Simplifier resource page is found, the last tab on the page is the issues tab. Clicking on this will bring up a page where a new issue should be raised by clicking the New Issue button.
This will only require a title and the details of the issue or comment. All other issues logged for this Simplifier resource will be available from this page and you can check these or find out whether this issue has already been logged, if required.
If you cannot locate the Simplifier resource, or it is not appropriate to log an issue at the Simplifier resource level, then you should raise an issue at the project level. In this case, the title and/or issue text should identify which part of the UK Core Implementation is the subject of the issue being raised. See the Creating a Simplifier Issue at Project Level section for how to do this.
Issues for new UK Core FHIR assets should be raised at the UK Core project level the issue must indicate the use case or details of the requirement as to why the new asset is needed.
To create a issue at the project level, navigate to the project. Once you are in the project, click on the issues tab and then the create button to create the issue.