-
Notifications
You must be signed in to change notification settings - Fork 6
-
Notifications
You must be signed in to change notification settings - Fork 6
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
PractitionerRole: Add PractitionerRole.specialty #23
Comments
@dt-r Can I please get some guidance on mapping SA data to FHIR? Proposed SA attribute --> AU Core PractitionerRole element in AU Core Test Data Also need to check what the system for the above coding is. Also need to check if new columns should be added for specialty1_coding3 to be populated with the closest match from Clinical Specialty value set: https://www.healthterminologies.gov.au/integration/R4/fhir/ValueSet/clinical-specialty-1 |
@StephThaoOng, please advise which terminology i.e. ANZSCO, LOINC, SNOMED, etc. is proposed here. I want at least one if not more SNOMED CT specialities where we can consider a practitioner to have a corresponding speciality from the preferred valueset for PractitionerRole.specialty. If that is not suitable then from wider SNOMED CT. Michael Osborne can perform that for you. This is the implementation advice in HL7 AU implementation guides. There may additionally be proposed that some of the Services Australia provided ANZSCO values for a provider populate one or more codings in PractitionerRole.specialty. If that is so, please confirm in the comments in that those values are not already used in PractitionerRole.code. |
@MichaeOsbourne Can you please action this favour today? @dt-r Thanks for the clarification. Please note that until the Smile CDR fix for multiple codings is released, loading the Sparked dev FHIR server with test data enriched with multiple codings is blocked. |
@MichaelOsbourne Additional request as discussed - can you please derive the PractitionerRole.specialty from the Service Australia (SA) provide data for the following PractitionerRoles:
The SA provided SPECIALTY/SPECIALISATION data will map to PractitionerRole.code. |
@dt-r The PractitionerRole.specialty codes from clinical-speciality-1 valueset are not really aligned with the ANZSCO codes provided in the SA data. So although they have a similar, but different description, the latter should not be derived explicitly from the ANZSCO code. |
I have added specialties from the clinical specialty ValueSet to the examples indicated in @StephThaoOng 's comment. |
Added ANZCO mapping to SNOMED CT clinical specialties - noting that 12 codes had no mapping. |
Yes, I understand. I am looking for specialty codes that would apply to the Pracitioners we've created. In terms of clarifying the request for 'correspond to Services Australia provided data' is about the persona as a whole and shouldn't conflict. It should be the kind of specialty you would expect for that persona. I do not expect that those codes are equivalent, I agree that these are not the same concept. |
I have added Specialty to majority of PractitionerRole resources derived from Services Australia Provider Specialty that Michael mapped to clinical-specility-1 ValueSet. |
PractitioneRole.specialty is not present in the PractitioneRole instances that correspond to Services Australia provided data. This should be added, it is must support in AU Core.
The text was updated successfully, but these errors were encountered: