You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 18, 2026. It is now read-only.
So I'm working on a CCDA to FHIR converter, which recursively parses CCDA resources and generates a nested tree of FHIR resources. Which was fine in a previous implementation, because it was untyped. But now that I'm using generated TypeScript bindings, they mandate that nested resources should be Reference-s instead:
Meaning I should somehow store resources somewhere instead of recursively including them in the tree. Which most likely means global state, and global state is not nice. Is there any possibility that you may allow raw resources in addition to Reference-s in the fields where nested resources are included?
So I'm working on a CCDA to FHIR converter, which recursively parses CCDA resources and generates a nested tree of FHIR resources. Which was fine in a previous implementation, because it was untyped. But now that I'm using generated TypeScript bindings, they mandate that nested resources should be
Reference-s instead:Meaning I should somehow store resources somewhere instead of recursively including them in the tree. Which most likely means global state, and global state is not nice. Is there any possibility that you may allow raw resources in addition to
Reference-s in the fields where nested resources are included?