This page is part of the FHIR Specification (v0.0.82: DSTU 1). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions Operation-valueset-batch This is the narrative for the resource. See also the XML or JSON format. Batch Mode Validation OPERATION: Batch Mode Validation Validate a set of concepts against value sets in a single oeration Typically, this would be called when a validating a resource or document that contains many codes, to reduce network latency events URL: [base]/ValueSet/$Batch Mode Validation Parameters Use Name Cardinality Type Documentation IN item 0..* An item to be validated concept 1..1 CodeableConcept A codeable concept to be validated. If the source is a coding, or a code/system pair, wrap it in a CodeableConcept uri 1..1 uri The value set to validate the concept against. This is a logical value set identifier (i.e. ValueSet.identifier). The server must know the value set (e.g. it is defined explicitly in the server's valuesets, or it is defined implicitly by some code system known to the server IN date 0..1 dateTime The date for which the validation should be checked. Normally, this is the current conditions (which is the default values) but under some circumstances, systems need to validate that a correct code was used at some point in the past. A typical example of this would be where code selection is constrained to the set of codes that were available when the patient was treated, not when the record is being edited. Note that which date is appropriate is a matter for implementation policy. OUT item 0..* The outcome of validating an item. There must be an entry for every item in the same order result 1..1 boolean True if the concept details supplied are valid message 0..1 string Error details, if result = false. If this is provided when result = true, the message carries hints and wanrings display 0..1 string A valid display for the concept if the system wishes to display this to a user   Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification. © HL7.org 2011+. FHIR DSTU (v0.4.0-4902) generated on Fri, Mar 27, 2015 00:14+1100. Links: What's a DSTU? | Version History | Specification Map | Compare to DSTU1 | | Propose a change