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

Added Snomed CT AU guidance #866

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

mjosborne1
Copy link
Collaborator

Similar to US Core guidance page, I have added some guidance on using SCT AU in FHIR.

@JayMurdoch JayMurdoch requested a review from dt-r September 16, 2024 22:18
@@ -44,6 +44,61 @@ The following FMM levels are defined:

Reference should also be made to [Version Management Policy](http://hl7.org/fhir/R4/versions.html).

### SNOMED CT Australian Edition
[SNOMED CT](https://snomed.info/sct) (Systematized Nomenclature of Medicine – Clinical Terms) is a comprehensive clinical terminology widely used in healthcare to support the electronic exchange of clinical health information.
In Australia, SNOMED CT-AU extends SNOMED CT for recording structured clinical data in health
Copy link
Collaborator

@JayMurdoch JayMurdoch Sep 17, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider phrasing of the definition of SNOMED CT-AU to be more general, and not specific to health record. Eg

"In Australia, SNOMED CT Australian Edition (SNOMED CT-AU) extends SNOMED CT with local variations and customisation relevant to the Australian healthcare community."

https://www.healthterminologies.gov.au/understanding-clinical-terminology-landing/what-is-snomed-ct-and-amt/

### SNOMED CT Australian Edition
[SNOMED CT](https://snomed.info/sct) (Systematized Nomenclature of Medicine – Clinical Terms) is a comprehensive clinical terminology widely used in healthcare to support the electronic exchange of clinical health information.
In Australia, SNOMED CT-AU extends SNOMED CT for recording structured clinical data in health
records in Australian conditions. Many SNOMED CT-AU value sets have already been developed and published by the National Clinical Terminology Service [NCTS](https://www.healthterminologies.gov.au).
Copy link
Collaborator

@JayMurdoch JayMurdoch Sep 17, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest changing link to NCTS as "[National Clinical Terminology Service](https://www.healthterminologies.gov.au) (NCTS)."

{
"system": "http://snomed.info/sct,
"version": "http://snomed.info/sct/32506021000036107",
"code": "322236009",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While still a valid code in AU extension, is the intention of this example to show a code valid in the AU extension only? If so, change code and display to MPUU concept 23628011000036109|paracetamol 500 mg tablet|.

records in Australian conditions. Many SNOMED CT-AU value sets have already been developed and published by the National Clinical Terminology Service [NCTS](https://www.healthterminologies.gov.au).
These nationally agreed and published value sets are maximal in nature to support reuse across multiple use cases and support the breadth of the ecosystem to enable interoperability.

#### SNOMED CT Version Options
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While options are listed, no guidance is provided as to why one should be selected over another. Consider inclusion of guidance - eg option two and three enable validation of AU codes.

Copy link
Collaborator

@JayMurdoch JayMurdoch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See inline comments. Thanks

Copy link
Collaborator

@dt-r dt-r left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR cannot proceed without an approved spec Jira. Please raise a change request.

@mjosborne1
Copy link
Collaborator Author

This PR cannot proceed without an approved spec Jira. Please raise a change request.

Thanks Danielle - Is the guidance to go into the Balloted version or current version? Just need to know for the JIRA ticket.

@dt-r
Copy link
Collaborator

dt-r commented Sep 17, 2024

This PR cannot proceed without an approved spec Jira. Please raise a change request.

Thanks Danielle - Is the guidance to go into the Balloted version or current version? Just need to know for the JIRA ticket.

I'm not sure what you are asking; new changes cannot go into an already released version?

@mjosborne1
Copy link
Collaborator Author

Logged Change Request for consideration by FHIR WG : JIRA-48307

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.

3 participants