Because of prior changes, change all references to Step 4 to Step 3. This includes sub-steps.

Needed to occur because of deleting Step 2

In Annex B which is informative.

Present Step 2 has been deleted

O

The resolution of this issue is correlated to issue # 41 because the issue and the resolution of both issues have dependencies.

Issue: The name of the Business Element in the example beginning on the bottom of page 52 was VitalSignObservationActionFocus. Based on the work of the FTF, this name is not appropriate and should not be used. The name is inappropriate because Vital Sign Observation term as the ContentConcept property (formerly the StatementConcept Property) should be ObservationActivity. The name is also not appropriate because the term for the DataElementConcept Property, formerly ActionFocus, should be ContextFocus based on advice of the SMEs in the FTF.

he resolution of this issue is correlated to issue # 42 because the issue and the resolution of both issues have dependencies.

Issue: The name of the Business Element in the example beginning on the bottom of page 52 was VitalSignObservationActionFocus. Based on the work of the FTF, this name is not appropriate and should not be used.

Proposed Resolution: The name is inappropriate because Vital Sign Observation term as the ContextConcept property (formerly the StatementConcept Property) should be ObservationActivity. The name is also not appropriate because the term for the DataElementConcept Property, formerly ActionFocus, should be ContextFocus based on advice of the SMEs in the FTF.

Presently the wording of "MDMI Business Elements are synonyms" is not correct.

having the word "are" in first sentence leading off this section could be misleading and is not proper English.

Related to Issues 41 and 42

Issue: Graph description is incorrect as the ContextConcept is not VitalSignObservation.

Proposed Resolution: Removed words vital sign.

The term "a semantic unit" is ambiguous and does not convey the concept appropriately.

The word "The" is missing before "KBS Team"

Issue: The term smallest semantic unit is undefined in the document and it is ambiguous.

Proposed Resolution: Replace the phase with the phase "business concept" which is used in the description of the term MDMI Business Element and is appropriate in this context.

the term SEER was not defined in Annex A.

The term MHDM is not defined and inaccurate.

Relationship is missing in MagicDraw diagram. It appears to have been the result of an editing error as is has shown up in all versions of 8.2 I see in document.

Issue: the present name of the association is repository.

Proposed Resolution: The name of the association should be changed to registry based on other proposed resolutions

the SemanticElement is used in the UML model

Not an issue .... original language acceptable

In the Annex B, based on the work in the FTF the term VitalSignObservationActionFocus is not valid.

Issue: the term Referent Index appeared in the document. It was deprecated in the 2.0 submission.

Proposed Resolution: Changed the term Referent Index to SEER.

During the FTF process, there was one change made to the name of a property in a class and there were one or two changes made to class names to remove possible ambiguities. In addition, as different modeling tools used to develop the diagrams throughout the 2.0 process, new diagrams were generated for Section 8. At some point during the review process, it was discovered that an important relationship was missing.