Skip to end of metadata
Go to start of metadata

Virtual Patient Specifications and Description Recommendations:

1.       I propose making the inclusion of the player optional and changing the SCORM requirement to include a Resource Content Package and Content Aggregation Model (ie no player/player in pkg). Implications are: player in package optional, organization in manifest optional, html launch file optional, metadata at the package level. This would allow for the use case of including the player and enabling VPs to be played in SCORM LMSs, but it also enables the use case of sending data from one vp system to another or leveraging a server-based player.

2.       Put healthcaremetadata.xsd and healthcarevocabularies.xsd at the root of the content package. Because of the way SCORM validates metadata files, any metadata files using the healthcare extensions would need to have healthcaremetadata at the root of the package.

3.       SCORM is now up to 4th edition. I recommend updating the version used by MVP from 3rd edition to 4th edition. The only change would be in the version indicated in the metadata of the manifest.

4.       The activitymodel.xsd Probability element has values that are upper case - On and Off. This is inconsistent with other data types. I recommend changing to lowercase. Same with NavigateGlobal and CounterRuleEnabled.

5.       The Operand element in activitymodel.xsd could be a regular expression pointing to an activity node or vpd element. If anyone would like to author a regular expression, your help would be much appreciated.

Virtual Patient Player Specification

1.       I propose making the inclusion of the player optional and changing the SCORM requirement to include a Resource Content Package and Content Aggregation Model (ie no player/player in pkg). Implications are: player in package optional, organization in manifest optional, html launch file optional, metadata at the package level. This would allow for the use case of including the player and enabling VPs to be played in SCORM LMSs, but it also enables the use case of sending data from one vp system to another or leveraging a server-based player.

2.       SCORM is now up to 4th edition. I recommend updating the version used by MVP from 3rd edition to 4th edition. The only change would be in the version indicated in the metadata of the manifest.

3.       I don't think the Medication element is one that should get recorded by the player because the user does not interact directly with the Medication element, the user interacts with the Intervention element, which may contain a Medication. (p 34)

  • No labels