FHIR IG analytics| Package | accdr.fhir.ig.pkg |
| Resource Type | ImplementationGuide |
| Id | ca-on-accdr-r4-implementationguide.json |
| FHIR Version | R4 |
No resources found
No resources found
No narrative content found in resource
FHIR
FHIRsmith{
"resourceType": "ImplementationGuide",
"id": "accdr.fhir.ig.pkg",
"version": "0.9.29",
"name": "Accdr_fhir_ig_pkg",
"status": "draft",
"publisher": "fang.cao",
"description": "Ontario Health",
"jurisdiction": [
{
"coding": [
{
"system": "urn:iso:std:iso:3166",
"code": "CA"
}
]
}
],
"packageId": "accdr.fhir.ig.pkg",
"fhirVersion": [
"4.0.1"
],
"dependsOn": [
{
"packageId": "ca.on.ehr.r4",
"version": "1.0.0-snapshot14"
}
],
"definition": {
"resource": [
{
"reference": {
"reference": "CodeSystem/acCDR-contact-point-use"
},
"name": "acCDRContactPointUse",
"description": "This code is used for contact point."
},
{
"reference": {
"reference": "ValueSet/acCDR-encounter-participant-type"
},
"name": "EncounterParticipantType",
"description": "Participant type for physicians supported by Ontario Health."
},
{
"reference": {
"reference": "ValueSet/encounter-priority"
},
"name": "EncounterPriority",
"description": "The Canadian Triage and Acuity Scale (CTAS) is a scale used to determine the triage level. Triage level categorizes the patient according to the type and severity of the patient’s initial presenting signs and symptoms. This value set is used in element encounter.priority in FHIR and is contributed in PV2-40 in HL7 v2"
},
{
"reference": {
"reference": "StructureDefinition/893c516a-258a-4bf8-812f-6923fd384cc1"
},
"name": "BedTypeExtension",
"description": "An instance of StructureDefinition"
},
{
"reference": {
"reference": "CodeSystem/CanadianTriageAcuityScale"
},
"name": "CanadianTriageAcuityScale",
"description": "The Canadian Triage and Acuity Scale (CTAS) is a scale used to determine the triage level. Triage level categorizes the patient according to the type and severity of the patient’s initial presenting signs and symptoms."
},
{
"reference": {
"reference": "CapabilityStatement/ON-clinical-data-repository-server"
},
"name": "Ontario Clinical Data Repository FHIR R4 Capability Statement",
"description": "This is the FHIR R4 capability statement for Ontario Clinical Data Repository"
},
{
"reference": {
"reference": "StructureDefinition/fe000522-0913-473f-a5e3-a73e8e9a8642"
},
"name": "CDRDocumentReference",
"description": "DocumentReference"
},
{
"reference": {
"reference": "ConceptMap/cm-acCDR-provcode"
},
"name": "v2toFHIRmapforacCDRProvinceCode",
"description": "This concept map maps State/Province codes used in acCDR v2 to the state and province abbreviations supported by Ontario Health interfaces"
},
{
"reference": {
"reference": "ConceptMap/cm-acCDR-address-type"
},
"name": "v2toFHIRmapforacCDRAddressType",
"description": "An instance of ConceptMap"
},
{
"reference": {
"reference": "ConceptMap/cm-CDR-document-status"
},
"name": "v2toFHIRmapforacCDRDocumentStatus",
"description": "An instance of ConceptMap"
},
{
"reference": {
"reference": "ConceptMap/cm-contact-point-system"
},
"name": "v2toFHIRmapforacCDRContactPointSystem",
"description": "An instance of ConceptMap"
},
{
"reference": {
"reference": "ConceptMap/cm-accdr-contact-point-use"
},
"name": "v2toFHIRmapforacCDRContactPointUse",
"description": "An instance of ConceptMap"
},
{
"reference": {
"reference": "ConceptMap/cm-accdr-EncounterClass"
},
"name": "v2toFHIRmapforacCDREncounterClass",
"description": "An instance of ConceptMap"
},
{
"reference": {
"reference": "ConceptMap/cm-acCDR-mime-type"
},
"name": "v2toFHIRMapforacCDRMimeType",
"description": "An instance of ConceptMap"
},
{
"reference": {
"reference": "ConceptMap/cm-accdr-name-use"
},
"name": "v2toFHIRmapforacCDRNameUse",
"description": "An instance of ConceptMap"
},
{
"reference": {
"reference": "CodeSystem/acCDR-document-category"
},
"name": "acCDRDocumentCategory",
"description": "This code system includes all document ontology part codes not in http://loinc.org that are locally defined by Ontario Health to identify Document category (sample subset only provided below)"
},
{
"reference": {
"reference": "ConceptMap/cm-accdr-address-use"
},
"name": "v2toFHIRmapforacCDRAddressUse",
"description": "An instance of ConceptMap"
},
{
"reference": {
"reference": "ConceptMap/cm-CDR-administrative-gender"
},
"name": "v2toFHIRmapforAdministrativeGender",
"description": "An instance of ConceptMap"
},
{
"reference": {
"reference": "CodeSystem/cs-accdr-bed-desc-code"
},
"name": "acCDRBedDescCode",
"description": "This code is used to extend the LocationPhysicaType value set. It specifies the aspect of the patient location data being contributed in PV1-3 (Assigned Patient Location) in HL7 v2 and used in FHIR element Encounter.location.physicalType"
},
{
"reference": {
"reference": "CodeSystem/cs-acCDR-v2DocumentStatus"
},
"name": "v2AccdrDocumentStatus",
"description": "Code specifying the completion status of the document."
},
{
"reference": {
"reference": "CodeSystem/v2-accdr-encounter-class"
},
"name": "v2AccdrEncounterClass",
"description": "This code is used to extend the Encounter Class value set. It specifies the encounter being contributed in PV1-2 (Patient Class) in HL7 v2 and used in FHIR element Encounter.class"
},
{
"reference": {
"reference": "CodeSystem/acCDR-province-state-code"
},
"name": "v2AccdrProvinceStateCode",
"description": "This code system includes the state and province abbreviations used in acCDR v2"
},
{
"reference": {
"reference": "CodeSystem/CDF-v2-Message-type"
},
"name": "v2CdfMessageType",
"description": "Ontario Health Codes for v2 Message Type"
},
{
"reference": {
"reference": "CodeSystem/code-type"
},
"name": "CodeType",
"description": "Code specifying the acCDR document code type."
},
{
"reference": {
"reference": "CodeSystem/provincial-ext-document-type"
},
"name": "ProvincialExtDocumentType",
"description": "Temporary provincial document type codes (locally defined ConnectingOntario C-codes) created as placeholders for LOINC document codes. These codes are created as required and are replaced in the solution when LOINC codes become available from Regenstrief. The codes provided here are examples only."
},
{
"reference": {
"reference": "CodeSystem/cs-local-PV1-4values"
},
"name": "v2AccdrLocalPV14Values",
"description": "This code system contains all Local PV1-4 Codes contributed by over 160 HIC organizations to identify the local Encounter Type. The listing below is an example."
},
{
"reference": {
"reference": "ValueSet/document-category"
},
"name": "DocumentCategory",
"description": "Logical Definition: This value set includes all document ontology part codes from http://loinc.org plus any CGTA Ontology Codes locally defined by Ontario Health from http://ehealthontario.ca/fhir/CodeSystem/acCDR-document-category. (sample only provided below)"
},
{
"reference": {
"reference": "CodeSystem/document-KOD"
},
"name": "DocumentKOD",
"description": "Code specifying the acCDR document code type."
},
{
"reference": {
"reference": "CodeSystem/document-role"
},
"name": "DocumentRole",
"description": "The document-role property in LOINC characterizes the general function, responsibility, or capabilities of the author in relation to a document. The role category is a high-level classification that does not get as detailed as specialty or subspecialty so as to avoid potential overlap with the subject matter domain axis. (example Physician, Nurse, Social worker, Device etc). It is used in the element category:sliceCategory-role in FHIR in the Composition and DocumentReference profiles. This value set contains Role codes supported by acCDR - some from LOINC ontology parts and some OntarioHealth defined codes. This resource is an informative sample value set only; a reference subset containing the expanded values can be found in the latest acCDR Terminology Worksheet."
},
{
"reference": {
"reference": "CodeSystem/document-setting"
},
"name": "DocumentSetting",
"description": "The document-setting property in LOINC is a coarse definition of the Care Setting. It is not equivalent to location which typically has more locally defined meanings. It is used in the element category:sliceCategory-Setting in FHIR in the Composition and DocumentReference profiles. This value set contains Setting codes supported by acCDR - some from LOINC ontology parts and some OntarioHealth defined codes. This resource is an informative sample value set only; a reference subset containing the expanded values can be found in the latest acCDR Terminology Worksheet"
},
{
"reference": {
"reference": "CodeSystem/document-SMD"
},
"name": "DocumentSMD",
"description": "The document-subject-matter-domain property in LOINC characterizes the general focus or domain of knowledge represented within the content of the note. Typically values represent medical specialties but there is no requirement that the author have licensure or registration in that field. (example Audiology, Neurology, Cardiac Surgery, Nephrology etc). It is used in the element category:sliceCategory-subject-matter-domain in FHIR in the Composition and DocumentReference profiles. This value set contains SMD codes supported by acCDR - some from LOINC ontology parts and some OntarioHealth defined codes. This resource is an informative sample value set only; a reference subset containing the expanded values can be found in the latest acCDR Terminology Worksheet."
},
{
"reference": {
"reference": "CodeSystem/document-TOS"
},
"name": "DocumentTOS",
"description": "The document-type-of-service property in LOINC characterizes the healthcare service or activity provided to/for the patient (or other subject of the service) that is described in the document. It is used in the element category:sliceCategory-type-of-service in FHIR in the Composition and DocumentReference profiles. This value set contains TOS codes supported by acCDR - some from LOINC ontology parts and some OntarioHealth defined codes. This resource is an informative sample value set only; a reference subset containing the expanded values can be found in the latest acCDR Terminology Worksheet."
},
{
"reference": {
"reference": "SearchParameter/Encounter-date-start"
},
"name": "date-start",
"description": "The actual start date of the Encounter (Backport from R5). The parameter cannot repeat or have multiple values."
},
{
"reference": {
"reference": "SearchParameter/Encounter-end-date"
},
"name": "end-date",
"description": "The actual end date of the Encounter (Backport from R5). The parameter cannot repeat or have multiple values."
},
{
"reference": {
"reference": "Encounter/123"
},
"name": "Encounter for #123",
"description": "A(n) finished encounter of class inpatient encounter"
},
{
"reference": {
"reference": "AllergyIntolerance/123"
},
"name": "Allergic to eggs",
"description": "A(n) food allergy or intolerance of Patient/patient1"
},
{
"reference": {
"reference": "Bundle/BundleSearchEncounterResponse"
},
"name": "BundleSearchEncounterResponse",
"description": "Bundle of type searchset"
},
{
"reference": {
"reference": "Bundle/discharge-summary-example-with-resource-entries"
},
"name": "discharge-summary-example-with-resource-entries",
"description": "Bundle of type document"
},
{
"reference": {
"reference": "Bundle/doc-bundle-example-001"
},
"name": "doc-bundle-example-001",
"description": "Bundle of type document"
},
{
"reference": {
"reference": "DocumentReference/docRef-containing-bundle-example"
},
"name": "docRef-containing-bundle-example",
"description": "The current document reference of category Discharge summarization for #test-patient"
},
{
"reference": {
"reference": "Bundle/FetchDocumentReferenceResponseExample"
},
"name": "FetchDocumentReferenceResponseExample",
"description": "Bundle of type searchset"
},
{
"reference": {
"reference": "Bundle/search-document-response-example"
},
"name": "search-document-response-example",
"description": "Bundle of type searchset"
},
{
"reference": {
"reference": "DocumentReference/example"
},
"name": "example",
"description": "The current document reference for #test-patient"
},
{
"reference": {
"reference": "Patient/123"
},
"name": "Onjohn1 Onsmith1",
"description": "Patient from Toronto, CAN"
},
{
"reference": {
"reference": "Bundle/BundleSearchAllergyResponse"
},
"name": "BundleSearchAllergyResponse",
"description": "Bundle of type searchset"
},
{
"reference": {
"reference": "StructureDefinition/ext-document-code-type"
},
"name": "Document Type",
"description": "An instance of StructureDefinition"
},
{
"reference": {
"reference": "StructureDefinition/8078e43d-4a3c-4742-873a-54cea909e8cb"
},
"name": "LOINC Ontology Axis",
"description": "An instance of StructureDefinition"
},
{
"reference": {
"reference": "StructureDefinition/patient-birthTime"
},
"name": "Birth Time",
"description": "The time of day that the Patient was born. This includes the date to ensure that the timezone information can be communicated effectively."
},
{
"reference": {
"reference": "StructureDefinition/1896d8dc-002b-49bd-b8b6-5efedf1cdcce"
},
"name": "HealthCardVersionCode",
"description": "An assigned sequence code, uniquely identifying a Health Card issued (or potentially issued) to a Registered Person"
},
{
"reference": {
"reference": "StructureDefinition/addb36e1-b171-4273-9360-d321b3e2beea"
},
"name": "DIN is Representative",
"description": "If set to true, indicates that the medication code sent was chosen as a "representative" code of a drug picked at a more general level. I.e. The user didn't actually choose this specific code. The intended constraints around what drug should be supplied are conveyed by the request's substitution rules."
},
{
"reference": {
"reference": "StructureDefinition/00759f9f-2d5e-42b6-8de0-65b99bd5a6b9"
},
"name": "Medication Strength Description",
"description": "Provides a textual description of the strength of the active ingredient(s) in the medication"
},
{
"reference": {
"reference": "StructureDefinition/396ba4c5-85b9-453d-a584-8d5fd8730d07"
},
"name": "Note",
"description": "An instance of StructureDefinition"
},
{
"reference": {
"reference": "StructureDefinition/7c179b18-8f7a-4cac-b1b6-4d0248d24479"
},
"name": "Recipient",
"description": "Copied Practitioner - Identify practitioners who are to be copied on this order/report. It is important to identify all cc’d practitioners so that each practitioner is aware who is copied, and to ensure that the report is available to each practitioner through the practitioner query."
},
{
"reference": {
"reference": "ValueSet/identifier-type"
},
"name": "IdentifierType",
"description": "A coded type for an identifier that can be used to determine which identifier to use for a specific purpose"
},
{
"reference": {
"reference": "ValueSet/local-document-types"
},
"name": "LocalDocumentType",
"description": "This value set contains all Local Codes contributed by over 160 sending systems (code systems) in HL7v2 OBR-4 and/or OBX-3 to identify the local document type/section. Each contributing site has their own set of local codes/code systems defined by OIDs. This value set contains over 145,000 local codes. These local codes are used in FHIR by elements Composition.type, Composition.section.code, DocumentReference.type. The listing below is an example of codes from two local coding systems identified by the OIDS 2.16.840.1.113883.3.239.23.10.102.8 (Trillium Muse system report codes), and 2.16.840.1.113883.3.239.23.18.10.1(SickKids EPIC system report codes). This resource is an informative value set and not the full list."
},
{
"reference": {
"reference": "CodeSystem/acCDR-MimeType"
},
"name": "MimeType",
"description": "The value set identifies attachment mime type supported by acCDR"
},
{
"reference": {
"reference": "ValueSet/provincial-document-types"
},
"name": "ProvincialDocumentType",
"description": "Logical Definition: This value set contains all Provincial document type Codes. It include codes from http://loinc.org where SCALE_TYP = Doc and all locally defined Connecting Ontario C_xxxx Codes."
},
{
"reference": {
"reference": "StructureDefinition/additional-binding"
},
"name": "Additional Binding Extension",
"description": "Extension definition for Additional Binding. Additional Bindings are in the R5 Element Definition; this extension is used in prior versions (instead of the R5 cross-version extension)"
},
{
"reference": {
"reference": "ValueSet/identifier-type"
},
"name": "Identifier Type Codes",
"description": "A coded type for an identifier that can be used to determine which identifier to use for a specific purpose."
},
{
"reference": {
"reference": "ValueSet/acCDR-AddressType"
},
"name": "AddressType",
"description": "Codes supported by eHealth Ontario indicating the type of address (physical/postal). This is strict sub-set of the core FHIR value set."
},
{
"reference": {
"reference": "ValueSet/acCDR-address-use"
},
"name": "AddressUse",
"description": "Codes supported by eHealth Ontario indicating how the patient address is used. This is strict sub-set of the core FHIR value set."
},
{
"reference": {
"reference": "ValueSet/accdr-vs-location-physical-type"
},
"name": "LocationPhysicalType",
"description": "Location Physical Type - this value set specifies the aspect of the patient location data being contributed in PV1-3 (Assigned Patient Location) in HL7 v2 and used in FHIR element Encounter.location.physicalType"
},
{
"reference": {
"reference": "ValueSet/acCDR-MimeType"
},
"name": "MimeType",
"description": "Attachment mime type supported by acCDR"
},
{
"reference": {
"reference": "ValueSet/acCDRProvinceStateCode"
},
"name": "v2AccdrProvinceStateCode",
"description": "Codes for provinces, states and territories supported by acCDR"
},
{
"reference": {
"reference": "ValueSet/accdrv2observationstatus"
},
"name": "ObservationStatus",
"description": "v2 Observation Status. It is used in the acCDR v2 specification in OBX.11. Is not identical to v2 table 0085"
},
{
"reference": {
"reference": "ValueSet/acCDRPatientContactRelationship"
},
"name": "PatientContactRelationship",
"description": "A code specifying relationship to the patient"
},
{
"reference": {
"reference": "ValueSet/document-code-type"
},
"name": "CodeType",
"description": "Code specifying the acCDR Document code type."
},
{
"reference": {
"reference": "ValueSet/accdrv2documentstatus"
},
"name": "DocumentStatus",
"description": "v2 Completion Status of Document. It is used in the acCDR v2 specification in OBR.25"
},
{
"reference": {
"reference": "ValueSet/encounter.class"
},
"name": "EncounterClass",
"description": "Encounter Class - this value set is contributed in PV1-2 in HL7 v2 and is used in element Encounter.class in FHIR"
},
{
"reference": {
"reference": "ValueSet/ICD10CA"
},
"name": "ICD10CAAllCode",
"description": "This subset contains all concepts represented by the [ICD-10 CA](https://terminology.hl7.org/CodeSystem-icd10-CA.html) code system.\\n\\nThis is a broad data exchange value set that is intended to support semantic interoperability and conformance testing. It is recommended that jurisdictions define and implement more specific clinically curated subsets that contain a portion of these concepts for data capture at the point of care for their specific use case.\\n\\nFurther details about ICD-10 CA are available from the [Canadian Institute for Health Information (CIHI)](https://www.cihi.ca)."
},
{
"reference": {
"reference": "ValueSet/documentKOD"
},
"name": "DocumentKOD",
"description": "The document-kind property in LOINC Characterizes the general structure of the document at a macro level. It is used in the element category:sliceCategory-kind-of-document in FHIR in the Composition and DocumentReference profiles.This value set contains Kind of Document codes supported by acCDR - some from LOINC ontology parts and some OntarioHealth defined codes. This resource is an informative sample value set only; a reference subset containing the expanded values can be found in the latest acCDR Terminology Worksheet."
},
{
"reference": {
"reference": "ValueSet/LOINCOntologyPartType"
},
"name": "LOINCOntologyPartTypes",
"description": "Indicates the Clinical document Ontology Part Type from the LOINC Document Ontology."
},
{
"reference": {
"reference": "ValueSet/practitionerspecialtywithFrench"
},
"name": "PractitionerSpecialtywithFrench",
"description": "Codes supported by eHealth Ontario indicating the clinical, medical, surgical or other healthcare-related service specialty of a practitioner who interacts, treats or provides such services to or for a patient."
},
{
"reference": {
"reference": "ValueSet/local-PV1-4values"
},
"name": "LocalEncounterType",
"description": "This value set contains all Local PV1-4 Codes contributed by over 160 HIC organizations to identify the local Encounter Type. The listing below is an example of codes from three local coding systems identified by the OIDS 2.16.840.1.113883.3.239.22.1.83.239.23.98 (The Ottawa Hospital), 2.16.840.1.113883.3.239.22.1.83.4.1.12201 (UHN) and 2.16.840.1.113883.3.239.22.1.83.239.23.18(SickKids). This resource is an informative value set and not the full list"
},
{
"reference": {
"reference": "ValueSet/documentRole"
},
"name": "DocumentRole",
"description": "The document-role property in LOINC characterizes the general function, responsibility, or capabilities of the author in relation to a document. The role category is a high-level classification that does not get as detailed as specialty or subspecialty so as to avoid potential overlap with the subject matter domain axis. (example Physician, Nurse, Social worker, Device etc). It is used in the element category:sliceCategory-role in FHIR in the Composition and DocumentReference profiles. This value set contains Role codes supported by acCDR - some from LOINC ontology parts and some OntarioHealth defined codes. This resource is an informative sample value set only; a reference subset containing the expanded values can be found in the latest acCDR Terminology Worksheet."
},
{
"reference": {
"reference": "ValueSet/documentsetting"
},
"name": "DocumentSetting",
"description": "The document-setting property in LOINC is a coarse definition of the Care Setting. It is not equivalent to location which typically has more locally defined meanings. It is used in the element category:sliceCategory-Setting in FHIR in the Composition and DocumentReference profiles. This value set contains Setting codes supported by acCDR - some from LOINC ontology parts and some OntarioHealth defined codes. This resource is an informative sample value set only; a reference subset containing the expanded values can be found in the latest acCDR Terminology Worksheet."
},
{
"reference": {
"reference": "ValueSet/documentSMD"
},
"name": "DocumentSMD",
"description": "The document-subject-matter-domain property in LOINC characterizes the general focus or domain of knowledge represented within the content of the note. Typically values represent medical specialties but there is no requirement that the author have licensure or registration in that field. (example Audiology, Neurology, Cardiac Surgery, Nephrology etc). It is used in the element category:sliceCategory-subject-matter-domain in FHIR in the Composition and DocumentReference profiles. This value set contains SMD codes supported by acCDR - some from LOINC ontology parts and some OntarioHealth defined codes. This resource is an informative sample value set only; a reference subset containing the expanded values can be found in the latest acCDR Terminology Worksheet."
},
{
"reference": {
"reference": "ValueSet/documentTOS"
},
"name": "DocumentTOS",
"description": "The document-type-of-service property in LOINC characterizes the healthcare service or activity provided to/for the patient (or other subject of the service) that is described in the document. It is used in the element category:sliceCategory-type-of-service in FHIR in the Composition and DocumentReference profiles. This value set contains TOS codes supported by acCDR - some from LOINC ontology parts and some OntarioHealth defined codes. This resource is an informative sample value set only; a reference subset containing the expanded values can be found in the latest acCDR Terminology Worksheet."
}
],
"page": {
"nameUrl": "Home.md",
"title": "Home",
"generation": "markdown",
"page": [
{
"nameUrl": "Home-duplicate-2.md",
"title": "Home",
"generation": "markdown",
"page": [
{
"nameUrl": "Introduction.md",
"title": "Introduction",
"generation": "markdown"
},
{
"nameUrl": "Scope.md",
"title": "Scope",
"generation": "markdown"
},
{
"nameUrl": "IntendedAudience.md",
"title": "Intended Audience",
"generation": "markdown"
},
{
"nameUrl": "IdentifierPolicy.md",
"title": "Identifier Policy",
"generation": "markdown"
},
{
"nameUrl": "Glossary.md",
"title": "Glossary",
"generation": "markdown"
},
{
"nameUrl": "RevisionHistory.md",
"title": "Revision History",
"generation": "markdown"
},
{
"nameUrl": "KnownIssues.md",
"title": "Known Issues",
"generation": "markdown"
}
]
},
{
"nameUrl": "BusinessContext.md",
"title": "Business Context",
"generation": "markdown",
"page": [
{
"nameUrl": "BusinessContext-duplicate-2.md",
"title": "Business Context",
"generation": "markdown"
},
{
"nameUrl": "BusinessModel.md",
"title": "Business Model",
"generation": "markdown"
},
{
"nameUrl": "BusinessData.md",
"title": "Business Data",
"generation": "markdown"
},
{
"nameUrl": "UseCases.md",
"title": "Use Cases",
"generation": "markdown"
},
{
"nameUrl": "BusinessRules.md",
"title": "Business Rules",
"generation": "markdown"
}
]
},
{
"nameUrl": "ImplementationGuidance.md",
"title": "Implementation Guidance",
"generation": "markdown",
"page": [
{
"nameUrl": "ImplementationGuidance-duplicate-2.md",
"title": "Implementation Guidance",
"generation": "markdown"
},
{
"nameUrl": "ConsumerResponsibility.md",
"title": "Consumer Responsibility",
"generation": "markdown"
},
{
"nameUrl": "ImplementationConsiderations.md",
"title": "Implementation Considerations",
"generation": "markdown"
},
{
"nameUrl": "ConnectivitySummary.md",
"title": "Connectivity Summary",
"generation": "markdown"
}
]
},
{
"nameUrl": "ProfilesOperations.md",
"title": "Profiles & Operations",
"generation": "markdown",
"page": [
{
"nameUrl": "Index.md",
"title": "Index",
"generation": "markdown"
},
{
"nameUrl": "Profiles---Operations.md",
"title": "Profiles & Operations",
"generation": "markdown"
},
{
"nameUrl": "Operation--Fetch-DocumentReference.md",
"title": "Operation: Fetch DocumentReference",
"generation": "markdown"
},
{
"nameUrl": "Operation--Search-Document.md",
"title": "Operation: Search Document",
"generation": "markdown"
},
{
"nameUrl": "Operation--Search-Encounter.md",
"title": "Operation: Search Encounter",
"generation": "markdown"
},
{
"nameUrl": "Operation-Search-AllergyIntolerance.md",
"title": "Operation: Search AllergyIntolerance",
"generation": "markdown"
},
{
"nameUrl": "Interaction-FHIR-Batch-Query.md",
"title": "Interaction: FHIR Batch Query",
"generation": "markdown"
},
{
"nameUrl": "Profile--Binary.md",
"title": "Profile: Binary",
"generation": "markdown"
},
{
"nameUrl": "Profile--Bundle--Document.md",
"title": "Profile: Bundle (Document)",
"generation": "markdown"
},
{
"nameUrl": "Profile--Bundle--Search-Result.md",
"title": "Profile: Bundle (Search Result)",
"generation": "markdown"
},
{
"nameUrl": "Profile--Composition.md",
"title": "Profile: Composition",
"generation": "markdown"
},
{
"nameUrl": "Profile--DocumentReference.md",
"title": "Profile: DocumentReference",
"generation": "markdown"
},
{
"nameUrl": "Profile--Encounter.md",
"title": "Profile: Encounter",
"generation": "markdown"
},
{
"nameUrl": "Profile-AllergyIntolerance.md",
"title": "Profile: AllergyIntolerance",
"generation": "markdown"
},
{
"nameUrl": "Profile--Location.md",
"title": "Profile: Location",
"generation": "markdown"
},
{
"nameUrl": "Profile--OperationOutcome.md",
"title": "Profile: OperationOutcome",
"generation": "markdown"
},
{
"nameUrl": "Profile--Organization.md",
"title": "Profile: Organization",
"generation": "markdown"
},
{
"nameUrl": "Profile--Patient.md",
"title": "Profile: Patient",
"generation": "markdown"
},
{
"nameUrl": "Profile--Practitioner.md",
"title": "Profile: Practitioner",
"generation": "markdown"
},
{
"nameUrl": "Profile--PractitionerRole.md",
"title": "Profile: PractitionerRole",
"generation": "markdown"
},
{
"nameUrl": "Profile-Condition.md",
"title": "Profile: Condition",
"generation": "markdown"
},
{
"nameUrl": "Profile-ServiceRequest.md",
"title": "Profile: ServiceRequest",
"generation": "markdown"
}
]
},
{
"nameUrl": "CapabilityStatement.md",
"title": "Capability Statement",
"generation": "markdown",
"page": [
{
"nameUrl": "CapabilityStatement-duplicate-2.md",
"title": "Capability Statement",
"generation": "markdown"
},
{
"nameUrl": "ResponseHandling.md",
"title": "Response Handling",
"generation": "markdown"
}
]
},
{
"nameUrl": "Terminology.md",
"title": "Terminology",
"generation": "markdown",
"page": [
{
"nameUrl": "Terminology-duplicate-2.md",
"title": "Terminology",
"generation": "markdown"
},
{
"nameUrl": "TerminologyUpdates.md",
"title": "Terminology Updates",
"generation": "markdown"
},
{
"nameUrl": "Identifiers.md",
"title": "Identifiers",
"generation": "markdown"
}
]
},
{
"nameUrl": "Downloads.md",
"title": "Downloads",
"generation": "markdown"
}
]
}
}
}