Open dennisverspuij opened 4 years ago
The xsd's were chosen as they define the spec. You need to have prior knowledge of the spec in order to parse profiles.
Enabling parsing from an arbitrary profile is definitely possible, but not trivial. It is something I can look at, but I am not planning on dedicating significant time to this project in the near term.
If you wish to work on a PR or provide sponsorship, either would provide additional motivation for this to take priority over other projects.
Hi, I'm also interested in for French implementation. https://simplifier.net/frenchprofiledfhirar
Hi everyone. Can I use this library as a fhir server implementation after generating the classes based on the artifacts generated via SUSHI? Is there anyone with similar experience implementing this? What are the differences between using this library and HAPI FHIR? What are the differences between validations of value-set codes and other constraints of this library and full fledged fhir server? Thanks
Hi, I am looking for a PHP FHIR client model code generation library that supports profiles other than core STU3/R4. This library looks great - and about the only one for PHP - but unfortunately generates code based on the xsd's instead of xml/json structure definitions, like the libraries for other languages do. I was wondering why it was chosen to do so, and whether or not is is possible or planned to support structure definitions instead? Or do you know of other ways to e.g. generate xsd's based on custom profiles? In particular I'd like to implement model classes supporting the dutch HL7/MedMij standards. Thanks!