API documentation for HeyDonto API users
curl -i -X GET \ 'https://docs.heydonto.com/_mock/apis/fhir/openapi/fhir/capability-statement?_count=0&_page_token=string' \ -H 'Authorization: Bearer <YOUR_JWT_HERE>'
Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.
Indicates the purpose of this bundle - how it is intended to be used.
An instant in time - known at least to the second
A series of links that provide context to this bundle.
An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).
A signature along with supporting context. The signature may be a digital signature that is cryptographic in nature, or some other signature acceptable to the domain. This other signature may be as simple as a graphical image representing a hand-written signature, or a signature ceremony Different signature approaches have different utilities.
{ "resourceType": "Bundle", "type": "searchset", "total": 100, "link": [ { … }, { … }, { … }, { … } ], "entry": [ { … } ] }
This is a CapabilityStatement resource
Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
A human-readable summary of the resource conveying the essential clinical and business information for the resource.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
The status of this capability statement. Enables tracking the life-cycle of the content.
A date, date-time or partial date (e.g. just year or year + month). If hours and minutes are specified, a time zone SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates.
Contact details to assist a user in finding and communicating with the publisher.
A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate capability statement instances.
A legal or geographic region in which the capability statement is intended to be used.
A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
The way that this statement is intended to be used, to describe an actual running instance of software, a particular product (kind, not instance of software) or a class of implementation (e.g. a desired purchase).
Reference to a canonical URL of another CapabilityStatement that this software implements. This capability statement is a published API description that corresponds to a business service. The server may actually implement a subset of the capability statement it claims to implement, so the capability statement must specify the full capability details.
Reference to a canonical URL of another CapabilityStatement that this software adds to. The capability statement automatically includes everything in the other statement, and it is not duplicated, though the server may repeat the same resources, interactions and operations to add additional details to them.
A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
The version of the FHIR specification that this CapabilityStatement describes (which SHALL be the same as the FHIR version of the CapabilityStatement itself). There is no default value.
A list of the formats supported by this implementation using their content types.
A list of the patch formats supported by this implementation using their content types.
A list of implementation guides that the server does (or should) support in their entirety.
A definition of the restful capabilities of the solution, if any.
A description of the messaging capabilities of the solution.
A document definition.
curl -i -X POST \ https://docs.heydonto.com/_mock/apis/fhir/openapi/fhir/capability-statement \ -H 'Authorization: Bearer <YOUR_JWT_HERE>' \ -H 'Content-Type: application/json' \ -d '{ "resourceType": "CapabilityStatement", "id": "example", "text": { "status": "generated", "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n\t\t\t<p>The EHR Server supports the following transactions for the resource Person: read, vread, \n update, history, search(name,gender), create and updates.</p>\n\t\t\t<p>The EHR System supports the following message: admin-notify::Person.</p>\n\t\t\t<p>The EHR Application has a \n <a href=\"http://fhir.hl7.org/base/Profilebc054d23-75e1-4dc6-aca5-838b6b1ac81d/_history/b5fdd9fc-b021-4ea1-911a-721a60663796\">general document profile</a>.\n </p>\n\t\t</div>" }, "url": "urn:uuid:68D043B5-9ECF-4559-A57A-396E0D452311", "version": "20130510", "name": "ACME-EHR", "title": "ACME EHR capability statement", "status": "draft", "experimental": true, "date": "2012-01-04", "publisher": "ACME Corporation", "contact": [ { "name": "System Administrator", "telecom": [ { "system": "email", "value": "wile@acme.org" } ] } ], "description": "This is the FHIR capability statement for the main EHR at ACME for the private interface - it does not describe the public interface", "useContext": [ { "code": { "system": "http://terminology.hl7.org/CodeSystem/usage-context-type", "code": "focus" }, "valueCodeableConcept": { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/variant-state", "code": "positive" } ] } } ], "jurisdiction": [ { "coding": [ { "system": "urn:iso:std:iso:3166", "code": "US", "display": "United States of America (the)" } ] } ], "purpose": "Main EHR capability statement, published for contracting and operational support", "copyright": "Copyright © Acme Healthcare and GoodCorp EHR Systems", "kind": "instance", "instantiates": [ "http://ihe.org/fhir/CapabilityStatement/pixm-client" ], "software": { "name": "EHR", "version": "0.00.020.2134", "releaseDate": "2012-01-04" }, "implementation": { "description": "main EHR at ACME", "url": "http://10.2.3.4/fhir" }, "fhirVersion": "4.0.1", "format": [ "xml", "json" ], "patchFormat": [ "application/xml-patch+xml", "application/json-patch+json" ], "implementationGuide": [ "http://hl7.org/fhir/us/lab" ], "rest": [ { "mode": "server", "documentation": "Main FHIR endpoint for acem health", "security": { "cors": true, "service": [ { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/restful-security-service", "code": "SMART-on-FHIR" } ] } ], "description": "See Smart on FHIR documentation" }, "resource": [ { "type": "Patient", "profile": "http://registry.fhir.org/r4/StructureDefinition/7896271d-57f6-4231-89dc-dcc91eab2416", "supportedProfile": [ "http://registry.fhir.org/r4/StructureDefinition/00ab9e7a-06c7-4f77-9234-4154ca1e3347" ], "documentation": "This server does not let the clients create identities.", "interaction": [ { "code": "read" }, { "code": "vread", "documentation": "Only supported for patient records since 12-Dec 2012" }, { "code": "update" }, { "code": "history-instance" }, { "code": "create" }, { "code": "history-type" } ], "versioning": "versioned-update", "readHistory": true, "updateCreate": false, "conditionalCreate": true, "conditionalRead": "full-support", "conditionalUpdate": false, "conditionalDelete": "not-supported", "searchInclude": [ "Organization" ], "searchRevInclude": [ "Person" ], "searchParam": [ { "name": "identifier", "definition": "http://hl7.org/fhir/SearchParameter/Patient-identifier", "type": "token", "documentation": "Only supports search by institution MRN" }, { "name": "general-practitioner", "definition": "http://hl7.org/fhir/SearchParameter/Patient-general-practitioner", "type": "reference" } ] } ], "interaction": [ { "code": "transaction" }, { "code": "history-system" } ], "compartment": [ "http://hl7.org/fhir/CompartmentDefinition/patient" ] } ], "messaging": [ { "endpoint": [ { "protocol": { "system": "http://terminology.hl7.org/CodeSystem/message-transport", "code": "mllp" }, "address": "mllp:10.1.1.10:9234" } ], "reliableCache": 30, "documentation": "ADT A08 equivalent for external system notifications", "supportedMessage": [ { "mode": "receiver", "definition": "MessageDefinition/example" } ] } ], "document": [ { "mode": "consumer", "documentation": "Basic rules for all documents in the EHR system", "profile": "http://fhir.hl7.org/base/Profilebc054d23-75e1-4dc6-aca5-838b6b1ac81d/_history/b5fdd9fc-b021-4ea1-911a-721a60663796" } ] }'
This is a CapabilityStatement resource
Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
A human-readable summary of the resource conveying the essential clinical and business information for the resource.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
The status of this capability statement. Enables tracking the life-cycle of the content.
A date, date-time or partial date (e.g. just year or year + month). If hours and minutes are specified, a time zone SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates.
Contact details to assist a user in finding and communicating with the publisher.
A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate capability statement instances.
A legal or geographic region in which the capability statement is intended to be used.
A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
The way that this statement is intended to be used, to describe an actual running instance of software, a particular product (kind, not instance of software) or a class of implementation (e.g. a desired purchase).
Reference to a canonical URL of another CapabilityStatement that this software implements. This capability statement is a published API description that corresponds to a business service. The server may actually implement a subset of the capability statement it claims to implement, so the capability statement must specify the full capability details.
Reference to a canonical URL of another CapabilityStatement that this software adds to. The capability statement automatically includes everything in the other statement, and it is not duplicated, though the server may repeat the same resources, interactions and operations to add additional details to them.
A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
The version of the FHIR specification that this CapabilityStatement describes (which SHALL be the same as the FHIR version of the CapabilityStatement itself). There is no default value.
A list of the formats supported by this implementation using their content types.
A list of the patch formats supported by this implementation using their content types.
A list of implementation guides that the server does (or should) support in their entirety.
A definition of the restful capabilities of the solution, if any.
A description of the messaging capabilities of the solution.
A document definition.
{ "resourceType": "CapabilityStatement", "id": "example", "text": { "status": "generated", "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n\t\t\t<p>The EHR Server supports the following transactions for the resource Person: read, vread, \n update, history, search(name,gender), create and updates.</p>\n\t\t\t<p>The EHR System supports the following message: admin-notify::Person.</p>\n\t\t\t<p>The EHR Application has a \n <a href=\"http://fhir.hl7.org/base/Profilebc054d23-75e1-4dc6-aca5-838b6b1ac81d/_history/b5fdd9fc-b021-4ea1-911a-721a60663796\">general document profile</a>.\n </p>\n\t\t</div>" }, "url": "urn:uuid:68D043B5-9ECF-4559-A57A-396E0D452311", "version": "20130510", "name": "ACME-EHR", "title": "ACME EHR capability statement", "status": "draft", "experimental": true, "date": "2012-01-04", "publisher": "ACME Corporation", "contact": [ { … } ], "description": "This is the FHIR capability statement for the main EHR at ACME for the private interface - it does not describe the public interface", "useContext": [ { … } ], "jurisdiction": [ { … } ], "purpose": "Main EHR capability statement, published for contracting and operational support", "copyright": "Copyright © Acme Healthcare and GoodCorp EHR Systems", "kind": "instance", "instantiates": [ "http://ihe.org/fhir/CapabilityStatement/pixm-client" ], "software": { "name": "EHR", "version": "0.00.020.2134", "releaseDate": "2012-01-04" }, "implementation": { "description": "main EHR at ACME", "url": "http://10.2.3.4/fhir" }, "fhirVersion": "4.0.1", "format": [ "xml", "json" ], "patchFormat": [ "application/xml-patch+xml", "application/json-patch+json" ], "implementationGuide": [ "http://hl7.org/fhir/us/lab" ], "rest": [ { … } ], "messaging": [ { … } ], "document": [ { … } ] }
curl -i -X GET \ 'https://docs.heydonto.com/_mock/apis/fhir/openapi/fhir/capability-statement/{id}' \ -H 'Authorization: Bearer <YOUR_JWT_HERE>'
This is a CapabilityStatement resource
Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
A human-readable summary of the resource conveying the essential clinical and business information for the resource.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
The status of this capability statement. Enables tracking the life-cycle of the content.
A date, date-time or partial date (e.g. just year or year + month). If hours and minutes are specified, a time zone SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates.
Contact details to assist a user in finding and communicating with the publisher.
A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate capability statement instances.
A legal or geographic region in which the capability statement is intended to be used.
A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
The way that this statement is intended to be used, to describe an actual running instance of software, a particular product (kind, not instance of software) or a class of implementation (e.g. a desired purchase).
Reference to a canonical URL of another CapabilityStatement that this software implements. This capability statement is a published API description that corresponds to a business service. The server may actually implement a subset of the capability statement it claims to implement, so the capability statement must specify the full capability details.
Reference to a canonical URL of another CapabilityStatement that this software adds to. The capability statement automatically includes everything in the other statement, and it is not duplicated, though the server may repeat the same resources, interactions and operations to add additional details to them.
A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
The version of the FHIR specification that this CapabilityStatement describes (which SHALL be the same as the FHIR version of the CapabilityStatement itself). There is no default value.
A list of the formats supported by this implementation using their content types.
A list of the patch formats supported by this implementation using their content types.
A list of implementation guides that the server does (or should) support in their entirety.
A definition of the restful capabilities of the solution, if any.
A description of the messaging capabilities of the solution.
A document definition.
{ "resourceType": "CapabilityStatement", "id": "example", "text": { "status": "generated", "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n\t\t\t<p>The EHR Server supports the following transactions for the resource Person: read, vread, \n update, history, search(name,gender), create and updates.</p>\n\t\t\t<p>The EHR System supports the following message: admin-notify::Person.</p>\n\t\t\t<p>The EHR Application has a \n <a href=\"http://fhir.hl7.org/base/Profilebc054d23-75e1-4dc6-aca5-838b6b1ac81d/_history/b5fdd9fc-b021-4ea1-911a-721a60663796\">general document profile</a>.\n </p>\n\t\t</div>" }, "url": "urn:uuid:68D043B5-9ECF-4559-A57A-396E0D452311", "version": "20130510", "name": "ACME-EHR", "title": "ACME EHR capability statement", "status": "draft", "experimental": true, "date": "2012-01-04", "publisher": "ACME Corporation", "contact": [ { … } ], "description": "This is the FHIR capability statement for the main EHR at ACME for the private interface - it does not describe the public interface", "useContext": [ { … } ], "jurisdiction": [ { … } ], "purpose": "Main EHR capability statement, published for contracting and operational support", "copyright": "Copyright © Acme Healthcare and GoodCorp EHR Systems", "kind": "instance", "instantiates": [ "http://ihe.org/fhir/CapabilityStatement/pixm-client" ], "software": { "name": "EHR", "version": "0.00.020.2134", "releaseDate": "2012-01-04" }, "implementation": { "description": "main EHR at ACME", "url": "http://10.2.3.4/fhir" }, "fhirVersion": "4.0.1", "format": [ "xml", "json" ], "patchFormat": [ "application/xml-patch+xml", "application/json-patch+json" ], "implementationGuide": [ "http://hl7.org/fhir/us/lab" ], "rest": [ { … } ], "messaging": [ { … } ], "document": [ { … } ] }
This is a CapabilityStatement resource
Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
A human-readable summary of the resource conveying the essential clinical and business information for the resource.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
The status of this capability statement. Enables tracking the life-cycle of the content.
A date, date-time or partial date (e.g. just year or year + month). If hours and minutes are specified, a time zone SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates.
Contact details to assist a user in finding and communicating with the publisher.
A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate capability statement instances.
A legal or geographic region in which the capability statement is intended to be used.
A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
The way that this statement is intended to be used, to describe an actual running instance of software, a particular product (kind, not instance of software) or a class of implementation (e.g. a desired purchase).
Reference to a canonical URL of another CapabilityStatement that this software implements. This capability statement is a published API description that corresponds to a business service. The server may actually implement a subset of the capability statement it claims to implement, so the capability statement must specify the full capability details.
Reference to a canonical URL of another CapabilityStatement that this software adds to. The capability statement automatically includes everything in the other statement, and it is not duplicated, though the server may repeat the same resources, interactions and operations to add additional details to them.
A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
The version of the FHIR specification that this CapabilityStatement describes (which SHALL be the same as the FHIR version of the CapabilityStatement itself). There is no default value.
A list of the formats supported by this implementation using their content types.
A list of the patch formats supported by this implementation using their content types.
A list of implementation guides that the server does (or should) support in their entirety.
A definition of the restful capabilities of the solution, if any.
A description of the messaging capabilities of the solution.
A document definition.
curl -i -X PUT \ 'https://docs.heydonto.com/_mock/apis/fhir/openapi/fhir/capability-statement/{id}' \ -H 'Authorization: Bearer <YOUR_JWT_HERE>' \ -H 'Content-Type: application/json' \ -d '{ "resourceType": "CapabilityStatement", "id": "example", "text": { "status": "generated", "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n\t\t\t<p>The EHR Server supports the following transactions for the resource Person: read, vread, \n update, history, search(name,gender), create and updates.</p>\n\t\t\t<p>The EHR System supports the following message: admin-notify::Person.</p>\n\t\t\t<p>The EHR Application has a \n <a href=\"http://fhir.hl7.org/base/Profilebc054d23-75e1-4dc6-aca5-838b6b1ac81d/_history/b5fdd9fc-b021-4ea1-911a-721a60663796\">general document profile</a>.\n </p>\n\t\t</div>" }, "url": "urn:uuid:68D043B5-9ECF-4559-A57A-396E0D452311", "version": "20130510", "name": "ACME-EHR", "title": "ACME EHR capability statement", "status": "draft", "experimental": true, "date": "2012-01-04", "publisher": "ACME Corporation", "contact": [ { "name": "System Administrator", "telecom": [ { "system": "email", "value": "wile@acme.org" } ] } ], "description": "This is the FHIR capability statement for the main EHR at ACME for the private interface - it does not describe the public interface", "useContext": [ { "code": { "system": "http://terminology.hl7.org/CodeSystem/usage-context-type", "code": "focus" }, "valueCodeableConcept": { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/variant-state", "code": "positive" } ] } } ], "jurisdiction": [ { "coding": [ { "system": "urn:iso:std:iso:3166", "code": "US", "display": "United States of America (the)" } ] } ], "purpose": "Main EHR capability statement, published for contracting and operational support", "copyright": "Copyright © Acme Healthcare and GoodCorp EHR Systems", "kind": "instance", "instantiates": [ "http://ihe.org/fhir/CapabilityStatement/pixm-client" ], "software": { "name": "EHR", "version": "0.00.020.2134", "releaseDate": "2012-01-04" }, "implementation": { "description": "main EHR at ACME", "url": "http://10.2.3.4/fhir" }, "fhirVersion": "4.0.1", "format": [ "xml", "json" ], "patchFormat": [ "application/xml-patch+xml", "application/json-patch+json" ], "implementationGuide": [ "http://hl7.org/fhir/us/lab" ], "rest": [ { "mode": "server", "documentation": "Main FHIR endpoint for acem health", "security": { "cors": true, "service": [ { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/restful-security-service", "code": "SMART-on-FHIR" } ] } ], "description": "See Smart on FHIR documentation" }, "resource": [ { "type": "Patient", "profile": "http://registry.fhir.org/r4/StructureDefinition/7896271d-57f6-4231-89dc-dcc91eab2416", "supportedProfile": [ "http://registry.fhir.org/r4/StructureDefinition/00ab9e7a-06c7-4f77-9234-4154ca1e3347" ], "documentation": "This server does not let the clients create identities.", "interaction": [ { "code": "read" }, { "code": "vread", "documentation": "Only supported for patient records since 12-Dec 2012" }, { "code": "update" }, { "code": "history-instance" }, { "code": "create" }, { "code": "history-type" } ], "versioning": "versioned-update", "readHistory": true, "updateCreate": false, "conditionalCreate": true, "conditionalRead": "full-support", "conditionalUpdate": false, "conditionalDelete": "not-supported", "searchInclude": [ "Organization" ], "searchRevInclude": [ "Person" ], "searchParam": [ { "name": "identifier", "definition": "http://hl7.org/fhir/SearchParameter/Patient-identifier", "type": "token", "documentation": "Only supports search by institution MRN" }, { "name": "general-practitioner", "definition": "http://hl7.org/fhir/SearchParameter/Patient-general-practitioner", "type": "reference" } ] } ], "interaction": [ { "code": "transaction" }, { "code": "history-system" } ], "compartment": [ "http://hl7.org/fhir/CompartmentDefinition/patient" ] } ], "messaging": [ { "endpoint": [ { "protocol": { "system": "http://terminology.hl7.org/CodeSystem/message-transport", "code": "mllp" }, "address": "mllp:10.1.1.10:9234" } ], "reliableCache": 30, "documentation": "ADT A08 equivalent for external system notifications", "supportedMessage": [ { "mode": "receiver", "definition": "MessageDefinition/example" } ] } ], "document": [ { "mode": "consumer", "documentation": "Basic rules for all documents in the EHR system", "profile": "http://fhir.hl7.org/base/Profilebc054d23-75e1-4dc6-aca5-838b6b1ac81d/_history/b5fdd9fc-b021-4ea1-911a-721a60663796" } ] }'
This is a CapabilityStatement resource
Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
A human-readable summary of the resource conveying the essential clinical and business information for the resource.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
The status of this capability statement. Enables tracking the life-cycle of the content.
A date, date-time or partial date (e.g. just year or year + month). If hours and minutes are specified, a time zone SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates.
Contact details to assist a user in finding and communicating with the publisher.
A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate capability statement instances.
A legal or geographic region in which the capability statement is intended to be used.
A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
The way that this statement is intended to be used, to describe an actual running instance of software, a particular product (kind, not instance of software) or a class of implementation (e.g. a desired purchase).
Reference to a canonical URL of another CapabilityStatement that this software implements. This capability statement is a published API description that corresponds to a business service. The server may actually implement a subset of the capability statement it claims to implement, so the capability statement must specify the full capability details.
Reference to a canonical URL of another CapabilityStatement that this software adds to. The capability statement automatically includes everything in the other statement, and it is not duplicated, though the server may repeat the same resources, interactions and operations to add additional details to them.
A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation.
The version of the FHIR specification that this CapabilityStatement describes (which SHALL be the same as the FHIR version of the CapabilityStatement itself). There is no default value.
A list of the formats supported by this implementation using their content types.
A list of the patch formats supported by this implementation using their content types.
A list of implementation guides that the server does (or should) support in their entirety.
A definition of the restful capabilities of the solution, if any.
A description of the messaging capabilities of the solution.
A document definition.
{ "resourceType": "CapabilityStatement", "id": "example", "text": { "status": "generated", "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n\t\t\t<p>The EHR Server supports the following transactions for the resource Person: read, vread, \n update, history, search(name,gender), create and updates.</p>\n\t\t\t<p>The EHR System supports the following message: admin-notify::Person.</p>\n\t\t\t<p>The EHR Application has a \n <a href=\"http://fhir.hl7.org/base/Profilebc054d23-75e1-4dc6-aca5-838b6b1ac81d/_history/b5fdd9fc-b021-4ea1-911a-721a60663796\">general document profile</a>.\n </p>\n\t\t</div>" }, "url": "urn:uuid:68D043B5-9ECF-4559-A57A-396E0D452311", "version": "20130510", "name": "ACME-EHR", "title": "ACME EHR capability statement", "status": "draft", "experimental": true, "date": "2012-01-04", "publisher": "ACME Corporation", "contact": [ { … } ], "description": "This is the FHIR capability statement for the main EHR at ACME for the private interface - it does not describe the public interface", "useContext": [ { … } ], "jurisdiction": [ { … } ], "purpose": "Main EHR capability statement, published for contracting and operational support", "copyright": "Copyright © Acme Healthcare and GoodCorp EHR Systems", "kind": "instance", "instantiates": [ "http://ihe.org/fhir/CapabilityStatement/pixm-client" ], "software": { "name": "EHR", "version": "0.00.020.2134", "releaseDate": "2012-01-04" }, "implementation": { "description": "main EHR at ACME", "url": "http://10.2.3.4/fhir" }, "fhirVersion": "4.0.1", "format": [ "xml", "json" ], "patchFormat": [ "application/xml-patch+xml", "application/json-patch+json" ], "implementationGuide": [ "http://hl7.org/fhir/us/lab" ], "rest": [ { … } ], "messaging": [ { … } ], "document": [ { … } ] }
curl -i -X DELETE \ 'https://docs.heydonto.com/_mock/apis/fhir/openapi/fhir/capability-statement/{id}' \ -H 'Authorization: Bearer <YOUR_JWT_HERE>'
{ "statusText": "OK", "status": 200 }
curl -i -X GET \ 'https://docs.heydonto.com/_mock/apis/fhir/openapi/fhir/capability-statement/{id}/history' \ -H 'Authorization: Bearer <YOUR_JWT_HERE>'
A list of entries representing historical versions of the resource.
{ "resourceType": "Bundle", "type": "history", "entry": [ { … } ], "total": 2 }