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

Implement /convert endpoint for xml/json conversion #165

Open
rkorytkowski opened this issue Feb 22, 2024 · 2 comments
Open

Implement /convert endpoint for xml/json conversion #165

rkorytkowski opened this issue Feb 22, 2024 · 2 comments

Comments

@rkorytkowski
Copy link

rkorytkowski commented Feb 22, 2024

The endpoint should accept POST requests with content in xml or json format and call the convert feature of the validator to transform input to xml or json. It should accept headers:

For Output:

  1. Accept: application/json
  2. Accept: application/xml

For Input:

  1. Content-Type: application/json
  2. Content-Type: application/xml

The conversion endpoint could also be extended to support conversion from/to different FHIR versions with URL parameters fromVersion and toVersion.

I'd like to work on this feature once approved.

@rkorytkowski rkorytkowski changed the title Implement /conversion endpoint for xml/json conversion Implement /convert endpoint for xml/json conversion Mar 7, 2024
rkorytkowski added a commit to rkorytkowski/org.hl7.fhir.validator-wrapper that referenced this issue Mar 7, 2024
@rkorytkowski
Copy link
Author

Draft PR at #167

@lawley
Copy link

lawley commented Apr 2, 2024

https://www.hl7.org/fhir/resource-operation-convert.html provides a spec for this.
It should also handle fhirVersion=... in the Accept & Content-Type headers

rkorytkowski added a commit to rkorytkowski/org.hl7.fhir.validator-wrapper that referenced this issue Apr 29, 2024
rkorytkowski added a commit to rkorytkowski/org.hl7.fhir.validator-wrapper that referenced this issue Apr 29, 2024
rkorytkowski added a commit to rkorytkowski/org.hl7.fhir.validator-wrapper that referenced this issue Apr 29, 2024
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

2 participants