[Bug]: FHIR Hack Using Deprecated and/or Outdated Resources
Closed this issue · 4 comments
Which Hack?
027-FHIRPoweredHealthcare
Current Behavior
Hello! I'm on the FHIR team and found this resource through a bug report on our FHIR OSS repo. Love the project and I have some update suggestions to align this to our product offerings since we've had some updates.
We released Azure Health Data Services as our new, preferred FHIR offering a couple of months ago. Microsoft trainings around FHIR should all be using this new offering.
The Health Architectures site has now been deprecated. Any dependencies you need from there should be pulled into your repo and maintained. See this repo for an example.
Expected Behavior
- Exercises use Azure Health Data Services FHIR Service, not API for FHIR
- Exercises don't use Health Architectures
- FHIR Proxy should only be used under consideration.
Steps To Reproduce
No response
Environment
No response
Anything else?
Please let me know if you need any advisory help on this! 😄
Code of Conduct
- I agree to follow this project's Code of Conduct
@mikaelweave Thanks for submitting this issue! I will contact the authors to update it.
Since the FHIR ecosystem reference architectures from the Health Architectures site leveraged in the FHIR Powered Healthcare hack have been deprecated, its contents are currently being updated to align with hack contents in the azure-health-data-services-workshop repo.
The following are the proposed changes for WTH FHIR Powered Healthcare hack contents:
- Ch 1 - Change FHIR ingestion architecture to the new OSS FHIR Bulk Loader ingestion pipeline. Note: It will no longer requires AD Admin access.
- Challenge 2 & 3 - Change HL7 & C-CDA to FHIR conversion to use new $convert-data API operation in FHIR Service.
- Challenge 5 - Remove (no longer deploying FHIR Server Samples architecture in the deprecated Ch 1 infrastructure)
- Challenge 9 - Change to use new FHIR-to-Synapse analytics pipeline. It will auto export new FHIR data as Parquet file into a ‘fhir’ Blob container and auto populate external tables and views in Synapse SQL Serverless Pool for secondary use cases.
Additional changes proposed:
- Challenge 7 - Replace existing export & anonymize pipeline to use $export API operation in FHIR Service
- Challenge 8 - Replace with MedTech Services in Azure Health Data Services, and use IoT mapper tool to map sample messages.