Confusing conditions in `parse_reply` method about fhir_client HOT 2 OPEN

The issue is that the FHIR:: module contains R4 resources only, and the FHIR::STU3:: module contains STU3 resources only, and the FHIR::DSTU2:: module contains DSTU2 resources only.

The client can parse different FHIR versions, but it does not monkey-patch any of the FHIR modules.

So, when you explicitly call FHIR::CommunicationRequest... you are explicitly saying "use R4 CommunicationRequest."

Apologies if this was not obvious or a point of confusion. We hope to improve the documentation and examples for this gem in the future. This should be a topic we cover.

from fhir_client.

Thanks @jawalonoski for the quick reply. The problem is that the behaviour is not the same for each client version. If we look more closely to the parse_reply method:

• case (i) if the client version is dstu2 I would go through FHIR::DSTU2::Xml.from_xml anyway
• case (ii) if the client version is r4 I would go through FHIR::Xml.from_xml , except if I explicitly call FHIR::DSTU2::...Read, in which case I would go through FHIR::DSTU2::Xml.from_xml
• case (iii) if the client version is stu3 it depends only on the module I call the read method on:
  • FHIR::DSTU2::...Read -> FHIR::DSTU2::Xml.from_xml
  • FHIR::...Read -> FHIR::Xml.from_xml
  • FHIR::STU3::...Read -> FHIR::STU3::Xml.from_xml

In other words:

• case (i) The client version takes precedence over the module called
• case (ii) No clear priority between the client version and the module called
• case (iii) The module takes precedence over the client version

from fhir_client.