Redundant DisplayPrecision extension
Redundant DisplayPrecision extension
Redundant DisplayedBy extension
Clarify scope of clause 6
Clarify scope of clause 6
Proposal for update Maximum delay to real time. For a measurement or calculation, the maximum delay to real time is the estimated or known maximum difference between the point in time when a physical variable value has been present and when the value has been computed and is ready for communication excluding communication delay. For a setting, the maximum delay to real time is the estimated or known maximum difference between the point in time when a setting has been confirmed to be applicable and...
R0014 to R0019: Remove "e.g." as it is confusing
R0014 to R0018: Remove "e.g." as it is confusing
TR0128 should cover @Samples as well
Proving uniqueness for an ID that potentially stems from an external system or is manually entered by a user is not really possible. The requirement was rephrased: If a primary source of patient identification is available, an SDC PARTICIPANT SHALL provide the primary patient identifier by including a pm:Identification element in pm:PatientContextState with pm:Identification/pm:Type/@Code = MDC_ATTR_PT_ID. Do we still need the restriction in P11073-10700 Comments: #170?
Unique PCI/Number fourced without same pm:Type
Unique PCI/Number fourced without same pm:Type
Forbidding ActiveDeterminationPeriod breaks operating mode pattern
At the moment the requirements Stefan suggested seem to be aimed at 10701. Do we really need them in 10700?
The order is important, if a node contains child nodes which are identical from a Descriptor perspective (type, unit e.g for metrics). An SDC Consumer needs some way of dealing with that situation, especially for mapping to something displayed/given to a user. Therefore, the order within children must be absolute and static. Without that, SDC Consumers cannot deal with SDC Provides that do not make elements uniquely identifiable by their Descriptor element values. As long as in SDC it is allowed...
R1133 - R1139: Applicable international standards?
R1110 & R1113: Separation of technical & usability reqs?
R1048 and R1053 were numbers for the headings of chapters the comment applies to all requirements in the sections. R1048: Sharing Context Information R1053: Sharing Metric Information
R1048 & R1053: Difference between context- and metric information
R0032& R1022: Where to make non-conformities available?
Home