5

I've looked at the documentation for creating profiles for FHIR, and I've used Forge to create some xml that I believe is valid to describe a profile. I can't find in the documentation where it actually states what request I need to make to the RESTful api to actually add a new profile.

Any ideas?

Andy
  • 3,228
  • 8
  • 40
  • 65

1 Answers1

3

You can of course just "store" your profiles on a FHIR server by POSTing them to a FHIR endpoint, but you probably mean: can I actively let instances be validated against the StructureDefinition?

There are two ways, both of which require a bit of experimentation to see which public servers support them:

  • Any FHIR instance may declare it adheres to a StructureDefinition, by adding the canononical url (StructureDefinition.url) to the instances meta.profile as shown below. Servers may pick this up on a POST and validate the instance against the stated profile:
  <Patient>
    <id value="44Q3"/>
    <meta>
      <profile value="http://example.org/StructureDefinition/PatientNL"/>
    </meta>
  </Patient>
Günter Zöchbauer
  • 623,577
  • 216
  • 2,003
  • 1,567
Ewout Kramer
  • 984
  • 6
  • 9
  • So posting the `StructureDefinition` doesn't have any effect on the behavior of a FHIR server or is this just implementation specific whether a server uses these SDs for validation or not? – Günter Zöchbauer Oct 17 '16 at 11:42
  • Correct, posting a SD will not change the behavior of FHIR servers. But as Ewout already said, a FHIR server may validate an instance against the profile(s) listed in the metadata of that instance. – Mirjam Baltus Oct 17 '16 at 12:19