Unattributed Code Systems

Copyright Fragment

This fragment is not visible to the reader

This publication includes IP covered under the following statements.

Copyright and Registered Trademark Uses

External References

Type Reference Content
web www.openhealthhub.com contact : Open Health Hub: https://www.openhealthhub.com , support@openhealthhub.com
web your-his.com https://your-his.com/Subscription-Notification/CarePlan
web your-his.com https://your-his.com/Subscription-Notification/QuestionnaireResponse
web www.postman.com Postman Collection
web support.openhealthhub.com Open Health Hub Support portal
web www.openhealthhub.com Get in touch
web www.openhealthhub.com IG © 2025+ Open Health Hub . Package ohh-fhir#0.1.0 based on FHIR 4.0.1 . Generated 2025-12-03
Links: Table of Contents | QA Report | Postman Collection
web www.postman.com Links: Table of Contents | QA Report | Postman Collection
web github.com JavaScript FHIR QuestionnaireResponse Client Example
web github.com For a complete example on how to decrypt the answers, refer to our FhirClient example respository where examples can be found for several popular programming languages.
web mathjs.org Formulas mostly follow mathjs syntax. There is exactly one exception to this, which is the variables. To clarify which QuestionnaireItem result is used in a formula, the variables used in the formulas will be replaced by the linkId, surrounded by $, of the QuestionnaireItem result that should replace the variable. This linkId may be specified by using the Export label field in the Designer and does not necessarily follow mathjs’s syntax.
web github.com Get familiar with our FHIR REST APIs and FHIR Client Example Repository . You can play with our sandbox with the listed credentials.
web hapifhir.io When implementing your own client we strongly advise using an available FHIR library (e.g. HAPI for Java or Firely for C#), and don't try to parse the responses yourself. This will prevent unexpected errors when changes are made in the structure of the responses (e.g. when we enrich our FHIR data with new fields or extensions).
web fire.ly When implementing your own client we strongly advise using an available FHIR library (e.g. HAPI for Java or Firely for C#), and don't try to parse the responses yourself. This will prevent unexpected errors when changes are made in the structure of the responses (e.g. when we enrich our FHIR data with new fields or extensions).
web www.postman.com Our Postman Collection offers a great start at discovering our FHIR REST APIs in a sandbox environment. It is pre-configured with the sandbox credentials (api-key, openid credentials), so you can start right away:
web openhealthhub.atlassian.net Request for an Open Health Hub API developer account.
web improvedesigner.openhealthhub.com Register your own Form Designer account or deliver your API key to one of your colleagues who already has an Improve Designer account.
web github.com Start building your own App project using this documentation and our example FHIR Client Example Repository .
web admin.openhealthhub.com Open Health Hub uses API keys and OpenID Connect to allow access to the FHIR API. After getting an account, you or one of your colleagues can get the API Key from the Open Health Hub Manager .
web www.openhealthhub.com Welcome to the Open Health Hub Implementation guide! You can use our FHIR API to access the Open Health Hub Open API endpoints based on HL7 FHIR , which can interact with the Open Health Hub and SMART on FHIR applications for questionnaires and information.
web www.openhealthhub.com This way you can integrate our solution for digital forms in your own platform, portal or application. This saves both healthcare professionals and patients a lot of time. You can also become an Open HealthHub partner and get access to our technical expertise, training program and more to support your integration.
web en.wikipedia.org Before going into detail with the exposed FHIR APIs it's important to note that all dates and timestamps mentioned in these APIs are in UTC . This means that any localization of these dates and timestamps will need to happen on the client side. For exact details on how to fill these, we recommend looking into the FHIR documentation

Internal Images

API_overview.png
API_overview.png
FHIR.png
FHIR.png
Hub-Fhir-Mapping-v2.png
Hub-Fhir-Mapping-v2.png
tree-filter.png
tree-filter.png