Activity for Stefan Schlichting
-
Stefan Schlichting modified ticket #19
R0010/R0011 wording
-
ACCEPTED.
-
Proposal: Move second sentence to note. Change sentence to "Acceptable credentials are those credentials that can be processed by the RECEIVER."
-
See https://en.wikipedia.org/wiki/Substring#Prefix Difference between "prefix" and "proper prefix"
-
See https://en.wikipedia.org/wiki/Substring#Prefix
-
It should be considered to use http://docs.oasis-open.org/ws-dd/ns/discovery/2009/01/rfc3986, esp. for discovery of locations where you want to have not one specific bed, but a ward. strcmp0 will not work. As far as I know, prefix always includes S1==S2.
-
Please provide more specific examples.
-
I second David. This would be a useful extension. Maybe model it similar to SystemErrorReport/ReportPart/ErrorCode as a CodedValue so that you can use public and private codes for the error.
-
Add an operation to clear a program
-
Can you explain the problem with the references?
-
Can you please provide the arguments for both pm:AbstractMetricValue and @Value. The text should always be read as "there is no new determined value available". For measurements or calculation there can be a situations where there may be no pm:AbstractMetricValue esp. after a new start.
-
Can you please provide the arguments for both pm:AbstractMetricValue and pm:AbstractMetricValue/@Value
-
Please check how this ticket relates to the DerivationMethod attribute of metrics.
-
The example in the last note is maybe not appropiate and does not need to lead to a disassociation state of the context. Probably it would be better to just remove the validator for the associated context if the confirmation by the validator for the association can no longer be guarenteed.
-
Please clarify the meaning of "unintentionally leaving" which I assume would be the opposite to "intentional leaving" defined as: ... the SDC SERVICE PROVIDER itself or its USER intends the context association to end because the actual context of the physical or logical component is changing . Is this related to correction of a misconfigured context?
-
Regarding If an SDC SERVICE PROVIDER is intentionally disassociated from a context state, the SDC SERVICE PROVIDER SHALL change the corresponding @ContextAssociation to "Dis" and identify a validator for this new association state. This would need a ticket for BICEPS as currently the validator has the following definition: OPTIONAL list of actors (e.g., persons, devices or any identifiable systems) which have confirmed that a binding of a context state to an MDS is correct. The description should...
-
The content of the proposed new requirement ( incl. the figure) An SDC SERVICE PROVIDER SHALL change its @ContextAssociation according to the transitions in figure ContextAssociation state diagram. Should be a ticket to include a note to BICEPS from my persepctive. I don't see any reason to make this a requirement.
-
Add time zone note/req for ISO 8601
-
Added in [521a58]
-
Add codes for next/previous value operations
-
Add Operations to activate/deactive all alarm associated with a CTE
-
Added in [389e03]
-
Add operation to allow adjustment of limits for all alert conditions
-
Added MDC_ACT_AUTO_ADJUST_ALL_LIMITS in [b19a1c]
-
Add MDC_PDMO actions
-
MDC_ACT_ADMIT_PT is not usable for updating an existing admitted patient
-
Added in [4a8b09]
-
Add MDC_PDMO actions
-
Added in [0b73c6]
-
The ticket should be closed. Section 3.1 referes to the IEEE Standards Dictionary Online for those terms not defined in this document. In the IEEE Standards Dictionary Online Medical Device System is defined.
-
From my perspective there should be a clear distinction between the relevance/rank, the unqiue identification, the user perceived identification and the display of elements on a UI. Rank: The rank is an optional ATTRIBUTE allowing finer distinction of ALERT CONDITION priorities where a relationship between ranks exists. Clinical Relevance: Clinical Relevance is somewhat similar to similar, but for other elements of the containment tree. Clinical Releance is used in lists (e.g. of Channels, Metrics)...
-
Move definition to P11073-10701
-
Access level is really a category and not a hierarchy, but the categories may be subsets of each other, e.g. User and Clinical Super User. Your example would be encoded with AccessLevel=CSUsr which would indicate that the Service Consumer should prevent access from a Service Technician. If required: it is always possible to add multiple operations with different accesslevel or AccessLevel=Oth with some extension to model complex access level indications from the Service Provider perspective. Proposal:...
-
Can you resolve the reference BPKP1107? I dont see it in the pre-ballot draft.
-
The reference should be to the PKP (set of requirements) called out in the 20701: SDC Service Consumer and SDC Service Provider. This already is a reference to the mandatory requirements (see Table 3 - 20701).
-
Remove MDC_ACT_RETRIEVE_CALIB_INFO
-
Add MDC_ACT_SET_ALL_BODYSITES
-
Add MDC_ACT_SET_BODYSITE
-
Clarify that MDC_ACT_ALERT_SIGNAL_DELEGATION_TAKE_OVER takes over delegation for one CTE
-
Add MDC_ACT_SET_BODYSITE
-
Remove OID assignment for Base PKP
-
Add generalized requirements from sections 6.2.3 - 6.2.5
-
Remove clause 6.2.4 Sharing Alarm Information
-
Remove 6.2.5 Performing External Control
-
Remove clause 6.2.4 Sharing Alarm Information
-
Remove 6.2.3 Sharing Metric Information
-
Alternativly, change the documentation to: The rank is an optional 0-based index ATTRIBUTE allowing finer distinction of ALERT CONDITION priorities. The smaller the absolute rank index, the higher is the priority of the ALERT CONDITION. NOTE - It is recommended to not use negative rank index in order to avoid confusion.
-
Proposal: Change to same wording as for the slot. Indicate that the rank may negative and that the highest rank is the highest priority.
-
Change Namespace "tns:" to "ext:" for the elements from Extension Model
-
CHANGE throughout the document
-
Spelling errors in B.219
-
Change accordingly
-
R0133 What with system contexts in different MDS instances
-
Change to something similar like: There shall be only one associated patient context state for each patient context descriptor. There shall be only one associated location context state for each location context descriptor.
-
Clarify ACK for visual alert signals
-
CHANGE ...is currently not generated... to is currently either not generated or generated in a limited way of the same manifestation ... Add note: For visual signals it may not stop complete, but just reduces the visual impression, e.g. stop flashing.
-
Add RefractoryTime to Operations
-
9.1 Wrong reference
-
B.103 AlertSignalDescriptor/@ConditionSignaled
-
CHANGE The ALERT CONDITION signaled SHALL be in the same ALERT SYSTEM or in an ALERT SYSTEM that is underneath the ALERT SYSTEM of this ALERT SIGNAL in the CONTAINMENT TREE. ADD similar sentence to AlertConditionDescriptor/Source => e.g. not another VMD or the MDS AlertSignalDescriptor/@ConditionSignaled => e.g. not another VMD or the MDS ScoState/@InvocationRequested ScoState/@InvocationRequired ScoState/OperationGroup/@Operations AbstractOperationDescriptor/@OperationTarget Not needed as already...
-
Change SHOULD to MAY in R0099
-
R0025 should contain AbstractMetricState\ActivationState
-
Remove "e.g." in R0014-R0019
-
Improve Figure D.14
-
Improve Figure D.14
-
Proposed removal of D.6 Alert signal generation Maybe include after fixing Table 9 to depict the content of Table 9.
-
PresentPhysiologicalAlarmConditions and PresentTechnicalAlarmConditions
-
Add an explanantion to "5.3.13 AlertSystem" that the fields contain the present ALARM CONDITIONS in order to allow a consumer to determine if an update has been missed.
-
Extension of B.46 AbstractMetricDescriptor/Relation/@Kind
-
Won't fix use ECE as @Kind and define a pm:Relation/pm:Code to classify the target-actual effect pattern
-
pm:AbstractComponentState does not exist, however being referenced
-
ACCEPTED. Change "pm:AbstractComponentState" to "pm:AbstractDeviceComponentState" throughout the document.
-
Order of multiple elements
-
Add a note R0034: The change of the order of ELEMENTs with a multiplicity of more than 1 is considered a change of the content of the ELEMENT.
-
Add information to xc spec that a change in the order of the allowed values results in either a descriptor version change or a state version change depending on where the allowed values are used
-
Lifetimeperiod should start would determinationtime
-
Accepted. Change Figure 8 to let the LifeTimePeriod start from DeterminationTime. maybe change to StopTime instead of DeterminationTime.
-
Define the element separation of a "list"
-
Add a Note to Table 2 to column Description in Row: Types Note: "NOTE - 'List of' indicates that the type is using the mechanisms of xsd:list
-
Model RelationKind as its own type
-
Would need to be included in a revision of the schema. Hence, we leave the ticket open.
-
B.231 Tweak LimitAlertConditionDescriptor documentation
-
Change Documentation to: LimitAlertConditionDescriptor is a specialization of a ALERT CONDITION where the ALERT CONDITION is present if at least one limit for a referenced source has been violated.
-
C.7 Documentation is ambigious and formally incorrect
-
Proposal: Change C.7 documentation to the effect: "...The HANDLE reference SHALL be omitted if an pm:MdsDescriptor is inserted, updated or deleted." Add a NOTE: For update and deletes of descriptors that are not pm:MDSDescriptors the HANDLE reference can be omitted.
-
Hi, the ticket has been accepted for the amendment. All the best Stefan
-
Allow for type ref in Get services
-
B.76 AbstractOperationState/@OperatingMode
-
Based on discussion today. Improve documentation for NA and Dis
-
Figure 13 (Page 60)
-
Based on discussion today: Proposal: Add "o -> Started"
-
D.5 Remote control - add waiting report to diagram
-
Based on discussion today Change Figure D.13 accordingly.
-
Add further explanations to B.446 QualityIndicator
-
Based on dicussion today: Add a note to QualityIndicator to explain how a meaningful Qi behaves.
-
C.91 SetAlertState/ProposedAlertState has cardinality of 1
-
Based on dicussion today: Either add extension for addtional ProposedAlertStates or change cardinality in the schema.
-
Battery objects on VMDs
-
Proposal: Add 0...n Battery objects wrapped inside an Element inside of the ext:Extension of the VMD element. Note: Could be combined with other meta-data elements from MDS.
-
B.202 DistributionSampleArrayMetricDescriptor - misspelling
1 >
