OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: HAVE Issues


My team has found some more issues in the HAVE standard:

1.       Issue with non-typing of Boolean in have:Pediatrics (pg 40 of the documentation)

2.        The structure as defined in the schema (documentation is not clear) obfuscates the 1:1 mapping between capacity and bed/subcat types (pages 24-29)

3.       Example #1 on page 29 does not validate for multiple reasons:

a.       Lead/Trailing Spaces before element values (also a problem in example 2)

b.      Available is not a valid choice (also a problem in example 2)

c.       You can’t have a bedtype followed by a capacity followed by a subcategorybedtype – this shouldn’t be (see below)

4.       Constraints 2 & 5 for subcatbedtype are contradictory.  How can the parent bed type be both NotAvailable and Available? (page 26)

5.       TriageCodeValue and TriageCountQuality are listed as may use multiple but that is only for the TriageCode parent (page 20-21)

 

The example shows what we should have done, it just is wrong in the schema:

Example:

<BedCapacity>

<BedType>AdultICU</BedType>

<Capacity>

  <CapacityStatus>Vacant/Available</CapacityStatus>

</Capacity>

<SubCategoryBedType>Surgery</SubCategoryBedType>

<Capacity>

  <CapacityStatus>Vacant/Available</CapacityStatus>

  <AvailableCount>40</AvailableCount>

</Capacity>

<SubCategoryBedType>General</SubCategoryBedType>

<Capacity>

  <CapacityStatus>Vacant/Available</CapacityStatus>

  <AvailableCount>20</AvailableCount>

</Capacity>

</BedCapacity>

 

This example shows a clear 1:1 mapping for each bedtype or subcatbedtype and a capacity status.  Makes sense…Problem is that isn’t how it’s structured in the schema…

<BedCapacity>

            <BedType>AdultICU</BedType>

            <BedType>AdultICU</BedType>

            <BedType>AdultICU</BedType>

            <SubCategoryBedType>text</SubCategoryBedType>

            <SubCategoryBedType>text</SubCategoryBedType>

            <SubCategoryBedType>text</SubCategoryBedType>

            <Capacity>

                        <CapacityStatus>Vacant/Available</CapacityStatus>

                        <AvailableCount>0</AvailableCount>

                        <BaselineCount>0</BaselineCount>

                        <AdditionalCapacityCount24Hr>0</AdditionalCapacityCount24Hr>

                        <AdditionalCapacityCount72Hr>0</AdditionalCapacityCount72Hr>

            </Capacity>

            <Capacity>

                        <CapacityStatus>Vacant/Available</CapacityStatus>

                        <AvailableCount>0</AvailableCount>

                        <BaselineCount>0</BaselineCount>

                        <AdditionalCapacityCount24Hr>0</AdditionalCapacityCount24Hr>

                        <AdditionalCapacityCount72Hr>0</AdditionalCapacityCount72Hr>

            </Capacity>

            <Capacity>

                        <CapacityStatus>Vacant/Available</CapacityStatus>

                        <AvailableCount>0</AvailableCount>

                        <BaselineCount>0</BaselineCount>

                        <AdditionalCapacityCount24Hr>0</AdditionalCapacityCount24Hr>

                        <AdditionalCapacityCount72Hr>0</AdditionalCapacityCount72Hr>

            </Capacity>

            <CommentText>String</CommentText>

            <CommentText>String</CommentText>

            <CommentText>String</CommentText>

</BedCapacity>

 

This gives no clear 1:1 mapping.

We can discuss this in the TC call today.

Don McGarry

Office: 315-838-2669

Cell: 315-383-1197

dmcgarry@mitre.org

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]