| Your name |
Organization |
Comment |
Related to elements |
Staff recommendations |
Status |
| Valerie Smothers |
MedBiquitous |
Virtual Patient developers should put specific comments on the schema in this column. |
Enter the XML elements to which this comment relates in this column. |
Leave this blank for recommentations on the comment. |
Schema updated, updates pending, changes to spec only, or no changes made. |
| Grace Huang |
Harvard Medical School |
I'm just making uninformed comments based on what I see in the XML schema: |
|
|
|
| Grace Huang |
Harvard Medical School |
How much should the \"voice\" of virtual preceptors be reflected in the schema? For example\, for any given interview question\, a patient response might also be associated with a preceptor text response as to why that question is relevant or not. |
related to InterviewitemType (line 143)\, ExamType (line 171)\, etc. |
This type of feedback should be reflected in the activity model.
|
no changes made
|
| Grace Huang |
Harvard Medical School |
Picky comment: \"Description\" is misspelled. |
"line 89 under \"ChiefComplaintType\ |
Corrected! good catch. |
Schema updated
|
| Marc Triola |
NYUSM |
We would like to see more functionality added to interview questions such as metadata about the questions (i.e. open ended\, screening question). This would support rich feedback about the interview. |
|
Can you tell us more about this, Marc?
|
|
| Marc Triola |
NYUSM |
Need some way to identify the definitive or final diagnosis for a case |
DifferentialDiagnosis |
Author diagnosis has been added to the schema as has liklihood for differential diagnosis.
|
Schema updated
|
| Yanko Michea |
UCHC |
I get a validation error (using XMLSpy): 'string' must refer to an existing simple or complex type... cannot resolve declaration or definition 'string'. http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/#src-resolve |
it first appears on line 222; |
Corrected. Thanks. |
Schema updated
|
| Yanko Michea |
UCHC |
Patient Demographics Race vs Ethnic Group ... is there any plan to adopt some external referent such as HL7 codes? |
|
In general we've thought HL7 too complex.
|
No changes made
|
| Yanko Michea |
UCHC |
How would you recommend to represent helthcare events (followup visits\, surgery\, etc) within the context of the Section? |
Sections |
I think this gets into the activity model.
|
No changes made
|
| Yanko Michea |
UCHC |
Following the idea of healthcare events\, there is the concept of Actors for instance.... should we describe who is involved in a particular event (nurse\, physician\, therapist...) |
Sections |
I think this would be part of the global state model or activity model.
|
No changes made
|
Nabil Zary
|
KI |
Picky comment: rename \"InterviewitemType\" to \"InterviewItemType\" for syntax consistency
|
line 132
|
Good catch!
|
Schema updated
|
Nabil Zary
|
KI |
Suggests the introduction of superCategoryId attribute to support subcategories. We propose a very flexible solution that is not web-sp specific.
<xsd:complexType name="CategoryType">
<xsd:simpleContent>
<xsd:extension base="NonNullString">
<xsd:attribute name="source" type="xsd:string"/>
<xsd:attribute name="sourceid" type="xsd:string"/>
<xsd:attribute name="superCategoryId" type="xsd:string"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
|
CategoryType
|
Based on our call this morning, I think you would use the Activity node sections in the activity model to represent the hierarchy of subsections.
|
No changes made
|
Nabil Zary
|
KI |
Suggests the introduction of VPDMediaType to provide support for media VPD. In some of our cases, media IS the data.
<xsd:complexType name="VPDMediaType">
<xsd:sequence>
<xsd:element name="MediaId" type="xsd:string" minOccurs="1" maxOccurs="1"/>
<xsd:element name="Location" type="xsd:string" minOccurs="1" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
|
New MediaType
|
Sounds fine. For consistency with our naming conventions, the element will be Media and the type will be MediaType.
|
Schema updated
|
Nabil Zary
|
KI |
Suggests a modification to provide support for VPDMediaType.
<xsd:complexType name="InterviewitemType">
<xsd:sequence>
<xsd:element name="Question" type="HumanLanguageString" maxOccurs="unbounded"/>
<xsd:element name="Response" type="HumanLanguageString" maxOccurs="unbounded"/>
<xsd:element name="Media" type="VPDMediaType" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:string"/>
</xsd:complexType>
|
InterviewitemType |
Sounds fine.
Should response be optional? |
Schema updated
|
Nabil Zary
|
KI |
Suggests a modification to provide support for VPDMediaType.
<xsd:complexType name="ExamType">
<xsd:sequence>
<xsd:element name="ExamName" type="HumanLanguageString" maxOccurs="unbounded"/>
<xsd:element name="LocationOnBody" type="LocationOnBodyType"/>
<xsd:element name="Action" type="NonNullString"/>
<xsd:element name="Finding" type="HumanLanguageString" maxOccurs="unbounded"/>
<xsd:element name="Media" type="VPDMediaType" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:string"/>
</xsd:complexType>
|
ExamType |
Sounds fine.
Should finding be optional? |
Schema updated.
|
| Nabil Zary |
KI |
Suggests a modification to provide support for VPDMediaType.
<xsd:complexType name="TestType">
<xsd:sequence>
<xsd:element name="TestName" type="HumanLanguageString" maxOccurs="unbounded"/>
<xsd:element name="Unit" type="NonNullString"/>
<xsd:element name="Result" type="NonNullString"/>
<xsd:element name="Normal" type="NonNullString"/>
<xsd:element name="Media" type="VPDMediaType" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:string"/>
</xsd:complexType>
</root>
|
TestType |
Sounds fine.
Should result be optional? |
Schema updated
|
