Generated using schema builder version 3.2.4. Stylesheets:
StaticMifToXsd.xsl version 2.0
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven.
All rights reserved. Redistribution and use in source and binary forms, with
or without modification, are permitted provided that the following
conditions are met: 1. Redistributions of source code must retain the above
copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software
must display the following acknowledgement: This product includes
software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE
REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by
$Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
$Id: Vocabulary.xml,v 1.1 2005/08/25 11:33:46 mcraig Exp $ RoseTree XML
to Schema: $Id: VocabXMLtoXSD.xsl,v 1.6 2005/05/24 00:14:18 lmckenzi Exp
$
The following types are used internally in data types
The following types are used for structural RIM
attributes
Generated by $Id: v3dt-schema.xsl,v 1.5 2005/05/24 05:44:38
lmckenzi Exp $
Generated using schema builder version 3.2.4. Stylesheets:
StaticMifToXsd.xsl version 2.0
Source Information
Rendered by: RoseTree 3.0.8
Rendered on: 7/30/2005 T24:53:20
This model was rendered into XML using software provided to HL7 by Beeler Consulting LLC.
Transform: $RCSfile: infrastructureRoot.xsd,v $ $Revision: 1.3 $ $Date: 2005/08/24 19:54:59 $
Generated using schema builder version: 2.0
RIM MIF Infrastructure Root to Schema Transform: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Static MIF to Schema Transform: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Package Id Conversion: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by $Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by $Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
Generated by $Id: v3dt-schema.xsl,v 1.5 2005/05/24 05:44:38 lmckenzi Exp $
$Id: Vocabulary.xml,v 1.1 2005/08/25 11:33:46 mcraig Exp $ RoseTree XML to Schema: $Id: VocabXMLtoXSD.xsl,v 1.6 2005/05/24 00:14:18 lmckenzi Exp $
The following types are used internally in data types
The following types are used for structural RIM attributes
Generated using schema builder version 3.2.4. Stylesheets:
StaticMifToXsd.xsl version 2.0
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven.
All rights reserved. Redistribution and use in source and binary forms, with
or without modification, are permitted provided that the following
conditions are met: 1. Redistributions of source code must retain the above
copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software
must display the following acknowledgement: This product includes
software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE
REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by
$Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
$Id: Vocabulary.xml,v 1.1 2005/08/25 11:33:46 mcraig Exp $ RoseTree XML
to Schema: $Id: VocabXMLtoXSD.xsl,v 1.6 2005/05/24 00:14:18 lmckenzi Exp
$
The following types are used internally in data types
The following types are used for structural RIM
attributes
Generated by $Id: v3dt-schema.xsl,v 1.5 2005/05/24 05:44:38
lmckenzi Exp $
Generated using schema builder version 3.2.4. Stylesheets:
StaticMifToXsd.xsl version 2.0
Source Information
Rendered by: RoseTree 3.0.8
Rendered on: 7/30/2005 T24:53:20
This model was rendered into XML using software provided to HL7 by Beeler Consulting LLC.
Transform: $RCSfile: infrastructureRoot.xsd,v $ $Revision: 1.3 $ $Date: 2005/08/24 19:54:59 $
Generated using schema builder version: 2.0
RIM MIF Infrastructure Root to Schema Transform: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Static MIF to Schema Transform: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Package Id Conversion: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by $Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by $Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
Generated by $Id: v3dt-schema.xsl,v 1.5 2005/05/24 05:44:38 lmckenzi Exp $
$Id: Vocabulary.xml,v 1.1 2005/08/25 11:33:46 mcraig Exp $ RoseTree XML to Schema: $Id: VocabXMLtoXSD.xsl,v 1.6 2005/05/24 00:14:18 lmckenzi Exp $
The following types are used internally in data types
The following types are used for structural RIM attributes
Generated using schema builder version 3.2.4. Stylesheets:
StaticMifToXsd.xsl version 2.0
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven.
All rights reserved. Redistribution and use in source and binary forms, with
or without modification, are permitted provided that the following
conditions are met: 1. Redistributions of source code must retain the above
copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software
must display the following acknowledgement: This product includes
software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE
REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by
$Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
$Id: Vocabulary.xml,v 1.1 2005/08/25 11:33:46 mcraig Exp $ RoseTree XML
to Schema: $Id: VocabXMLtoXSD.xsl,v 1.6 2005/05/24 00:14:18 lmckenzi Exp
$
The following types are used internally in data types
The following types are used for structural RIM
attributes
Generated by $Id: v3dt-schema.xsl,v 1.5 2005/05/24 05:44:38
lmckenzi Exp $
Generated using schema builder version 3.2.4. Stylesheets:
StaticMifToXsd.xsl version 2.0
Source Information
Rendered by: RoseTree 3.0.8
Rendered on: 7/30/2005 T24:53:20
This model was rendered into XML using software provided to HL7 by Beeler Consulting LLC.
Transform: $RCSfile: infrastructureRoot.xsd,v $ $Revision: 1.3 $ $Date: 2005/08/24 19:54:59 $
Generated using schema builder version: 2.0
RIM MIF Infrastructure Root to Schema Transform: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Static MIF to Schema Transform: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Package Id Conversion: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by $Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by $Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
Generated by $Id: v3dt-schema.xsl,v 1.5 2005/05/24 05:44:38 lmckenzi Exp $
$Id: Vocabulary.xml,v 1.1 2005/08/25 11:33:46 mcraig Exp $ RoseTree XML to Schema: $Id: VocabXMLtoXSD.xsl,v 1.6 2005/05/24 00:14:18 lmckenzi Exp $
The following types are used internally in data types
The following types are used for structural RIM attributes
Generated using schema builder version 3.2.4. Stylesheets:
StaticMifToXsd.xsl version 2.0
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven.
All rights reserved. Redistribution and use in source and binary forms, with
or without modification, are permitted provided that the following
conditions are met: 1. Redistributions of source code must retain the above
copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software
must display the following acknowledgement: This product includes
software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE
REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by
$Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
$Id: Vocabulary.xml,v 1.1 2005/08/25 11:33:46 mcraig Exp $ RoseTree XML
to Schema: $Id: VocabXMLtoXSD.xsl,v 1.6 2005/05/24 00:14:18 lmckenzi Exp
$
The following types are used internally in data types
The following types are used for structural RIM
attributes
Generated by $Id: v3dt-schema.xsl,v 1.5 2005/05/24 05:44:38
lmckenzi Exp $
Generated using schema builder version 3.2.4. Stylesheets:
StaticMifToXsd.xsl version 2.0
Source Information
Rendered by: RoseTree 3.0.8
Rendered on: 7/30/2005 T24:53:20
This model was rendered into XML using software provided to HL7 by Beeler Consulting LLC.
Transform: $RCSfile: infrastructureRoot.xsd,v $ $Revision: 1.3 $ $Date: 2005/08/24 19:54:59 $
Generated using schema builder version: 2.0
RIM MIF Infrastructure Root to Schema Transform: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Static MIF to Schema Transform: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Package Id Conversion: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by $Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by $Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
Generated by $Id: v3dt-schema.xsl,v 1.5 2005/05/24 05:44:38 lmckenzi Exp $
$Id: Vocabulary.xml,v 1.1 2005/08/25 11:33:46 mcraig Exp $ RoseTree XML to Schema: $Id: VocabXMLtoXSD.xsl,v 1.6 2005/05/24 00:14:18 lmckenzi Exp $
The following types are used internally in data types
The following types are used for structural RIM attributes
Generated using schema builder version 3.2.4. Stylesheets:
StaticMifToXsd.xsl version 2.0
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven.
All rights reserved. Redistribution and use in source and binary forms, with
or without modification, are permitted provided that the following
conditions are met: 1. Redistributions of source code must retain the above
copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software
must display the following acknowledgement: This product includes
software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE
REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by
$Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
$Id: Vocabulary.xml,v 1.1 2005/08/25 11:33:46 mcraig Exp $ RoseTree XML
to Schema: $Id: VocabXMLtoXSD.xsl,v 1.6 2005/05/24 00:14:18 lmckenzi Exp
$
The following types are used internally in data types
The following types are used for structural RIM
attributes
Generated by $Id: v3dt-schema.xsl,v 1.5 2005/05/24 05:44:38
lmckenzi Exp $
Generated using schema builder version 3.2.4. Stylesheets:
StaticMifToXsd.xsl version 2.0
Source Information
Rendered by: RoseTree 3.0.8
Rendered on: 7/30/2005 T24:53:20
This model was rendered into XML using software provided to HL7 by Beeler Consulting LLC.
Transform: $RCSfile: infrastructureRoot.xsd,v $ $Revision: 1.3 $ $Date: 2005/08/24 19:54:59 $
Generated using schema builder version: 2.0
RIM MIF Infrastructure Root to Schema Transform: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Static MIF to Schema Transform: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Package Id Conversion: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by $Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by $Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
Generated by $Id: v3dt-schema.xsl,v 1.5 2005/05/24 05:44:38 lmckenzi Exp $
$Id: Vocabulary.xml,v 1.1 2005/08/25 11:33:46 mcraig Exp $ RoseTree XML to Schema: $Id: VocabXMLtoXSD.xsl,v 1.6 2005/05/24 00:14:18 lmckenzi Exp $
The following types are used internally in data types
The following types are used for structural RIM attributes
Generated using schema builder version 3.2.4. Stylesheets:
StaticMifToXsd.xsl version 2.0
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven.
All rights reserved. Redistribution and use in source and binary forms, with
or without modification, are permitted provided that the following
conditions are met: 1. Redistributions of source code must retain the above
copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software
must display the following acknowledgement: This product includes
software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE
REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by
$Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
$Id: Vocabulary.xml,v 1.1 2005/08/25 11:33:46 mcraig Exp $ RoseTree XML
to Schema: $Id: VocabXMLtoXSD.xsl,v 1.6 2005/05/24 00:14:18 lmckenzi Exp
$
The following types are used internally in data types
The following types are used for structural RIM
attributes
Generated by $Id: v3dt-schema.xsl,v 1.5 2005/05/24 05:44:38
lmckenzi Exp $
Generated using schema builder version 3.2.4. Stylesheets:
StaticMifToXsd.xsl version 2.0
Source Information
Rendered by: RoseTree 3.0.8
Rendered on: 7/30/2005 T24:53:20
This model was rendered into XML using software provided to HL7 by Beeler Consulting LLC.
Transform: $RCSfile: infrastructureRoot.xsd,v $ $Revision: 1.3 $ $Date: 2005/08/24 19:54:59 $
Generated using schema builder version: 2.0
RIM MIF Infrastructure Root to Schema Transform: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Static MIF to Schema Transform: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Package Id Conversion: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by $Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by $Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
Generated by $Id: v3dt-schema.xsl,v 1.5 2005/05/24 05:44:38 lmckenzi Exp $
$Id: Vocabulary.xml,v 1.1 2005/08/25 11:33:46 mcraig Exp $ RoseTree XML to Schema: $Id: VocabXMLtoXSD.xsl,v 1.6 2005/05/24 00:14:18 lmckenzi Exp $
The following types are used internally in data types
The following types are used for structural RIM attributes
Generated using schema builder version 3.2.4. Stylesheets:
StaticMifToXsd.xsl version 2.0
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven.
All rights reserved. Redistribution and use in source and binary forms, with
or without modification, are permitted provided that the following
conditions are met: 1. Redistributions of source code must retain the above
copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software
must display the following acknowledgement: This product includes
software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE
REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by
$Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
$Id: Vocabulary.xml,v 1.1 2005/08/25 11:33:46 mcraig Exp $ RoseTree XML
to Schema: $Id: VocabXMLtoXSD.xsl,v 1.6 2005/05/24 00:14:18 lmckenzi Exp
$
The following types are used internally in data types
The following types are used for structural RIM
attributes
Generated by $Id: v3dt-schema.xsl,v 1.5 2005/05/24 05:44:38
lmckenzi Exp $
Generated using schema builder version 3.2.4. Stylesheets:
StaticMifToXsd.xsl version 2.0
Source Information
Rendered by: RoseTree 3.0.8
Rendered on: 7/30/2005 T24:53:20
This model was rendered into XML using software provided to HL7 by Beeler Consulting LLC.
Transform: $RCSfile: infrastructureRoot.xsd,v $ $Revision: 1.3 $ $Date: 2005/08/24 19:54:59 $
Generated using schema builder version: 2.0
RIM MIF Infrastructure Root to Schema Transform: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Static MIF to Schema Transform: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Package Id Conversion: $Id: infrastructureRoot.xsd,v 1.3 2005/08/24 19:54:59 mcraig Exp $
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by $Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
Copyright (c) 2001, 2002, 2003, 2004, 2005 Health Level Seven. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by Health Level Seven. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Generated by $Id: gsd2xsd.xsl,v 1.4 2005/04/17 03:20:15 lmckenzi Exp $
Generated by $Id: v3dt-schema.xsl,v 1.5 2005/05/24 05:44:38 lmckenzi Exp $
$Id: Vocabulary.xml,v 1.1 2005/08/25 11:33:46 mcraig Exp $ RoseTree XML to Schema: $Id: VocabXMLtoXSD.xsl,v 1.6 2005/05/24 00:14:18 lmckenzi Exp $
The following types are used internally in data types
The following types are used for structural RIM attributes
vocSet: D11527 (C-0-D11527-cpt)
vocSet: D11527 (C-0-D11527-cpt)
vocSet: D11527 (C-0-D11527-cpt)
vocSet: D11527 (C-0-D11527-cpt)
vocSet: D11527 (C-0-D11527-cpt)
vocSet: D11527 (C-0-D11527-cpt)
vocSet: D11527 (C-0-D11527-cpt)
specDomain: V19442
(C-0-D11527-V13856-V19445-V19442-cpt)
specDomain: V19442
(C-0-D11527-V13856-V19445-V19442-cpt)
specDomain: V19442
(C-0-D11527-V13856-V19445-V19442-cpt)
specDomain: V19442
(C-0-D11527-V13856-V19445-V19442-cpt)
specDomain: V19442
(C-0-D11527-V13856-V19445-V19442-cpt)
specDomain: V19442
(C-0-D11527-V13856-V19445-V19442-cpt)
specDomain: V19442
(C-0-D11527-V13856-V19445-V19442-cpt)
specDomain: V19580
(C-0-D11527-V13856-V11529-V19580-cpt)
specDomain: V19580
(C-0-D11527-V13856-V11529-V19580-cpt)
specDomain: V19580
(C-0-D11527-V13856-V11529-V19580-cpt)
specDomain: V19580
(C-0-D11527-V13856-V11529-V19580-cpt)
specDomain: V19580
(C-0-D11527-V13856-V11529-V19580-cpt)
specDomain: V19580
(C-0-D11527-V13856-V11529-V19580-cpt)
specDomain: V19580
(C-0-D11527-V13856-V11529-V19580-cpt)
specDomain: V14002 (C-0-D11527-V13856-V14002-cpt)
specDomain: V14002 (C-0-D11527-V13856-V14002-cpt)
specDomain: V14002 (C-0-D11527-V13856-V14002-cpt)
specDomain: V14002 (C-0-D11527-V13856-V14002-cpt)
specDomain: V14002 (C-0-D11527-V13856-V14002-cpt)
specDomain: V14002 (C-0-D11527-V13856-V14002-cpt)
specDomain: V14002 (C-0-D11527-V13856-V14002-cpt)
specDomain: V11534 (C-0-D11527-V13856-V11534-cpt)
specDomain: V11534 (C-0-D11527-V13856-V11534-cpt)
specDomain: V11534 (C-0-D11527-V13856-V11534-cpt)
specDomain: V11534 (C-0-D11527-V13856-V11534-cpt)
specDomain: V11534 (C-0-D11527-V13856-V11534-cpt)
specDomain: V11534 (C-0-D11527-V13856-V11534-cpt)
specDomain: V11534 (C-0-D11527-V13856-V11534-cpt)
specDomain: V18938
(C-0-D11527-V13856-V19445-V19442-V18938-cpt)
specDomain: V18938
(C-0-D11527-V13856-V19445-V19442-V18938-cpt)
specDomain: V18938
(C-0-D11527-V13856-V19445-V19442-V18938-cpt)
specDomain: V18938
(C-0-D11527-V13856-V19445-V19442-V18938-cpt)
specDomain: V18938
(C-0-D11527-V13856-V19445-V19442-V18938-cpt)
specDomain: V18938
(C-0-D11527-V13856-V19445-V19442-V18938-cpt)
specDomain: V18938
(C-0-D11527-V13856-V19445-V19442-V18938-cpt)
specDomain: V19444
(C-0-D11527-V13856-V19445-V19444-cpt)
specDomain: V19444
(C-0-D11527-V13856-V19445-V19444-cpt)
specDomain: V19444
(C-0-D11527-V13856-V19445-V19444-cpt)
specDomain: V19444
(C-0-D11527-V13856-V19445-V19444-cpt)
specDomain: V19444
(C-0-D11527-V13856-V19445-V19444-cpt)
specDomain: V19444
(C-0-D11527-V13856-V19445-V19444-cpt)
specDomain: V19444
(C-0-D11527-V13856-V19445-V19444-cpt)
specDomain: V19441
(C-0-D11527-V13856-V19445-V19441-cpt)
specDomain: V19441
(C-0-D11527-V13856-V19445-V19441-cpt)
specDomain: V19441
(C-0-D11527-V13856-V19445-V19441-cpt)
specDomain: V19441
(C-0-D11527-V13856-V19445-V19441-cpt)
specDomain: V19441
(C-0-D11527-V13856-V19445-V19441-cpt)
specDomain: V19441
(C-0-D11527-V13856-V19445-V19441-cpt)
specDomain: V19441
(C-0-D11527-V13856-V19445-V19441-cpt)
specDomain: V14003
(C-0-D11527-V13856-V14002-V14003-cpt)
specDomain: V14003
(C-0-D11527-V13856-V14002-V14003-cpt)
specDomain: V14003
(C-0-D11527-V13856-V14002-V14003-cpt)
specDomain: V14003
(C-0-D11527-V13856-V14002-V14003-cpt)
specDomain: V14003
(C-0-D11527-V13856-V14002-V14003-cpt)
specDomain: V14003
(C-0-D11527-V13856-V14002-V14003-cpt)
specDomain: V14003
(C-0-D11527-V13856-V14002-V14003-cpt)
specDomain: V11529 (C-0-D11527-V13856-V11529-cpt)
specDomain: V11529 (C-0-D11527-V13856-V11529-cpt)
specDomain: V11529 (C-0-D11527-V13856-V11529-cpt)
specDomain: V11529 (C-0-D11527-V13856-V11529-cpt)
specDomain: V11529 (C-0-D11527-V13856-V11529-cpt)
specDomain: V11529 (C-0-D11527-V13856-V11529-cpt)
specDomain: V11529 (C-0-D11527-V13856-V11529-cpt)
specDomain: V18875
(C-0-D11527-V13856-V11529-V18875-cpt)
specDomain: V18875
(C-0-D11527-V13856-V11529-V18875-cpt)
specDomain: V18875
(C-0-D11527-V13856-V11529-V18875-cpt)
specDomain: V18875
(C-0-D11527-V13856-V11529-V18875-cpt)
specDomain: V18875
(C-0-D11527-V13856-V11529-V18875-cpt)
specDomain: V18875
(C-0-D11527-V13856-V11529-V18875-cpt)
specDomain: V18875
(C-0-D11527-V13856-V11529-V18875-cpt)
specDomain: V19443
(C-0-D11527-V13856-V19445-V19443-cpt)
specDomain: V19443
(C-0-D11527-V13856-V19445-V19443-cpt)
specDomain: V19443
(C-0-D11527-V13856-V19445-V19443-cpt)
specDomain: V19443
(C-0-D11527-V13856-V19445-V19443-cpt)
specDomain: V19443
(C-0-D11527-V13856-V19445-V19443-cpt)
specDomain: V19443
(C-0-D11527-V13856-V19445-V19443-cpt)
specDomain: V19443
(C-0-D11527-V13856-V19445-V19443-cpt)
specDomain: V11530
(C-0-D11527-V13856-V11529-V19580-V11530-cpt)
specDomain: V11530
(C-0-D11527-V13856-V11529-V19580-V11530-cpt)
specDomain: V11530
(C-0-D11527-V13856-V11529-V19580-V11530-cpt)
specDomain: V11530
(C-0-D11527-V13856-V11529-V19580-V11530-cpt)
specDomain: V11530
(C-0-D11527-V13856-V11529-V19580-V11530-cpt)
specDomain: V11530
(C-0-D11527-V13856-V11529-V19580-V11530-cpt)
specDomain: V11530
(C-0-D11527-V13856-V11529-V19580-V11530-cpt)
abstDomain: V17893
(C-0-D11527-V13856-V11529-V17893-cpt)
abstDomain: V17893
(C-0-D11527-V13856-V11529-V17893-cpt)
abstDomain: V17893
(C-0-D11527-V13856-V11529-V17893-cpt)
abstDomain: V17893
(C-0-D11527-V13856-V11529-V17893-cpt)
abstDomain: V17893
(C-0-D11527-V13856-V11529-V17893-cpt)
abstDomain: V17893
(C-0-D11527-V13856-V11529-V17893-cpt)
abstDomain: V17893
(C-0-D11527-V13856-V11529-V17893-cpt)
specDomain: V13856 (C-0-D11527-V13856-cpt)
specDomain: V13856 (C-0-D11527-V13856-cpt)
specDomain: V13856 (C-0-D11527-V13856-cpt)
specDomain: V13856 (C-0-D11527-V13856-cpt)
specDomain: V13856 (C-0-D11527-V13856-cpt)
specDomain: V13856 (C-0-D11527-V13856-cpt)
specDomain: V13856 (C-0-D11527-V13856-cpt)
specDomain: V11535 (C-0-D11527-V13856-V11535-cpt)
specDomain: V11535 (C-0-D11527-V13856-V11535-cpt)
specDomain: V11535 (C-0-D11527-V13856-V11535-cpt)
specDomain: V11535 (C-0-D11527-V13856-V11535-cpt)
specDomain: V11535 (C-0-D11527-V13856-V11535-cpt)
specDomain: V11535 (C-0-D11527-V13856-V11535-cpt)
specDomain: V11535 (C-0-D11527-V13856-V11535-cpt)
specDomain: V13948
(C-0-D11527-V13856-V19445-V19442-V18938-V13948-cpt)
specDomain: V13948
(C-0-D11527-V13856-V19445-V19442-V18938-V13948-cpt)
specDomain: V13948
(C-0-D11527-V13856-V19445-V19442-V18938-V13948-cpt)
specDomain: V13948
(C-0-D11527-V13856-V19445-V19442-V18938-V13948-cpt)
specDomain: V13948
(C-0-D11527-V13856-V19445-V19442-V18938-V13948-cpt)
specDomain: V13948
(C-0-D11527-V13856-V19445-V19442-V18938-V13948-cpt)
specDomain: V13948
(C-0-D11527-V13856-V19445-V19442-V18938-V13948-cpt)
abstDomain: V19445 (C-0-D11527-V13856-V19445-cpt)
abstDomain: V19445 (C-0-D11527-V13856-V19445-cpt)
abstDomain: V19445 (C-0-D11527-V13856-V19445-cpt)
abstDomain: V19445 (C-0-D11527-V13856-V19445-cpt)
abstDomain: V19445 (C-0-D11527-V13856-V19445-cpt)
abstDomain: V19445 (C-0-D11527-V13856-V19445-cpt)
abstDomain: V19445 (C-0-D11527-V13856-V19445-cpt)
abstDomain: V10197 (C-0-D10196-V10197-cpt)
abstDomain: V10197 (C-0-D10196-V10197-cpt)
abstDomain: V10197 (C-0-D10196-V10197-cpt)
abstDomain: V10197 (C-0-D10196-V10197-cpt)
abstDomain: V10197 (C-0-D10196-V10197-cpt)
abstDomain: V10197 (C-0-D10196-V10197-cpt)
abstDomain: V10197 (C-0-D10196-V10197-cpt)
specDomain: V10199 (C-0-D10196-V16742-V10199-cpt)
specDomain: V10199 (C-0-D10196-V16742-V10199-cpt)
specDomain: V10199 (C-0-D10196-V16742-V10199-cpt)
specDomain: V10199 (C-0-D10196-V16742-V10199-cpt)
specDomain: V10199 (C-0-D10196-V16742-V10199-cpt)
specDomain: V10199 (C-0-D10196-V16742-V10199-cpt)
specDomain: V10199 (C-0-D10196-V16742-V10199-cpt)
abstDomain: V10202 (C-0-D10196-V10202-cpt)
abstDomain: V10202 (C-0-D10196-V10202-cpt)
abstDomain: V10202 (C-0-D10196-V10202-cpt)
abstDomain: V10202 (C-0-D10196-V10202-cpt)
abstDomain: V10202 (C-0-D10196-V10202-cpt)
abstDomain: V10202 (C-0-D10196-V10202-cpt)
abstDomain: V10202 (C-0-D10196-V10202-cpt)
abstDomain: V14900 (C-0-D10317-V10329-V14900-cpt)
abstDomain: V14900 (C-0-D10317-V10329-V14900-cpt)
abstDomain: V14900 (C-0-D10317-V10329-V14900-cpt)
abstDomain: V14900 (C-0-D10317-V10329-V14900-cpt)
abstDomain: V14900 (C-0-D10317-V10329-V14900-cpt)
abstDomain: V14900 (C-0-D10317-V10329-V14900-cpt)
abstDomain: V14900 (C-0-D10317-V10329-V14900-cpt)
abstDomain: V18977 (C-0-D10317-V18977-cpt)
abstDomain: V18977 (C-0-D10317-V18977-cpt)
abstDomain: V18977 (C-0-D10317-V18977-cpt)
abstDomain: V18977 (C-0-D10317-V18977-cpt)
abstDomain: V18977 (C-0-D10317-V18977-cpt)
abstDomain: V18977 (C-0-D10317-V18977-cpt)
abstDomain: V18977 (C-0-D10317-V18977-cpt)
abstDomain: V19618
(C-0-D10317-V10329-V14900-V19618-cpt)
abstDomain: V19618
(C-0-D10317-V10329-V14900-V19618-cpt)
abstDomain: V19618
(C-0-D10317-V10329-V14900-V19618-cpt)
abstDomain: V19618
(C-0-D10317-V10329-V14900-V19618-cpt)
abstDomain: V19618
(C-0-D10317-V10329-V14900-V19618-cpt)
abstDomain: V19618
(C-0-D10317-V10329-V14900-V19618-cpt)
abstDomain: V19618
(C-0-D10317-V10329-V14900-V19618-cpt)
specDomain: V18660 (C-0-D10317-V10337-V18660-cpt)
specDomain: V18660 (C-0-D10317-V10337-V18660-cpt)
specDomain: V18660 (C-0-D10317-V10337-V18660-cpt)
specDomain: V18660 (C-0-D10317-V10337-V18660-cpt)
specDomain: V18660 (C-0-D10317-V10337-V18660-cpt)
specDomain: V18660 (C-0-D10317-V10337-V18660-cpt)
specDomain: V18660 (C-0-D10317-V10337-V18660-cpt)
specDomain: V10342 (C-0-D10317-V10337-V10342-cpt)
specDomain: V10342 (C-0-D10317-V10337-V10342-cpt)
specDomain: V10342 (C-0-D10317-V10337-V10342-cpt)
specDomain: V10342 (C-0-D10317-V10337-V10342-cpt)
specDomain: V10342 (C-0-D10317-V10337-V10342-cpt)
specDomain: V10342 (C-0-D10317-V10337-V10342-cpt)
specDomain: V10342 (C-0-D10317-V10337-V10342-cpt)
specDomain: V10318 (C-0-D10317-V10318-cpt)
specDomain: V10318 (C-0-D10317-V10318-cpt)
specDomain: V10318 (C-0-D10317-V10318-cpt)
specDomain: V10318 (C-0-D10317-V10318-cpt)
specDomain: V10318 (C-0-D10317-V10318-cpt)
specDomain: V10318 (C-0-D10317-V10318-cpt)
specDomain: V10318 (C-0-D10317-V10318-cpt)
abstDomain: V19625 (C-0-D10317-V10324-V19625-cpt)
abstDomain: V19625 (C-0-D10317-V10324-V19625-cpt)
abstDomain: V19625 (C-0-D10317-V10324-V19625-cpt)
abstDomain: V19625 (C-0-D10317-V10324-V19625-cpt)
abstDomain: V19625 (C-0-D10317-V10324-V19625-cpt)
abstDomain: V19625 (C-0-D10317-V10324-V19625-cpt)
abstDomain: V19625 (C-0-D10317-V10324-V19625-cpt)
specDomain: V10324 (C-0-D10317-V10324-cpt)
specDomain: V10324 (C-0-D10317-V10324-cpt)
specDomain: V10324 (C-0-D10317-V10324-cpt)
specDomain: V10324 (C-0-D10317-V10324-cpt)
specDomain: V10324 (C-0-D10317-V10324-cpt)
specDomain: V10324 (C-0-D10317-V10324-cpt)
specDomain: V10324 (C-0-D10317-V10324-cpt)
specDomain: V10329 (C-0-D10317-V10329-cpt)
specDomain: V10329 (C-0-D10317-V10329-cpt)
specDomain: V10329 (C-0-D10317-V10329-cpt)
specDomain: V10329 (C-0-D10317-V10329-cpt)
specDomain: V10329 (C-0-D10317-V10329-cpt)
specDomain: V10329 (C-0-D10317-V10329-cpt)
specDomain: V10329 (C-0-D10317-V10329-cpt)
abstDomain: V19617
(C-0-D10317-V10329-V14900-V19617-cpt)
abstDomain: V19617
(C-0-D10317-V10329-V14900-V19617-cpt)
abstDomain: V19617
(C-0-D10317-V10329-V14900-V19617-cpt)
abstDomain: V19617
(C-0-D10317-V10329-V14900-V19617-cpt)
abstDomain: V19617
(C-0-D10317-V10329-V14900-V19617-cpt)
abstDomain: V19617
(C-0-D10317-V10329-V14900-V19617-cpt)
abstDomain: V19617
(C-0-D10317-V10329-V14900-V19617-cpt)
specDomain: V19376 (C-0-D10317-V18977-V19376-cpt)
specDomain: V19376 (C-0-D10317-V18977-V19376-cpt)
specDomain: V19376 (C-0-D10317-V18977-V19376-cpt)
specDomain: V19376 (C-0-D10317-V18977-V19376-cpt)
specDomain: V19376 (C-0-D10317-V18977-V19376-cpt)
specDomain: V19376 (C-0-D10317-V18977-V19376-cpt)
specDomain: V19376 (C-0-D10317-V18977-V19376-cpt)
specDomain: V10338 (C-0-D10317-V10337-V10338-cpt)
specDomain: V10338 (C-0-D10317-V10337-V10338-cpt)
specDomain: V10338 (C-0-D10317-V10337-V10338-cpt)
specDomain: V10338 (C-0-D10317-V10337-V10338-cpt)
specDomain: V10338 (C-0-D10317-V10337-V10338-cpt)
specDomain: V10338 (C-0-D10317-V10337-V10338-cpt)
specDomain: V10338 (C-0-D10317-V10337-V10338-cpt)
specDomain: V10337 (C-0-D10317-V10337-cpt)
specDomain: V10337 (C-0-D10317-V10337-cpt)
specDomain: V10337 (C-0-D10317-V10337-cpt)
specDomain: V10337 (C-0-D10317-V10337-cpt)
specDomain: V10337 (C-0-D10317-V10337-cpt)
specDomain: V10337 (C-0-D10317-V10337-cpt)
specDomain: V10337 (C-0-D10317-V10337-cpt)
Mailing and home or office addresses. A sequence of
address parts, such as street or post office Box, city, postal code,
country, etc.
Mailing and home or office addresses. A sequence of
address parts, such as street or post office Box, city, postal code,
country, etc.
Mailing and home or office addresses. A sequence of
address parts, such as street or post office Box, city, postal code,
country, etc.
Mailing and home or office addresses. A sequence of
address parts, such as street or post office Box, city, postal code,
country, etc.
Mailing and home or office addresses. A sequence of
address parts, such as street or post office Box, city, postal code,
country, etc.
Mailing and home or office addresses. A sequence of
address parts, such as street or post office Box, city, postal code,
country, etc.
Mailing and home or office addresses. A sequence of
address parts, such as street or post office Box, city, postal code,
country, etc.
A General Timing
Specification (GTS) specifying the periods
of time during which the address can be used.
This is used to specify different addresses for
different times of the year or to refer to historical
addresses.
A General Timing
Specification (GTS) specifying the periods
of time during which the address can be used.
This is used to specify different addresses for
different times of the year or to refer to historical
addresses.
A General Timing
Specification (GTS) specifying the periods
of time during which the address can be used.
This is used to specify different addresses for
different times of the year or to refer to historical
addresses.
A General Timing
Specification (GTS) specifying the periods
of time during which the address can be used.
This is used to specify different addresses for
different times of the year or to refer to historical
addresses.
A General Timing
Specification (GTS) specifying the periods
of time during which the address can be used.
This is used to specify different addresses for
different times of the year or to refer to historical
addresses.
A General Timing
Specification (GTS) specifying the periods
of time during which the address can be used.
This is used to specify different addresses for
different times of the year or to refer to historical
addresses.
A General Timing
Specification (GTS) specifying the periods
of time during which the address can be used.
This is used to specify different addresses for
different times of the year or to refer to historical
addresses.
A boolean value specifying whether
the order of the address parts is known or not.
While the address parts are always a Sequence, the
order in which they are presented may or may not be
known. Where this matters, the isNotOrdered
property can be used to convey this information.
A boolean value specifying whether
the order of the address parts is known or not.
While the address parts are always a Sequence, the
order in which they are presented may or may not be
known. Where this matters, the isNotOrdered
property can be used to convey this information.
A boolean value specifying whether
the order of the address parts is known or not.
While the address parts are always a Sequence, the
order in which they are presented may or may not be
known. Where this matters, the isNotOrdered
property can be used to convey this information.
A boolean value specifying whether
the order of the address parts is known or not.
While the address parts are always a Sequence, the
order in which they are presented may or may not be
known. Where this matters, the isNotOrdered
property can be used to convey this information.
A boolean value specifying whether
the order of the address parts is known or not.
While the address parts are always a Sequence, the
order in which they are presented may or may not be
known. Where this matters, the isNotOrdered
property can be used to convey this information.
A boolean value specifying whether
the order of the address parts is known or not.
While the address parts are always a Sequence, the
order in which they are presented may or may not be
known. Where this matters, the isNotOrdered
property can be used to convey this information.
A boolean value specifying whether
the order of the address parts is known or not.
While the address parts are always a Sequence, the
order in which they are presented may or may not be
known. Where this matters, the isNotOrdered
property can be used to convey this information.
A set of codes advising a system or
user which address in a set of like addresses to
select for a given purpose.
A set of codes advising a system or
user which address in a set of like addresses to
select for a given purpose.
A set of codes advising a system or
user which address in a set of like addresses to
select for a given purpose.
A set of codes advising a system or
user which address in a set of like addresses to
select for a given purpose.
A set of codes advising a system or
user which address in a set of like addresses to
select for a given purpose.
A set of codes advising a system or
user which address in a set of like addresses to
select for a given purpose.
A set of codes advising a system or
user which address in a set of like addresses to
select for a given purpose.
Defines the basic properties of every data value. This
is an abstract type, meaning that no value can be just a data value
without belonging to any concrete type. Every concrete type is a
specialization of this general abstract DataValue type.
An exceptional value expressing missing
information and possibly the reason why the information is
missing.
An exceptional value expressing missing
information and possibly the reason why the information is
missing.
An exceptional value expressing missing
information and possibly the reason why the information is
missing.
An exceptional value expressing missing
information and possibly the reason why the information is
missing.
An exceptional value expressing missing
information and possibly the reason why the information is
missing.
An exceptional value expressing missing
information and possibly the reason why the information is
missing.
An exceptional value expressing missing
information and possibly the reason why the information is
missing.
vocSet: D10609 (C-0-D10609-cpt)
vocSet: D10609 (C-0-D10609-cpt)
vocSet: D10609 (C-0-D10609-cpt)
vocSet: D10609 (C-0-D10609-cpt)
vocSet: D10609 (C-0-D10609-cpt)
vocSet: D10609 (C-0-D10609-cpt)
vocSet: D10609 (C-0-D10609-cpt)
A character string that may have a type-tag signifying
its role in the address. Typical parts that exist in about
every address are street, house number, or post box, postal code, city,
country but other roles may be defined regionally, nationally, or on an
enterprise level (e.g. in military addresses). Addresses are usually
broken up into lines, which are indicated by special line-breaking
delimiter elements (e.g., DEL).
A character string that may have a type-tag signifying
its role in the address. Typical parts that exist in about
every address are street, house number, or post box, postal code, city,
country but other roles may be defined regionally, nationally, or on an
enterprise level (e.g. in military addresses). Addresses are usually
broken up into lines, which are indicated by special line-breaking
delimiter elements (e.g., DEL).
A character string that may have a type-tag signifying
its role in the address. Typical parts that exist in about
every address are street, house number, or post box, postal code, city,
country but other roles may be defined regionally, nationally, or on an
enterprise level (e.g. in military addresses). Addresses are usually
broken up into lines, which are indicated by special line-breaking
delimiter elements (e.g., DEL).
A character string that may have a type-tag signifying
its role in the address. Typical parts that exist in about
every address are street, house number, or post box, postal code, city,
country but other roles may be defined regionally, nationally, or on an
enterprise level (e.g. in military addresses). Addresses are usually
broken up into lines, which are indicated by special line-breaking
delimiter elements (e.g., DEL).
A character string that may have a type-tag signifying
its role in the address. Typical parts that exist in about
every address are street, house number, or post box, postal code, city,
country but other roles may be defined regionally, nationally, or on an
enterprise level (e.g. in military addresses). Addresses are usually
broken up into lines, which are indicated by special line-breaking
delimiter elements (e.g., DEL).
A character string that may have a type-tag signifying
its role in the address. Typical parts that exist in about
every address are street, house number, or post box, postal code, city,
country but other roles may be defined regionally, nationally, or on an
enterprise level (e.g. in military addresses). Addresses are usually
broken up into lines, which are indicated by special line-breaking
delimiter elements (e.g., DEL).
A character string that may have a type-tag signifying
its role in the address. Typical parts that exist in about
every address are street, house number, or post box, postal code, city,
country but other roles may be defined regionally, nationally, or on an
enterprise level (e.g. in military addresses). Addresses are usually
broken up into lines, which are indicated by special line-breaking
delimiter elements (e.g., DEL).
Specifies whether an address part
names the street, city, country, postal code, post
box, etc. If the type is NULL the address part is
unclassified and would simply appear on an address
label as is.
Specifies whether an address part
names the street, city, country, postal code, post
box, etc. If the type is NULL the address part is
unclassified and would simply appear on an address
label as is.
Specifies whether an address part
names the street, city, country, postal code, post
box, etc. If the type is NULL the address part is
unclassified and would simply appear on an address
label as is.
Specifies whether an address part
names the street, city, country, postal code, post
box, etc. If the type is NULL the address part is
unclassified and would simply appear on an address
label as is.
Specifies whether an address part
names the street, city, country, postal code, post
box, etc. If the type is NULL the address part is
unclassified and would simply appear on an address
label as is.
Specifies whether an address part
names the street, city, country, postal code, post
box, etc. If the type is NULL the address part is
unclassified and would simply appear on an address
label as is.
Specifies whether an address part
names the street, city, country, postal code, post
box, etc. If the type is NULL the address part is
unclassified and would simply appear on an address
label as is.
The character string data type stands for text data,
primarily intended for machine processing (e.g., sorting, querying,
indexing, etc.) Used for names, symbols, and formal expressions.
The character string data type stands for text data,
primarily intended for machine processing (e.g., sorting, querying,
indexing, etc.) Used for names, symbols, and formal expressions.
The character string data type stands for text data,
primarily intended for machine processing (e.g., sorting, querying,
indexing, etc.) Used for names, symbols, and formal expressions.
The character string data type stands for text data,
primarily intended for machine processing (e.g., sorting, querying,
indexing, etc.) Used for names, symbols, and formal expressions.
The character string data type stands for text data,
primarily intended for machine processing (e.g., sorting, querying,
indexing, etc.) Used for names, symbols, and formal expressions.
The character string data type stands for text data,
primarily intended for machine processing (e.g., sorting, querying,
indexing, etc.) Used for names, symbols, and formal expressions.
The character string data type stands for text data,
primarily intended for machine processing (e.g., sorting, querying,
indexing, etc.) Used for names, symbols, and formal expressions.
Data that is primarily intended for human interpretation
or for further machine processing is outside the scope of HL7. This
includes unformatted or formatted written language, multimedia data, or
structured information as defined by a different standard (e.g.,
XML-signatures.) Instead of the data itself, an ED may contain
only a reference (see TEL.) Note that the ST data type is a
specialization of the ED data type when the ED media type is text/plain.
Data that is primarily intended for human interpretation
or for further machine processing is outside the scope of HL7. This
includes unformatted or formatted written language, multimedia data, or
structured information as defined by a different standard (e.g.,
XML-signatures.) Instead of the data itself, an ED may contain
only a reference (see TEL.) Note that the ST data type is a
specialization of the ED data type when the ED media type is text/plain.
Data that is primarily intended for human interpretation
or for further machine processing is outside the scope of HL7. This
includes unformatted or formatted written language, multimedia data, or
structured information as defined by a different standard (e.g.,
XML-signatures.) Instead of the data itself, an ED may contain
only a reference (see TEL.) Note that the ST data type is a
specialization of the ED data type when the ED media type is text/plain.
Data that is primarily intended for human interpretation
or for further machine processing is outside the scope of HL7. This
includes unformatted or formatted written language, multimedia data, or
structured information as defined by a different standard (e.g.,
XML-signatures.) Instead of the data itself, an ED may contain
only a reference (see TEL.) Note that the ST data type is a
specialization of the ED data type when the ED media type is text/plain.
Data that is primarily intended for human interpretation
or for further machine processing is outside the scope of HL7. This
includes unformatted or formatted written language, multimedia data, or
structured information as defined by a different standard (e.g.,
XML-signatures.) Instead of the data itself, an ED may contain
only a reference (see TEL.) Note that the ST data type is a
specialization of the ED data type when the ED media type is text/plain.
Data that is primarily intended for human interpretation
or for further machine processing is outside the scope of HL7. This
includes unformatted or formatted written language, multimedia data, or
structured information as defined by a different standard (e.g.,
XML-signatures.) Instead of the data itself, an ED may contain
only a reference (see TEL.) Note that the ST data type is a
specialization of the ED data type when the ED media type is text/plain.
Data that is primarily intended for human interpretation
or for further machine processing is outside the scope of HL7. This
includes unformatted or formatted written language, multimedia data, or
structured information as defined by a different standard (e.g.,
XML-signatures.) Instead of the data itself, an ED may contain
only a reference (see TEL.) Note that the ST data type is a
specialization of the ED data type when the ED media type is text/plain.
A telecommunication address
(TEL), such as a URL for HTTP or FTP, which
will resolve to precisely the same binary
data that could as well have been provided
as inline data.
A telecommunication address
(TEL), such as a URL for HTTP or FTP, which
will resolve to precisely the same binary
data that could as well have been provided
as inline data.
A telecommunication address
(TEL), such as a URL for HTTP or FTP, which
will resolve to precisely the same binary
data that could as well have been provided
as inline data.
A telecommunication address
(TEL), such as a URL for HTTP or FTP, which
will resolve to precisely the same binary
data that could as well have been provided
as inline data.
A telecommunication address
(TEL), such as a URL for HTTP or FTP, which
will resolve to precisely the same binary
data that could as well have been provided
as inline data.
A telecommunication address
(TEL), such as a URL for HTTP or FTP, which
will resolve to precisely the same binary
data that could as well have been provided
as inline data.
A telecommunication address
(TEL), such as a URL for HTTP or FTP, which
will resolve to precisely the same binary
data that could as well have been provided
as inline data.
Indicates whether the raw byte data
is compressed, and what compression algorithm was
used.
Indicates whether the raw byte data
is compressed, and what compression algorithm was
used.
Indicates whether the raw byte data
is compressed, and what compression algorithm was
used.
Indicates whether the raw byte data
is compressed, and what compression algorithm was
used.
Indicates whether the raw byte data
is compressed, and what compression algorithm was
used.
Indicates whether the raw byte data
is compressed, and what compression algorithm was
used.
Indicates whether the raw byte data
is compressed, and what compression algorithm was
used.
The integrity check is a short
binary value representing a cryptographically
strong checksum that is calculated over the binary
data. The purpose of this property, when
communicated with a reference is for anyone to validate
later whether the reference still resolved to the same
data that the reference resolved to when the encapsulated
data value with reference was created.
The integrity check is a short
binary value representing a cryptographically
strong checksum that is calculated over the binary
data. The purpose of this property, when
communicated with a reference is for anyone to validate
later whether the reference still resolved to the same
data that the reference resolved to when the encapsulated
data value with reference was created.
The integrity check is a short
binary value representing a cryptographically
strong checksum that is calculated over the binary
data. The purpose of this property, when
communicated with a reference is for anyone to validate
later whether the reference still resolved to the same
data that the reference resolved to when the encapsulated
data value with reference was created.
The integrity check is a short
binary value representing a cryptographically
strong checksum that is calculated over the binary
data. The purpose of this property, when
communicated with a reference is for anyone to validate
later whether the reference still resolved to the same
data that the reference resolved to when the encapsulated
data value with reference was created.
The integrity check is a short
binary value representing a cryptographically
strong checksum that is calculated over the binary
data. The purpose of this property, when
communicated with a reference is for anyone to validate
later whether the reference still resolved to the same
data that the reference resolved to when the encapsulated
data value with reference was created.
The integrity check is a short
binary value representing a cryptographically
strong checksum that is calculated over the binary
data. The purpose of this property, when
communicated with a reference is for anyone to validate
later whether the reference still resolved to the same
data that the reference resolved to when the encapsulated
data value with reference was created.
The integrity check is a short
binary value representing a cryptographically
strong checksum that is calculated over the binary
data. The purpose of this property, when
communicated with a reference is for anyone to validate
later whether the reference still resolved to the same
data that the reference resolved to when the encapsulated
data value with reference was created.
Specifies the algorithm used to
compute the integrityCheck value.
Specifies the algorithm used to
compute the integrityCheck value.
Specifies the algorithm used to
compute the integrityCheck value.
Specifies the algorithm used to
compute the integrityCheck value.
Specifies the algorithm used to
compute the integrityCheck value.
Specifies the algorithm used to
compute the integrityCheck value.
Specifies the algorithm used to
compute the integrityCheck value.
For character based information the
language property specifies the human language of
the text.
For character based information the
language property specifies the human language of
the text.
For character based information the
language property specifies the human language of
the text.
For character based information the
language property specifies the human language of
the text.
For character based information the
language property specifies the human language of
the text.
For character based information the
language property specifies the human language of
the text.
For character based information the
language property specifies the human language of
the text.
Identifies the type of the
encapsulated data and identifies a method to
interpret or render the data.
Identifies the type of the
encapsulated data and identifies a method to
interpret or render the data.
Identifies the type of the
encapsulated data and identifies a method to
interpret or render the data.
Identifies the type of the
encapsulated data and identifies a method to
interpret or render the data.
Identifies the type of the
encapsulated data and identifies a method to
interpret or render the data.
Identifies the type of the
encapsulated data and identifies a method to
interpret or render the data.
Identifies the type of the
encapsulated data and identifies a method to
interpret or render the data.
Binary data is a raw block of bits. Binary data is a
protected type that MUST not be used outside the data type
specification.
Binary data is a raw block of bits. Binary data is a
protected type that MUST not be used outside the data type
specification.
Binary data is a raw block of bits. Binary data is a
protected type that MUST not be used outside the data type
specification.
Binary data is a raw block of bits. Binary data is a
protected type that MUST not be used outside the data type
specification.
Binary data is a raw block of bits. Binary data is a
protected type that MUST not be used outside the data type
specification.
Binary data is a raw block of bits. Binary data is a
protected type that MUST not be used outside the data type
specification.
Binary data is a raw block of bits. Binary data is a
protected type that MUST not be used outside the data type
specification.
Specifies the representation of the
binary data that is the content of the binary data
value.
Specifies the representation of the
binary data that is the content of the binary data
value.
Specifies the representation of the
binary data that is the content of the binary data
value.
Specifies the representation of the
binary data that is the content of the binary data
value.
Specifies the representation of the
binary data that is the content of the binary data
value.
Specifies the representation of the
binary data that is the content of the binary data
value.
Specifies the representation of the
binary data that is the content of the binary data
value.
A telephone number (voice or fax), e-mail address, or
other locator for a resource (information or service) mediated by
telecommunication equipment. The address is specified as a Universal
Resource Locator (URL) qualified by time specification and use codes
that help in deciding which address to use for a given time and
purpose.
A telephone number (voice or fax), e-mail address, or
other locator for a resource (information or service) mediated by
telecommunication equipment. The address is specified as a Universal
Resource Locator (URL) qualified by time specification and use codes
that help in deciding which address to use for a given time and
purpose.
A telephone number (voice or fax), e-mail address, or
other locator for a resource (information or service) mediated by
telecommunication equipment. The address is specified as a Universal
Resource Locator (URL) qualified by time specification and use codes
that help in deciding which address to use for a given time and
purpose.
A telephone number (voice or fax), e-mail address, or
other locator for a resource (information or service) mediated by
telecommunication equipment. The address is specified as a Universal
Resource Locator (URL) qualified by time specification and use codes
that help in deciding which address to use for a given time and
purpose.
A telephone number (voice or fax), e-mail address, or
other locator for a resource (information or service) mediated by
telecommunication equipment. The address is specified as a Universal
Resource Locator (URL) qualified by time specification and use codes
that help in deciding which address to use for a given time and
purpose.
A telephone number (voice or fax), e-mail address, or
other locator for a resource (information or service) mediated by
telecommunication equipment. The address is specified as a Universal
Resource Locator (URL) qualified by time specification and use codes
that help in deciding which address to use for a given time and
purpose.
A telephone number (voice or fax), e-mail address, or
other locator for a resource (information or service) mediated by
telecommunication equipment. The address is specified as a Universal
Resource Locator (URL) qualified by time specification and use codes
that help in deciding which address to use for a given time and
purpose.
Specifies the periods of time
during which the telecommunication address can
be used. For a telephone number, this can
indicate the time of day in which the party can
be reached on that telephone. For a web
address, it may specify a time range in which
the web content is promised to be available
under the given address.
Specifies the periods of time
during which the telecommunication address can
be used. For a telephone number, this can
indicate the time of day in which the party can
be reached on that telephone. For a web
address, it may specify a time range in which
the web content is promised to be available
under the given address.
Specifies the periods of time
during which the telecommunication address can
be used. For a telephone number, this can
indicate the time of day in which the party can
be reached on that telephone. For a web
address, it may specify a time range in which
the web content is promised to be available
under the given address.
Specifies the periods of time
during which the telecommunication address can
be used. For a telephone number, this can
indicate the time of day in which the party can
be reached on that telephone. For a web
address, it may specify a time range in which
the web content is promised to be available
under the given address.
Specifies the periods of time
during which the telecommunication address can
be used. For a telephone number, this can
indicate the time of day in which the party can
be reached on that telephone. For a web
address, it may specify a time range in which
the web content is promised to be available
under the given address.
Specifies the periods of time
during which the telecommunication address can
be used. For a telephone number, this can
indicate the time of day in which the party can
be reached on that telephone. For a web
address, it may specify a time range in which
the web content is promised to be available
under the given address.
Specifies the periods of time
during which the telecommunication address can
be used. For a telephone number, this can
indicate the time of day in which the party can
be reached on that telephone. For a web
address, it may specify a time range in which
the web content is promised to be available
under the given address.
One or more codes advising a system
or user which telecommunication address in a set of
like addresses to select for a given
telecommunication need.
One or more codes advising a system
or user which telecommunication address in a set of
like addresses to select for a given
telecommunication need.
One or more codes advising a system
or user which telecommunication address in a set of
like addresses to select for a given
telecommunication need.
One or more codes advising a system
or user which telecommunication address in a set of
like addresses to select for a given
telecommunication need.
One or more codes advising a system
or user which telecommunication address in a set of
like addresses to select for a given
telecommunication need.
One or more codes advising a system
or user which telecommunication address in a set of
like addresses to select for a given
telecommunication need.
One or more codes advising a system
or user which telecommunication address in a set of
like addresses to select for a given
telecommunication need.
A telecommunications address specified according to
Internet standard RFC 1738 [http://www.ietf.org/rfc/rfc1738.txt]. The
URL specifies the protocol and the contact point defined by that
protocol for the resource. Notable uses of the telecommunication
address data type are for telephone and telefax numbers, e-mail
addresses, Hypertext references, FTP references, etc.
A telecommunications address specified according to
Internet standard RFC 1738 [http://www.ietf.org/rfc/rfc1738.txt]. The
URL specifies the protocol and the contact point defined by that
protocol for the resource. Notable uses of the telecommunication
address data type are for telephone and telefax numbers, e-mail
addresses, Hypertext references, FTP references, etc.
A telecommunications address specified according to
Internet standard RFC 1738 [http://www.ietf.org/rfc/rfc1738.txt]. The
URL specifies the protocol and the contact point defined by that
protocol for the resource. Notable uses of the telecommunication
address data type are for telephone and telefax numbers, e-mail
addresses, Hypertext references, FTP references, etc.
A telecommunications address specified according to
Internet standard RFC 1738 [http://www.ietf.org/rfc/rfc1738.txt]. The
URL specifies the protocol and the contact point defined by that
protocol for the resource. Notable uses of the telecommunication
address data type are for telephone and telefax numbers, e-mail
addresses, Hypertext references, FTP references, etc.
A telecommunications address specified according to
Internet standard RFC 1738 [http://www.ietf.org/rfc/rfc1738.txt]. The
URL specifies the protocol and the contact point defined by that
protocol for the resource. Notable uses of the telecommunication
address data type are for telephone and telefax numbers, e-mail
addresses, Hypertext references, FTP references, etc.
A telecommunications address specified according to
Internet standard RFC 1738 [http://www.ietf.org/rfc/rfc1738.txt]. The
URL specifies the protocol and the contact point defined by that
protocol for the resource. Notable uses of the telecommunication
address data type are for telephone and telefax numbers, e-mail
addresses, Hypertext references, FTP references, etc.
A telecommunications address specified according to
Internet standard RFC 1738 [http://www.ietf.org/rfc/rfc1738.txt]. The
URL specifies the protocol and the contact point defined by that
protocol for the resource. Notable uses of the telecommunication
address data type are for telephone and telefax numbers, e-mail
addresses, Hypertext references, FTP references, etc.
A telecommunications address specified according to
Internet standard RFC 1738 [http://www.ietf.org/rfc/rfc1738.txt]. The
URL specifies the protocol and the contact point defined by that
protocol for the resource. Notable uses of the telecommunication
address data type are for telephone and telefax numbers, e-mail
addresses, Hypertext references, FTP references, etc.
A telecommunications address specified according to
Internet standard RFC 1738 [http://www.ietf.org/rfc/rfc1738.txt]. The
URL specifies the protocol and the contact point defined by that
protocol for the resource. Notable uses of the telecommunication
address data type are for telephone and telefax numbers, e-mail
addresses, Hypertext references, FTP references, etc.
A telecommunications address specified according to
Internet standard RFC 1738 [http://www.ietf.org/rfc/rfc1738.txt]. The
URL specifies the protocol and the contact point defined by that
protocol for the resource. Notable uses of the telecommunication
address data type are for telephone and telefax numbers, e-mail
addresses, Hypertext references, FTP references, etc.
A telecommunications address specified according to
Internet standard RFC 1738 [http://www.ietf.org/rfc/rfc1738.txt]. The
URL specifies the protocol and the contact point defined by that
protocol for the resource. Notable uses of the telecommunication
address data type are for telephone and telefax numbers, e-mail
addresses, Hypertext references, FTP references, etc.
A telecommunications address specified according to
Internet standard RFC 1738 [http://www.ietf.org/rfc/rfc1738.txt]. The
URL specifies the protocol and the contact point defined by that
protocol for the resource. Notable uses of the telecommunication
address data type are for telephone and telefax numbers, e-mail
addresses, Hypertext references, FTP references, etc.
A telecommunications address specified according to
Internet standard RFC 1738 [http://www.ietf.org/rfc/rfc1738.txt]. The
URL specifies the protocol and the contact point defined by that
protocol for the resource. Notable uses of the telecommunication
address data type are for telephone and telefax numbers, e-mail
addresses, Hypertext references, FTP references, etc.
A telecommunications address specified according to
Internet standard RFC 1738 [http://www.ietf.org/rfc/rfc1738.txt]. The
URL specifies the protocol and the contact point defined by that
protocol for the resource. Notable uses of the telecommunication
address data type are for telephone and telefax numbers, e-mail
addresses, Hypertext references, FTP references, etc.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A quantity specifying a point on the axis of natural
time. A point in time is most often represented as a calendar
expression.
A quantity specifying a point on the axis of natural
time. A point in time is most often represented as a calendar
expression.
A quantity specifying a point on the axis of natural
time. A point in time is most often represented as a calendar
expression.
A quantity specifying a point on the axis of natural
time. A point in time is most often represented as a calendar
expression.
A quantity specifying a point on the axis of natural
time. A point in time is most often represented as a calendar
expression.
A quantity specifying a point on the axis of natural
time. A point in time is most often represented as a calendar
expression.
A quantity specifying a point on the axis of natural
time. A point in time is most often represented as a calendar
expression.
The quantity data type is an abstract generalization
for all data types (1) whose value set has an order relation
(less-or-equal) and (2) where difference is defined in all of the data
type's totally ordered value subsets. The quantity type abstraction is
needed in defining certain other types, such as the interval and
the probability distribution.
The quantity data type is an abstract generalization
for all data types (1) whose value set has an order relation
(less-or-equal) and (2) where difference is defined in all of the data
type's totally ordered value subsets. The quantity type abstraction is
needed in defining certain other types, such as the interval and
the probability distribution.
The quantity data type is an abstract generalization
for all data types (1) whose value set has an order relation
(less-or-equal) and (2) where difference is defined in all of the data
type's totally ordered value subsets. The quantity type abstraction is
needed in defining certain other types, such as the interval and
the probability distribution.
The quantity data type is an abstract generalization
for all data types (1) whose value set has an order relation
(less-or-equal) and (2) where difference is defined in all of the data
type's totally ordered value subsets. The quantity type abstraction is
needed in defining certain other types, such as the interval and
the probability distribution.
The quantity data type is an abstract generalization
for all data types (1) whose value set has an order relation
(less-or-equal) and (2) where difference is defined in all of the data
type's totally ordered value subsets. The quantity type abstraction is
needed in defining certain other types, such as the interval and
the probability distribution.
The quantity data type is an abstract generalization
for all data types (1) whose value set has an order relation
(less-or-equal) and (2) where difference is defined in all of the data
type's totally ordered value subsets. The quantity type abstraction is
needed in defining certain other types, such as the interval and
the probability distribution.
The quantity data type is an abstract generalization
for all data types (1) whose value set has an order relation
(less-or-equal) and (2) where difference is defined in all of the data
type's totally ordered value subsets. The quantity type abstraction is
needed in defining certain other types, such as the interval and
the probability distribution.
A quantity specifying a point on the axis of natural
time. A point in time is most often represented as a calendar
expression.
A quantity specifying a point on the axis of natural
time. A point in time is most often represented as a calendar
expression.
A quantity specifying a point on the axis of natural
time. A point in time is most often represented as a calendar
expression.
A quantity specifying a point on the axis of natural
time. A point in time is most often represented as a calendar
expression.
A quantity specifying a point on the axis of natural
time. A point in time is most often represented as a calendar
expression.
A quantity specifying a point on the axis of natural
time. A point in time is most often represented as a calendar
expression.
A quantity specifying a point on the axis of natural
time. A point in time is most often represented as a calendar
expression.
vocSet: D17416 (C-0-D17416-cpt)
vocSet: D17416 (C-0-D17416-cpt)
vocSet: D17416 (C-0-D17416-cpt)
vocSet: D17416 (C-0-D17416-cpt)
vocSet: D17416 (C-0-D17416-cpt)
vocSet: D17416 (C-0-D17416-cpt)
vocSet: D17416 (C-0-D17416-cpt)
A thumbnail is an abbreviated rendition of the
full data. A thumbnail requires significantly fewer
resources than the full data, while still maintaining some
distinctive similarity with the full data. A thumbnail is
typically used with by-reference encapsulated data. It allows a
user to select data more efficiently before actually
downloading through the reference.
A thumbnail is an abbreviated rendition of the
full data. A thumbnail requires significantly fewer
resources than the full data, while still maintaining some
distinctive similarity with the full data. A thumbnail is
typically used with by-reference encapsulated data. It allows a
user to select data more efficiently before actually
downloading through the reference.
A thumbnail is an abbreviated rendition of the
full data. A thumbnail requires significantly fewer
resources than the full data, while still maintaining some
distinctive similarity with the full data. A thumbnail is
typically used with by-reference encapsulated data. It allows a
user to select data more efficiently before actually
downloading through the reference.
A thumbnail is an abbreviated rendition of the
full data. A thumbnail requires significantly fewer
resources than the full data, while still maintaining some
distinctive similarity with the full data. A thumbnail is
typically used with by-reference encapsulated data. It allows a
user to select data more efficiently before actually
downloading through the reference.
A thumbnail is an abbreviated rendition of the
full data. A thumbnail requires significantly fewer
resources than the full data, while still maintaining some
distinctive similarity with the full data. A thumbnail is
typically used with by-reference encapsulated data. It allows a
user to select data more efficiently before actually
downloading through the reference.
A thumbnail is an abbreviated rendition of the
full data. A thumbnail requires significantly fewer
resources than the full data, while still maintaining some
distinctive similarity with the full data. A thumbnail is
typically used with by-reference encapsulated data. It allows a
user to select data more efficiently before actually
downloading through the reference.
A thumbnail is an abbreviated rendition of the
full data. A thumbnail requires significantly fewer
resources than the full data, while still maintaining some
distinctive similarity with the full data. A thumbnail is
typically used with by-reference encapsulated data. It allows a
user to select data more efficiently before actually
downloading through the reference.
vocSet: D10620 (C-0-D10620-cpt)
vocSet: D10620 (C-0-D10620-cpt)
vocSet: D10620 (C-0-D10620-cpt)
vocSet: D10620 (C-0-D10620-cpt)
vocSet: D10620 (C-0-D10620-cpt)
vocSet: D10620 (C-0-D10620-cpt)
vocSet: D10620 (C-0-D10620-cpt)
Binary data is a raw block of bits. Binary data is a
protected type that MUST not be used outside the data type
specification.
Binary data is a raw block of bits. Binary data is a
protected type that MUST not be used outside the data type
specification.
Binary data is a raw block of bits. Binary data is a
protected type that MUST not be used outside the data type
specification.
Binary data is a raw block of bits. Binary data is a
protected type that MUST not be used outside the data type
specification.
Binary data is a raw block of bits. Binary data is a
protected type that MUST not be used outside the data type
specification.
Binary data is a raw block of bits. Binary data is a
protected type that MUST not be used outside the data type
specification.
Binary data is a raw block of bits. Binary data is a
protected type that MUST not be used outside the data type
specification.
vocSet: D17385 (C-0-D17385-cpt)
vocSet: D17385 (C-0-D17385-cpt)
vocSet: D17385 (C-0-D17385-cpt)
vocSet: D17385 (C-0-D17385-cpt)
vocSet: D17385 (C-0-D17385-cpt)
vocSet: D17385 (C-0-D17385-cpt)
vocSet: D17385 (C-0-D17385-cpt)
vocSet: D10642 (C-0-D10642-cpt)
vocSet: D10642 (C-0-D10642-cpt)
vocSet: D10642 (C-0-D10642-cpt)
vocSet: D10642 (C-0-D10642-cpt)
vocSet: D10642 (C-0-D10642-cpt)
vocSet: D10642 (C-0-D10642-cpt)
vocSet: D10642 (C-0-D10642-cpt)
The Boolean type stands for the values of two-valued
logic. A Boolean value can be either true or false, or, as
any other value may be NULL.
The Boolean type stands for the values of two-valued
logic. A Boolean value can be either true or false, or, as
any other value may be NULL.
The Boolean type stands for the values of two-valued
logic. A Boolean value can be either true or false, or, as
any other value may be NULL.
The Boolean type stands for the values of two-valued
logic. A Boolean value can be either true or false, or, as
any other value may be NULL.
The Boolean type stands for the values of two-valued
logic. A Boolean value can be either true or false, or, as
any other value may be NULL.
The Boolean type stands for the values of two-valued
logic. A Boolean value can be either true or false, or, as
any other value may be NULL.
The Boolean type stands for the values of two-valued
logic. A Boolean value can be either true or false, or, as
any other value may be NULL.
specDomain: V10651 (C-0-D10642-V10651-cpt)
specDomain: V10651 (C-0-D10642-V10651-cpt)
specDomain: V10651 (C-0-D10642-V10651-cpt)
specDomain: V10651 (C-0-D10642-V10651-cpt)
specDomain: V10651 (C-0-D10642-V10651-cpt)
specDomain: V10651 (C-0-D10642-V10651-cpt)
specDomain: V10651 (C-0-D10642-V10651-cpt)
abstDomain: V190 (C-0-D201-V190-cpt)
abstDomain: V190 (C-0-D201-V190-cpt)
abstDomain: V190 (C-0-D201-V190-cpt)
abstDomain: V190 (C-0-D201-V190-cpt)
abstDomain: V190 (C-0-D201-V190-cpt)
abstDomain: V190 (C-0-D201-V190-cpt)
abstDomain: V190 (C-0-D201-V190-cpt)
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
abstDomain: V14832 (C-0-D14824-V14832-cpt)
abstDomain: V14832 (C-0-D14824-V14832-cpt)
abstDomain: V14832 (C-0-D14824-V14832-cpt)
abstDomain: V14832 (C-0-D14824-V14832-cpt)
abstDomain: V14832 (C-0-D14824-V14832-cpt)
abstDomain: V14832 (C-0-D14824-V14832-cpt)
abstDomain: V14832 (C-0-D14824-V14832-cpt)
specDomain: V10614
(C-0-D10609-V10610-V10612-V10614-cpt)
specDomain: V10614
(C-0-D10609-V10610-V10612-V10614-cpt)
specDomain: V10614
(C-0-D10609-V10610-V10612-V10614-cpt)
specDomain: V10614
(C-0-D10609-V10610-V10612-V10614-cpt)
specDomain: V10614
(C-0-D10609-V10610-V10612-V10614-cpt)
specDomain: V10614
(C-0-D10609-V10610-V10612-V10614-cpt)
specDomain: V10614
(C-0-D10609-V10610-V10612-V10614-cpt)
abstDomain: V14835 (C-0-D14824-V14835-cpt)
abstDomain: V14835 (C-0-D14824-V14835-cpt)
abstDomain: V14835 (C-0-D14824-V14835-cpt)
abstDomain: V14835 (C-0-D14824-V14835-cpt)
abstDomain: V14835 (C-0-D14824-V14835-cpt)
abstDomain: V14835 (C-0-D14824-V14835-cpt)
abstDomain: V14835 (C-0-D14824-V14835-cpt)
The Boolean type stands for the values of two-valued
logic. A Boolean value can be either true or false, or, as
any other value may be NULL.
The Boolean type stands for the values of two-valued
logic. A Boolean value can be either true or false, or, as
any other value may be NULL.
The Boolean type stands for the values of two-valued
logic. A Boolean value can be either true or false, or, as
any other value may be NULL.
The Boolean type stands for the values of two-valued
logic. A Boolean value can be either true or false, or, as
any other value may be NULL.
The Boolean type stands for the values of two-valued
logic. A Boolean value can be either true or false, or, as
any other value may be NULL.
The Boolean type stands for the values of two-valued
logic. A Boolean value can be either true or false, or, as
any other value may be NULL.
The Boolean type stands for the values of two-valued
logic. A Boolean value can be either true or false, or, as
any other value may be NULL.
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
The BooleanNonNull type is used where a Boolean cannot
have a null value. A Boolean value can be either true or false.
specDomain: V10649 (C-0-D10642-V14822-V10649-cpt)
specDomain: V10649 (C-0-D10642-V14822-V10649-cpt)
specDomain: V10649 (C-0-D10642-V14822-V10649-cpt)
specDomain: V10649 (C-0-D10642-V14822-V10649-cpt)
specDomain: V10649 (C-0-D10642-V14822-V10649-cpt)
specDomain: V10649 (C-0-D10642-V14822-V10649-cpt)
specDomain: V10649 (C-0-D10642-V14822-V10649-cpt)
The quantity in which the bag item
occurs in its containing bag.
The quantity in which the bag item
occurs in its containing bag.
The quantity in which the bag item
occurs in its containing bag.
The quantity in which the bag item
occurs in its containing bag.
The quantity in which the bag item
occurs in its containing bag.
The quantity in which the bag item
occurs in its containing bag.
The quantity in which the bag item
occurs in its containing bag.
A concept descriptor represents any kind of concept
usually by giving a code defined in a code system. A concept
descriptor can contain the original text or phrase that served as the
basis of the coding and one or more translations into different coding
systems. A concept descriptor can also contain qualifiers to describe,
e.g., the concept of a "left foot" as a postcoordinated term built
from the primary code "FOOT" and the qualifier "LEFT". In exceptional
cases, the concept descriptor need not contain a code but only the
original text describing that concept.
A concept descriptor represents any kind of concept
usually by giving a code defined in a code system. A concept
descriptor can contain the original text or phrase that served as the
basis of the coding and one or more translations into different coding
systems. A concept descriptor can also contain qualifiers to describe,
e.g., the concept of a "left foot" as a postcoordinated term built
from the primary code "FOOT" and the qualifier "LEFT". In exceptional
cases, the concept descriptor need not contain a code but only the
original text describing that concept.
A concept descriptor represents any kind of concept
usually by giving a code defined in a code system. A concept
descriptor can contain the original text or phrase that served as the
basis of the coding and one or more translations into different coding
systems. A concept descriptor can also contain qualifiers to describe,
e.g., the concept of a "left foot" as a postcoordinated term built
from the primary code "FOOT" and the qualifier "LEFT". In exceptional
cases, the concept descriptor need not contain a code but only the
original text describing that concept.
A concept descriptor represents any kind of concept
usually by giving a code defined in a code system. A concept
descriptor can contain the original text or phrase that served as the
basis of the coding and one or more translations into different coding
systems. A concept descriptor can also contain qualifiers to describe,
e.g., the concept of a "left foot" as a postcoordinated term built
from the primary code "FOOT" and the qualifier "LEFT". In exceptional
cases, the concept descriptor need not contain a code but only the
original text describing that concept.
A concept descriptor represents any kind of concept
usually by giving a code defined in a code system. A concept
descriptor can contain the original text or phrase that served as the
basis of the coding and one or more translations into different coding
systems. A concept descriptor can also contain qualifiers to describe,
e.g., the concept of a "left foot" as a postcoordinated term built
from the primary code "FOOT" and the qualifier "LEFT". In exceptional
cases, the concept descriptor need not contain a code but only the
original text describing that concept.
A concept descriptor represents any kind of concept
usually by giving a code defined in a code system. A concept
descriptor can contain the original text or phrase that served as the
basis of the coding and one or more translations into different coding
systems. A concept descriptor can also contain qualifiers to describe,
e.g., the concept of a "left foot" as a postcoordinated term built
from the primary code "FOOT" and the qualifier "LEFT". In exceptional
cases, the concept descriptor need not contain a code but only the
original text describing that concept.
A concept descriptor represents any kind of concept
usually by giving a code defined in a code system. A concept
descriptor can contain the original text or phrase that served as the
basis of the coding and one or more translations into different coding
systems. A concept descriptor can also contain qualifiers to describe,
e.g., the concept of a "left foot" as a postcoordinated term built
from the primary code "FOOT" and the qualifier "LEFT". In exceptional
cases, the concept descriptor need not contain a code but only the
original text describing that concept.
The text or phrase used as
the basis for the coding.
The text or phrase used as
the basis for the coding.
The text or phrase used as
the basis for the coding.
The text or phrase used as
the basis for the coding.
The text or phrase used as
the basis for the coding.
The text or phrase used as
the basis for the coding.
The text or phrase used as
the basis for the coding.
Specifies additional codes
that increase the specificity of the primary
code.
Specifies additional codes
that increase the specificity of the primary
code.
Specifies additional codes
that increase the specificity of the primary
code.
Specifies additional codes
that increase the specificity of the primary
code.
Specifies additional codes
that increase the specificity of the primary
code.
Specifies additional codes
that increase the specificity of the primary
code.
Specifies additional codes
that increase the specificity of the primary
code.
A set of other concept
descriptors that translate this concept
descriptor into other code systems.
A set of other concept
descriptors that translate this concept
descriptor into other code systems.
A set of other concept
descriptors that translate this concept
descriptor into other code systems.
A set of other concept
descriptors that translate this concept
descriptor into other code systems.
A set of other concept
descriptors that translate this concept
descriptor into other code systems.
A set of other concept
descriptors that translate this concept
descriptor into other code systems.
A set of other concept
descriptors that translate this concept
descriptor into other code systems.
The plain code symbol defined by the
code system. For example, "784.0" is the code
symbol of the ICD-9 code "784.0" for headache.
The plain code symbol defined by the
code system. For example, "784.0" is the code
symbol of the ICD-9 code "784.0" for headache.
The plain code symbol defined by the
code system. For example, "784.0" is the code
symbol of the ICD-9 code "784.0" for headache.
The plain code symbol defined by the
code system. For example, "784.0" is the code
symbol of the ICD-9 code "784.0" for headache.
The plain code symbol defined by the
code system. For example, "784.0" is the code
symbol of the ICD-9 code "784.0" for headache.
The plain code symbol defined by the
code system. For example, "784.0" is the code
symbol of the ICD-9 code "784.0" for headache.
The plain code symbol defined by the
code system. For example, "784.0" is the code
symbol of the ICD-9 code "784.0" for headache.
Specifies the code system that
defines the code.
Specifies the code system that
defines the code.
Specifies the code system that
defines the code.
Specifies the code system that
defines the code.
Specifies the code system that
defines the code.
Specifies the code system that
defines the code.
Specifies the code system that
defines the code.
A common name of the coding system.
A common name of the coding system.
A common name of the coding system.
A common name of the coding system.
A common name of the coding system.
A common name of the coding system.
A common name of the coding system.
If applicable, a version descriptor
defined specifically for the given code system.
If applicable, a version descriptor
defined specifically for the given code system.
If applicable, a version descriptor
defined specifically for the given code system.
If applicable, a version descriptor
defined specifically for the given code system.
If applicable, a version descriptor
defined specifically for the given code system.
If applicable, a version descriptor
defined specifically for the given code system.
If applicable, a version descriptor
defined specifically for the given code system.
A name or title for the code, under
which the sending system shows the code value to
its users.
A name or title for the code, under
which the sending system shows the code value to
its users.
A name or title for the code, under
which the sending system shows the code value to
its users.
A name or title for the code, under
which the sending system shows the code value to
its users.
A name or title for the code, under
which the sending system shows the code value to
its users.
A name or title for the code, under
which the sending system shows the code value to
its users.
A name or title for the code, under
which the sending system shows the code value to
its users.
A concept qualifier code with optionally named role.
Both qualifier role and value codes must be defined by the coding
system. For example, if SNOMED RT defines a concept "leg", a role
relation "has-laterality", and another concept "left", the concept role
relation allows to add the qualifier "has-laterality: left" to a primary
code "leg" to construct the meaning "left leg".
A concept qualifier code with optionally named role.
Both qualifier role and value codes must be defined by the coding
system. For example, if SNOMED RT defines a concept "leg", a role
relation "has-laterality", and another concept "left", the concept role
relation allows to add the qualifier "has-laterality: left" to a primary
code "leg" to construct the meaning "left leg".
A concept qualifier code with optionally named role.
Both qualifier role and value codes must be defined by the coding
system. For example, if SNOMED RT defines a concept "leg", a role
relation "has-laterality", and another concept "left", the concept role
relation allows to add the qualifier "has-laterality: left" to a primary
code "leg" to construct the meaning "left leg".
A concept qualifier code with optionally named role.
Both qualifier role and value codes must be defined by the coding
system. For example, if SNOMED RT defines a concept "leg", a role
relation "has-laterality", and another concept "left", the concept role
relation allows to add the qualifier "has-laterality: left" to a primary
code "leg" to construct the meaning "left leg".
A concept qualifier code with optionally named role.
Both qualifier role and value codes must be defined by the coding
system. For example, if SNOMED RT defines a concept "leg", a role
relation "has-laterality", and another concept "left", the concept role
relation allows to add the qualifier "has-laterality: left" to a primary
code "leg" to construct the meaning "left leg".
A concept qualifier code with optionally named role.
Both qualifier role and value codes must be defined by the coding
system. For example, if SNOMED RT defines a concept "leg", a role
relation "has-laterality", and another concept "left", the concept role
relation allows to add the qualifier "has-laterality: left" to a primary
code "leg" to construct the meaning "left leg".
A concept qualifier code with optionally named role.
Both qualifier role and value codes must be defined by the coding
system. For example, if SNOMED RT defines a concept "leg", a role
relation "has-laterality", and another concept "left", the concept role
relation allows to add the qualifier "has-laterality: left" to a primary
code "leg" to construct the meaning "left leg".
Specifies the manner in which
the concept role value contributes to the
meaning of a code phrase. For example, if
SNOMED RT defines a concept "leg", a role
relation "has-laterality", and another concept "left",
the concept role relation allows to add the qualifier
"has-laterality: left" to a primary code "leg" to
construct the meaning "left leg". In this example
"has-laterality" is the CR.name.
Specifies the manner in which
the concept role value contributes to the
meaning of a code phrase. For example, if
SNOMED RT defines a concept "leg", a role
relation "has-laterality", and another concept "left",
the concept role relation allows to add the qualifier
"has-laterality: left" to a primary code "leg" to
construct the meaning "left leg". In this example
"has-laterality" is the CR.name.
Specifies the manner in which
the concept role value contributes to the
meaning of a code phrase. For example, if
SNOMED RT defines a concept "leg", a role
relation "has-laterality", and another concept "left",
the concept role relation allows to add the qualifier
"has-laterality: left" to a primary code "leg" to
construct the meaning "left leg". In this example
"has-laterality" is the CR.name.
Specifies the manner in which
the concept role value contributes to the
meaning of a code phrase. For example, if
SNOMED RT defines a concept "leg", a role
relation "has-laterality", and another concept "left",
the concept role relation allows to add the qualifier
"has-laterality: left" to a primary code "leg" to
construct the meaning "left leg". In this example
"has-laterality" is the CR.name.
Specifies the manner in which
the concept role value contributes to the
meaning of a code phrase. For example, if
SNOMED RT defines a concept "leg", a role
relation "has-laterality", and another concept "left",
the concept role relation allows to add the qualifier
"has-laterality: left" to a primary code "leg" to
construct the meaning "left leg". In this example
"has-laterality" is the CR.name.
Specifies the manner in which
the concept role value contributes to the
meaning of a code phrase. For example, if
SNOMED RT defines a concept "leg", a role
relation "has-laterality", and another concept "left",
the concept role relation allows to add the qualifier
"has-laterality: left" to a primary code "leg" to
construct the meaning "left leg". In this example
"has-laterality" is the CR.name.
Specifies the manner in which
the concept role value contributes to the
meaning of a code phrase. For example, if
SNOMED RT defines a concept "leg", a role
relation "has-laterality", and another concept "left",
the concept role relation allows to add the qualifier
"has-laterality: left" to a primary code "leg" to
construct the meaning "left leg". In this example
"has-laterality" is the CR.name.
The concept that modifies the
primary code of a code phrase through the
role relation. For example, if SNOMED RT
defines a concept "leg", a role relation
"has-laterality", and another concept "left", the
concept role relation allows adding the qualifier
"has-laterality: left" to a primary code "leg" to
construct the meaning "left leg". In this example
"left" is the CR.value.
The concept that modifies the
primary code of a code phrase through the
role relation. For example, if SNOMED RT
defines a concept "leg", a role relation
"has-laterality", and another concept "left", the
concept role relation allows adding the qualifier
"has-laterality: left" to a primary code "leg" to
construct the meaning "left leg". In this example
"left" is the CR.value.
The concept that modifies the
primary code of a code phrase through the
role relation. For example, if SNOMED RT
defines a concept "leg", a role relation
"has-laterality", and another concept "left", the
concept role relation allows adding the qualifier
"has-laterality: left" to a primary code "leg" to
construct the meaning "left leg". In this example
"left" is the CR.value.
The concept that modifies the
primary code of a code phrase through the
role relation. For example, if SNOMED RT
defines a concept "leg", a role relation
"has-laterality", and another concept "left", the
concept role relation allows adding the qualifier
"has-laterality: left" to a primary code "leg" to
construct the meaning "left leg". In this example
"left" is the CR.value.
The concept that modifies the
primary code of a code phrase through the
role relation. For example, if SNOMED RT
defines a concept "leg", a role relation
"has-laterality", and another concept "left", the
concept role relation allows adding the qualifier
"has-laterality: left" to a primary code "leg" to
construct the meaning "left leg". In this example
"left" is the CR.value.
The concept that modifies the
primary code of a code phrase through the
role relation. For example, if SNOMED RT
defines a concept "leg", a role relation
"has-laterality", and another concept "left", the
concept role relation allows adding the qualifier
"has-laterality: left" to a primary code "leg" to
construct the meaning "left leg". In this example
"left" is the CR.value.
The concept that modifies the
primary code of a code phrase through the
role relation. For example, if SNOMED RT
defines a concept "leg", a role relation
"has-laterality", and another concept "left", the
concept role relation allows adding the qualifier
"has-laterality: left" to a primary code "leg" to
construct the meaning "left leg". In this example
"left" is the CR.value.
Indicates if the sense of the role
name is inverted. This can be used in cases where
the underlying code system defines inversion but
does not provide reciprocal pairs of role names. By
default, inverted is false.
Indicates if the sense of the role
name is inverted. This can be used in cases where
the underlying code system defines inversion but
does not provide reciprocal pairs of role names. By
default, inverted is false.
Indicates if the sense of the role
name is inverted. This can be used in cases where
the underlying code system defines inversion but
does not provide reciprocal pairs of role names. By
default, inverted is false.
Indicates if the sense of the role
name is inverted. This can be used in cases where
the underlying code system defines inversion but
does not provide reciprocal pairs of role names. By
default, inverted is false.
Indicates if the sense of the role
name is inverted. This can be used in cases where
the underlying code system defines inversion but
does not provide reciprocal pairs of role names. By
default, inverted is false.
Indicates if the sense of the role
name is inverted. This can be used in cases where
the underlying code system defines inversion but
does not provide reciprocal pairs of role names. By
default, inverted is false.
Indicates if the sense of the role
name is inverted. This can be used in cases where
the underlying code system defines inversion but
does not provide reciprocal pairs of role names. By
default, inverted is false.
Coded data, consists of a code, display name, code
system, and original text. Used when a single code value must be sent.
Coded data, consists of a code, display name, code
system, and original text. Used when a single code value must be sent.
Coded data, consists of a code, display name, code
system, and original text. Used when a single code value must be sent.
Coded data, consists of a code, display name, code
system, and original text. Used when a single code value must be sent.
Coded data, consists of a code, display name, code
system, and original text. Used when a single code value must be sent.
Coded data, consists of a code, display name, code
system, and original text. Used when a single code value must be sent.
Coded data, consists of a code, display name, code
system, and original text. Used when a single code value must be sent.
The text or phrase used as
the basis for the coding.
The text or phrase used as
the basis for the coding.
The text or phrase used as
the basis for the coding.
The text or phrase used as
the basis for the coding.
The text or phrase used as
the basis for the coding.
The text or phrase used as
the basis for the coding.
The text or phrase used as
the basis for the coding.
Coded data, consists of a coded value (CV)
and, optionally, coded value(s) from other coding systems that identify
the same concept. Used when alternative codes may exist.
Coded data, consists of a coded value (CV)
and, optionally, coded value(s) from other coding systems that identify
the same concept. Used when alternative codes may exist.
Coded data, consists of a coded value (CV)
and, optionally, coded value(s) from other coding systems that identify
the same concept. Used when alternative codes may exist.
Coded data, consists of a coded value (CV)
and, optionally, coded value(s) from other coding systems that identify
the same concept. Used when alternative codes may exist.
Coded data, consists of a coded value (CV)
and, optionally, coded value(s) from other coding systems that identify
the same concept. Used when alternative codes may exist.
Coded data, consists of a coded value (CV)
and, optionally, coded value(s) from other coding systems that identify
the same concept. Used when alternative codes may exist.
Coded data, consists of a coded value (CV)
and, optionally, coded value(s) from other coding systems that identify
the same concept. Used when alternative codes may exist.
A unique identifier string is a character string which
identifies an object in a globally unique and timeless manner. The
allowable formats and values and procedures of this data type are
strictly controlled by HL7. At this time, user-assigned identifiers may
be certain character representations of ISO Object Identifiers (OID) and
DCE Universally Unique Identifiers (UUID). HL7 also reserves
the right to assign other forms of UIDs, such as mnemonic identifiers
for code systems.
A unique identifier string is a character string which
identifies an object in a globally unique and timeless manner. The
allowable formats and values and procedures of this data type are
strictly controlled by HL7. At this time, user-assigned identifiers may
be certain character representations of ISO Object Identifiers (OID) and
DCE Universally Unique Identifiers (UUID). HL7 also reserves
the right to assign other forms of UIDs, such as mnemonic identifiers
for code systems.
A unique identifier string is a character string which
identifies an object in a globally unique and timeless manner. The
allowable formats and values and procedures of this data type are
strictly controlled by HL7. At this time, user-assigned identifiers may
be certain character representations of ISO Object Identifiers (OID) and
DCE Universally Unique Identifiers (UUID). HL7 also reserves
the right to assign other forms of UIDs, such as mnemonic identifiers
for code systems.
A unique identifier string is a character string which
identifies an object in a globally unique and timeless manner. The
allowable formats and values and procedures of this data type are
strictly controlled by HL7. At this time, user-assigned identifiers may
be certain character representations of ISO Object Identifiers (OID) and
DCE Universally Unique Identifiers (UUID). HL7 also reserves
the right to assign other forms of UIDs, such as mnemonic identifiers
for code systems.
A unique identifier string is a character string which
identifies an object in a globally unique and timeless manner. The
allowable formats and values and procedures of this data type are
strictly controlled by HL7. At this time, user-assigned identifiers may
be certain character representations of ISO Object Identifiers (OID) and
DCE Universally Unique Identifiers (UUID). HL7 also reserves
the right to assign other forms of UIDs, such as mnemonic identifiers
for code systems.
A unique identifier string is a character string which
identifies an object in a globally unique and timeless manner. The
allowable formats and values and procedures of this data type are
strictly controlled by HL7. At this time, user-assigned identifiers may
be certain character representations of ISO Object Identifiers (OID) and
DCE Universally Unique Identifiers (UUID). HL7 also reserves
the right to assign other forms of UIDs, such as mnemonic identifiers
for code systems.
A unique identifier string is a character string which
identifies an object in a globally unique and timeless manner. The
allowable formats and values and procedures of this data type are
strictly controlled by HL7. At this time, user-assigned identifiers may
be certain character representations of ISO Object Identifiers (OID) and
DCE Universally Unique Identifiers (UUID). HL7 also reserves
the right to assign other forms of UIDs, such as mnemonic identifiers
for code systems.
The character string data type stands for text data,
primarily intended for machine processing (e.g., sorting, querying,
indexing, etc.) Used for names, symbols, and formal expressions.
The character string data type stands for text data,
primarily intended for machine processing (e.g., sorting, querying,
indexing, etc.) Used for names, symbols, and formal expressions.
The character string data type stands for text data,
primarily intended for machine processing (e.g., sorting, querying,
indexing, etc.) Used for names, symbols, and formal expressions.
The character string data type stands for text data,
primarily intended for machine processing (e.g., sorting, querying,
indexing, etc.) Used for names, symbols, and formal expressions.
The character string data type stands for text data,
primarily intended for machine processing (e.g., sorting, querying,
indexing, etc.) Used for names, symbols, and formal expressions.
The character string data type stands for text data,
primarily intended for machine processing (e.g., sorting, querying,
indexing, etc.) Used for names, symbols, and formal expressions.
The character string data type stands for text data,
primarily intended for machine processing (e.g., sorting, querying,
indexing, etc.) Used for names, symbols, and formal expressions.
Integer numbers (-1,0,1,2, 100, 3398129, etc.) are
precise numbers that are results of counting and enumerating.
Integer numbers are discrete, the set of integers is infinite but
countable. No arbitrary limit is imposed on the range of integer
numbers. Two NULL flavors are defined for the positive and negative
infinity.
Integer numbers (-1,0,1,2, 100, 3398129, etc.) are
precise numbers that are results of counting and enumerating.
Integer numbers are discrete, the set of integers is infinite but
countable. No arbitrary limit is imposed on the range of integer
numbers. Two NULL flavors are defined for the positive and negative
infinity.
Integer numbers (-1,0,1,2, 100, 3398129, etc.) are
precise numbers that are results of counting and enumerating.
Integer numbers are discrete, the set of integers is infinite but
countable. No arbitrary limit is imposed on the range of integer
numbers. Two NULL flavors are defined for the positive and negative
infinity.
Integer numbers (-1,0,1,2, 100, 3398129, etc.) are
precise numbers that are results of counting and enumerating.
Integer numbers are discrete, the set of integers is infinite but
countable. No arbitrary limit is imposed on the range of integer
numbers. Two NULL flavors are defined for the positive and negative
infinity.
Integer numbers (-1,0,1,2, 100, 3398129, etc.) are
precise numbers that are results of counting and enumerating.
Integer numbers are discrete, the set of integers is infinite but
countable. No arbitrary limit is imposed on the range of integer
numbers. Two NULL flavors are defined for the positive and negative
infinity.
Integer numbers (-1,0,1,2, 100, 3398129, etc.) are
precise numbers that are results of counting and enumerating.
Integer numbers are discrete, the set of integers is infinite but
countable. No arbitrary limit is imposed on the range of integer
numbers. Two NULL flavors are defined for the positive and negative
infinity.
Integer numbers (-1,0,1,2, 100, 3398129, etc.) are
precise numbers that are results of counting and enumerating.
Integer numbers are discrete, the set of integers is infinite but
countable. No arbitrary limit is imposed on the range of integer
numbers. Two NULL flavors are defined for the positive and negative
infinity.
The quantity in which the bag item
occurs in its containing bag.
The quantity in which the bag item
occurs in its containing bag.
The quantity in which the bag item
occurs in its containing bag.
The quantity in which the bag item
occurs in its containing bag.
The quantity in which the bag item
occurs in its containing bag.
The quantity in which the bag item
occurs in its containing bag.
The quantity in which the bag item
occurs in its containing bag.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A dimensioned quantity expressing the result of a
measurement act.
A dimensioned quantity expressing the result of a
measurement act.
A dimensioned quantity expressing the result of a
measurement act.
A dimensioned quantity expressing the result of a
measurement act.
A dimensioned quantity expressing the result of a
measurement act.
A dimensioned quantity expressing the result of a
measurement act.
A dimensioned quantity expressing the result of a
measurement act.
An alternative representation
of the same physical quantity expressed in a
different unit, of a different unit code
system and possibly with a different value.
An alternative representation
of the same physical quantity expressed in a
different unit, of a different unit code
system and possibly with a different value.
An alternative representation
of the same physical quantity expressed in a
different unit, of a different unit code
system and possibly with a different value.
An alternative representation
of the same physical quantity expressed in a
different unit, of a different unit code
system and possibly with a different value.
An alternative representation
of the same physical quantity expressed in a
different unit, of a different unit code
system and possibly with a different value.
An alternative representation
of the same physical quantity expressed in a
different unit, of a different unit code
system and possibly with a different value.
An alternative representation
of the same physical quantity expressed in a
different unit, of a different unit code
system and possibly with a different value.
The unit of measure specified in the
Unified Code for Units of Measure (UCUM)
[http://aurora.rg.iupui.edu/UCUM].
The unit of measure specified in the
Unified Code for Units of Measure (UCUM)
[http://aurora.rg.iupui.edu/UCUM].
The unit of measure specified in the
Unified Code for Units of Measure (UCUM)
[http://aurora.rg.iupui.edu/UCUM].
The unit of measure specified in the
Unified Code for Units of Measure (UCUM)
[http://aurora.rg.iupui.edu/UCUM].
The unit of measure specified in the
Unified Code for Units of Measure (UCUM)
[http://aurora.rg.iupui.edu/UCUM].
The unit of measure specified in the
Unified Code for Units of Measure (UCUM)
[http://aurora.rg.iupui.edu/UCUM].
The unit of measure specified in the
Unified Code for Units of Measure (UCUM)
[http://aurora.rg.iupui.edu/UCUM].
The magnitude of the quantity
measured in terms of the unit.
The magnitude of the quantity
measured in terms of the unit.
The magnitude of the quantity
measured in terms of the unit.
The magnitude of the quantity
measured in terms of the unit.
The magnitude of the quantity
measured in terms of the unit.
The magnitude of the quantity
measured in terms of the unit.
The magnitude of the quantity
measured in terms of the unit.
A representation of a physical quantity in a unit from
any code system. Used to show alternative representation for a physical
quantity.
A representation of a physical quantity in a unit from
any code system. Used to show alternative representation for a physical
quantity.
A representation of a physical quantity in a unit from
any code system. Used to show alternative representation for a physical
quantity.
A representation of a physical quantity in a unit from
any code system. Used to show alternative representation for a physical
quantity.
A representation of a physical quantity in a unit from
any code system. Used to show alternative representation for a physical
quantity.
A representation of a physical quantity in a unit from
any code system. Used to show alternative representation for a physical
quantity.
A representation of a physical quantity in a unit from
any code system. Used to show alternative representation for a physical
quantity.
The magnitude of the measurement
value in terms of the unit specified in the code.
The magnitude of the measurement
value in terms of the unit specified in the code.
The magnitude of the measurement
value in terms of the unit specified in the code.
The magnitude of the measurement
value in terms of the unit specified in the code.
The magnitude of the measurement
value in terms of the unit specified in the code.
The magnitude of the measurement
value in terms of the unit specified in the code.
The magnitude of the measurement
value in terms of the unit specified in the code.
Fractional numbers. Typically used whenever quantities
are measured, estimated, or computed from other real numbers. The
typical representation is decimal, where the number of significant
decimal digits is known as the precision. Real numbers are needed beyond
integers whenever quantities of the real world are measured,
estimated, or computed from other real numbers. The term "Real number"
in this specification is used to mean that fractional values are covered
without necessarily implying the full set of the mathematical real
numbers.
Fractional numbers. Typically used whenever quantities
are measured, estimated, or computed from other real numbers. The
typical representation is decimal, where the number of significant
decimal digits is known as the precision. Real numbers are needed beyond
integers whenever quantities of the real world are measured,
estimated, or computed from other real numbers. The term "Real number"
in this specification is used to mean that fractional values are covered
without necessarily implying the full set of the mathematical real
numbers.
Fractional numbers. Typically used whenever quantities
are measured, estimated, or computed from other real numbers. The
typical representation is decimal, where the number of significant
decimal digits is known as the precision. Real numbers are needed beyond
integers whenever quantities of the real world are measured,
estimated, or computed from other real numbers. The term "Real number"
in this specification is used to mean that fractional values are covered
without necessarily implying the full set of the mathematical real
numbers.
Fractional numbers. Typically used whenever quantities
are measured, estimated, or computed from other real numbers. The
typical representation is decimal, where the number of significant
decimal digits is known as the precision. Real numbers are needed beyond
integers whenever quantities of the real world are measured,
estimated, or computed from other real numbers. The term "Real number"
in this specification is used to mean that fractional values are covered
without necessarily implying the full set of the mathematical real
numbers.
Fractional numbers. Typically used whenever quantities
are measured, estimated, or computed from other real numbers. The
typical representation is decimal, where the number of significant
decimal digits is known as the precision. Real numbers are needed beyond
integers whenever quantities of the real world are measured,
estimated, or computed from other real numbers. The term "Real number"
in this specification is used to mean that fractional values are covered
without necessarily implying the full set of the mathematical real
numbers.
Fractional numbers. Typically used whenever quantities
are measured, estimated, or computed from other real numbers. The
typical representation is decimal, where the number of significant
decimal digits is known as the precision. Real numbers are needed beyond
integers whenever quantities of the real world are measured,
estimated, or computed from other real numbers. The term "Real number"
in this specification is used to mean that fractional values are covered
without necessarily implying the full set of the mathematical real
numbers.
Fractional numbers. Typically used whenever quantities
are measured, estimated, or computed from other real numbers. The
typical representation is decimal, where the number of significant
decimal digits is known as the precision. Real numbers are needed beyond
integers whenever quantities of the real world are measured,
estimated, or computed from other real numbers. The term "Real number"
in this specification is used to mean that fractional values are covered
without necessarily implying the full set of the mathematical real
numbers.
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
vocSet: D10684 (C-0-D10684-cpt)
vocSet: D10684 (C-0-D10684-cpt)
vocSet: D10684 (C-0-D10684-cpt)
vocSet: D10684 (C-0-D10684-cpt)
vocSet: D10684 (C-0-D10684-cpt)
vocSet: D10684 (C-0-D10684-cpt)
vocSet: D10684 (C-0-D10684-cpt)
abstDomain: V10701 (C-0-D10684-V10701-cpt)
abstDomain: V10701 (C-0-D10684-V10701-cpt)
abstDomain: V10701 (C-0-D10684-V10701-cpt)
abstDomain: V10701 (C-0-D10684-V10701-cpt)
abstDomain: V10701 (C-0-D10684-V10701-cpt)
abstDomain: V10701 (C-0-D10684-V10701-cpt)
abstDomain: V10701 (C-0-D10684-V10701-cpt)
abstDomain: V10685 (C-0-D10684-V10685-cpt)
abstDomain: V10685 (C-0-D10684-V10685-cpt)
abstDomain: V10685 (C-0-D10684-V10685-cpt)
abstDomain: V10685 (C-0-D10684-V10685-cpt)
abstDomain: V10685 (C-0-D10684-V10685-cpt)
abstDomain: V10685 (C-0-D10684-V10685-cpt)
abstDomain: V10685 (C-0-D10684-V10685-cpt)
Coded data in its simplest form, consists of a code.
The code system and code system version is fixed by the context in
which the CS value occurs. CS is used for coded attributes that have a
single HL7-defined value set.
Coded data in its simplest form, consists of a code.
The code system and code system version is fixed by the context in
which the CS value occurs. CS is used for coded attributes that have a
single HL7-defined value set.
Coded data in its simplest form, consists of a code.
The code system and code system version is fixed by the context in
which the CS value occurs. CS is used for coded attributes that have a
single HL7-defined value set.
Coded data in its simplest form, consists of a code.
The code system and code system version is fixed by the context in
which the CS value occurs. CS is used for coded attributes that have a
single HL7-defined value set.
Coded data in its simplest form, consists of a code.
The code system and code system version is fixed by the context in
which the CS value occurs. CS is used for coded attributes that have a
single HL7-defined value set.
Coded data in its simplest form, consists of a code.
The code system and code system version is fixed by the context in
which the CS value occurs. CS is used for coded attributes that have a
single HL7-defined value set.
Coded data in its simplest form, consists of a code.
The code system and code system version is fixed by the context in
which the CS value occurs. CS is used for coded attributes that have a
single HL7-defined value set.
Coded data, where the domain from which the codeset comes
is ordered. The Coded Ordinal data type adds semantics related to
ordering so that models that make use of such domains may introduce
model elements that involve statements about the order of the terms in a
domain.
Coded data, where the domain from which the codeset comes
is ordered. The Coded Ordinal data type adds semantics related to
ordering so that models that make use of such domains may introduce
model elements that involve statements about the order of the terms in a
domain.
Coded data, where the domain from which the codeset comes
is ordered. The Coded Ordinal data type adds semantics related to
ordering so that models that make use of such domains may introduce
model elements that involve statements about the order of the terms in a
domain.
Coded data, where the domain from which the codeset comes
is ordered. The Coded Ordinal data type adds semantics related to
ordering so that models that make use of such domains may introduce
model elements that involve statements about the order of the terms in a
domain.
Coded data, where the domain from which the codeset comes
is ordered. The Coded Ordinal data type adds semantics related to
ordering so that models that make use of such domains may introduce
model elements that involve statements about the order of the terms in a
domain.
Coded data, where the domain from which the codeset comes
is ordered. The Coded Ordinal data type adds semantics related to
ordering so that models that make use of such domains may introduce
model elements that involve statements about the order of the terms in a
domain.
Coded data, where the domain from which the codeset comes
is ordered. The Coded Ordinal data type adds semantics related to
ordering so that models that make use of such domains may introduce
model elements that involve statements about the order of the terms in a
domain.
An identifier that uniquely identifies a thing or object.
Examples are object identifier for HL7 RIM objects, medical record
number, order id, service catalog item id, Vehicle Identification Number
(VIN), etc. Instance identifiers are defined based on ISO object
identifiers.
An identifier that uniquely identifies a thing or object.
Examples are object identifier for HL7 RIM objects, medical record
number, order id, service catalog item id, Vehicle Identification Number
(VIN), etc. Instance identifiers are defined based on ISO object
identifiers.
An identifier that uniquely identifies a thing or object.
Examples are object identifier for HL7 RIM objects, medical record
number, order id, service catalog item id, Vehicle Identification Number
(VIN), etc. Instance identifiers are defined based on ISO object
identifiers.
An identifier that uniquely identifies a thing or object.
Examples are object identifier for HL7 RIM objects, medical record
number, order id, service catalog item id, Vehicle Identification Number
(VIN), etc. Instance identifiers are defined based on ISO object
identifiers.
An identifier that uniquely identifies a thing or object.
Examples are object identifier for HL7 RIM objects, medical record
number, order id, service catalog item id, Vehicle Identification Number
(VIN), etc. Instance identifiers are defined based on ISO object
identifiers.
An identifier that uniquely identifies a thing or object.
Examples are object identifier for HL7 RIM objects, medical record
number, order id, service catalog item id, Vehicle Identification Number
(VIN), etc. Instance identifiers are defined based on ISO object
identifiers.
An identifier that uniquely identifies a thing or object.
Examples are object identifier for HL7 RIM objects, medical record
number, order id, service catalog item id, Vehicle Identification Number
(VIN), etc. Instance identifiers are defined based on ISO object
identifiers.
A human readable name or mnemonic
for the assigning authority. This name may be
provided solely for the convenience of unaided
humans interpreting an II value and can have no
computational meaning. Note: no automated
processing must depend on the assigning authority
name to be present in any form.
A human readable name or mnemonic
for the assigning authority. This name may be
provided solely for the convenience of unaided
humans interpreting an II value and can have no
computational meaning. Note: no automated
processing must depend on the assigning authority
name to be present in any form.
A human readable name or mnemonic
for the assigning authority. This name may be
provided solely for the convenience of unaided
humans interpreting an II value and can have no
computational meaning. Note: no automated
processing must depend on the assigning authority
name to be present in any form.
A human readable name or mnemonic
for the assigning authority. This name may be
provided solely for the convenience of unaided
humans interpreting an II value and can have no
computational meaning. Note: no automated
processing must depend on the assigning authority
name to be present in any form.
A human readable name or mnemonic
for the assigning authority. This name may be
provided solely for the convenience of unaided
humans interpreting an II value and can have no
computational meaning. Note: no automated
processing must depend on the assigning authority
name to be present in any form.
A human readable name or mnemonic
for the assigning authority. This name may be
provided solely for the convenience of unaided
humans interpreting an II value and can have no
computational meaning. Note: no automated
processing must depend on the assigning authority
name to be present in any form.
A human readable name or mnemonic
for the assigning authority. This name may be
provided solely for the convenience of unaided
humans interpreting an II value and can have no
computational meaning. Note: no automated
processing must depend on the assigning authority
name to be present in any form.
Specifies if the identifier is
intended for human display and data entry
(displayable = true) as opposed to pure machine
interoperation (displayable = false).
Specifies if the identifier is
intended for human display and data entry
(displayable = true) as opposed to pure machine
interoperation (displayable = false).
Specifies if the identifier is
intended for human display and data entry
(displayable = true) as opposed to pure machine
interoperation (displayable = false).
Specifies if the identifier is
intended for human display and data entry
(displayable = true) as opposed to pure machine
interoperation (displayable = false).
Specifies if the identifier is
intended for human display and data entry
(displayable = true) as opposed to pure machine
interoperation (displayable = false).
Specifies if the identifier is
intended for human display and data entry
(displayable = true) as opposed to pure machine
interoperation (displayable = false).
Specifies if the identifier is
intended for human display and data entry
(displayable = true) as opposed to pure machine
interoperation (displayable = false).
A character string as a unique
identifier within the scope of the identifier root.
A character string as a unique
identifier within the scope of the identifier root.
A character string as a unique
identifier within the scope of the identifier root.
A character string as a unique
identifier within the scope of the identifier root.
A character string as a unique
identifier within the scope of the identifier root.
A character string as a unique
identifier within the scope of the identifier root.
A character string as a unique
identifier within the scope of the identifier root.
A unique identifier that guarantees
the global uniqueness of the instance identifier.
The root alone may be the entire instance
identifier.
A unique identifier that guarantees
the global uniqueness of the instance identifier.
The root alone may be the entire instance
identifier.
A unique identifier that guarantees
the global uniqueness of the instance identifier.
The root alone may be the entire instance
identifier.
A unique identifier that guarantees
the global uniqueness of the instance identifier.
The root alone may be the entire instance
identifier.
A unique identifier that guarantees
the global uniqueness of the instance identifier.
The root alone may be the entire instance
identifier.
A unique identifier that guarantees
the global uniqueness of the instance identifier.
The root alone may be the entire instance
identifier.
A unique identifier that guarantees
the global uniqueness of the instance identifier.
The root alone may be the entire instance
identifier.
A name for an organization. A sequence of name parts.
A name for an organization. A sequence of name parts.
A name for an organization. A sequence of name parts.
A name for an organization. A sequence of name parts.
A name for an organization. A sequence of name parts.
A name for an organization. A sequence of name parts.
A name for an organization. A sequence of name parts.
A name for a person, organization, place or thing. A
sequence of name parts, such as given name or family name, prefix,
suffix, etc. Examples for entity name values are "Jim Bob Walton, Jr.",
"Health Level Seven, Inc.", "Lake Tahoe", etc. An entity name may be as
simple as a character string or may consist of several entity name
parts, such as, "Jim", "Bob", "Walton", and "Jr.", "Health Level Seven"
and "Inc.", "Lake" and "Tahoe".
A name for a person, organization, place or thing. A
sequence of name parts, such as given name or family name, prefix,
suffix, etc. Examples for entity name values are "Jim Bob Walton, Jr.",
"Health Level Seven, Inc.", "Lake Tahoe", etc. An entity name may be as
simple as a character string or may consist of several entity name
parts, such as, "Jim", "Bob", "Walton", and "Jr.", "Health Level Seven"
and "Inc.", "Lake" and "Tahoe".
A name for a person, organization, place or thing. A
sequence of name parts, such as given name or family name, prefix,
suffix, etc. Examples for entity name values are "Jim Bob Walton, Jr.",
"Health Level Seven, Inc.", "Lake Tahoe", etc. An entity name may be as
simple as a character string or may consist of several entity name
parts, such as, "Jim", "Bob", "Walton", and "Jr.", "Health Level Seven"
and "Inc.", "Lake" and "Tahoe".
A name for a person, organization, place or thing. A
sequence of name parts, such as given name or family name, prefix,
suffix, etc. Examples for entity name values are "Jim Bob Walton, Jr.",
"Health Level Seven, Inc.", "Lake Tahoe", etc. An entity name may be as
simple as a character string or may consist of several entity name
parts, such as, "Jim", "Bob", "Walton", and "Jr.", "Health Level Seven"
and "Inc.", "Lake" and "Tahoe".
A name for a person, organization, place or thing. A
sequence of name parts, such as given name or family name, prefix,
suffix, etc. Examples for entity name values are "Jim Bob Walton, Jr.",
"Health Level Seven, Inc.", "Lake Tahoe", etc. An entity name may be as
simple as a character string or may consist of several entity name
parts, such as, "Jim", "Bob", "Walton", and "Jr.", "Health Level Seven"
and "Inc.", "Lake" and "Tahoe".
A name for a person, organization, place or thing. A
sequence of name parts, such as given name or family name, prefix,
suffix, etc. Examples for entity name values are "Jim Bob Walton, Jr.",
"Health Level Seven, Inc.", "Lake Tahoe", etc. An entity name may be as
simple as a character string or may consist of several entity name
parts, such as, "Jim", "Bob", "Walton", and "Jr.", "Health Level Seven"
and "Inc.", "Lake" and "Tahoe".
A name for a person, organization, place or thing. A
sequence of name parts, such as given name or family name, prefix,
suffix, etc. Examples for entity name values are "Jim Bob Walton, Jr.",
"Health Level Seven, Inc.", "Lake Tahoe", etc. An entity name may be as
simple as a character string or may consist of several entity name
parts, such as, "Jim", "Bob", "Walton", and "Jr.", "Health Level Seven"
and "Inc.", "Lake" and "Tahoe".
An interval of time
specifying the time during which the name is
or was used for the entity. This accomodates
the fact that people change names for
people, places and things.
An interval of time
specifying the time during which the name is
or was used for the entity. This accomodates
the fact that people change names for
people, places and things.
An interval of time
specifying the time during which the name is
or was used for the entity. This accomodates
the fact that people change names for
people, places and things.
An interval of time
specifying the time during which the name is
or was used for the entity. This accomodates
the fact that people change names for
people, places and things.
An interval of time
specifying the time during which the name is
or was used for the entity. This accomodates
the fact that people change names for
people, places and things.
An interval of time
specifying the time during which the name is
or was used for the entity. This accomodates
the fact that people change names for
people, places and things.
An interval of time
specifying the time during which the name is
or was used for the entity. This accomodates
the fact that people change names for
people, places and things.
A set of codes advising a system or
user which name in a set of like names to select
for a given purpose. A name without specific use
code might be a default name useful for any
purpose, but a name with a specific use code would
be preferred for that respective purpose.
A set of codes advising a system or
user which name in a set of like names to select
for a given purpose. A name without specific use
code might be a default name useful for any
purpose, but a name with a specific use code would
be preferred for that respective purpose.
A set of codes advising a system or
user which name in a set of like names to select
for a given purpose. A name without specific use
code might be a default name useful for any
purpose, but a name with a specific use code would
be preferred for that respective purpose.
A set of codes advising a system or
user which name in a set of like names to select
for a given purpose. A name without specific use
code might be a default name useful for any
purpose, but a name with a specific use code would
be preferred for that respective purpose.
A set of codes advising a system or
user which name in a set of like names to select
for a given purpose. A name without specific use
code might be a default name useful for any
purpose, but a name with a specific use code would
be preferred for that respective purpose.
A set of codes advising a system or
user which name in a set of like names to select
for a given purpose. A name without specific use
code might be a default name useful for any
purpose, but a name with a specific use code would
be preferred for that respective purpose.
A set of codes advising a system or
user which name in a set of like names to select
for a given purpose. A name without specific use
code might be a default name useful for any
purpose, but a name with a specific use code would
be preferred for that respective purpose.
A character string token representing a part of a name.
May have a type code signifying the role of the part in the whole entity
name, and a qualifier code for more detail about the name part type.
Typical name parts for person names are given names, and family names,
titles, etc.
A character string token representing a part of a name.
May have a type code signifying the role of the part in the whole entity
name, and a qualifier code for more detail about the name part type.
Typical name parts for person names are given names, and family names,
titles, etc.
A character string token representing a part of a name.
May have a type code signifying the role of the part in the whole entity
name, and a qualifier code for more detail about the name part type.
Typical name parts for person names are given names, and family names,
titles, etc.
A character string token representing a part of a name.
May have a type code signifying the role of the part in the whole entity
name, and a qualifier code for more detail about the name part type.
Typical name parts for person names are given names, and family names,
titles, etc.
A character string token representing a part of a name.
May have a type code signifying the role of the part in the whole entity
name, and a qualifier code for more detail about the name part type.
Typical name parts for person names are given names, and family names,
titles, etc.
A character string token representing a part of a name.
May have a type code signifying the role of the part in the whole entity
name, and a qualifier code for more detail about the name part type.
Typical name parts for person names are given names, and family names,
titles, etc.
A character string token representing a part of a name.
May have a type code signifying the role of the part in the whole entity
name, and a qualifier code for more detail about the name part type.
Typical name parts for person names are given names, and family names,
titles, etc.
Indicates whether the name part is a
given name, family name, prefix, suffix, etc.
Indicates whether the name part is a
given name, family name, prefix, suffix, etc.
Indicates whether the name part is a
given name, family name, prefix, suffix, etc.
Indicates whether the name part is a
given name, family name, prefix, suffix, etc.
Indicates whether the name part is a
given name, family name, prefix, suffix, etc.
Indicates whether the name part is a
given name, family name, prefix, suffix, etc.
Indicates whether the name part is a
given name, family name, prefix, suffix, etc.
The qualifier is a set of codes each
of which specifies a certain subcategory of the
name part in addition to the main name part type.
For example, a given name may be flagged as a
nickname, a family name may be a pseudonym or a
name of public records.
The qualifier is a set of codes each
of which specifies a certain subcategory of the
name part in addition to the main name part type.
For example, a given name may be flagged as a
nickname, a family name may be a pseudonym or a
name of public records.
The qualifier is a set of codes each
of which specifies a certain subcategory of the
name part in addition to the main name part type.
For example, a given name may be flagged as a
nickname, a family name may be a pseudonym or a
name of public records.
The qualifier is a set of codes each
of which specifies a certain subcategory of the
name part in addition to the main name part type.
For example, a given name may be flagged as a
nickname, a family name may be a pseudonym or a
name of public records.
The qualifier is a set of codes each
of which specifies a certain subcategory of the
name part in addition to the main name part type.
For example, a given name may be flagged as a
nickname, a family name may be a pseudonym or a
name of public records.
The qualifier is a set of codes each
of which specifies a certain subcategory of the
name part in addition to the main name part type.
For example, a given name may be flagged as a
nickname, a family name may be a pseudonym or a
name of public records.
The qualifier is a set of codes each
of which specifies a certain subcategory of the
name part in addition to the main name part type.
For example, a given name may be flagged as a
nickname, a family name may be a pseudonym or a
name of public records.
vocSet: D15880 (C-0-D15880-cpt)
vocSet: D15880 (C-0-D15880-cpt)
vocSet: D15880 (C-0-D15880-cpt)
vocSet: D15880 (C-0-D15880-cpt)
vocSet: D15880 (C-0-D15880-cpt)
vocSet: D15880 (C-0-D15880-cpt)
vocSet: D15880 (C-0-D15880-cpt)
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Coded data, consists of a code, display name, code
system, and original text. Used when a single code value must be sent.
Coded data, consists of a code, display name, code
system, and original text. Used when a single code value must be sent.
Coded data, consists of a code, display name, code
system, and original text. Used when a single code value must be sent.
Coded data, consists of a code, display name, code
system, and original text. Used when a single code value must be sent.
Coded data, consists of a code, display name, code
system, and original text. Used when a single code value must be sent.
Coded data, consists of a code, display name, code
system, and original text. Used when a single code value must be sent.
Coded data, consists of a code, display name, code
system, and original text. Used when a single code value must be sent.
specDomain: V11595
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-V11595-cpt)
specDomain: V11595
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-V11595-cpt)
specDomain: V11595
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-V11595-cpt)
specDomain: V11595
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-V11595-cpt)
specDomain: V11595
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-V11595-cpt)
specDomain: V11595
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-V11595-cpt)
specDomain: V11595
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-V11595-cpt)
specDomain: V10889 (C-0-D10882-V19463-V10889-cpt)
specDomain: V10889 (C-0-D10882-V19463-V10889-cpt)
specDomain: V10889 (C-0-D10882-V19463-V10889-cpt)
specDomain: V10889 (C-0-D10882-V19463-V10889-cpt)
specDomain: V10889 (C-0-D10882-V19463-V10889-cpt)
specDomain: V10889 (C-0-D10882-V19463-V10889-cpt)
specDomain: V10889 (C-0-D10882-V19463-V10889-cpt)
specDomain: V13940 (C-0-D11555-V13940-cpt)
specDomain: V13940 (C-0-D11555-V13940-cpt)
specDomain: V13940 (C-0-D11555-V13940-cpt)
specDomain: V13940 (C-0-D11555-V13940-cpt)
specDomain: V13940 (C-0-D11555-V13940-cpt)
specDomain: V13940 (C-0-D11555-V13940-cpt)
specDomain: V13940 (C-0-D11555-V13940-cpt)
A restriction of entity name that is effectively a simple
string used for a simple name for things and places.
A restriction of entity name that is effectively a simple
string used for a simple name for things and places.
A restriction of entity name that is effectively a simple
string used for a simple name for things and places.
A restriction of entity name that is effectively a simple
string used for a simple name for things and places.
A restriction of entity name that is effectively a simple
string used for a simple name for things and places.
A restriction of entity name that is effectively a simple
string used for a simple name for things and places.
A restriction of entity name that is effectively a simple
string used for a simple name for things and places.
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
specDomain: V19584 (C-0-D10901-V10286-V19584-cpt)
specDomain: V19584 (C-0-D10901-V10286-V19584-cpt)
specDomain: V19584 (C-0-D10901-V10286-V19584-cpt)
specDomain: V19584 (C-0-D10901-V10286-V19584-cpt)
specDomain: V19584 (C-0-D10901-V10286-V19584-cpt)
specDomain: V19584 (C-0-D10901-V10286-V19584-cpt)
specDomain: V19584 (C-0-D10901-V10286-V19584-cpt)
specDomain: V11580
(C-0-D11555-V13940-V19313-V19105-V11580-cpt)
specDomain: V11580
(C-0-D11555-V13940-V19313-V19105-V11580-cpt)
specDomain: V11580
(C-0-D11555-V13940-V19313-V19105-V11580-cpt)
specDomain: V11580
(C-0-D11555-V13940-V19313-V19105-V11580-cpt)
specDomain: V11580
(C-0-D11555-V13940-V19313-V19105-V11580-cpt)
specDomain: V11580
(C-0-D11555-V13940-V19313-V19105-V11580-cpt)
specDomain: V11580
(C-0-D11555-V13940-V19313-V19105-V11580-cpt)
specDomain: V11622
(C-0-D10882-V13922-V10883-V13934-V11622-cpt)
specDomain: V11622
(C-0-D10882-V13922-V10883-V13934-V11622-cpt)
specDomain: V11622
(C-0-D10882-V13922-V10883-V13934-V11622-cpt)
specDomain: V11622
(C-0-D10882-V13922-V10883-V13934-V11622-cpt)
specDomain: V11622
(C-0-D10882-V13922-V10883-V13934-V11622-cpt)
specDomain: V11622
(C-0-D10882-V13922-V10883-V13934-V11622-cpt)
specDomain: V11622
(C-0-D10882-V13922-V10883-V13934-V11622-cpt)
vocSet: D10878 (C-0-D10878-cpt)
vocSet: D10878 (C-0-D10878-cpt)
vocSet: D10878 (C-0-D10878-cpt)
vocSet: D10878 (C-0-D10878-cpt)
vocSet: D10878 (C-0-D10878-cpt)
vocSet: D10878 (C-0-D10878-cpt)
vocSet: D10878 (C-0-D10878-cpt)
specDomain: V10418
(C-0-D11555-V13940-V19313-V19105-V10418-cpt)
specDomain: V10418
(C-0-D11555-V13940-V19313-V19105-V10418-cpt)
specDomain: V10418
(C-0-D11555-V13940-V19313-V19105-V10418-cpt)
specDomain: V10418
(C-0-D11555-V13940-V19313-V19105-V10418-cpt)
specDomain: V10418
(C-0-D11555-V13940-V19313-V19105-V10418-cpt)
specDomain: V10418
(C-0-D11555-V13940-V19313-V19105-V10418-cpt)
specDomain: V10418
(C-0-D11555-V13940-V19313-V19105-V10418-cpt)
specDomain: V10430
(C-0-D11555-V13940-V10429-V10430-cpt)
specDomain: V10430
(C-0-D11555-V13940-V10429-V10430-cpt)
specDomain: V10430
(C-0-D11555-V13940-V10429-V10430-cpt)
specDomain: V10430
(C-0-D11555-V13940-V10429-V10430-cpt)
specDomain: V10430
(C-0-D11555-V13940-V10429-V10430-cpt)
specDomain: V10430
(C-0-D11555-V13940-V10429-V10430-cpt)
specDomain: V10430
(C-0-D11555-V13940-V10429-V10430-cpt)
specDomain: V13934
(C-0-D10882-V13922-V10883-V13934-cpt)
specDomain: V13934
(C-0-D10882-V13922-V10883-V13934-cpt)
specDomain: V13934
(C-0-D10882-V13922-V10883-V13934-cpt)
specDomain: V13934
(C-0-D10882-V13922-V10883-V13934-cpt)
specDomain: V13934
(C-0-D10882-V13922-V10883-V13934-cpt)
specDomain: V13934
(C-0-D10882-V13922-V10883-V13934-cpt)
specDomain: V13934
(C-0-D10882-V13922-V10883-V13934-cpt)
specDomain: V10441
(C-0-D11555-V13940-V10428-V10441-cpt)
specDomain: V10441
(C-0-D11555-V13940-V10428-V10441-cpt)
specDomain: V10441
(C-0-D11555-V13940-V10428-V10441-cpt)
specDomain: V10441
(C-0-D11555-V13940-V10428-V10441-cpt)
specDomain: V10441
(C-0-D11555-V13940-V10428-V10441-cpt)
specDomain: V10441
(C-0-D11555-V13940-V10428-V10441-cpt)
specDomain: V10441
(C-0-D11555-V13940-V10428-V10441-cpt)
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that is being
divided in the ratio. The default is the
integer number 1 (one).
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
The quantity that devides the
numerator in the ratio. The default is the
integer number 1 (one). The denominator must
not be zero.
A monetary amount is a quantity expressing the amount of
money in some currency. Currencies are the units in which monetary
amounts are denominated in different economic regions. While the
monetary amount is a single kind of quantity (money) the exchange rates
between the different units are variable. This is the principle
difference between physical quantity and monetary amounts, and the
reason why currency units are not physical units.
A monetary amount is a quantity expressing the amount of
money in some currency. Currencies are the units in which monetary
amounts are denominated in different economic regions. While the
monetary amount is a single kind of quantity (money) the exchange rates
between the different units are variable. This is the principle
difference between physical quantity and monetary amounts, and the
reason why currency units are not physical units.
A monetary amount is a quantity expressing the amount of
money in some currency. Currencies are the units in which monetary
amounts are denominated in different economic regions. While the
monetary amount is a single kind of quantity (money) the exchange rates
between the different units are variable. This is the principle
difference between physical quantity and monetary amounts, and the
reason why currency units are not physical units.
A monetary amount is a quantity expressing the amount of
money in some currency. Currencies are the units in which monetary
amounts are denominated in different economic regions. While the
monetary amount is a single kind of quantity (money) the exchange rates
between the different units are variable. This is the principle
difference between physical quantity and monetary amounts, and the
reason why currency units are not physical units.
A monetary amount is a quantity expressing the amount of
money in some currency. Currencies are the units in which monetary
amounts are denominated in different economic regions. While the
monetary amount is a single kind of quantity (money) the exchange rates
between the different units are variable. This is the principle
difference between physical quantity and monetary amounts, and the
reason why currency units are not physical units.
A monetary amount is a quantity expressing the amount of
money in some currency. Currencies are the units in which monetary
amounts are denominated in different economic regions. While the
monetary amount is a single kind of quantity (money) the exchange rates
between the different units are variable. This is the principle
difference between physical quantity and monetary amounts, and the
reason why currency units are not physical units.
A monetary amount is a quantity expressing the amount of
money in some currency. Currencies are the units in which monetary
amounts are denominated in different economic regions. While the
monetary amount is a single kind of quantity (money) the exchange rates
between the different units are variable. This is the principle
difference between physical quantity and monetary amounts, and the
reason why currency units are not physical units.
The currency unit as defined in ISO
4217.
The currency unit as defined in ISO
4217.
The currency unit as defined in ISO
4217.
The currency unit as defined in ISO
4217.
The currency unit as defined in ISO
4217.
The currency unit as defined in ISO
4217.
The currency unit as defined in ISO
4217.
The magnitude of the monetary amount
in terms of the currency unit.
The magnitude of the monetary amount
in terms of the currency unit.
The magnitude of the monetary amount
in terms of the currency unit.
The magnitude of the monetary amount
in terms of the currency unit.
The magnitude of the monetary amount
in terms of the currency unit.
The magnitude of the monetary amount
in terms of the currency unit.
The magnitude of the monetary amount
in terms of the currency unit.
abstDomain: V19375 (C-0-D10196-V19375-cpt)
abstDomain: V19375 (C-0-D10196-V19375-cpt)
abstDomain: V19375 (C-0-D10196-V19375-cpt)
abstDomain: V19375 (C-0-D10196-V19375-cpt)
abstDomain: V19375 (C-0-D10196-V19375-cpt)
abstDomain: V19375 (C-0-D10196-V19375-cpt)
abstDomain: V19375 (C-0-D10196-V19375-cpt)
vocSet: D10901 (C-0-D10901-cpt)
vocSet: D10901 (C-0-D10901-cpt)
vocSet: D10901 (C-0-D10901-cpt)
vocSet: D10901 (C-0-D10901-cpt)
vocSet: D10901 (C-0-D10901-cpt)
vocSet: D10901 (C-0-D10901-cpt)
vocSet: D10901 (C-0-D10901-cpt)
vocSet: D16031 (C-0-D16031-cpt)
vocSet: D16031 (C-0-D16031-cpt)
vocSet: D16031 (C-0-D16031-cpt)
vocSet: D16031 (C-0-D16031-cpt)
vocSet: D16031 (C-0-D16031-cpt)
vocSet: D16031 (C-0-D16031-cpt)
vocSet: D16031 (C-0-D16031-cpt)
abstDomain: V18934 (C-0-D16478-V18934-cpt)
abstDomain: V18934 (C-0-D16478-V18934-cpt)
abstDomain: V18934 (C-0-D16478-V18934-cpt)
abstDomain: V18934 (C-0-D16478-V18934-cpt)
abstDomain: V18934 (C-0-D16478-V18934-cpt)
abstDomain: V18934 (C-0-D16478-V18934-cpt)
abstDomain: V18934 (C-0-D16478-V18934-cpt)
abstDomain: V18937 (C-0-D16478-V18937-cpt)
abstDomain: V18937 (C-0-D16478-V18937-cpt)
abstDomain: V18937 (C-0-D16478-V18937-cpt)
abstDomain: V18937 (C-0-D16478-V18937-cpt)
abstDomain: V18937 (C-0-D16478-V18937-cpt)
abstDomain: V18937 (C-0-D16478-V18937-cpt)
abstDomain: V18937 (C-0-D16478-V18937-cpt)
abstDomain: V18935 (C-0-D16478-V18935-cpt)
abstDomain: V18935 (C-0-D16478-V18935-cpt)
abstDomain: V18935 (C-0-D16478-V18935-cpt)
abstDomain: V18935 (C-0-D16478-V18935-cpt)
abstDomain: V18935 (C-0-D16478-V18935-cpt)
abstDomain: V18935 (C-0-D16478-V18935-cpt)
abstDomain: V18935 (C-0-D16478-V18935-cpt)
abstDomain: V18936 (C-0-D16478-V18936-cpt)
abstDomain: V18936 (C-0-D16478-V18936-cpt)
abstDomain: V18936 (C-0-D16478-V18936-cpt)
abstDomain: V18936 (C-0-D16478-V18936-cpt)
abstDomain: V18936 (C-0-D16478-V18936-cpt)
abstDomain: V18936 (C-0-D16478-V18936-cpt)
abstDomain: V18936 (C-0-D16478-V18936-cpt)
vocSet: D17388 (C-0-D17388-cpt)
vocSet: D17388 (C-0-D17388-cpt)
vocSet: D17388 (C-0-D17388-cpt)
vocSet: D17388 (C-0-D17388-cpt)
vocSet: D17388 (C-0-D17388-cpt)
vocSet: D17388 (C-0-D17388-cpt)
vocSet: D17388 (C-0-D17388-cpt)
specDomain: V17887 (C-0-D10642-V17887-cpt)
specDomain: V17887 (C-0-D10642-V17887-cpt)
specDomain: V17887 (C-0-D10642-V17887-cpt)
specDomain: V17887 (C-0-D10642-V17887-cpt)
specDomain: V17887 (C-0-D10642-V17887-cpt)
specDomain: V17887 (C-0-D10642-V17887-cpt)
specDomain: V17887 (C-0-D10642-V17887-cpt)
A code for a common (periodical) activity of
daily living based on which the event related periodic
interval is specified.
A code for a common (periodical) activity of
daily living based on which the event related periodic
interval is specified.
A code for a common (periodical) activity of
daily living based on which the event related periodic
interval is specified.
A code for a common (periodical) activity of
daily living based on which the event related periodic
interval is specified.
A code for a common (periodical) activity of
daily living based on which the event related periodic
interval is specified.
A code for a common (periodical) activity of
daily living based on which the event related periodic
interval is specified.
A code for a common (periodical) activity of
daily living based on which the event related periodic
interval is specified.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
A code for a common
(periodical) activity of daily living based
on which the event related periodic interval
is specified.
A code for a common
(periodical) activity of daily living based
on which the event related periodic interval
is specified.
A code for a common
(periodical) activity of daily living based
on which the event related periodic interval
is specified.
A code for a common
(periodical) activity of daily living based
on which the event related periodic interval
is specified.
A code for a common
(periodical) activity of daily living based
on which the event related periodic interval
is specified.
A code for a common
(periodical) activity of daily living based
on which the event related periodic interval
is specified.
A code for a common
(periodical) activity of daily living based
on which the event related periodic interval
is specified.
An interval of elapsed time
(duration, not absolute point in time) that
marks the offsets for the beginning, width
and end of the event-related periodic
interval measured from the time each such event
actually occurred.
An interval of elapsed time
(duration, not absolute point in time) that
marks the offsets for the beginning, width
and end of the event-related periodic
interval measured from the time each such event
actually occurred.
An interval of elapsed time
(duration, not absolute point in time) that
marks the offsets for the beginning, width
and end of the event-related periodic
interval measured from the time each such event
actually occurred.
An interval of elapsed time
(duration, not absolute point in time) that
marks the offsets for the beginning, width
and end of the event-related periodic
interval measured from the time each such event
actually occurred.
An interval of elapsed time
(duration, not absolute point in time) that
marks the offsets for the beginning, width
and end of the event-related periodic
interval measured from the time each such event
actually occurred.
An interval of elapsed time
(duration, not absolute point in time) that
marks the offsets for the beginning, width
and end of the event-related periodic
interval measured from the time each such event
actually occurred.
An interval of elapsed time
(duration, not absolute point in time) that
marks the offsets for the beginning, width
and end of the event-related periodic
interval measured from the time each such event
actually occurred.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
The primary measure of
variance/uncertainty of the value (the
square root of the sum of the squares of the
differences between all data points and the mean).
The standard deviation is used to normalize the data
for computing the distribution function. Applications
that cannot deal with probability distributions can
still get an idea about the confidence level by looking
at the standard deviation.
The primary measure of
variance/uncertainty of the value (the
square root of the sum of the squares of the
differences between all data points and the mean).
The standard deviation is used to normalize the data
for computing the distribution function. Applications
that cannot deal with probability distributions can
still get an idea about the confidence level by looking
at the standard deviation.
The primary measure of
variance/uncertainty of the value (the
square root of the sum of the squares of the
differences between all data points and the mean).
The standard deviation is used to normalize the data
for computing the distribution function. Applications
that cannot deal with probability distributions can
still get an idea about the confidence level by looking
at the standard deviation.
The primary measure of
variance/uncertainty of the value (the
square root of the sum of the squares of the
differences between all data points and the mean).
The standard deviation is used to normalize the data
for computing the distribution function. Applications
that cannot deal with probability distributions can
still get an idea about the confidence level by looking
at the standard deviation.
The primary measure of
variance/uncertainty of the value (the
square root of the sum of the squares of the
differences between all data points and the mean).
The standard deviation is used to normalize the data
for computing the distribution function. Applications
that cannot deal with probability distributions can
still get an idea about the confidence level by looking
at the standard deviation.
The primary measure of
variance/uncertainty of the value (the
square root of the sum of the squares of the
differences between all data points and the mean).
The standard deviation is used to normalize the data
for computing the distribution function. Applications
that cannot deal with probability distributions can
still get an idea about the confidence level by looking
at the standard deviation.
The primary measure of
variance/uncertainty of the value (the
square root of the sum of the squares of the
differences between all data points and the mean).
The standard deviation is used to normalize the data
for computing the distribution function. Applications
that cannot deal with probability distributions can
still get an idea about the confidence level by looking
at the standard deviation.
A code specifying the type of
probability distribution. Possible values are as
shown in the attached table. The NULL value
(unknown) for the type code indicates that the
probability distribution type is unknown. In that
case, the standard deviation has the meaning of an
informal guess.
A code specifying the type of
probability distribution. Possible values are as
shown in the attached table. The NULL value
(unknown) for the type code indicates that the
probability distribution type is unknown. In that
case, the standard deviation has the meaning of an
informal guess.
A code specifying the type of
probability distribution. Possible values are as
shown in the attached table. The NULL value
(unknown) for the type code indicates that the
probability distribution type is unknown. In that
case, the standard deviation has the meaning of an
informal guess.
A code specifying the type of
probability distribution. Possible values are as
shown in the attached table. The NULL value
(unknown) for the type code indicates that the
probability distribution type is unknown. In that
case, the standard deviation has the meaning of an
informal guess.
A code specifying the type of
probability distribution. Possible values are as
shown in the attached table. The NULL value
(unknown) for the type code indicates that the
probability distribution type is unknown. In that
case, the standard deviation has the meaning of an
informal guess.
A code specifying the type of
probability distribution. Possible values are as
shown in the attached table. The NULL value
(unknown) for the type code indicates that the
probability distribution type is unknown. In that
case, the standard deviation has the meaning of an
informal guess.
A code specifying the type of
probability distribution. Possible values are as
shown in the attached table. The NULL value
(unknown) for the type code indicates that the
probability distribution type is unknown. In that
case, the standard deviation has the meaning of an
informal guess.
vocSet: D10747 (C-0-D10747-cpt)
vocSet: D10747 (C-0-D10747-cpt)
vocSet: D10747 (C-0-D10747-cpt)
vocSet: D10747 (C-0-D10747-cpt)
vocSet: D10747 (C-0-D10747-cpt)
vocSet: D10747 (C-0-D10747-cpt)
vocSet: D10747 (C-0-D10747-cpt)
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
The primary measure of
variance/uncertainty of the value (the
square root of the sum of the squares of the
differences between all data points and the mean).
The standard deviation is used to normalize the data
for computing the distribution function. Applications
that cannot deal with probability distributions can
still get an idea about the confidence level by looking
at the standard deviation.
The primary measure of
variance/uncertainty of the value (the
square root of the sum of the squares of the
differences between all data points and the mean).
The standard deviation is used to normalize the data
for computing the distribution function. Applications
that cannot deal with probability distributions can
still get an idea about the confidence level by looking
at the standard deviation.
The primary measure of
variance/uncertainty of the value (the
square root of the sum of the squares of the
differences between all data points and the mean).
The standard deviation is used to normalize the data
for computing the distribution function. Applications
that cannot deal with probability distributions can
still get an idea about the confidence level by looking
at the standard deviation.
The primary measure of
variance/uncertainty of the value (the
square root of the sum of the squares of the
differences between all data points and the mean).
The standard deviation is used to normalize the data
for computing the distribution function. Applications
that cannot deal with probability distributions can
still get an idea about the confidence level by looking
at the standard deviation.
The primary measure of
variance/uncertainty of the value (the
square root of the sum of the squares of the
differences between all data points and the mean).
The standard deviation is used to normalize the data
for computing the distribution function. Applications
that cannot deal with probability distributions can
still get an idea about the confidence level by looking
at the standard deviation.
The primary measure of
variance/uncertainty of the value (the
square root of the sum of the squares of the
differences between all data points and the mean).
The standard deviation is used to normalize the data
for computing the distribution function. Applications
that cannot deal with probability distributions can
still get an idea about the confidence level by looking
at the standard deviation.
The primary measure of
variance/uncertainty of the value (the
square root of the sum of the squares of the
differences between all data points and the mean).
The standard deviation is used to normalize the data
for computing the distribution function. Applications
that cannot deal with probability distributions can
still get an idea about the confidence level by looking
at the standard deviation.
A code specifying the type of
probability distribution. Possible values are as
shown in the attached table. The NULL value
(unknown) for the type code indicates that the
probability distribution type is unknown. In that
case, the standard deviation has the meaning of an
informal guess.
A code specifying the type of
probability distribution. Possible values are as
shown in the attached table. The NULL value
(unknown) for the type code indicates that the
probability distribution type is unknown. In that
case, the standard deviation has the meaning of an
informal guess.
A code specifying the type of
probability distribution. Possible values are as
shown in the attached table. The NULL value
(unknown) for the type code indicates that the
probability distribution type is unknown. In that
case, the standard deviation has the meaning of an
informal guess.
A code specifying the type of
probability distribution. Possible values are as
shown in the attached table. The NULL value
(unknown) for the type code indicates that the
probability distribution type is unknown. In that
case, the standard deviation has the meaning of an
informal guess.
A code specifying the type of
probability distribution. Possible values are as
shown in the attached table. The NULL value
(unknown) for the type code indicates that the
probability distribution type is unknown. In that
case, the standard deviation has the meaning of an
informal guess.
A code specifying the type of
probability distribution. Possible values are as
shown in the attached table. The NULL value
(unknown) for the type code indicates that the
probability distribution type is unknown. In that
case, the standard deviation has the meaning of an
informal guess.
A code specifying the type of
probability distribution. Possible values are as
shown in the attached table. The NULL value
(unknown) for the type code indicates that the
probability distribution type is unknown. In that
case, the standard deviation has the meaning of an
informal guess.
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
A code for a common
(periodical) activity of daily living based
on which the event related periodic interval
is specified.
A code for a common
(periodical) activity of daily living based
on which the event related periodic interval
is specified.
A code for a common
(periodical) activity of daily living based
on which the event related periodic interval
is specified.
A code for a common
(periodical) activity of daily living based
on which the event related periodic interval
is specified.
A code for a common
(periodical) activity of daily living based
on which the event related periodic interval
is specified.
A code for a common
(periodical) activity of daily living based
on which the event related periodic interval
is specified.
A code for a common
(periodical) activity of daily living based
on which the event related periodic interval
is specified.
An interval of elapsed time
(duration, not absolute point in time) that
marks the offsets for the beginning, width
and end of the event-related periodic
interval measured from the time each such event
actually occurred.
An interval of elapsed time
(duration, not absolute point in time) that
marks the offsets for the beginning, width
and end of the event-related periodic
interval measured from the time each such event
actually occurred.
An interval of elapsed time
(duration, not absolute point in time) that
marks the offsets for the beginning, width
and end of the event-related periodic
interval measured from the time each such event
actually occurred.
An interval of elapsed time
(duration, not absolute point in time) that
marks the offsets for the beginning, width
and end of the event-related periodic
interval measured from the time each such event
actually occurred.
An interval of elapsed time
(duration, not absolute point in time) that
marks the offsets for the beginning, width
and end of the event-related periodic
interval measured from the time each such event
actually occurred.
An interval of elapsed time
(duration, not absolute point in time) that
marks the offsets for the beginning, width
and end of the event-related periodic
interval measured from the time each such event
actually occurred.
An interval of elapsed time
(duration, not absolute point in time) that
marks the offsets for the beginning, width
and end of the event-related periodic
interval measured from the time each such event
actually occurred.
specDomain: V11623
(C-0-D10882-V13922-V10883-V13934-V11623-cpt)
specDomain: V11623
(C-0-D10882-V13922-V10883-V13934-V11623-cpt)
specDomain: V11623
(C-0-D10882-V13922-V10883-V13934-V11623-cpt)
specDomain: V11623
(C-0-D10882-V13922-V10883-V13934-V11623-cpt)
specDomain: V11623
(C-0-D10882-V13922-V10883-V13934-V11623-cpt)
specDomain: V11623
(C-0-D10882-V13922-V10883-V13934-V11623-cpt)
specDomain: V11623
(C-0-D10882-V13922-V10883-V13934-V11623-cpt)
specDomain: V10884 (C-0-D10882-V13922-V10884-cpt)
specDomain: V10884 (C-0-D10882-V13922-V10884-cpt)
specDomain: V10884 (C-0-D10882-V13922-V10884-cpt)
specDomain: V10884 (C-0-D10882-V13922-V10884-cpt)
specDomain: V10884 (C-0-D10882-V13922-V10884-cpt)
specDomain: V10884 (C-0-D10882-V13922-V10884-cpt)
specDomain: V10884 (C-0-D10882-V13922-V10884-cpt)
specDomain: V10883 (C-0-D10882-V13922-V10883-cpt)
specDomain: V10883 (C-0-D10882-V13922-V10883-cpt)
specDomain: V10883 (C-0-D10882-V13922-V10883-cpt)
specDomain: V10883 (C-0-D10882-V13922-V10883-cpt)
specDomain: V10883 (C-0-D10882-V13922-V10883-cpt)
specDomain: V10883 (C-0-D10882-V13922-V10883-cpt)
specDomain: V10883 (C-0-D10882-V13922-V10883-cpt)
specDomain: V11621
(C-0-D10882-V13922-V10884-V11621-cpt)
specDomain: V11621
(C-0-D10882-V13922-V10884-V11621-cpt)
specDomain: V11621
(C-0-D10882-V13922-V10884-V11621-cpt)
specDomain: V11621
(C-0-D10882-V13922-V10884-V11621-cpt)
specDomain: V11621
(C-0-D10882-V13922-V10884-V11621-cpt)
specDomain: V11621
(C-0-D10882-V13922-V10884-V11621-cpt)
specDomain: V11621
(C-0-D10882-V13922-V10884-V11621-cpt)
specDomain: V10892 (C-0-D10882-V13922-V10892-cpt)
specDomain: V10892 (C-0-D10882-V13922-V10892-cpt)
specDomain: V10892 (C-0-D10882-V13922-V10892-cpt)
specDomain: V10892 (C-0-D10882-V13922-V10892-cpt)
specDomain: V10892 (C-0-D10882-V13922-V10892-cpt)
specDomain: V10892 (C-0-D10882-V13922-V10892-cpt)
specDomain: V10892 (C-0-D10882-V13922-V10892-cpt)
specDomain: V10879 (C-0-D10878-V10879-cpt)
specDomain: V10879 (C-0-D10878-V10879-cpt)
specDomain: V10879 (C-0-D10878-V10879-cpt)
specDomain: V10879 (C-0-D10878-V10879-cpt)
specDomain: V10879 (C-0-D10878-V10879-cpt)
specDomain: V10879 (C-0-D10878-V10879-cpt)
specDomain: V10879 (C-0-D10878-V10879-cpt)
vocSet: D15888 (C-0-D15888-cpt)
vocSet: D15888 (C-0-D15888-cpt)
vocSet: D15888 (C-0-D15888-cpt)
vocSet: D15888 (C-0-D15888-cpt)
vocSet: D15888 (C-0-D15888-cpt)
vocSet: D15888 (C-0-D15888-cpt)
vocSet: D15888 (C-0-D15888-cpt)
specDomain: V19619 (C-0-D15913-V200-V19619-cpt)
specDomain: V19619 (C-0-D15913-V200-V19619-cpt)
specDomain: V19619 (C-0-D15913-V200-V19619-cpt)
specDomain: V19619 (C-0-D15913-V200-V19619-cpt)
specDomain: V19619 (C-0-D15913-V200-V19619-cpt)
specDomain: V19619 (C-0-D15913-V200-V19619-cpt)
specDomain: V19619 (C-0-D15913-V200-V19619-cpt)
vocSet: D15913 (C-0-D15913-cpt)
vocSet: D15913 (C-0-D15913-cpt)
vocSet: D15913 (C-0-D15913-cpt)
vocSet: D15913 (C-0-D15913-cpt)
vocSet: D15913 (C-0-D15913-cpt)
vocSet: D15913 (C-0-D15913-cpt)
vocSet: D15913 (C-0-D15913-cpt)
This is the start-value of the
generated list.
This is the start-value of the
generated list.
This is the start-value of the
generated list.
This is the start-value of the
generated list.
This is the start-value of the
generated list.
This is the start-value of the
generated list.
This is the start-value of the
generated list.
The difference between one value
and its previous different value. For example,
to generate the sequence (1; 4; 7; 10; 13; ...)
the increment is 3; likewise to generate the
sequence (1; 1; 4; 4; 7; 7; 10; 10; 13; 13;
...) the increment is also 3.
The difference between one value
and its previous different value. For example,
to generate the sequence (1; 4; 7; 10; 13; ...)
the increment is 3; likewise to generate the
sequence (1; 1; 4; 4; 7; 7; 10; 10; 13; 13;
...) the increment is also 3.
The difference between one value
and its previous different value. For example,
to generate the sequence (1; 4; 7; 10; 13; ...)
the increment is 3; likewise to generate the
sequence (1; 1; 4; 4; 7; 7; 10; 10; 13; 13;
...) the increment is also 3.
The difference between one value
and its previous different value. For example,
to generate the sequence (1; 4; 7; 10; 13; ...)
the increment is 3; likewise to generate the
sequence (1; 1; 4; 4; 7; 7; 10; 10; 13; 13;
...) the increment is also 3.
The difference between one value
and its previous different value. For example,
to generate the sequence (1; 4; 7; 10; 13; ...)
the increment is 3; likewise to generate the
sequence (1; 1; 4; 4; 7; 7; 10; 10; 13; 13;
...) the increment is also 3.
The difference between one value
and its previous different value. For example,
to generate the sequence (1; 4; 7; 10; 13; ...)
the increment is 3; likewise to generate the
sequence (1; 1; 4; 4; 7; 7; 10; 10; 13; 13;
...) the increment is also 3.
The difference between one value
and its previous different value. For example,
to generate the sequence (1; 4; 7; 10; 13; ...)
the increment is 3; likewise to generate the
sequence (1; 1; 4; 4; 7; 7; 10; 10; 13; 13;
...) the increment is also 3.
The integer by which the index for
the sequence is divided, effectively the number of
times the sequence generates the same sequence item
value before incrementing to the next sequence item
value. For example, to generate the sequence (1; 1;
1; 2; 2; 2; 3; 3; 3; ...) the denominator is 3.
The integer by which the index for
the sequence is divided, effectively the number of
times the sequence generates the same sequence item
value before incrementing to the next sequence item
value. For example, to generate the sequence (1; 1;
1; 2; 2; 2; 3; 3; 3; ...) the denominator is 3.
The integer by which the index for
the sequence is divided, effectively the number of
times the sequence generates the same sequence item
value before incrementing to the next sequence item
value. For example, to generate the sequence (1; 1;
1; 2; 2; 2; 3; 3; 3; ...) the denominator is 3.
The integer by which the index for
the sequence is divided, effectively the number of
times the sequence generates the same sequence item
value before incrementing to the next sequence item
value. For example, to generate the sequence (1; 1;
1; 2; 2; 2; 3; 3; 3; ...) the denominator is 3.
The integer by which the index for
the sequence is divided, effectively the number of
times the sequence generates the same sequence item
value before incrementing to the next sequence item
value. For example, to generate the sequence (1; 1;
1; 2; 2; 2; 3; 3; 3; ...) the denominator is 3.
The integer by which the index for
the sequence is divided, effectively the number of
times the sequence generates the same sequence item
value before incrementing to the next sequence item
value. For example, to generate the sequence (1; 1;
1; 2; 2; 2; 3; 3; 3; ...) the denominator is 3.
The integer by which the index for
the sequence is divided, effectively the number of
times the sequence generates the same sequence item
value before incrementing to the next sequence item
value. For example, to generate the sequence (1; 1;
1; 2; 2; 2; 3; 3; 3; ...) the denominator is 3.
If non-NULL, specifies that the
sequence alternates, i.e., after this many
increments, the sequence item values roll over to
start from the initial sequence item value. For
example, the sequence (1; 2; 3; 1; 2; 3; 1; 2; 3;
...) has period 3; also the sequence (1; 1; 2; 2;
3; 3; 1; 1; 2; 2; 3; 3; ...) has period 3 too.
If non-NULL, specifies that the
sequence alternates, i.e., after this many
increments, the sequence item values roll over to
start from the initial sequence item value. For
example, the sequence (1; 2; 3; 1; 2; 3; 1; 2; 3;
...) has period 3; also the sequence (1; 1; 2; 2;
3; 3; 1; 1; 2; 2; 3; 3; ...) has period 3 too.
If non-NULL, specifies that the
sequence alternates, i.e., after this many
increments, the sequence item values roll over to
start from the initial sequence item value. For
example, the sequence (1; 2; 3; 1; 2; 3; 1; 2; 3;
...) has period 3; also the sequence (1; 1; 2; 2;
3; 3; 1; 1; 2; 2; 3; 3; ...) has period 3 too.
If non-NULL, specifies that the
sequence alternates, i.e., after this many
increments, the sequence item values roll over to
start from the initial sequence item value. For
example, the sequence (1; 2; 3; 1; 2; 3; 1; 2; 3;
...) has period 3; also the sequence (1; 1; 2; 2;
3; 3; 1; 1; 2; 2; 3; 3; ...) has period 3 too.
If non-NULL, specifies that the
sequence alternates, i.e., after this many
increments, the sequence item values roll over to
start from the initial sequence item value. For
example, the sequence (1; 2; 3; 1; 2; 3; 1; 2; 3;
...) has period 3; also the sequence (1; 1; 2; 2;
3; 3; 1; 1; 2; 2; 3; 3; ...) has period 3 too.
If non-NULL, specifies that the
sequence alternates, i.e., after this many
increments, the sequence item values roll over to
start from the initial sequence item value. For
example, the sequence (1; 2; 3; 1; 2; 3; 1; 2; 3;
...) has period 3; also the sequence (1; 1; 2; 2;
3; 3; 1; 1; 2; 2; 3; 3; ...) has period 3 too.
If non-NULL, specifies that the
sequence alternates, i.e., after this many
increments, the sequence item values roll over to
start from the initial sequence item value. For
example, the sequence (1; 2; 3; 1; 2; 3; 1; 2; 3;
...) has period 3; also the sequence (1; 1; 2; 2;
3; 3; 1; 1; 2; 2; 3; 3; ...) has period 3 too.
This is the start-value of the
generated list.
This is the start-value of the
generated list.
This is the start-value of the
generated list.
This is the start-value of the
generated list.
This is the start-value of the
generated list.
This is the start-value of the
generated list.
This is the start-value of the
generated list.
The difference between one value
and its previous different value. For example,
to generate the sequence (1; 4; 7; 10; 13; ...)
the increment is 3; likewise to generate the
sequence (1; 1; 4; 4; 7; 7; 10; 10; 13; 13;
...) the increment is also 3.
The difference between one value
and its previous different value. For example,
to generate the sequence (1; 4; 7; 10; 13; ...)
the increment is 3; likewise to generate the
sequence (1; 1; 4; 4; 7; 7; 10; 10; 13; 13;
...) the increment is also 3.
The difference between one value
and its previous different value. For example,
to generate the sequence (1; 4; 7; 10; 13; ...)
the increment is 3; likewise to generate the
sequence (1; 1; 4; 4; 7; 7; 10; 10; 13; 13;
...) the increment is also 3.
The difference between one value
and its previous different value. For example,
to generate the sequence (1; 4; 7; 10; 13; ...)
the increment is 3; likewise to generate the
sequence (1; 1; 4; 4; 7; 7; 10; 10; 13; 13;
...) the increment is also 3.
The difference between one value
and its previous different value. For example,
to generate the sequence (1; 4; 7; 10; 13; ...)
the increment is 3; likewise to generate the
sequence (1; 1; 4; 4; 7; 7; 10; 10; 13; 13;
...) the increment is also 3.
The difference between one value
and its previous different value. For example,
to generate the sequence (1; 4; 7; 10; 13; ...)
the increment is 3; likewise to generate the
sequence (1; 1; 4; 4; 7; 7; 10; 10; 13; 13;
...) the increment is also 3.
The difference between one value
and its previous different value. For example,
to generate the sequence (1; 4; 7; 10; 13; ...)
the increment is 3; likewise to generate the
sequence (1; 1; 4; 4; 7; 7; 10; 10; 13; 13;
...) the increment is also 3.
The integer by which the index for
the sequence is divided, effectively the number of
times the sequence generates the same sequence item
value before incrementing to the next sequence item
value. For example, to generate the sequence (1; 1;
1; 2; 2; 2; 3; 3; 3; ...) the denominator is 3.
The integer by which the index for
the sequence is divided, effectively the number of
times the sequence generates the same sequence item
value before incrementing to the next sequence item
value. For example, to generate the sequence (1; 1;
1; 2; 2; 2; 3; 3; 3; ...) the denominator is 3.
The integer by which the index for
the sequence is divided, effectively the number of
times the sequence generates the same sequence item
value before incrementing to the next sequence item
value. For example, to generate the sequence (1; 1;
1; 2; 2; 2; 3; 3; 3; ...) the denominator is 3.
The integer by which the index for
the sequence is divided, effectively the number of
times the sequence generates the same sequence item
value before incrementing to the next sequence item
value. For example, to generate the sequence (1; 1;
1; 2; 2; 2; 3; 3; 3; ...) the denominator is 3.
The integer by which the index for
the sequence is divided, effectively the number of
times the sequence generates the same sequence item
value before incrementing to the next sequence item
value. For example, to generate the sequence (1; 1;
1; 2; 2; 2; 3; 3; 3; ...) the denominator is 3.
The integer by which the index for
the sequence is divided, effectively the number of
times the sequence generates the same sequence item
value before incrementing to the next sequence item
value. For example, to generate the sequence (1; 1;
1; 2; 2; 2; 3; 3; 3; ...) the denominator is 3.
The integer by which the index for
the sequence is divided, effectively the number of
times the sequence generates the same sequence item
value before incrementing to the next sequence item
value. For example, to generate the sequence (1; 1;
1; 2; 2; 2; 3; 3; 3; ...) the denominator is 3.
If non-NULL, specifies that the
sequence alternates, i.e., after this many
increments, the sequence item values roll over to
start from the initial sequence item value. For
example, the sequence (1; 2; 3; 1; 2; 3; 1; 2; 3;
...) has period 3; also the sequence (1; 1; 2; 2;
3; 3; 1; 1; 2; 2; 3; 3; ...) has period 3 too.
If non-NULL, specifies that the
sequence alternates, i.e., after this many
increments, the sequence item values roll over to
start from the initial sequence item value. For
example, the sequence (1; 2; 3; 1; 2; 3; 1; 2; 3;
...) has period 3; also the sequence (1; 1; 2; 2;
3; 3; 1; 1; 2; 2; 3; 3; ...) has period 3 too.
If non-NULL, specifies that the
sequence alternates, i.e., after this many
increments, the sequence item values roll over to
start from the initial sequence item value. For
example, the sequence (1; 2; 3; 1; 2; 3; 1; 2; 3;
...) has period 3; also the sequence (1; 1; 2; 2;
3; 3; 1; 1; 2; 2; 3; 3; ...) has period 3 too.
If non-NULL, specifies that the
sequence alternates, i.e., after this many
increments, the sequence item values roll over to
start from the initial sequence item value. For
example, the sequence (1; 2; 3; 1; 2; 3; 1; 2; 3;
...) has period 3; also the sequence (1; 1; 2; 2;
3; 3; 1; 1; 2; 2; 3; 3; ...) has period 3 too.
If non-NULL, specifies that the
sequence alternates, i.e., after this many
increments, the sequence item values roll over to
start from the initial sequence item value. For
example, the sequence (1; 2; 3; 1; 2; 3; 1; 2; 3;
...) has period 3; also the sequence (1; 1; 2; 2;
3; 3; 1; 1; 2; 2; 3; 3; ...) has period 3 too.
If non-NULL, specifies that the
sequence alternates, i.e., after this many
increments, the sequence item values roll over to
start from the initial sequence item value. For
example, the sequence (1; 2; 3; 1; 2; 3; 1; 2; 3;
...) has period 3; also the sequence (1; 1; 2; 2;
3; 3; 1; 1; 2; 2; 3; 3; ...) has period 3 too.
If non-NULL, specifies that the
sequence alternates, i.e., after this many
increments, the sequence item values roll over to
start from the initial sequence item value. For
example, the sequence (1; 2; 3; 1; 2; 3; 1; 2; 3;
...) has period 3; also the sequence (1; 1; 2; 2;
3; 3; 1; 1; 2; 2; 3; 3; ...) has period 3 too.
specDomain: V10330 (C-0-D10317-V10329-V10330-cpt)
specDomain: V10330 (C-0-D10317-V10329-V10330-cpt)
specDomain: V10330 (C-0-D10317-V10329-V10330-cpt)
specDomain: V10330 (C-0-D10317-V10329-V10330-cpt)
specDomain: V10330 (C-0-D10317-V10329-V10330-cpt)
specDomain: V10330 (C-0-D10317-V10329-V10330-cpt)
specDomain: V10330 (C-0-D10317-V10329-V10330-cpt)
specDomain: V10628 (C-0-D201-V190-V10628-cpt)
specDomain: V10628 (C-0-D201-V190-V10628-cpt)
specDomain: V10628 (C-0-D201-V190-V10628-cpt)
specDomain: V10628 (C-0-D201-V190-V10628-cpt)
specDomain: V10628 (C-0-D201-V190-V10628-cpt)
specDomain: V10628 (C-0-D201-V190-V10628-cpt)
specDomain: V10628 (C-0-D201-V190-V10628-cpt)
The time interval during
which the given information was, is, or is
expected to be valid. The interval can be
open or closed, as well as infinite or undefined on
either side.
The time interval during
which the given information was, is, or is
expected to be valid. The interval can be
open or closed, as well as infinite or undefined on
either side.
The time interval during
which the given information was, is, or is
expected to be valid. The interval can be
open or closed, as well as infinite or undefined on
either side.
The time interval during
which the given information was, is, or is
expected to be valid. The interval can be
open or closed, as well as infinite or undefined on
either side.
The time interval during
which the given information was, is, or is
expected to be valid. The interval can be
open or closed, as well as infinite or undefined on
either side.
The time interval during
which the given information was, is, or is
expected to be valid. The interval can be
open or closed, as well as infinite or undefined on
either side.
The time interval during
which the given information was, is, or is
expected to be valid. The interval can be
open or closed, as well as infinite or undefined on
either side.
The time interval during
which the given information was, is, or is
expected to be valid. The interval can be
open or closed, as well as infinite or undefined on
either side.
The time interval during
which the given information was, is, or is
expected to be valid. The interval can be
open or closed, as well as infinite or undefined on
either side.
The time interval during
which the given information was, is, or is
expected to be valid. The interval can be
open or closed, as well as infinite or undefined on
either side.
The time interval during
which the given information was, is, or is
expected to be valid. The interval can be
open or closed, as well as infinite or undefined on
either side.
The time interval during
which the given information was, is, or is
expected to be valid. The interval can be
open or closed, as well as infinite or undefined on
either side.
The time interval during
which the given information was, is, or is
expected to be valid. The interval can be
open or closed, as well as infinite or undefined on
either side.
The time interval during
which the given information was, is, or is
expected to be valid. The interval can be
open or closed, as well as infinite or undefined on
either side.
abstDomain: V14839 (C-0-D14824-V14839-cpt)
abstDomain: V14839 (C-0-D14824-V14839-cpt)
abstDomain: V14839 (C-0-D14824-V14839-cpt)
abstDomain: V14839 (C-0-D14824-V14839-cpt)
abstDomain: V14839 (C-0-D14824-V14839-cpt)
abstDomain: V14839 (C-0-D14824-V14839-cpt)
abstDomain: V14839 (C-0-D14824-V14839-cpt)
Integer numbers (-1,0,1,2, 100, 3398129, etc.) are
precise numbers that are results of counting and enumerating.
Integer numbers are discrete, the set of integers is infinite but
countable. No arbitrary limit is imposed on the range of integer
numbers. Two NULL flavors are defined for the positive and negative
infinity.
Integer numbers (-1,0,1,2, 100, 3398129, etc.) are
precise numbers that are results of counting and enumerating.
Integer numbers are discrete, the set of integers is infinite but
countable. No arbitrary limit is imposed on the range of integer
numbers. Two NULL flavors are defined for the positive and negative
infinity.
Integer numbers (-1,0,1,2, 100, 3398129, etc.) are
precise numbers that are results of counting and enumerating.
Integer numbers are discrete, the set of integers is infinite but
countable. No arbitrary limit is imposed on the range of integer
numbers. Two NULL flavors are defined for the positive and negative
infinity.
Integer numbers (-1,0,1,2, 100, 3398129, etc.) are
precise numbers that are results of counting and enumerating.
Integer numbers are discrete, the set of integers is infinite but
countable. No arbitrary limit is imposed on the range of integer
numbers. Two NULL flavors are defined for the positive and negative
infinity.
Integer numbers (-1,0,1,2, 100, 3398129, etc.) are
precise numbers that are results of counting and enumerating.
Integer numbers are discrete, the set of integers is infinite but
countable. No arbitrary limit is imposed on the range of integer
numbers. Two NULL flavors are defined for the positive and negative
infinity.
Integer numbers (-1,0,1,2, 100, 3398129, etc.) are
precise numbers that are results of counting and enumerating.
Integer numbers are discrete, the set of integers is infinite but
countable. No arbitrary limit is imposed on the range of integer
numbers. Two NULL flavors are defined for the positive and negative
infinity.
Integer numbers (-1,0,1,2, 100, 3398129, etc.) are
precise numbers that are results of counting and enumerating.
Integer numbers are discrete, the set of integers is infinite but
countable. No arbitrary limit is imposed on the range of integer
numbers. Two NULL flavors are defined for the positive and negative
infinity.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The low limit of the
interval.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference
between high and low boundary. The
purpose of distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The high limit of
the interval.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The high limit of the
interval.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The arithmetic mean of
the interval (low plus high divided
by 2). The purpose of distinguishing the center
as a semantic property is for conversions of intervals
from and to point values.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
The difference between
high and low boundary. The purpose of
distinguishing a width property is to
handle all cases of incomplete information
symmetrically. In any interval representation only
two of the three properties high, low, and width need
to be stated and the third can be derived.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
Fractional numbers. Typically used whenever quantities
are measured, estimated, or computed from other real numbers. The
typical representation is decimal, where the number of significant
decimal digits is known as the precision. Real numbers are needed beyond
integers whenever quantities of the real world are measured,
estimated, or computed from other real numbers. The term "Real number"
in this specification is used to mean that fractional values are covered
without necessarily implying the full set of the mathematical real
numbers.
Fractional numbers. Typically used whenever quantities
are measured, estimated, or computed from other real numbers. The
typical representation is decimal, where the number of significant
decimal digits is known as the precision. Real numbers are needed beyond
integers whenever quantities of the real world are measured,
estimated, or computed from other real numbers. The term "Real number"
in this specification is used to mean that fractional values are covered
without necessarily implying the full set of the mathematical real
numbers.
Fractional numbers. Typically used whenever quantities
are measured, estimated, or computed from other real numbers. The
typical representation is decimal, where the number of significant
decimal digits is known as the precision. Real numbers are needed beyond
integers whenever quantities of the real world are measured,
estimated, or computed from other real numbers. The term "Real number"
in this specification is used to mean that fractional values are covered
without necessarily implying the full set of the mathematical real
numbers.
Fractional numbers. Typically used whenever quantities
are measured, estimated, or computed from other real numbers. The
typical representation is decimal, where the number of significant
decimal digits is known as the precision. Real numbers are needed beyond
integers whenever quantities of the real world are measured,
estimated, or computed from other real numbers. The term "Real number"
in this specification is used to mean that fractional values are covered
without necessarily implying the full set of the mathematical real
numbers.
Fractional numbers. Typically used whenever quantities
are measured, estimated, or computed from other real numbers. The
typical representation is decimal, where the number of significant
decimal digits is known as the precision. Real numbers are needed beyond
integers whenever quantities of the real world are measured,
estimated, or computed from other real numbers. The term "Real number"
in this specification is used to mean that fractional values are covered
without necessarily implying the full set of the mathematical real
numbers.
Fractional numbers. Typically used whenever quantities
are measured, estimated, or computed from other real numbers. The
typical representation is decimal, where the number of significant
decimal digits is known as the precision. Real numbers are needed beyond
integers whenever quantities of the real world are measured,
estimated, or computed from other real numbers. The term "Real number"
in this specification is used to mean that fractional values are covered
without necessarily implying the full set of the mathematical real
numbers.
Fractional numbers. Typically used whenever quantities
are measured, estimated, or computed from other real numbers. The
typical representation is decimal, where the number of significant
decimal digits is known as the precision. Real numbers are needed beyond
integers whenever quantities of the real world are measured,
estimated, or computed from other real numbers. The term "Real number"
in this specification is used to mean that fractional values are covered
without necessarily implying the full set of the mathematical real
numbers.
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
Specifies whether the limit is
included in the interval (interval is closed) or
excluded from the interval (interval is open).
specDomain: V16773
(C-0-D11555-V13940-V16930-V16773-cpt)
specDomain: V16773
(C-0-D11555-V13940-V16930-V16773-cpt)
specDomain: V16773
(C-0-D11555-V13940-V16930-V16773-cpt)
specDomain: V16773
(C-0-D11555-V13940-V16930-V16773-cpt)
specDomain: V16773
(C-0-D11555-V13940-V16930-V16773-cpt)
specDomain: V16773
(C-0-D11555-V13940-V16930-V16773-cpt)
specDomain: V16773
(C-0-D11555-V13940-V16930-V16773-cpt)
vocSet: D14824 (C-0-D14824-cpt)
vocSet: D14824 (C-0-D14824-cpt)
vocSet: D14824 (C-0-D14824-cpt)
vocSet: D14824 (C-0-D14824-cpt)
vocSet: D14824 (C-0-D14824-cpt)
vocSet: D14824 (C-0-D14824-cpt)
vocSet: D14824 (C-0-D14824-cpt)
abstDomain: V14848 (C-0-D14824-V14848-cpt)
abstDomain: V14848 (C-0-D14824-V14848-cpt)
abstDomain: V14848 (C-0-D14824-V14848-cpt)
abstDomain: V14848 (C-0-D14824-V14848-cpt)
abstDomain: V14848 (C-0-D14824-V14848-cpt)
abstDomain: V14848 (C-0-D14824-V14848-cpt)
abstDomain: V14848 (C-0-D14824-V14848-cpt)
abstDomain: V14850 (C-0-D14824-V14850-cpt)
abstDomain: V14850 (C-0-D14824-V14850-cpt)
abstDomain: V14850 (C-0-D14824-V14850-cpt)
abstDomain: V14850 (C-0-D14824-V14850-cpt)
abstDomain: V14850 (C-0-D14824-V14850-cpt)
abstDomain: V14850 (C-0-D14824-V14850-cpt)
abstDomain: V14850 (C-0-D14824-V14850-cpt)
specDomain: V19591 (C-0-D15913-V200-V19591-cpt)
specDomain: V19591 (C-0-D15913-V200-V19591-cpt)
specDomain: V19591 (C-0-D15913-V200-V19591-cpt)
specDomain: V19591 (C-0-D15913-V200-V19591-cpt)
specDomain: V19591 (C-0-D15913-V200-V19591-cpt)
specDomain: V19591 (C-0-D15913-V200-V19591-cpt)
specDomain: V19591 (C-0-D15913-V200-V19591-cpt)
abstDomain: V17860 (C-0-D10637-V17860-cpt)
abstDomain: V17860 (C-0-D10637-V17860-cpt)
abstDomain: V17860 (C-0-D10637-V17860-cpt)
abstDomain: V17860 (C-0-D10637-V17860-cpt)
abstDomain: V17860 (C-0-D10637-V17860-cpt)
abstDomain: V17860 (C-0-D10637-V17860-cpt)
abstDomain: V17860 (C-0-D10637-V17860-cpt)
specDomain: V10610 (C-0-D10609-V10610-cpt)
specDomain: V10610 (C-0-D10609-V10610-cpt)
specDomain: V10610 (C-0-D10609-V10610-cpt)
specDomain: V10610 (C-0-D10609-V10610-cpt)
specDomain: V10610 (C-0-D10609-V10610-cpt)
specDomain: V10610 (C-0-D10609-V10610-cpt)
specDomain: V10610 (C-0-D10609-V10610-cpt)
A globally unique string representing an ISO Object
Identifier (OID) in a form that consists only of non-negative numbers
with no leading zeros and dots (e.g., "2.16.840.1.113883.3.1").
According to ISO, OIDs are paths in a tree structure, with the left-most
number representing the root and the right-most number representing a
leaf.
A globally unique string representing an ISO Object
Identifier (OID) in a form that consists only of non-negative numbers
with no leading zeros and dots (e.g., "2.16.840.1.113883.3.1").
According to ISO, OIDs are paths in a tree structure, with the left-most
number representing the root and the right-most number representing a
leaf.
A globally unique string representing an ISO Object
Identifier (OID) in a form that consists only of non-negative numbers
with no leading zeros and dots (e.g., "2.16.840.1.113883.3.1").
According to ISO, OIDs are paths in a tree structure, with the left-most
number representing the root and the right-most number representing a
leaf.
A globally unique string representing an ISO Object
Identifier (OID) in a form that consists only of non-negative numbers
with no leading zeros and dots (e.g., "2.16.840.1.113883.3.1").
According to ISO, OIDs are paths in a tree structure, with the left-most
number representing the root and the right-most number representing a
leaf.
A globally unique string representing an ISO Object
Identifier (OID) in a form that consists only of non-negative numbers
with no leading zeros and dots (e.g., "2.16.840.1.113883.3.1").
According to ISO, OIDs are paths in a tree structure, with the left-most
number representing the root and the right-most number representing a
leaf.
A globally unique string representing an ISO Object
Identifier (OID) in a form that consists only of non-negative numbers
with no leading zeros and dots (e.g., "2.16.840.1.113883.3.1").
According to ISO, OIDs are paths in a tree structure, with the left-most
number representing the root and the right-most number representing a
leaf.
A globally unique string representing an ISO Object
Identifier (OID) in a form that consists only of non-negative numbers
with no leading zeros and dots (e.g., "2.16.840.1.113883.3.1").
According to ISO, OIDs are paths in a tree structure, with the left-most
number representing the root and the right-most number representing a
leaf.
abstDomain: V15889 (C-0-D15888-V15889-cpt)
abstDomain: V15889 (C-0-D15888-V15889-cpt)
abstDomain: V15889 (C-0-D15888-V15889-cpt)
abstDomain: V15889 (C-0-D15888-V15889-cpt)
abstDomain: V15889 (C-0-D15888-V15889-cpt)
abstDomain: V15889 (C-0-D15888-V15889-cpt)
abstDomain: V15889 (C-0-D15888-V15889-cpt)
abstDomain: V15914 (C-0-D15913-V15914-cpt)
abstDomain: V15914 (C-0-D15913-V15914-cpt)
abstDomain: V15914 (C-0-D15913-V15914-cpt)
abstDomain: V15914 (C-0-D15913-V15914-cpt)
abstDomain: V15914 (C-0-D15913-V15914-cpt)
abstDomain: V15914 (C-0-D15913-V15914-cpt)
abstDomain: V15914 (C-0-D15913-V15914-cpt)
specDomain: V10616 (C-0-D10609-V10610-V10616-cpt)
specDomain: V10616 (C-0-D10609-V10610-V10616-cpt)
specDomain: V10616 (C-0-D10609-V10610-V10616-cpt)
specDomain: V10616 (C-0-D10609-V10610-V10616-cpt)
specDomain: V10616 (C-0-D10609-V10610-V10616-cpt)
specDomain: V10616 (C-0-D10609-V10610-V10616-cpt)
specDomain: V10616 (C-0-D10609-V10610-V10616-cpt)
abstDomain: V10247 (C-0-D10901-V10247-cpt)
abstDomain: V10247 (C-0-D10901-V10247-cpt)
abstDomain: V10247 (C-0-D10901-V10247-cpt)
abstDomain: V10247 (C-0-D10901-V10247-cpt)
abstDomain: V10247 (C-0-D10901-V10247-cpt)
abstDomain: V10247 (C-0-D10901-V10247-cpt)
abstDomain: V10247 (C-0-D10901-V10247-cpt)
specDomain: V19032 (C-0-D10901-V19032-cpt)
specDomain: V19032 (C-0-D10901-V19032-cpt)
specDomain: V19032 (C-0-D10901-V19032-cpt)
specDomain: V19032 (C-0-D10901-V19032-cpt)
specDomain: V19032 (C-0-D10901-V19032-cpt)
specDomain: V19032 (C-0-D10901-V19032-cpt)
specDomain: V19032 (C-0-D10901-V19032-cpt)
abstDomain: V10251 (C-0-D10901-V10251-cpt)
abstDomain: V10251 (C-0-D10901-V10251-cpt)
abstDomain: V10251 (C-0-D10901-V10251-cpt)
abstDomain: V10251 (C-0-D10901-V10251-cpt)
abstDomain: V10251 (C-0-D10901-V10251-cpt)
abstDomain: V10251 (C-0-D10901-V10251-cpt)
abstDomain: V10251 (C-0-D10901-V10251-cpt)
specDomain: V10263 (C-0-D10901-V10263-cpt)
specDomain: V10263 (C-0-D10901-V10263-cpt)
specDomain: V10263 (C-0-D10901-V10263-cpt)
specDomain: V10263 (C-0-D10901-V10263-cpt)
specDomain: V10263 (C-0-D10901-V10263-cpt)
specDomain: V10263 (C-0-D10901-V10263-cpt)
specDomain: V10263 (C-0-D10901-V10263-cpt)
specDomain: V10248 (C-0-D10901-V10248-cpt)
specDomain: V10248 (C-0-D10901-V10248-cpt)
specDomain: V10248 (C-0-D10901-V10248-cpt)
specDomain: V10248 (C-0-D10901-V10248-cpt)
specDomain: V10248 (C-0-D10901-V10248-cpt)
specDomain: V10248 (C-0-D10901-V10248-cpt)
specDomain: V10248 (C-0-D10901-V10248-cpt)
specDomain: V10298 (C-0-D10901-V10286-V10298-cpt)
specDomain: V10298 (C-0-D10901-V10286-V10298-cpt)
specDomain: V10298 (C-0-D10901-V10286-V10298-cpt)
specDomain: V10298 (C-0-D10901-V10286-V10298-cpt)
specDomain: V10298 (C-0-D10901-V10286-V10298-cpt)
specDomain: V10298 (C-0-D10901-V10286-V10298-cpt)
specDomain: V10298 (C-0-D10901-V10286-V10298-cpt)
specDomain: V10286 (C-0-D10901-V10286-cpt)
specDomain: V10286 (C-0-D10901-V10286-cpt)
specDomain: V10286 (C-0-D10901-V10286-cpt)
specDomain: V10286 (C-0-D10901-V10286-cpt)
specDomain: V10286 (C-0-D10901-V10286-cpt)
specDomain: V10286 (C-0-D10901-V10286-cpt)
specDomain: V10286 (C-0-D10901-V10286-cpt)
specDomain: V10302 (C-0-D10901-V10302-cpt)
specDomain: V10302 (C-0-D10901-V10302-cpt)
specDomain: V10302 (C-0-D10901-V10302-cpt)
specDomain: V10302 (C-0-D10901-V10302-cpt)
specDomain: V10302 (C-0-D10901-V10302-cpt)
specDomain: V10302 (C-0-D10901-V10302-cpt)
specDomain: V10302 (C-0-D10901-V10302-cpt)
specDomain: V10259 (C-0-D10901-V10259-cpt)
specDomain: V10259 (C-0-D10901-V10259-cpt)
specDomain: V10259 (C-0-D10901-V10259-cpt)
specDomain: V10259 (C-0-D10901-V10259-cpt)
specDomain: V10259 (C-0-D10901-V10259-cpt)
specDomain: V10259 (C-0-D10901-V10259-cpt)
specDomain: V10259 (C-0-D10901-V10259-cpt)
abstDomain: V10666 (C-0-D15888-V10659-V10666-cpt)
abstDomain: V10666 (C-0-D15888-V10659-V10666-cpt)
abstDomain: V10666 (C-0-D15888-V10659-V10666-cpt)
abstDomain: V10666 (C-0-D15888-V10659-V10666-cpt)
abstDomain: V10666 (C-0-D15888-V10659-V10666-cpt)
abstDomain: V10666 (C-0-D15888-V10659-V10666-cpt)
abstDomain: V10666 (C-0-D15888-V10659-V10666-cpt)
abstDomain: V10660 (C-0-D15888-V10659-V10660-cpt)
abstDomain: V10660 (C-0-D15888-V10659-V10660-cpt)
abstDomain: V10660 (C-0-D15888-V10659-V10660-cpt)
abstDomain: V10660 (C-0-D15888-V10659-V10660-cpt)
abstDomain: V10660 (C-0-D15888-V10659-V10660-cpt)
abstDomain: V10660 (C-0-D15888-V10659-V10660-cpt)
abstDomain: V10660 (C-0-D15888-V10659-V10660-cpt)
abstDomain: V10671 (C-0-D15888-V10659-V10671-cpt)
abstDomain: V10671 (C-0-D15888-V10659-V10671-cpt)
abstDomain: V10671 (C-0-D15888-V10659-V10671-cpt)
abstDomain: V10671 (C-0-D15888-V10659-V10671-cpt)
abstDomain: V10671 (C-0-D15888-V10659-V10671-cpt)
abstDomain: V10671 (C-0-D15888-V10659-V10671-cpt)
abstDomain: V10671 (C-0-D15888-V10659-V10671-cpt)
abstDomain: V10659 (C-0-D15888-V10659-cpt)
abstDomain: V10659 (C-0-D15888-V10659-cpt)
abstDomain: V10659 (C-0-D15888-V10659-cpt)
abstDomain: V10659 (C-0-D15888-V10659-cpt)
abstDomain: V10659 (C-0-D15888-V10659-cpt)
abstDomain: V10659 (C-0-D15888-V10659-cpt)
abstDomain: V10659 (C-0-D15888-V10659-cpt)
abstDomain: V200 (C-0-D15913-V200-cpt)
abstDomain: V200 (C-0-D15913-V200-cpt)
abstDomain: V200 (C-0-D15913-V200-cpt)
abstDomain: V200 (C-0-D15913-V200-cpt)
abstDomain: V200 (C-0-D15913-V200-cpt)
abstDomain: V200 (C-0-D15913-V200-cpt)
abstDomain: V200 (C-0-D15913-V200-cpt)
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
A prototype of the repeating
interval specifying the duration of each
occurrence and anchors the periodic interval
sequence at a certain point in time.
A prototype of the repeating
interval specifying the duration of each
occurrence and anchors the periodic interval
sequence at a certain point in time.
A prototype of the repeating
interval specifying the duration of each
occurrence and anchors the periodic interval
sequence at a certain point in time.
A prototype of the repeating
interval specifying the duration of each
occurrence and anchors the periodic interval
sequence at a certain point in time.
A prototype of the repeating
interval specifying the duration of each
occurrence and anchors the periodic interval
sequence at a certain point in time.
A prototype of the repeating
interval specifying the duration of each
occurrence and anchors the periodic interval
sequence at a certain point in time.
A prototype of the repeating
interval specifying the duration of each
occurrence and anchors the periodic interval
sequence at a certain point in time.
A time duration specifying a
reciprocal measure of the frequency at which
the periodic interval repeats.
A time duration specifying a
reciprocal measure of the frequency at which
the periodic interval repeats.
A time duration specifying a
reciprocal measure of the frequency at which
the periodic interval repeats.
A time duration specifying a
reciprocal measure of the frequency at which
the periodic interval repeats.
A time duration specifying a
reciprocal measure of the frequency at which
the periodic interval repeats.
A time duration specifying a
reciprocal measure of the frequency at which
the periodic interval repeats.
A time duration specifying a
reciprocal measure of the frequency at which
the periodic interval repeats.
Specifies if and how the repetitions
are aligned to the cycles of the underlying
calendar (e.g., to distinguish every 30 days from
"the 5th of every month".) A non-aligned periodic
interval recurs independently from the calendar. An
aligned periodic interval is synchronized with the
calendar.
Specifies if and how the repetitions
are aligned to the cycles of the underlying
calendar (e.g., to distinguish every 30 days from
"the 5th of every month".) A non-aligned periodic
interval recurs independently from the calendar. An
aligned periodic interval is synchronized with the
calendar.
Specifies if and how the repetitions
are aligned to the cycles of the underlying
calendar (e.g., to distinguish every 30 days from
"the 5th of every month".) A non-aligned periodic
interval recurs independently from the calendar. An
aligned periodic interval is synchronized with the
calendar.
Specifies if and how the repetitions
are aligned to the cycles of the underlying
calendar (e.g., to distinguish every 30 days from
"the 5th of every month".) A non-aligned periodic
interval recurs independently from the calendar. An
aligned periodic interval is synchronized with the
calendar.
Specifies if and how the repetitions
are aligned to the cycles of the underlying
calendar (e.g., to distinguish every 30 days from
"the 5th of every month".) A non-aligned periodic
interval recurs independently from the calendar. An
aligned periodic interval is synchronized with the
calendar.
Specifies if and how the repetitions
are aligned to the cycles of the underlying
calendar (e.g., to distinguish every 30 days from
"the 5th of every month".) A non-aligned periodic
interval recurs independently from the calendar. An
aligned periodic interval is synchronized with the
calendar.
Specifies if and how the repetitions
are aligned to the cycles of the underlying
calendar (e.g., to distinguish every 30 days from
"the 5th of every month".) A non-aligned periodic
interval recurs independently from the calendar. An
aligned periodic interval is synchronized with the
calendar.
Indicates whether the exact timing
is up to the party executing the schedule (e.g., to
distinguish "every 8 hours" from "3 times a day".)
Indicates whether the exact timing
is up to the party executing the schedule (e.g., to
distinguish "every 8 hours" from "3 times a day".)
Indicates whether the exact timing
is up to the party executing the schedule (e.g., to
distinguish "every 8 hours" from "3 times a day".)
Indicates whether the exact timing
is up to the party executing the schedule (e.g., to
distinguish "every 8 hours" from "3 times a day".)
Indicates whether the exact timing
is up to the party executing the schedule (e.g., to
distinguish "every 8 hours" from "3 times a day".)
Indicates whether the exact timing
is up to the party executing the schedule (e.g., to
distinguish "every 8 hours" from "3 times a day".)
Indicates whether the exact timing
is up to the party executing the schedule (e.g., to
distinguish "every 8 hours" from "3 times a day".)
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
Note: because this type is defined as an extension of
SXCM_T, all of the attributes and elements accepted for T are also
accepted by this definition. However, they are NOT allowed by the
normative description of this type. Unfortunately, we cannot write a
general purpose schematron contraints to provide that extra validation,
thus applications must be aware that instance (fragments) that pass
validation with this might might still not be legal.
A prototype of the repeating
interval specifying the duration of each
occurrence and anchors the periodic interval
sequence at a certain point in time.
A prototype of the repeating
interval specifying the duration of each
occurrence and anchors the periodic interval
sequence at a certain point in time.
A prototype of the repeating
interval specifying the duration of each
occurrence and anchors the periodic interval
sequence at a certain point in time.
A prototype of the repeating
interval specifying the duration of each
occurrence and anchors the periodic interval
sequence at a certain point in time.
A prototype of the repeating
interval specifying the duration of each
occurrence and anchors the periodic interval
sequence at a certain point in time.
A prototype of the repeating
interval specifying the duration of each
occurrence and anchors the periodic interval
sequence at a certain point in time.
A prototype of the repeating
interval specifying the duration of each
occurrence and anchors the periodic interval
sequence at a certain point in time.
A time duration specifying a
reciprocal measure of the frequency at which
the periodic interval repeats.
A time duration specifying a
reciprocal measure of the frequency at which
the periodic interval repeats.
A time duration specifying a
reciprocal measure of the frequency at which
the periodic interval repeats.
A time duration specifying a
reciprocal measure of the frequency at which
the periodic interval repeats.
A time duration specifying a
reciprocal measure of the frequency at which
the periodic interval repeats.
A time duration specifying a
reciprocal measure of the frequency at which
the periodic interval repeats.
A time duration specifying a
reciprocal measure of the frequency at which
the periodic interval repeats.
Specifies if and how the repetitions
are aligned to the cycles of the underlying
calendar (e.g., to distinguish every 30 days from
"the 5th of every month".) A non-aligned periodic
interval recurs independently from the calendar. An
aligned periodic interval is synchronized with the
calendar.
Specifies if and how the repetitions
are aligned to the cycles of the underlying
calendar (e.g., to distinguish every 30 days from
"the 5th of every month".) A non-aligned periodic
interval recurs independently from the calendar. An
aligned periodic interval is synchronized with the
calendar.
Specifies if and how the repetitions
are aligned to the cycles of the underlying
calendar (e.g., to distinguish every 30 days from
"the 5th of every month".) A non-aligned periodic
interval recurs independently from the calendar. An
aligned periodic interval is synchronized with the
calendar.
Specifies if and how the repetitions
are aligned to the cycles of the underlying
calendar (e.g., to distinguish every 30 days from
"the 5th of every month".) A non-aligned periodic
interval recurs independently from the calendar. An
aligned periodic interval is synchronized with the
calendar.
Specifies if and how the repetitions
are aligned to the cycles of the underlying
calendar (e.g., to distinguish every 30 days from
"the 5th of every month".) A non-aligned periodic
interval recurs independently from the calendar. An
aligned periodic interval is synchronized with the
calendar.
Specifies if and how the repetitions
are aligned to the cycles of the underlying
calendar (e.g., to distinguish every 30 days from
"the 5th of every month".) A non-aligned periodic
interval recurs independently from the calendar. An
aligned periodic interval is synchronized with the
calendar.
Specifies if and how the repetitions
are aligned to the cycles of the underlying
calendar (e.g., to distinguish every 30 days from
"the 5th of every month".) A non-aligned periodic
interval recurs independently from the calendar. An
aligned periodic interval is synchronized with the
calendar.
Indicates whether the exact timing
is up to the party executing the schedule (e.g., to
distinguish "every 8 hours" from "3 times a day".)
Indicates whether the exact timing
is up to the party executing the schedule (e.g., to
distinguish "every 8 hours" from "3 times a day".)
Indicates whether the exact timing
is up to the party executing the schedule (e.g., to
distinguish "every 8 hours" from "3 times a day".)
Indicates whether the exact timing
is up to the party executing the schedule (e.g., to
distinguish "every 8 hours" from "3 times a day".)
Indicates whether the exact timing
is up to the party executing the schedule (e.g., to
distinguish "every 8 hours" from "3 times a day".)
Indicates whether the exact timing
is up to the party executing the schedule (e.g., to
distinguish "every 8 hours" from "3 times a day".)
Indicates whether the exact timing
is up to the party executing the schedule (e.g., to
distinguish "every 8 hours" from "3 times a day".)
A name for a person. A sequence of name parts, such as
given name or family name, prefix, suffix, etc. PN differs from EN
because the qualifier type cannot include LS (Legal Status).
A name for a person. A sequence of name parts, such as
given name or family name, prefix, suffix, etc. PN differs from EN
because the qualifier type cannot include LS (Legal Status).
A name for a person. A sequence of name parts, such as
given name or family name, prefix, suffix, etc. PN differs from EN
because the qualifier type cannot include LS (Legal Status).
A name for a person. A sequence of name parts, such as
given name or family name, prefix, suffix, etc. PN differs from EN
because the qualifier type cannot include LS (Legal Status).
A name for a person. A sequence of name parts, such as
given name or family name, prefix, suffix, etc. PN differs from EN
because the qualifier type cannot include LS (Legal Status).
A name for a person. A sequence of name parts, such as
given name or family name, prefix, suffix, etc. PN differs from EN
because the qualifier type cannot include LS (Legal Status).
A name for a person. A sequence of name parts, such as
given name or family name, prefix, suffix, etc. PN differs from EN
because the qualifier type cannot include LS (Legal Status).
vocSet: D10637 (C-0-D10637-cpt)
vocSet: D10637 (C-0-D10637-cpt)
vocSet: D10637 (C-0-D10637-cpt)
vocSet: D10637 (C-0-D10637-cpt)
vocSet: D10637 (C-0-D10637-cpt)
vocSet: D10637 (C-0-D10637-cpt)
vocSet: D10637 (C-0-D10637-cpt)
The probability assigned to the value, a decimal
number between 0 (very uncertain) and 1 (certain).
The probability assigned to the value, a decimal
number between 0 (very uncertain) and 1 (certain).
The probability assigned to the value, a decimal
number between 0 (very uncertain) and 1 (certain).
The probability assigned to the value, a decimal
number between 0 (very uncertain) and 1 (certain).
The probability assigned to the value, a decimal
number between 0 (very uncertain) and 1 (certain).
The probability assigned to the value, a decimal
number between 0 (very uncertain) and 1 (certain).
The probability assigned to the value, a decimal
number between 0 (very uncertain) and 1 (certain).
specDomain: V19615 (C-0-D11603-V19615-cpt)
specDomain: V19615 (C-0-D11603-V19615-cpt)
specDomain: V19615 (C-0-D11603-V19615-cpt)
specDomain: V19615 (C-0-D11603-V19615-cpt)
specDomain: V19615 (C-0-D11603-V19615-cpt)
specDomain: V19615 (C-0-D11603-V19615-cpt)
specDomain: V19615 (C-0-D11603-V19615-cpt)
vocSet: D11555 (C-0-D11555-cpt)
vocSet: D11555 (C-0-D11555-cpt)
vocSet: D11555 (C-0-D11555-cpt)
vocSet: D11555 (C-0-D11555-cpt)
vocSet: D11555 (C-0-D11555-cpt)
vocSet: D11555 (C-0-D11555-cpt)
vocSet: D11555 (C-0-D11555-cpt)
specDomain: V14006
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-cpt)
specDomain: V14006
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-cpt)
specDomain: V14006
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-cpt)
specDomain: V14006
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-cpt)
specDomain: V14006
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-cpt)
specDomain: V14006
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-cpt)
specDomain: V14006
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-cpt)
abstDomain: V19313 (C-0-D11555-V13940-V19313-cpt)
abstDomain: V19313 (C-0-D11555-V13940-V19313-cpt)
abstDomain: V19313 (C-0-D11555-V13940-V19313-cpt)
abstDomain: V19313 (C-0-D11555-V13940-V19313-cpt)
abstDomain: V19313 (C-0-D11555-V13940-V19313-cpt)
abstDomain: V19313 (C-0-D11555-V13940-V19313-cpt)
abstDomain: V19313 (C-0-D11555-V13940-V19313-cpt)
specDomain: V12205
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-V11595-V12205-cpt)
specDomain: V12205
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-V11595-V12205-cpt)
specDomain: V12205
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-V11595-V12205-cpt)
specDomain: V12205
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-V11595-V12205-cpt)
specDomain: V12205
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-V11595-V12205-cpt)
specDomain: V12205
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-V11595-V12205-cpt)
specDomain: V12205
(C-0-D11555-V13940-V19313-V19316-V10416-V14006-V11595-V12205-cpt)
specDomain: V11569
(C-0-D11555-V13940-V19313-V19316-V10416-V11569-cpt)
specDomain: V11569
(C-0-D11555-V13940-V19313-V19316-V10416-V11569-cpt)
specDomain: V11569
(C-0-D11555-V13940-V19313-V19316-V10416-V11569-cpt)
specDomain: V11569
(C-0-D11555-V13940-V19313-V19316-V10416-V11569-cpt)
specDomain: V11569
(C-0-D11555-V13940-V19313-V19316-V10416-V11569-cpt)
specDomain: V11569
(C-0-D11555-V13940-V19313-V19316-V10416-V11569-cpt)
specDomain: V11569
(C-0-D11555-V13940-V19313-V19316-V10416-V11569-cpt)
specDomain: V19089
(C-0-D11555-V13940-V10429-V10430-V19089-cpt)
specDomain: V19089
(C-0-D11555-V13940-V10429-V10430-V19089-cpt)
specDomain: V19089
(C-0-D11555-V13940-V10429-V10430-V19089-cpt)
specDomain: V19089
(C-0-D11555-V13940-V10429-V10430-V19089-cpt)
specDomain: V19089
(C-0-D11555-V13940-V10429-V10430-V19089-cpt)
specDomain: V19089
(C-0-D11555-V13940-V10429-V10430-V19089-cpt)
specDomain: V19089
(C-0-D11555-V13940-V10429-V10430-V19089-cpt)
specDomain: V19587
(C-0-D11555-V13940-V19313-V19316-V10416-V19587-cpt)
specDomain: V19587
(C-0-D11555-V13940-V19313-V19316-V10416-V19587-cpt)
specDomain: V19587
(C-0-D11555-V13940-V19313-V19316-V10416-V19587-cpt)
specDomain: V19587
(C-0-D11555-V13940-V19313-V19316-V10416-V19587-cpt)
specDomain: V19587
(C-0-D11555-V13940-V19313-V19316-V10416-V19587-cpt)
specDomain: V19587
(C-0-D11555-V13940-V19313-V19316-V10416-V19587-cpt)
specDomain: V19587
(C-0-D11555-V13940-V19313-V19316-V10416-V19587-cpt)
specDomain: V16815
(C-0-D11555-V13940-V10429-V16815-cpt)
specDomain: V16815
(C-0-D11555-V13940-V10429-V16815-cpt)
specDomain: V16815
(C-0-D11555-V13940-V10429-V16815-cpt)
specDomain: V16815
(C-0-D11555-V13940-V10429-V16815-cpt)
specDomain: V16815
(C-0-D11555-V13940-V10429-V16815-cpt)
specDomain: V16815
(C-0-D11555-V13940-V10429-V16815-cpt)
specDomain: V16815
(C-0-D11555-V13940-V10429-V16815-cpt)
abstDomain: V19316
(C-0-D11555-V13940-V19313-V19316-cpt)
abstDomain: V19316
(C-0-D11555-V13940-V19313-V19316-cpt)
abstDomain: V19316
(C-0-D11555-V13940-V19313-V19316-cpt)
abstDomain: V19316
(C-0-D11555-V13940-V19313-V19316-cpt)
abstDomain: V19316
(C-0-D11555-V13940-V19313-V19316-cpt)
abstDomain: V19316
(C-0-D11555-V13940-V19313-V19316-cpt)
abstDomain: V19316
(C-0-D11555-V13940-V19313-V19316-cpt)
abstDomain: V10428 (C-0-D11555-V13940-V10428-cpt)
abstDomain: V10428 (C-0-D11555-V13940-V10428-cpt)
abstDomain: V10428 (C-0-D11555-V13940-V10428-cpt)
abstDomain: V10428 (C-0-D11555-V13940-V10428-cpt)
abstDomain: V10428 (C-0-D11555-V13940-V10428-cpt)
abstDomain: V10428 (C-0-D11555-V13940-V10428-cpt)
abstDomain: V10428 (C-0-D11555-V13940-V10428-cpt)
abstDomain: V10429 (C-0-D11555-V13940-V10429-cpt)
abstDomain: V10429 (C-0-D11555-V13940-V10429-cpt)
abstDomain: V10429 (C-0-D11555-V13940-V10429-cpt)
abstDomain: V10429 (C-0-D11555-V13940-V10429-cpt)
abstDomain: V10429 (C-0-D11555-V13940-V10429-cpt)
abstDomain: V10429 (C-0-D11555-V13940-V10429-cpt)
abstDomain: V10429 (C-0-D11555-V13940-V10429-cpt)
abstDomain: V19105
(C-0-D11555-V13940-V19313-V19105-cpt)
abstDomain: V19105
(C-0-D11555-V13940-V19313-V19105-cpt)
abstDomain: V19105
(C-0-D11555-V13940-V19313-V19105-cpt)
abstDomain: V19105
(C-0-D11555-V13940-V19313-V19105-cpt)
abstDomain: V19105
(C-0-D11555-V13940-V19313-V19105-cpt)
abstDomain: V19105
(C-0-D11555-V13940-V19313-V19105-cpt)
abstDomain: V19105
(C-0-D11555-V13940-V19313-V19105-cpt)
abstDomain: V10416
(C-0-D11555-V13940-V19313-V19316-V10416-cpt)
abstDomain: V10416
(C-0-D11555-V13940-V19313-V19316-V10416-cpt)
abstDomain: V10416
(C-0-D11555-V13940-V19313-V19316-V10416-cpt)
abstDomain: V10416
(C-0-D11555-V13940-V19313-V19316-V10416-cpt)
abstDomain: V10416
(C-0-D11555-V13940-V19313-V19316-V10416-cpt)
abstDomain: V10416
(C-0-D11555-V13940-V19313-V19316-V10416-cpt)
abstDomain: V10416
(C-0-D11555-V13940-V19313-V19316-V10416-cpt)
specDomain: V16927
(C-0-D11555-V13940-V19313-V19105-V16927-cpt)
specDomain: V16927
(C-0-D11555-V13940-V19313-V19105-V16927-cpt)
specDomain: V16927
(C-0-D11555-V13940-V19313-V19105-V16927-cpt)
specDomain: V16927
(C-0-D11555-V13940-V19313-V19105-V16927-cpt)
specDomain: V16927
(C-0-D11555-V13940-V19313-V19105-V16927-cpt)
specDomain: V16927
(C-0-D11555-V13940-V19313-V19105-V16927-cpt)
specDomain: V16927
(C-0-D11555-V13940-V19313-V19105-V16927-cpt)
specDomain: V11591
(C-0-D11555-V13940-V10429-V11591-cpt)
specDomain: V11591
(C-0-D11555-V13940-V10429-V11591-cpt)
specDomain: V11591
(C-0-D11555-V13940-V10429-V11591-cpt)
specDomain: V11591
(C-0-D11555-V13940-V10429-V11591-cpt)
specDomain: V11591
(C-0-D11555-V13940-V10429-V11591-cpt)
specDomain: V11591
(C-0-D11555-V13940-V10429-V11591-cpt)
specDomain: V11591
(C-0-D11555-V13940-V10429-V11591-cpt)
vocSet: D11603 (C-0-D11603-cpt)
vocSet: D11603 (C-0-D11603-cpt)
vocSet: D11603 (C-0-D11603-cpt)
vocSet: D11603 (C-0-D11603-cpt)
vocSet: D11603 (C-0-D11603-cpt)
vocSet: D11603 (C-0-D11603-cpt)
vocSet: D11603 (C-0-D11603-cpt)
A quantity constructed as the quotient of a numerator
quantity divided by a denominator quantity. Common factors in the
numerator and denominator are not automatically cancelled out. RTO
supports titers (e.g., "1:128") and other quantities produced by
laboratories that truly represent ratios. Ratios are not simply
"structured numerics", particularly blood pressure measurements (e.g.
"120/60") are not ratios. In many cases REAL should be used instead
of RTO.
A quantity constructed as the quotient of a numerator
quantity divided by a denominator quantity. Common factors in the
numerator and denominator are not automatically cancelled out. RTO
supports titers (e.g., "1:128") and other quantities produced by
laboratories that truly represent ratios. Ratios are not simply
"structured numerics", particularly blood pressure measurements (e.g.
"120/60") are not ratios. In many cases REAL should be used instead
of RTO.
A quantity constructed as the quotient of a numerator
quantity divided by a denominator quantity. Common factors in the
numerator and denominator are not automatically cancelled out. RTO
supports titers (e.g., "1:128") and other quantities produced by
laboratories that truly represent ratios. Ratios are not simply
"structured numerics", particularly blood pressure measurements (e.g.
"120/60") are not ratios. In many cases REAL should be used instead
of RTO.
A quantity constructed as the quotient of a numerator
quantity divided by a denominator quantity. Common factors in the
numerator and denominator are not automatically cancelled out. RTO
supports titers (e.g., "1:128") and other quantities produced by
laboratories that truly represent ratios. Ratios are not simply
"structured numerics", particularly blood pressure measurements (e.g.
"120/60") are not ratios. In many cases REAL should be used instead
of RTO.
A quantity constructed as the quotient of a numerator
quantity divided by a denominator quantity. Common factors in the
numerator and denominator are not automatically cancelled out. RTO
supports titers (e.g., "1:128") and other quantities produced by
laboratories that truly represent ratios. Ratios are not simply
"structured numerics", particularly blood pressure measurements (e.g.
"120/60") are not ratios. In many cases REAL should be used instead
of RTO.
A quantity constructed as the quotient of a numerator
quantity divided by a denominator quantity. Common factors in the
numerator and denominator are not automatically cancelled out. RTO
supports titers (e.g., "1:128") and other quantities produced by
laboratories that truly represent ratios. Ratios are not simply
"structured numerics", particularly blood pressure measurements (e.g.
"120/60") are not ratios. In many cases REAL should be used instead
of RTO.
A quantity constructed as the quotient of a numerator
quantity divided by a denominator quantity. Common factors in the
numerator and denominator are not automatically cancelled out. RTO
supports titers (e.g., "1:128") and other quantities produced by
laboratories that truly represent ratios. Ratios are not simply
"structured numerics", particularly blood pressure measurements (e.g.
"120/60") are not ratios. In many cases REAL should be used instead
of RTO.
HL7 reserved identifiers are strings consisting only of
(US-ASCII) letters, digits and hyphens, where the first character must
be a letter. HL7 may assign these reserved identifiers as mnemonic
identifiers for major concepts of interest to HL7.
HL7 reserved identifiers are strings consisting only of
(US-ASCII) letters, digits and hyphens, where the first character must
be a letter. HL7 may assign these reserved identifiers as mnemonic
identifiers for major concepts of interest to HL7.
HL7 reserved identifiers are strings consisting only of
(US-ASCII) letters, digits and hyphens, where the first character must
be a letter. HL7 may assign these reserved identifiers as mnemonic
identifiers for major concepts of interest to HL7.
HL7 reserved identifiers are strings consisting only of
(US-ASCII) letters, digits and hyphens, where the first character must
be a letter. HL7 may assign these reserved identifiers as mnemonic
identifiers for major concepts of interest to HL7.
HL7 reserved identifiers are strings consisting only of
(US-ASCII) letters, digits and hyphens, where the first character must
be a letter. HL7 may assign these reserved identifiers as mnemonic
identifiers for major concepts of interest to HL7.
HL7 reserved identifiers are strings consisting only of
(US-ASCII) letters, digits and hyphens, where the first character must
be a letter. HL7 may assign these reserved identifiers as mnemonic
identifiers for major concepts of interest to HL7.
HL7 reserved identifiers are strings consisting only of
(US-ASCII) letters, digits and hyphens, where the first character must
be a letter. HL7 may assign these reserved identifiers as mnemonic
identifiers for major concepts of interest to HL7.
A ST that optionally may have a code attached.
The text must always be present if a code is present. The code is often
a local code.
A ST that optionally may have a code attached.
The text must always be present if a code is present. The code is often
a local code.
A ST that optionally may have a code attached.
The text must always be present if a code is present. The code is often
a local code.
A ST that optionally may have a code attached.
The text must always be present if a code is present. The code is often
a local code.
A ST that optionally may have a code attached.
The text must always be present if a code is present. The code is often
a local code.
A ST that optionally may have a code attached.
The text must always be present if a code is present. The code is often
a local code.
A ST that optionally may have a code attached.
The text must always be present if a code is present. The code is often
a local code.
The plain code symbol defined by the
code system. For example, "784.0" is the code
symbol of the ICD-9 code "784.0" for headache.
The plain code symbol defined by the
code system. For example, "784.0" is the code
symbol of the ICD-9 code "784.0" for headache.
The plain code symbol defined by the
code system. For example, "784.0" is the code
symbol of the ICD-9 code "784.0" for headache.
The plain code symbol defined by the
code system. For example, "784.0" is the code
symbol of the ICD-9 code "784.0" for headache.
The plain code symbol defined by the
code system. For example, "784.0" is the code
symbol of the ICD-9 code "784.0" for headache.
The plain code symbol defined by the
code system. For example, "784.0" is the code
symbol of the ICD-9 code "784.0" for headache.
The plain code symbol defined by the
code system. For example, "784.0" is the code
symbol of the ICD-9 code "784.0" for headache.
Specifies the code system that
defines the code.
Specifies the code system that
defines the code.
Specifies the code system that
defines the code.
Specifies the code system that
defines the code.
Specifies the code system that
defines the code.
Specifies the code system that
defines the code.
Specifies the code system that
defines the code.
A common name of the coding system.
A common name of the coding system.
A common name of the coding system.
A common name of the coding system.
A common name of the coding system.
A common name of the coding system.
A common name of the coding system.
If applicable, a version descriptor
defined specifically for the given code system.
If applicable, a version descriptor
defined specifically for the given code system.
If applicable, a version descriptor
defined specifically for the given code system.
If applicable, a version descriptor
defined specifically for the given code system.
If applicable, a version descriptor
defined specifically for the given code system.
If applicable, a version descriptor
defined specifically for the given code system.
If applicable, a version descriptor
defined specifically for the given code system.
A name or title for the code, under
which the sending system shows the code value to
its users.
A name or title for the code, under
which the sending system shows the code value to
its users.
A name or title for the code, under
which the sending system shows the code value to
its users.
A name or title for the code, under
which the sending system shows the code value to
its users.
A name or title for the code, under
which the sending system shows the code value to
its users.
A name or title for the code, under
which the sending system shows the code value to
its users.
A name or title for the code, under
which the sending system shows the code value to
its users.
The origin of the list item
value scale, i.e., the physical quantity that a
zero-digit in the sequence would represent.
The origin of the list item
value scale, i.e., the physical quantity that a
zero-digit in the sequence would represent.
The origin of the list item
value scale, i.e., the physical quantity that a
zero-digit in the sequence would represent.
The origin of the list item
value scale, i.e., the physical quantity that a
zero-digit in the sequence would represent.
The origin of the list item
value scale, i.e., the physical quantity that a
zero-digit in the sequence would represent.
The origin of the list item
value scale, i.e., the physical quantity that a
zero-digit in the sequence would represent.
The origin of the list item
value scale, i.e., the physical quantity that a
zero-digit in the sequence would represent.
A ratio-scale quantity that is
factored out of the digit sequence.
A ratio-scale quantity that is
factored out of the digit sequence.
A ratio-scale quantity that is
factored out of the digit sequence.
A ratio-scale quantity that is
factored out of the digit sequence.
A ratio-scale quantity that is
factored out of the digit sequence.
A ratio-scale quantity that is
factored out of the digit sequence.
A ratio-scale quantity that is
factored out of the digit sequence.
A sequence of raw digits for the
sample values. This is typically the raw output
of an A/D converter.
A sequence of raw digits for the
sample values. This is typically the raw output
of an A/D converter.
A sequence of raw digits for the
sample values. This is typically the raw output
of an A/D converter.
A sequence of raw digits for the
sample values. This is typically the raw output
of an A/D converter.
A sequence of raw digits for the
sample values. This is typically the raw output
of an A/D converter.
A sequence of raw digits for the
sample values. This is typically the raw output
of an A/D converter.
A sequence of raw digits for the
sample values. This is typically the raw output
of an A/D converter.
The origin of the list item
value scale, i.e., the physical quantity that a
zero-digit in the sequence would represent.
The origin of the list item
value scale, i.e., the physical quantity that a
zero-digit in the sequence would represent.
The origin of the list item
value scale, i.e., the physical quantity that a
zero-digit in the sequence would represent.
The origin of the list item
value scale, i.e., the physical quantity that a
zero-digit in the sequence would represent.
The origin of the list item
value scale, i.e., the physical quantity that a
zero-digit in the sequence would represent.
The origin of the list item
value scale, i.e., the physical quantity that a
zero-digit in the sequence would represent.
The origin of the list item
value scale, i.e., the physical quantity that a
zero-digit in the sequence would represent.
A ratio-scale quantity that is
factored out of the digit sequence.
A ratio-scale quantity that is
factored out of the digit sequence.
A ratio-scale quantity that is
factored out of the digit sequence.
A ratio-scale quantity that is
factored out of the digit sequence.
A ratio-scale quantity that is
factored out of the digit sequence.
A ratio-scale quantity that is
factored out of the digit sequence.
A ratio-scale quantity that is
factored out of the digit sequence.
A sequence of raw digits for the
sample values. This is typically the raw output
of an A/D converter.
A sequence of raw digits for the
sample values. This is typically the raw output
of an A/D converter.
A sequence of raw digits for the
sample values. This is typically the raw output
of an A/D converter.
A sequence of raw digits for the
sample values. This is typically the raw output
of an A/D converter.
A sequence of raw digits for the
sample values. This is typically the raw output
of an A/D converter.
A sequence of raw digits for the
sample values. This is typically the raw output
of an A/D converter.
A sequence of raw digits for the
sample values. This is typically the raw output
of an A/D converter.
specDomain: V19455
(C-0-D10882-V19463-V10889-V19455-cpt)
specDomain: V19455
(C-0-D10882-V19463-V10889-V19455-cpt)
specDomain: V19455
(C-0-D10882-V19463-V10889-V19455-cpt)
specDomain: V19455
(C-0-D10882-V19463-V10889-V19455-cpt)
specDomain: V19455
(C-0-D10882-V19463-V10889-V19455-cpt)
specDomain: V19455
(C-0-D10882-V19463-V10889-V19455-cpt)
specDomain: V19455
(C-0-D10882-V19463-V10889-V19455-cpt)
specDomain: V14822 (C-0-D10642-V14822-cpt)
specDomain: V14822 (C-0-D10642-V14822-cpt)
specDomain: V14822 (C-0-D10642-V14822-cpt)
specDomain: V14822 (C-0-D10642-V14822-cpt)
specDomain: V14822 (C-0-D10642-V14822-cpt)
specDomain: V14822 (C-0-D10642-V14822-cpt)
specDomain: V14822 (C-0-D10642-V14822-cpt)
specDomain: V10648 (C-0-D10642-V14822-V10648-cpt)
specDomain: V10648 (C-0-D10642-V14822-V10648-cpt)
specDomain: V10648 (C-0-D10642-V14822-V10648-cpt)
specDomain: V10648 (C-0-D10642-V14822-V10648-cpt)
specDomain: V10648 (C-0-D10642-V14822-V10648-cpt)
specDomain: V10648 (C-0-D10642-V14822-V10648-cpt)
specDomain: V10648 (C-0-D10642-V14822-V10648-cpt)
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
A code specifying whether the set
component is included (union) or excluded
(set-difference) from the set, or other set
operations with the current set component and the
set as constructed from the representation stream
up to the current point.
vocSet: D201 (C-0-D201-cpt)
vocSet: D201 (C-0-D201-cpt)
vocSet: D201 (C-0-D201-cpt)
vocSet: D201 (C-0-D201-cpt)
vocSet: D201 (C-0-D201-cpt)
vocSet: D201 (C-0-D201-cpt)
vocSet: D201 (C-0-D201-cpt)
abstDomain: V19590 (C-0-D10317-V10329-V19590-cpt)
abstDomain: V19590 (C-0-D10317-V10329-V19590-cpt)
abstDomain: V19590 (C-0-D10317-V10329-V19590-cpt)
abstDomain: V19590 (C-0-D10317-V10329-V19590-cpt)
abstDomain: V19590 (C-0-D10317-V10329-V19590-cpt)
abstDomain: V19590 (C-0-D10317-V10329-V19590-cpt)
abstDomain: V19590 (C-0-D10317-V10329-V19590-cpt)
abstDomain: V14825 (C-0-D14824-V14825-cpt)
abstDomain: V14825 (C-0-D14824-V14825-cpt)
abstDomain: V14825 (C-0-D14824-V14825-cpt)
abstDomain: V14825 (C-0-D14824-V14825-cpt)
abstDomain: V14825 (C-0-D14824-V14825-cpt)
abstDomain: V14825 (C-0-D14824-V14825-cpt)
abstDomain: V14825 (C-0-D14824-V14825-cpt)
vocSet: D10706 (C-0-D10706-cpt)
vocSet: D10706 (C-0-D10706-cpt)
vocSet: D10706 (C-0-D10706-cpt)
vocSet: D10706 (C-0-D10706-cpt)
vocSet: D10706 (C-0-D10706-cpt)
vocSet: D10706 (C-0-D10706-cpt)
vocSet: D10706 (C-0-D10706-cpt)
specDomain: V10612 (C-0-D10609-V10610-V10612-cpt)
specDomain: V10612 (C-0-D10609-V10610-V10612-cpt)
specDomain: V10612 (C-0-D10609-V10610-V10612-cpt)
specDomain: V10612 (C-0-D10609-V10610-V10612-cpt)
specDomain: V10612 (C-0-D10609-V10610-V10612-cpt)
specDomain: V10612 (C-0-D10609-V10610-V10612-cpt)
specDomain: V10612 (C-0-D10609-V10610-V10612-cpt)
vocSet: D14866 (C-0-D14866-cpt)
vocSet: D14866 (C-0-D14866-cpt)
vocSet: D14866 (C-0-D14866-cpt)
vocSet: D14866 (C-0-D14866-cpt)
vocSet: D14866 (C-0-D14866-cpt)
vocSet: D14866 (C-0-D14866-cpt)
vocSet: D14866 (C-0-D14866-cpt)
A DCE Universal Unique Identifier is a globally unique
string consisting of 5 groups of upper- or lower-case hexadecimal digits
having 8, 4, 4, 4, and 12 places respectively. UUIDs are assigned using
Ethernet MAC addresses, the point in time of creation and some random
components. This mix is believed to generate sufficiently unique
identifiers without any organizational policy for identifier assignment
(in fact this piggy-backs on the organization of MAC address
assignment.)
A DCE Universal Unique Identifier is a globally unique
string consisting of 5 groups of upper- or lower-case hexadecimal digits
having 8, 4, 4, 4, and 12 places respectively. UUIDs are assigned using
Ethernet MAC addresses, the point in time of creation and some random
components. This mix is believed to generate sufficiently unique
identifiers without any organizational policy for identifier assignment
(in fact this piggy-backs on the organization of MAC address
assignment.)
A DCE Universal Unique Identifier is a globally unique
string consisting of 5 groups of upper- or lower-case hexadecimal digits
having 8, 4, 4, 4, and 12 places respectively. UUIDs are assigned using
Ethernet MAC addresses, the point in time of creation and some random
components. This mix is believed to generate sufficiently unique
identifiers without any organizational policy for identifier assignment
(in fact this piggy-backs on the organization of MAC address
assignment.)
A DCE Universal Unique Identifier is a globally unique
string consisting of 5 groups of upper- or lower-case hexadecimal digits
having 8, 4, 4, 4, and 12 places respectively. UUIDs are assigned using
Ethernet MAC addresses, the point in time of creation and some random
components. This mix is believed to generate sufficiently unique
identifiers without any organizational policy for identifier assignment
(in fact this piggy-backs on the organization of MAC address
assignment.)
A DCE Universal Unique Identifier is a globally unique
string consisting of 5 groups of upper- or lower-case hexadecimal digits
having 8, 4, 4, 4, and 12 places respectively. UUIDs are assigned using
Ethernet MAC addresses, the point in time of creation and some random
components. This mix is believed to generate sufficiently unique
identifiers without any organizational policy for identifier assignment
(in fact this piggy-backs on the organization of MAC address
assignment.)
A DCE Universal Unique Identifier is a globally unique
string consisting of 5 groups of upper- or lower-case hexadecimal digits
having 8, 4, 4, 4, and 12 places respectively. UUIDs are assigned using
Ethernet MAC addresses, the point in time of creation and some random
components. This mix is believed to generate sufficiently unique
identifiers without any organizational policy for identifier assignment
(in fact this piggy-backs on the organization of MAC address
assignment.)
A DCE Universal Unique Identifier is a globally unique
string consisting of 5 groups of upper- or lower-case hexadecimal digits
having 8, 4, 4, 4, and 12 places respectively. UUIDs are assigned using
Ethernet MAC addresses, the point in time of creation and some random
components. This mix is believed to generate sufficiently unique
identifiers without any organizational policy for identifier assignment
(in fact this piggy-backs on the organization of MAC address
assignment.)
The probability assigned to the value, a
decimal number between 0 (very uncertain) and 1
(certain).
The probability assigned to the value, a
decimal number between 0 (very uncertain) and 1
(certain).
The probability assigned to the value, a
decimal number between 0 (very uncertain) and 1
(certain).
The probability assigned to the value, a
decimal number between 0 (very uncertain) and 1
(certain).
The probability assigned to the value, a
decimal number between 0 (very uncertain) and 1
(certain).
The probability assigned to the value, a
decimal number between 0 (very uncertain) and 1
(certain).
The probability assigned to the value, a
decimal number between 0 (very uncertain) and 1
(certain).
abstDomain: V14845 (C-0-D14824-V14845-cpt)
abstDomain: V14845 (C-0-D14824-V14845-cpt)
abstDomain: V14845 (C-0-D14824-V14845-cpt)
abstDomain: V14845 (C-0-D14824-V14845-cpt)
abstDomain: V14845 (C-0-D14824-V14845-cpt)
abstDomain: V14845 (C-0-D14824-V14845-cpt)
abstDomain: V14845 (C-0-D14824-V14845-cpt)
specDomain: V19613 (C-0-D201-V190-V19613-cpt)
specDomain: V19613 (C-0-D201-V190-V19613-cpt)
specDomain: V19613 (C-0-D201-V190-V19613-cpt)
specDomain: V19613 (C-0-D201-V190-V19613-cpt)
specDomain: V19613 (C-0-D201-V190-V19613-cpt)
specDomain: V19613 (C-0-D201-V190-V19613-cpt)
specDomain: V19613 (C-0-D201-V190-V19613-cpt)
abstDomain: V19604 (C-0-D11527-V13856-V19604-cpt)
abstDomain: V19604 (C-0-D11527-V13856-V19604-cpt)
abstDomain: V19604 (C-0-D11527-V13856-V19604-cpt)
abstDomain: V19604 (C-0-D11527-V13856-V19604-cpt)
abstDomain: V19604 (C-0-D11527-V13856-V19604-cpt)
abstDomain: V19604 (C-0-D11527-V13856-V19604-cpt)
abstDomain: V19604 (C-0-D11527-V13856-V19604-cpt)
abstDomain: V19603 (C-0-D11527-V13856-V19603-cpt)
abstDomain: V19603 (C-0-D11527-V13856-V19603-cpt)
abstDomain: V19603 (C-0-D11527-V13856-V19603-cpt)
abstDomain: V19603 (C-0-D11527-V13856-V19603-cpt)
abstDomain: V19603 (C-0-D11527-V13856-V19603-cpt)
abstDomain: V19603 (C-0-D11527-V13856-V19603-cpt)
abstDomain: V19603 (C-0-D11527-V13856-V19603-cpt)
abstDomain: V19371 (C-0-D10196-V19371-cpt)
abstDomain: V19371 (C-0-D10196-V19371-cpt)
abstDomain: V19371 (C-0-D10196-V19371-cpt)
abstDomain: V19371 (C-0-D10196-V19371-cpt)
abstDomain: V19371 (C-0-D10196-V19371-cpt)
abstDomain: V19371 (C-0-D10196-V19371-cpt)
abstDomain: V19371 (C-0-D10196-V19371-cpt)
abstDomain: V18943 (C-0-D10196-V18943-cpt)
abstDomain: V18943 (C-0-D10196-V18943-cpt)
abstDomain: V18943 (C-0-D10196-V18943-cpt)
abstDomain: V18943 (C-0-D10196-V18943-cpt)
abstDomain: V18943 (C-0-D10196-V18943-cpt)
abstDomain: V18943 (C-0-D10196-V18943-cpt)
abstDomain: V18943 (C-0-D10196-V18943-cpt)
abstDomain: V18965 (C-0-D10196-V18965-cpt)
abstDomain: V18965 (C-0-D10196-V18965-cpt)
abstDomain: V18965 (C-0-D10196-V18965-cpt)
abstDomain: V18965 (C-0-D10196-V18965-cpt)
abstDomain: V18965 (C-0-D10196-V18965-cpt)
abstDomain: V18965 (C-0-D10196-V18965-cpt)
abstDomain: V18965 (C-0-D10196-V18965-cpt)
abstDomain: V16742 (C-0-D10196-V16742-cpt)
abstDomain: V16742 (C-0-D10196-V16742-cpt)
abstDomain: V16742 (C-0-D10196-V16742-cpt)
abstDomain: V16742 (C-0-D10196-V16742-cpt)
abstDomain: V16742 (C-0-D10196-V16742-cpt)
abstDomain: V16742 (C-0-D10196-V16742-cpt)
abstDomain: V16742 (C-0-D10196-V16742-cpt)
abstDomain: V16735 (C-0-D10196-V16735-cpt)
abstDomain: V16735 (C-0-D10196-V16735-cpt)
abstDomain: V16735 (C-0-D10196-V16735-cpt)
abstDomain: V16735 (C-0-D10196-V16735-cpt)
abstDomain: V16735 (C-0-D10196-V16735-cpt)
abstDomain: V16735 (C-0-D10196-V16735-cpt)
abstDomain: V16735 (C-0-D10196-V16735-cpt)
abstDomain: V16730 (C-0-D10196-V16730-cpt)
abstDomain: V16730 (C-0-D10196-V16730-cpt)
abstDomain: V16730 (C-0-D10196-V16730-cpt)
abstDomain: V16730 (C-0-D10196-V16730-cpt)
abstDomain: V16730 (C-0-D10196-V16730-cpt)
abstDomain: V16730 (C-0-D10196-V16730-cpt)
abstDomain: V16730 (C-0-D10196-V16730-cpt)
abstDomain: V19372 (C-0-D10196-V19372-cpt)
abstDomain: V19372 (C-0-D10196-V19372-cpt)
abstDomain: V19372 (C-0-D10196-V19372-cpt)
abstDomain: V19372 (C-0-D10196-V19372-cpt)
abstDomain: V19372 (C-0-D10196-V19372-cpt)
abstDomain: V19372 (C-0-D10196-V19372-cpt)
abstDomain: V19372 (C-0-D10196-V19372-cpt)
abstDomain: V11610 (C-0-D10317-V11610-cpt)
abstDomain: V11610 (C-0-D10317-V11610-cpt)
abstDomain: V11610 (C-0-D10317-V11610-cpt)
abstDomain: V11610 (C-0-D10317-V11610-cpt)
abstDomain: V11610 (C-0-D10317-V11610-cpt)
abstDomain: V11610 (C-0-D10317-V11610-cpt)
abstDomain: V11610 (C-0-D10317-V11610-cpt)
abstDomain: V19446 (C-0-D10317-V19446-cpt)
abstDomain: V19446 (C-0-D10317-V19446-cpt)
abstDomain: V19446 (C-0-D10317-V19446-cpt)
abstDomain: V19446 (C-0-D10317-V19446-cpt)
abstDomain: V19446 (C-0-D10317-V19446-cpt)
abstDomain: V19446 (C-0-D10317-V19446-cpt)
abstDomain: V19446 (C-0-D10317-V19446-cpt)
abstDomain: V19447 (C-0-D10317-V19447-cpt)
abstDomain: V19447 (C-0-D10317-V19447-cpt)
abstDomain: V19447 (C-0-D10317-V19447-cpt)
abstDomain: V19447 (C-0-D10317-V19447-cpt)
abstDomain: V19447 (C-0-D10317-V19447-cpt)
abstDomain: V19447 (C-0-D10317-V19447-cpt)
abstDomain: V19447 (C-0-D10317-V19447-cpt)
abstDomain: V19000 (C-0-D10317-V19000-cpt)
abstDomain: V19000 (C-0-D10317-V19000-cpt)
abstDomain: V19000 (C-0-D10317-V19000-cpt)
abstDomain: V19000 (C-0-D10317-V19000-cpt)
abstDomain: V19000 (C-0-D10317-V19000-cpt)
abstDomain: V19000 (C-0-D10317-V19000-cpt)
abstDomain: V19000 (C-0-D10317-V19000-cpt)
abstDomain: V19005 (C-0-D10317-V19005-cpt)
abstDomain: V19005 (C-0-D10317-V19005-cpt)
abstDomain: V19005 (C-0-D10317-V19005-cpt)
abstDomain: V19005 (C-0-D10317-V19005-cpt)
abstDomain: V19005 (C-0-D10317-V19005-cpt)
abstDomain: V19005 (C-0-D10317-V19005-cpt)
abstDomain: V19005 (C-0-D10317-V19005-cpt)
abstDomain: V19562 (C-0-D10317-V19562-cpt)
abstDomain: V19562 (C-0-D10317-V19562-cpt)
abstDomain: V19562 (C-0-D10317-V19562-cpt)
abstDomain: V19562 (C-0-D10317-V19562-cpt)
abstDomain: V19562 (C-0-D10317-V19562-cpt)
abstDomain: V19562 (C-0-D10317-V19562-cpt)
abstDomain: V19562 (C-0-D10317-V19562-cpt)
abstDomain: V19647 (C-0-D10878-V19647-cpt)
abstDomain: V19647 (C-0-D10878-V19647-cpt)
abstDomain: V19647 (C-0-D10878-V19647-cpt)
abstDomain: V19647 (C-0-D10878-V19647-cpt)
abstDomain: V19647 (C-0-D10878-V19647-cpt)
abstDomain: V19647 (C-0-D10878-V19647-cpt)
abstDomain: V19647 (C-0-D10878-V19647-cpt)
abstDomain: V19458 (C-0-D10196-V19458-cpt)
abstDomain: V19458 (C-0-D10196-V19458-cpt)
abstDomain: V19458 (C-0-D10196-V19458-cpt)
abstDomain: V19458 (C-0-D10196-V19458-cpt)
abstDomain: V19458 (C-0-D10196-V19458-cpt)
abstDomain: V19458 (C-0-D10196-V19458-cpt)
abstDomain: V19458 (C-0-D10196-V19458-cpt)
abstDomain: V19459 (C-0-D10196-V19459-cpt)
abstDomain: V19459 (C-0-D10196-V19459-cpt)
abstDomain: V19459 (C-0-D10196-V19459-cpt)
abstDomain: V19459 (C-0-D10196-V19459-cpt)
abstDomain: V19459 (C-0-D10196-V19459-cpt)
abstDomain: V19459 (C-0-D10196-V19459-cpt)
abstDomain: V19459 (C-0-D10196-V19459-cpt)
abstDomain: V19367 (C-0-D11555-V13940-V19367-cpt)
abstDomain: V19367 (C-0-D11555-V13940-V19367-cpt)
abstDomain: V19367 (C-0-D11555-V13940-V19367-cpt)
abstDomain: V19367 (C-0-D11555-V13940-V19367-cpt)
abstDomain: V19367 (C-0-D11555-V13940-V19367-cpt)
abstDomain: V19367 (C-0-D11555-V13940-V19367-cpt)
abstDomain: V19367 (C-0-D11555-V13940-V19367-cpt)
abstDomain: V19460 (C-0-D10196-V19460-cpt)
abstDomain: V19460 (C-0-D10196-V19460-cpt)
abstDomain: V19460 (C-0-D10196-V19460-cpt)
abstDomain: V19460 (C-0-D10196-V19460-cpt)
abstDomain: V19460 (C-0-D10196-V19460-cpt)
abstDomain: V19460 (C-0-D10196-V19460-cpt)
abstDomain: V19460 (C-0-D10196-V19460-cpt)
abstDomain: V19368 (C-0-D11555-V13940-V19368-cpt)
abstDomain: V19368 (C-0-D11555-V13940-V19368-cpt)
abstDomain: V19368 (C-0-D11555-V13940-V19368-cpt)
abstDomain: V19368 (C-0-D11555-V13940-V19368-cpt)
abstDomain: V19368 (C-0-D11555-V13940-V19368-cpt)
abstDomain: V19368 (C-0-D11555-V13940-V19368-cpt)
abstDomain: V19368 (C-0-D11555-V13940-V19368-cpt)
abstDomain: V19461 (C-0-D10196-V19461-cpt)
abstDomain: V19461 (C-0-D10196-V19461-cpt)
abstDomain: V19461 (C-0-D10196-V19461-cpt)
abstDomain: V19461 (C-0-D10196-V19461-cpt)
abstDomain: V19461 (C-0-D10196-V19461-cpt)
abstDomain: V19461 (C-0-D10196-V19461-cpt)
abstDomain: V19461 (C-0-D10196-V19461-cpt)
abstDomain: V19605 (C-0-D10901-V19605-cpt)
abstDomain: V19605 (C-0-D10901-V19605-cpt)
abstDomain: V19605 (C-0-D10901-V19605-cpt)
abstDomain: V19605 (C-0-D10901-V19605-cpt)
abstDomain: V19605 (C-0-D10901-V19605-cpt)
abstDomain: V19605 (C-0-D10901-V19605-cpt)
abstDomain: V19605 (C-0-D10901-V19605-cpt)
abstDomain: V16764 (C-0-D10901-V16764-cpt)
abstDomain: V16764 (C-0-D10901-V16764-cpt)
abstDomain: V16764 (C-0-D10901-V16764-cpt)
abstDomain: V16764 (C-0-D10901-V16764-cpt)
abstDomain: V16764 (C-0-D10901-V16764-cpt)
abstDomain: V16764 (C-0-D10901-V16764-cpt)
abstDomain: V16764 (C-0-D10901-V16764-cpt)
abstDomain: V19462 (C-0-D10882-V19462-cpt)
abstDomain: V19462 (C-0-D10882-V19462-cpt)
abstDomain: V19462 (C-0-D10882-V19462-cpt)
abstDomain: V19462 (C-0-D10882-V19462-cpt)
abstDomain: V19462 (C-0-D10882-V19462-cpt)
abstDomain: V19462 (C-0-D10882-V19462-cpt)
abstDomain: V19462 (C-0-D10882-V19462-cpt)
abstDomain: V19463 (C-0-D10882-V19463-cpt)
abstDomain: V19463 (C-0-D10882-V19463-cpt)
abstDomain: V19463 (C-0-D10882-V19463-cpt)
abstDomain: V19463 (C-0-D10882-V19463-cpt)
abstDomain: V19463 (C-0-D10882-V19463-cpt)
abstDomain: V19463 (C-0-D10882-V19463-cpt)
abstDomain: V19463 (C-0-D10882-V19463-cpt)
abstDomain: V19366 (C-0-D10901-V19366-cpt)
abstDomain: V19366 (C-0-D10901-V19366-cpt)
abstDomain: V19366 (C-0-D10901-V19366-cpt)
abstDomain: V19366 (C-0-D10901-V19366-cpt)
abstDomain: V19366 (C-0-D10901-V19366-cpt)
abstDomain: V19366 (C-0-D10901-V19366-cpt)
abstDomain: V19366 (C-0-D10901-V19366-cpt)
abstDomain: V16772 (C-0-D11555-V13940-V16772-cpt)
abstDomain: V16772 (C-0-D11555-V13940-V16772-cpt)
abstDomain: V16772 (C-0-D11555-V13940-V16772-cpt)
abstDomain: V16772 (C-0-D11555-V13940-V16772-cpt)
abstDomain: V16772 (C-0-D11555-V13940-V16772-cpt)
abstDomain: V16772 (C-0-D11555-V13940-V16772-cpt)
abstDomain: V16772 (C-0-D11555-V13940-V16772-cpt)
abstDomain: V15881 (C-0-D15880-V15881-cpt)
abstDomain: V15881 (C-0-D15880-V15881-cpt)
abstDomain: V15881 (C-0-D15880-V15881-cpt)
abstDomain: V15881 (C-0-D15880-V15881-cpt)
abstDomain: V15881 (C-0-D15880-V15881-cpt)
abstDomain: V15881 (C-0-D15880-V15881-cpt)
abstDomain: V15881 (C-0-D15880-V15881-cpt)
abstDomain: V19080 (C-0-D10901-V19080-cpt)
abstDomain: V19080 (C-0-D10901-V19080-cpt)
abstDomain: V19080 (C-0-D10901-V19080-cpt)
abstDomain: V19080 (C-0-D10901-V19080-cpt)
abstDomain: V19080 (C-0-D10901-V19080-cpt)
abstDomain: V19080 (C-0-D10901-V19080-cpt)
abstDomain: V19080 (C-0-D10901-V19080-cpt)
abstDomain: V19600 (C-0-D10901-V19600-cpt)
abstDomain: V19600 (C-0-D10901-V19600-cpt)
abstDomain: V19600 (C-0-D10901-V19600-cpt)
abstDomain: V19600 (C-0-D10901-V19600-cpt)
abstDomain: V19600 (C-0-D10901-V19600-cpt)
abstDomain: V19600 (C-0-D10901-V19600-cpt)
abstDomain: V19600 (C-0-D10901-V19600-cpt)
abstDomain: V19601 (C-0-D10901-V19601-cpt)
abstDomain: V19601 (C-0-D10901-V19601-cpt)
abstDomain: V19601 (C-0-D10901-V19601-cpt)
abstDomain: V19601 (C-0-D10901-V19601-cpt)
abstDomain: V19601 (C-0-D10901-V19601-cpt)
abstDomain: V19601 (C-0-D10901-V19601-cpt)
abstDomain: V19601 (C-0-D10901-V19601-cpt)
abstDomain: V19083 (C-0-D10901-V19083-cpt)
abstDomain: V19083 (C-0-D10901-V19083-cpt)
abstDomain: V19083 (C-0-D10901-V19083-cpt)
abstDomain: V19083 (C-0-D10901-V19083-cpt)
abstDomain: V19083 (C-0-D10901-V19083-cpt)
abstDomain: V19083 (C-0-D10901-V19083-cpt)
abstDomain: V19083 (C-0-D10901-V19083-cpt)
abstDomain: V10653 (C-0-D15880-V10653-cpt)
abstDomain: V10653 (C-0-D15880-V10653-cpt)
abstDomain: V10653 (C-0-D15880-V10653-cpt)
abstDomain: V10653 (C-0-D15880-V10653-cpt)
abstDomain: V10653 (C-0-D15880-V10653-cpt)
abstDomain: V10653 (C-0-D15880-V10653-cpt)
abstDomain: V10653 (C-0-D15880-V10653-cpt)
abstDomain: V19382 (C-0-D11555-V13940-V19382-cpt)
abstDomain: V19382 (C-0-D11555-V13940-V19382-cpt)
abstDomain: V19382 (C-0-D11555-V13940-V19382-cpt)
abstDomain: V19382 (C-0-D11555-V13940-V19382-cpt)
abstDomain: V19382 (C-0-D11555-V13940-V19382-cpt)
abstDomain: V19382 (C-0-D11555-V13940-V19382-cpt)
abstDomain: V19382 (C-0-D11555-V13940-V19382-cpt)
abstDomain: V14008 (C-0-D11555-V13940-V14008-cpt)
abstDomain: V14008 (C-0-D11555-V13940-V14008-cpt)
abstDomain: V14008 (C-0-D11555-V13940-V14008-cpt)
abstDomain: V14008 (C-0-D11555-V13940-V14008-cpt)
abstDomain: V14008 (C-0-D11555-V13940-V14008-cpt)
abstDomain: V14008 (C-0-D11555-V13940-V14008-cpt)
abstDomain: V14008 (C-0-D11555-V13940-V14008-cpt)
abstDomain: V14013 (C-0-D11555-V13940-V14013-cpt)
abstDomain: V14013 (C-0-D11555-V13940-V14013-cpt)
abstDomain: V14013 (C-0-D11555-V13940-V14013-cpt)
abstDomain: V14013 (C-0-D11555-V13940-V14013-cpt)
abstDomain: V14013 (C-0-D11555-V13940-V14013-cpt)
abstDomain: V14013 (C-0-D11555-V13940-V14013-cpt)
abstDomain: V14013 (C-0-D11555-V13940-V14013-cpt)
abstDomain: V16930 (C-0-D11555-V13940-V16930-cpt)
abstDomain: V16930 (C-0-D11555-V13940-V16930-cpt)
abstDomain: V16930 (C-0-D11555-V13940-V16930-cpt)
abstDomain: V16930 (C-0-D11555-V13940-V16930-cpt)
abstDomain: V16930 (C-0-D11555-V13940-V16930-cpt)
abstDomain: V16930 (C-0-D11555-V13940-V16930-cpt)
abstDomain: V16930 (C-0-D11555-V13940-V16930-cpt)
abstDomain: V19395 (C-0-D11555-V13940-V19395-cpt)
abstDomain: V19395 (C-0-D11555-V13940-V19395-cpt)
abstDomain: V19395 (C-0-D11555-V13940-V19395-cpt)
abstDomain: V19395 (C-0-D11555-V13940-V19395-cpt)
abstDomain: V19395 (C-0-D11555-V13940-V19395-cpt)
abstDomain: V19395 (C-0-D11555-V13940-V19395-cpt)
abstDomain: V19395 (C-0-D11555-V13940-V19395-cpt)
abstDomain: V19606 (C-0-D10901-V19606-cpt)
abstDomain: V19606 (C-0-D10901-V19606-cpt)
abstDomain: V19606 (C-0-D10901-V19606-cpt)
abstDomain: V19606 (C-0-D10901-V19606-cpt)
abstDomain: V19606 (C-0-D10901-V19606-cpt)
abstDomain: V19606 (C-0-D10901-V19606-cpt)
abstDomain: V19606 (C-0-D10901-V19606-cpt)