Stream: implementers
Topic: xsd schema from IG
Michele Korell (Apr 30 2019 at 05:59):
Hello, when we build custom implementation guide, it is possible to generate directly the resources xsd schemas? Like those we can found in the download section?
Grahame Grieve (Apr 30 2019 at 07:27):
the IG publisher generates schematrons for any profiles in the IG. It's up to the author whether those are linked in the narrative anywhere but they are always inluded in the package for the IG in \xml
Michele Korell (Apr 30 2019 at 08:35):
Ok, thanks a lot for the fast reply. I was looking to the wiki and as explained at FHIR IG Framework page I undeerstand that I can find the generated xsd here: 'src-generated/schemas/fhir-single.xsd'. My IG is a fork of the CH-Core so, maybe, I need to look with @Oliver Egger if it is a problem in my configuration.
Grahame Grieve (Apr 30 2019 at 08:47):
the IGs don't change the base schema. they are set of rules on top of the schema - hence, the schematron
Michele Korell (Apr 30 2019 at 09:13):
Ok, I think that I didn't understand well how IG work. Actually we defined some extensions for our purpose and we want to provide web interfaces on BizTalk that permit the distribution across our system of our FHIR definitions. Did you know if someone did something like that?
Grahame Grieve (Apr 30 2019 at 09:18):
defining extensions is a common thing to do. but that doesn't change the schema.
Grahame Grieve (Apr 30 2019 at 09:19):
I can't talk about the Biztalk part, or what it means 'permit the distribution across your system'
Michele Korell (Apr 30 2019 at 11:06):
In our ecosystem the ERP produce V2 files, and new patient information system core is based on fhir, so the idea was to profit of microsoft .NET fhir implementation to convert and get the data from our ERP
Grahame Grieve (Apr 30 2019 at 11:09):
so that much makes sense, but it doesn't explain where you would like the schema to get involved
Michele Korell (Apr 30 2019 at 11:26):
The schema is used to declare the interface inside BizTalk to map the V2 file. Actually we are moving our patient information system on FHIR but we still have more than 200 apps on ours hospitals and BizTalk is at the core of distributing ERP patient data to others apps. For some apps we had good discussion with the vendors and they start to build RESTful FHIR interfaces with our help. For other app we need to map the new fhir resources to V2 or proprietary formats.
Grahame Grieve (Apr 30 2019 at 11:27):
so you use the base fhir schemas. the IGs are a set of information about how to use the structures described by the schemas
Michele Korell (Apr 30 2019 at 11:28):
BizTalk can use the xsd as mapping interface definition so our idea was to generate a schema with our rules to limit the interface mapping. This can simplify the read of the map and avoid some implementation error because it represent our internal guide.
Michele Korell (Apr 30 2019 at 11:29):
In the case that a vendor provide directly the fhir interface, we don't use BizTalk because it make no sense with RESTful endpoint.
Michele Korell (Apr 30 2019 at 11:30):
And we can use websocket to provide real time informations
Grahame Grieve (Apr 30 2019 at 11:31):
generate a schema with our rules to limit the interface mapping
So the problem here is that some of the facilities that the profiles do - and they are things that happen a lot - are not things that schema can describe - bindings, slicing, constraints
Grahame Grieve (Apr 30 2019 at 11:32):
the IG publisher does generate some schema that tries to do what it can to represent the profiles but they are not much used
Michele Korell (Apr 30 2019 at 11:38):
Maybe I have to seen if we can integrate validators into BizTalk to use our rules
Last updated: Apr 12 2022 at 19:14 UTC
