Skip to content

Latest commit

 

History

History
41 lines (25 loc) · 3.71 KB

README.md

File metadata and controls

41 lines (25 loc) · 3.71 KB

AU eRequesting FHIR Implementation Guide

AU eRequesting is provided to support the use of HL7® FHIR®© for clinical requesting and ordering in an Australian context. It sets the minimum expectations on FHIR resources to support conformance and implementation in systems.

Did you find an error?

If it's a specification error please search the issues list in Jira issue tracker to ensure the error was not already reported. You can use the Propose-a-change option at the bottom of each page of the IG to trigger the creation of a Jira issue.

If you've found an issue with this repository or it's contents then you please raise a GitHub issue.

Contributing to AU eRequesting Development

AU eRequesting R1 is in currently in development. Ballot for Comment is scheduled for February 2025.

1. Join the AU eRequesting Technical Design Group

See How to Register - Participant Information for information on how to participate in the AU eRequesting Technical Design Group and Clinical Design Group as part of Sparked, the Australian FHIR Accelerator. Visit the HL7 Australia - AU eRequesting Technical Design Group Home.

2. Discuss an issue in chat.fhir.org

If you have a question, feature request, or proposed change, the best place to start is Zulip e.g. the https://chat.fhir.org/#narrow/stream/179166-implementers stream. If what you want to discuss is specific to Australia you can post in the Australia stream https://chat.fhir.org/#narrow/stream/179173-australia.

3. Identify future work or raise discussion points

To identify future work or raise discussion points, you can post in the Australia stream https://chat.fhir.org/#narrow/stream/179173-australia or raise specification feedback through a Jira issue tracker.

4. Discuss with the team

Once the issue is logged, you should discuss with the team on chat.fhir.org in the australia > AU eRequest topic before attempting to make changes yourself. It's important to coordinate with the other people working on the project.

5. Create a pull request

When everyone has agreed on a course of action, IG changes should be submitted as a pull request for review in this repository.

To create a pull request:

  • Fork this repository to your GitHub account
  • Clone your fork to your local machine
  • Create a branch for your changes
  • Make your changes and push to your fork in GitHub
  • Create a pull request from the branch in your forked repository to this repository's master branch
  • Maintainers of this repository will then review and take appropriate action on your pull request