Create

Create is an Instance Level Interaction. All resources supported will include a createResource�mutation; where Resource�is the resource name, to create resource record. At a minimum, the create mutation SHALL support an input type that will adhere to the fields in the FHIR specification for the resource being created.

example

mutation CreateExample ($practitioner: PractitionerInput!) { createPractitioner(practitioner: $practitioner) { resource { meta { versionId lastUpdated profile } active birthDate gender id name { family text } identifier { id use value system } } } }

variables

{ "practitioner": { "birthDate": "1994-07-06", "name": [ { "family": "Shelton", "text": "Blake Shelton", "given": ["Blake"], "use": "OFFICIAL", "id": "official" } ], "identifier": [ { "type": { "coding": [ { "code": "2.1", "display": "Global Practitioner Identifier", "system": "urn:baxvs:carecomm-csa-codes" } ], "text": "Global Practitioner Identifier" }, "value": "overview@country.usa", "system": "urn:oid:1.3.6.1.4.1.50624.1.2.3" } ] } }

Base Resource Create Rules

A new resource must contain a product source identifier. The Directory will supply the source identifier automatically based on request headers. The Product Source Identifier describes what product created the record. Each resource will have one and only one product source identifier.

A new resource must contain a facility association identifier. The Directory will supply the facility association identifier automatically based on request headers. The Facility Association Identifier provides context of the facility associated with the resource. All resources require a minimum of one facility association identifier, however some resources may allow more than one. Check each resource to confirm the cardinality of the facility association identifier slice.

Conformance resources are excluded from the above rules (e.g. StructureDefinition, CodeSystem, ValueSet, etc.)