Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FHIR integration is more specific than it need to be #17

Open
flyaruu opened this issue Apr 9, 2021 · 1 comment
Open

FHIR integration is more specific than it need to be #17

flyaruu opened this issue Apr 9, 2021 · 1 comment

Comments

@flyaruu
Copy link
Contributor

flyaruu commented Apr 9, 2021

At the moment, the FHIR integration pattern isn't constrained to FHIR, it basically works for any 'foreign' source.
It offers two patterns:

  • Strongly typed. The integration supplies a type, and a parsing function byte[] -> T. Every source location needs to supply a T->Imessage function.
  • Directly. A source simply supplies a byte[] -> IMessage function
@flyaruu
Copy link
Contributor Author

flyaruu commented Apr 10, 2021

Implemented genericSource, which takes a body parser
TODO: Also add optional key parser
TODO: Implement FHIR implementation on top of this implementation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant