Stream: implementers
Topic: FHIR Certification
Ali Haider (Sep 14 2019 at 13:40):
I am currently working on implementation of FHIR API. My question is do I need to register it or is there any Certification required for FHIR API?
I have implemented Read operation in my FHIR API.
Metadata for my API is given below
{
"resourceType": "Conformance",
"text": {
"status": "generated",
"div": "<div>Generated Conformance Statement</ div>"
},
"url": "https://myorg.com/api/fhir/metadata",
"name": "EHR Conformance Statement",
"status": "draft",
"publisher": "org",
"date": "9/14/2019 9:36:42 AM",
"description": "Describes capabilities of this server",
"kind": "Instance",
"fhirVersion": "1.0.2",
"acceptUnknown": "no",
"format": [
"json"
],
"rest": [
{
"mode": "server",
"documentation": "All the functionality defined in FHIR",
"security": {
"extension": [
{
"url": "http://fhir-registry.smarthealthit.org/StructureDefinition/oauth-uris",
"extension": [
{
"url": "token",
"valueUri": "https://myorg.com/Token"
},
{
"url": "authorize",
"valueUri": "https://myorg.com/Authorize"
},
{
"url": "introspect",
"valueUri": "https://myorg.com/Introspect"
},
{
"url": "revoke",
"valueUri": "https://myorg.com/Revoke"
}
]
}
],
"cors": true,
"service": [
{
"coding": [
{
"system": "http://hl7.org/fhir/restful-security-service",
"code": "SMART-on-FHIR"
}
],
"text": "OAuth2 using SMART-on-FHIR profile (see http://docs.smarthealthit.org/)."
}
],
"description": "OAuth2 plus SMART extensions"
},
"resource": [
{
"type": "Conformance",
"interaction": [
{
"code": [
"read"
]
}
],
"searchParam": null
},
{
"type": "Patient",
"interaction": [
{
"code": [
"read"
]
}
],
"searchParam": null
},
{
"type": "Observation",
"interaction": [
{
"code": [
"read"
]
}
],
"searchParam": null
},
{
"type": "Immunization",
"interaction": [
{
"code": [
"read"
]
}
],
"searchParam": null
},
{
"type": "AllergyIntolerance",
"interaction": [
{
"code": [
"read"
]
}
],
"searchParam": null
},
{
"type": "Procedure",
"interaction": [
{
"code": [
"read"
]
}
],
"searchParam": null
},
{
"type": "Condition",
"interaction": [
{
"code": [
"read"
]
}
],
"searchParam": null
},
{
"type": "DiagnosticReport",
"interaction": [
{
"code": [
"read"
]
}
],
"searchParam": null
}
],
"operation": [
{
"name": "",
"definition": {
"reference": "",
"display": ""
}
},
{
"name": "docref",
"definition": {
"reference": "Argonaut Get DocumentReferences",
"display": "http://hl7.org/fhir/us/core/STU3/OperationDefinition-docref.html"
}
}
]
}
]
}
Lloyd McKenzie (Sep 14 2019 at 14:07):
There isn't currently any certification process required for FHIR - and there probably never will be for the 'core' specification given that technically you're FHIR conformant if you expose a Conformance/CapabilityStatement that declares "I don't support any resources, messages or documents". Instead, certification processes will typically be developed around implementation guides, and then probably only against those that are "normative" - i.e. they're locked down into backward compatibility mode such that a certification against one version would still have relevance with respect to later versions.
Lloyd McKenzie (Sep 14 2019 at 14:10):
There is an implementation registry you could put some information about your system in if you like. The link is here: https://www.fhir.org/implementations/registry/, though at the moment it doesn't seem to be resolving to the correct place. (@Grahame Grieve ?)
Grahame Grieve (Sep 14 2019 at 14:14):
fixing it is on my list
Ali Haider (Sep 14 2019 at 14:50):
Thank you @Lloyd McKenzie
I also need help regarding this URL 'http://fhir-registry.smarthealthit.org/StructureDefinition/oauth-uris' in Conformance document. Do I have to make a URL like this or I can use as it is in my Conformance document. I am currently working on a project and we have to integrate our API.
Lloyd McKenzie (Sep 14 2019 at 15:19):
StructureDefinition and Conformance are different resources. You should have a Conformance instance that's specific to your server. If you describe your capabilities at a resource-specific level, typically you'd have your own StructureDefinition instances too as they should reflect your server's specific constraints (which will often differ, at least subtly, from the 'standard' profiles published as part of specs ).
Ali Haider (Sep 14 2019 at 18:40):
should I have to define my own Restful Security Service URL as well and what would be the Code in Coding any idea about this....
Please see the below:
"service": [
{
"coding": [
{
"system": "http://hl7.org/fhir/restful-security-service",
"code": "SMART-on-FHIR"
}
], "text": "OAuth2 using SMART-on-FHIR profile (see http://docs.smarthealthit
}
], "description": "OAuth2 plus SMART extensions"
Last updated: Apr 12 2022 at 19:14 UTC
