In the previous blogpost I described how you could send a resource to Clinfhir using a Simplifier Connector. Today I am going describe how these connectors work and how a connector is made.
A connector will always have direct access to the resource and to the resource FHIR endpoint on the page from where the connector is started. That way a connector can either ask a different server to look up the resource, or post the resource to that server.
Before a resource is made public, it must go through a small vetting proces, because these scripts can still create vulnerable situations if not monitored.
In your Simplifier portal you get a list of all the connectors you are subscribed to. You can unsubscribe to them or subscribe to a new connector by using the Shop button. That way you only have to deal with Connectors that you are interested in.
The second connector we wrote that I want to introduce to you, is our FluentPathDemo. FhirPath (a specific implementation of FluentPath) is very likely going to be the language for the invariants (busines rules of Fhir Resources in STU3).
You can now send a simplifier resource to an updated FluentPath Demo.
- Go to Simplifier and find an example resource. For example, this one:
- Click on the Connect menu and choose “FluentPath Demo”
- You can now start typing FhirPath.
With the example resource above, in the FluentPath Demo you can type in
to get all identifiers of the contained resources.
If you type
contained.identifier.where(id = 'DNI')
you would get just the one identifier where the id equals DNI.
If you want to learn more about FhirPath, you can read about it here.
Next week, I will introduce a more complex Connector that calls validation on a different server.