This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Profile Tooling

From HL7Wiki
Revision as of 21:22, 14 September 2014 by GrahameGrieve (talk | contribs) (Created page with "This page gathers together links for tools that work with or on profiles for FHIR. Tools are categorised into several functional categories: = Editing / Authoring Profiles = ...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

This page gathers together links for tools that work with or on profiles for FHIR. Tools are categorised into several functional categories:

Editing / Authoring Profiles

The following choices exist for editing profiles

  • By Hand
    • Use a schema drive editor against Profile.xsd in the FHIR schemas
    • start with an existing profile (look for the link under the structure definition on the page for the resource)
    • edit the profile as you see fit
    • Note: profiles are full rich description of the content, and so they're pretty hard to edit by hand. You an do this but it's not the intention
  • Using Forge
    • see .. link to be provided...

Validating Resources against Profiles

Publishing Profiles

Implementation Guides

Public Registries

Data Entry Tools

Resources are able to declare that they conform to a profile 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:

Other validation libraries are planned, but not yet implemented