|
|
| Line 1: |
Line 1: |
| − | Resources are able to declare that they conform to a profile
| + | Content moved to [[Profile Tooling]] |
| − | by being "tagged" with the URI that identifies the profile.
| |
| − | The tags are moved as [[ Atom category elements]] in a bundle,
| |
| − | or in the [[ category header]] in an HTTP call. This is an example
| |
| − | profile tag in a bundle (e.g. Atom Feed):
| |
| − | | |
| − | <category term="http://hl7.org/fhir/tag/message" label="Message" scheme="http://hl7.org/fhir/tag"/>
| |
| − | | |
| − | And in the HTTP Headers:
| |
| − | | |
| − | Category: http://hl7.org/fhir/tag/message; scheme="http://hl7.org/fhir/tag"; label="Message"
| |
| − | | |
| − | Note that just because a resource conforms to the
| |
| − | rules of a profile, it is not guaranteed to actually
| |
| − | conforms to it.
| |
| − | | |
| − | In order to be confident that the resource
| |
| − | does conform, a user or application can ask a validation service
| |
| − | to check that it does conform by:
| |
| − | * Using the validation service via browser at http://fhir.healthintersections.com.au/open#upload. Notes:
| |
| − | ** Choose Operation "Validation", and the profile you want to use
| |
| − | ** In order to use this, the profile must first be uploaded onto the server
| |
| − | * use the validation service via REST - post XML or JSON to
| |
| − | ** [base]/[type]/_validate
| |
| − | ** http://fhir.healthintersections.com.au/open is the base for one server that implements validation
| |
| − | * use the validation jar (see the [[http://hl7.org/documentcenter/public/standards/FHIR/validator.zip the download]] for instructions)
| |
| − | * use the java classes directly (see the FHIR svn, see http://gforge.hl7.org/gf/project/fhir/)
| |
| − | | |
| − | Other validation libraries are planned, but not yet implemented
| |
