Your browser does not appear to support JavaScript. You may want to try one of the following:
You may want to try one of the following:
If the above does not work, try reloading the page yourself. Note that you will lose any unsaved changes:
shift
control
Show details
Hide details
This form has to be reloaded. This most likely happened because your session has expired, which might take to the login page. (If you think that you shouldn't see this message and that the problem persists, please contact support.)
effectiveTime is mandatory here. In many other specs it is required R only. NullFlavor not allowed?
Change from M to R, discussion needed
-
add the constarins for classCode="CLUSTER" and moodCode="EVN"
the current constrain request to valorize the organizer.code@dispalyName as "Vital Signs".
this is not what is expected in epSOS where the displayName is not necessarly in english
to be discussed because the IHE PCC template says <code code='46680005' displayName='Vital signs' codeSystem='2.16.840.1.113883.6.96' codeSystemName='SNOMED CT'/>The <code> element shall be recorded as shown above to indicate that this organizer captures information about patient vital signs.
specs just say The effective time element shall be present to indicate when the measurement was taken.
in the DECOR template an IVL_TS datatype is used : to be check if this is the rigth choice
the current template refer to the IHE PCC Vital Signs observation template
assign an epSOS template OID and use this for the inclusion
- At this moment the datatype of the effectiveTime of the Organizer is IVL_TS. Since we want this effectiveTime to be the same as the effectiveTime of the Observations and the Observations have datatype TS, we want to align the datatype to TS. This was confirmed by the semantic group tcon at 26/3/2018.The reasoning behind this change is the fact that an interval doesn't have a clinical meaning for a vital signs observation and a TS is granular enough.
- Change the datatype of the effectiveTime from IVL_TS to TS