GSoC 2015: Consuming FHIR Resources Midterm Presentation

OpenMRS wiki - GitHub - FHIR Specification -

FHIR Team: @sashrika @surangak @harsha89 @vaibhavhp

1 Like

Hi @sashrika,

Great work (of course) :smile:

My first comment: for error management - are the error messages that are shown to us returned in the form of operation outcome resources? I think we need to return operation outcome responses with the error data if anything were to fail. For example, If you can’t complete a CREATE because an identifier type is missing etc., then instead of just throwing it, you should return an operation outcome that contains an error message - see the exception handling that happens here:


Good work indeed!. Look forward to see the conditional updates works and simple audit mechanism works along with this.

@Suranga for now we throw a UnprocessableEntityException. see

According to the link you posted, I think that scenario is ok. “e.g. the “validate” operation requires a response of HTTP 422 Unprocessable Entity if the validation fails”. But yes, we have to understand which errors we should throw and which error we should show as operation outcome.

We will discuss this.

@harsha89 thank you :smile: , I will focus on error management and conditional updates first.