Hey Muhammad, I hope you are well. 

I hope you don't mind if I provide some feedback.

First, the serious feedback - It is important that reference ranges are linked to the unit of measure provided in the result. This is because a change to the units used in the source could then mean that you provide the incorrect reference range/flag. This could then in turn lead to someone misinterpreting the results in the destination system and impact the treatment of a patient.

Now to the less serious feedback - Some systems have extended the high/low flag so as to differentiate between something being slightly high, and something being extremely high. In the versions I have seen, this has been done as:

LLL - Extremely Low
LL - Severely Low
L - Moderately Low
N - Normal
H - Moderately High
HH - Severely High
HHH - Extremely High

It could make for an interesting expansion on what you have done so far.

Hey Rochdi.

The issue here is that you can't use the Arrow within the ON Clause and the alternative here would be to use ANSI Join syntax.

If it helps, the documentation (under Join Definitions) states that -> performs a left outer join? There's also a section further down for ON Clause if that is useful in any way.

Hey Sean.

I had considered using the values from Memory and Startup, but was unsure of the exact class to call it, so thank you.

I think my approach will be to use a util function which then returns a value based on SystemMode (I say based on, as I would want the same behavior even when failed over in a mirrored setting)