{ "resourceType": "ImplementationGuide", "implicitRules": "http://hl7.org/ImplementationGuide/ocp-ig", "text": { "status": "empty", "div": "
" }, "url": "http://hl7.org/ImplementationGuide/ocp-ig", "version": "1.0", "name": "Omnibus Care Plan", "status": "draft", "date": "2018-08-29T05:22:18.2303804+00:00", "contact": [ { "name": "Ioana Singureanu" } ], "copyright": "SAMHSA 2018", "fhirVersion": "3.0.1", "package": [ { "name": "OCP Profiles", "resource": [ { "example": false, "name": "OCP Appointment Profile", "description": "The Omnibus Care Plan (OCP) Appointment profile is used to provide information about a planned meeting that may be in the future or past. The resource only describes a single meeting, a series of repeating visits would require multiple appointment resources to be created for each instance. The visit scheduled by an appointment may be in person or remote (by phone, video conference, etc.) All that matters is that the time and usage of one or more individuals, locations and/or pieces of equipment is being fully or partially reserved for a designated period of time.", "sourceReference": { "reference": "http://hl7.org/fhir/StructureDefinition/ocp-appointment" } }, { "example": false, "name": "OCP Communication Profile", "description": "This OCP (Omnibus Care Plan) Communication profile describes an occurrence of information being transmitted. A communication is a conveyance of information from one entity, a sender, to another entity, a receiver and the information is delivered only once. The sender and receivers may be patients, practitioners, related persons, organizations, or devices. It identifies which core elements, extensions, and value sets SHALL be present in the resource when using this profile.\r\nCommunication does not deal with the duration of a call, it represents the fact that information was transferred at a particular point in time.", "sourceReference": { "reference": "http://hl7.org/fhir/StructureDefinition/ocp-communication" } }, { "example": false, "name": "OCP Coverage Profile", "description": "This profile describes minimum expectations for the Coverage resource to record, search and fetch basic reimbursements or payment for health care products and services about an individual Omnibus Care Plan (OCP) patient. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile.\r\nBase StructureDefinition for Coverage Resource.", "sourceReference": { "reference": "http://hl7.org/fhir/StructureDefinition/ocp-coverage" } }, { "example": false, "name": "OCP EpisodeOfCare Profile", "description": "The EpisodeOfCare Profile contains information about an association of a Omnibus Care Plan (OCP) Patient with a Healthcare Provider for a period of time under which related healthcare activities may occur. In many cases, this represents a period of time where the Healthcare Provider has some level of responsibility for the care of the patient regarding a specific condition or problem, even if not currently participating in an encounter.\r\nThe EpisodeOfCare profile is primarily used as a tracking resource, and contains details about the purpose of the care and can exist without any activities. The minimal information that would be required in an episode of care would be a OCP patient, organization and a reason for the ongoing association. Other reasons for creating an EpisodeOfCare could be for tracking the details required for government reporting or billing.\r\nThe primary difference between the EpisodeOfCare and the Encounter is that the Encounter records the details of an activity directly relating to the patient, while the EpisodeOfCare is the container that can link a series of Encounters together for problems/issues.", "sourceReference": { "reference": "http://hl7.org/fhir/StructureDefinition/ocp-episodeofcare" } }, { "example": false, "name": "OCP Flag Profile", "description": "The Omnibus Care Plan (OCP) Flag profile is used to alert practitioners to information that is important to influence their interaction with a Omnibus Care Plan (OCP) Patient prior to detailed review of the record. Flags are not used to convey information to a specific individual or organization. Flags are not raised as a result of a reported or proposed action.", "sourceReference": { "reference": "http://hl7.org/fhir/StructureDefinition/ocp-flag" } }, { "example": false, "name": "OCP HealthcareService Profile", "description": "The Omnibus Care Plan (OCP) HealthcareService profile is used to describe a single healthcare service or category of services that are provided by an organization at a location. The location of the services could be virtual, as with TeleMedicine Services. OCP HealthcareService resources do not represent Computer related Services (not SOA). The OCP HealthcareService resource can be used with the Schedule resource to define actual availability of the service. When creating an Appointment, the OCP HealthcareService is to be assigned to one of the participants. It is up to the scheduling system to determine if the service is available, and can be accepted.", "sourceReference": { "reference": "http://hl7.org/fhir/StructureDefinition/ocp-healthcareservice" } }, { "example": false, "name": "OCP Patient", "description": "This profile describes minimum expectations for the Patient resource to record, search and fetch basic demographics and other administrative information about an individual Omnibus Care Plan (OCP) patient. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile.\r\n\r\nDemographics and other administrative information about an individual or other health-related services.", "sourceReference": { "reference": "http://hl7.org/fhir/StructureDefinition/ocp-patient" } }, { "example": false, "name": "OCP Practitioner Profile", "description": "This profile describes about the Omnibus Care Plan (OCP) Practitioner who is directly or indirectly involved in the provisioning of healthcare.\r\nThe profile sets minimum expectations for OCP Practitioner resource to record [content] associated with a patient. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile.\r\nThis specification describes how OCP Practitioner populates a FHIR Practitioner resource. This OCP Practitioner profile does not use any contained resources. Contained resources allow the inadvertent sharing of Protected Information to unauthorized users and application. Therefore, any references to patients, providers, organizations are described as external references to resources stored on the same server.\r\nPractitioners include (but are not limited to): physicians, dentists, pharmacists, physician assistants, nurses, scribes, midwives, dietitians, therapists, optometrists, paramedics, medical technicians, laboratory scientists, prosthetic technicians, radiographers, social workers, professional home carers, official volunteers, receptionists handling patient registration, IT personnel merging or unmerging patient records.", "sourceReference": { "reference": "http://hl7.org/fhir/StructureDefinition/ocp-practitioner" } }, { "example": false, "name": "OCP RelatedPerson Profile", "description": "This profile is primarily used for attribution of information, since RelatedPersons are often a source of information about the Omnibus Care Plan (OCP) patient. For keeping information about people for contact purposes for a patient, use a Patient's Contact element. Some individuals may serve as both a Patient's Contact and a Related Person. Information about a person that is involved in the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process. \r\nRelatedPersons typically have a personal or non-healthcare-specific professional relationship to the patient.", "sourceReference": { "reference": "http://hl7.org/fhir/StructureDefinition/ocp-relatedperson" } }, { "example": false, "name": "OCP PractitionerRole Profile", "description": "This Omnibus Care Plan (OCP) PractitionerRole profile describes a specific set of roles/locations/specialties/services that a practitioner may perform at an organization for a period of time.\r\nThe profile identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile.\r\n\r\nPractitionerRole covers the recording of the location and types of services that Practitioners are able to provide for an organization.\r\n\r\nThe role, specialty, location and telecom properties can be repeated if required in other instances of the PractitionerRole. Some systems record a collection of service values for a single location, others record the single service and the list of locations it is available. Both are acceptable options for representing this data.\r\n\r\nQualifications (from the Practitioner resource) do not imply a Role, but might be considered when an Organization allocates practitioners to roles within their organization, and could provide useful information (such as expiry information) which could need to be tracked in some situations to ensure they continue to be eligible for a specific role.", "sourceReference": { "reference": "http://hl7.org/fhir/StructureDefinition/ocp-practitionerrole" } }, { "example": false, "name": "OCP Task Profile", "description": "This profile tracks the state of a task, enabling systems to ensure that tasks are completed. This information is kept separate from the operational details necessary to complete the task, as those details vary across and even within workflows. That detail is expected to be carried as the subject of the task. Tasks may have named inputs and outputs. Inputs represent information that may or must be present in order for a task to complete. Outputs represent intermediate or final results produced by a task.", "sourceReference": { "reference": "http://hl7.org/fhir/StructureDefinition/ocp-task" } } ] }, { "name": "C2S Profiles", "resource": [ { "example": false, "name": "C2S Consent Profile", "description": "The FHIR STU3 (Release 3) Consent profile describes how Consent2Share (C2S) application and associated access control solution uses FHIR resources to represent and persist patient consent for treatment, research, or disclosure (e.g. 42 CFR Part 2, Title 38). \r\nThis specification describes how C2S populates a FHIR Consent resource. This Consent profile does not use any contained resources. Contained resources allow the inadvertent sharing of Protected Information to unauthorized users and application. Therefore, any references to patients, providers, organizations are described as external references to resources stored on the same server. \r\n Dependencies: Consents that conform to this specification must include reference other resources: \r\n- Patient (as patient and/or consenting party), RelatedPerson (as consenting party) \r\n- Practitioner (custodians, information recipients), and - Organization (custodian, custodians, information recipients", "sourceReference": { "reference": "http://hl7.org/fhir/StructureDefinition/c2s-consent" } } ] }, { "name": "US Core References", "resource": [ { "name": "US Core Birth Sex Extension", "description": "A code classifying the person's sex assigned at birth as specified by the [Office of the National Coordinator for Health IT (ONC)](https://www.healthit.gov/newsroom/about-onc). This extension aligns with the C-CDA Birth Sex Observation (LOINC 76689-9).", "sourceReference": { "reference": "http://hl7.org/fhir/us/core/StructureDefinition/us-core-birthsex" } }, { "name": "US Core CareTeam Profile", "sourceReference": { "reference": "http://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam" } }, { "name": "US Core ethnicity Extension", "description": "Concepts classifying the person into a named category of humans sharing common history, traits, geographical origin or nationality. The ethnicity codes used to represent these concepts are based upon the [CDC ethnicity and Ethnicity Code Set Version 1.0](http://www.cdc.gov/phin/resources/vocabulary/index.html) which includes over 900 concepts for representing race and ethnicity of which 43 reference ethnicity. The ethnicity concepts are grouped by and pre-mapped to the 2 OMB ethnicity categories: - Hispanic or Latino - Not Hispanic or Latino.", "sourceReference": { "reference": "http://hl7.org/fhir/us/core/StructureDefinition/us-core-ethnicity" } }, { "example": false, "name": "US Core Location Profile", "sourceReference": { "reference": "http://hl7.org/fhir/us/core/StructureDefinition/us-core-location" } }, { "example": false, "name": "US Core Organization Profile", "sourceReference": { "reference": "http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization" } }, { "example": false, "name": "US Core Patient Profile", "description": "Defines constraints and extensions on the patient resource for the minimal set of data to query and retrieve patient demographic information.", "sourceReference": { "reference": "http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient" } }, { "name": "US Core Race Extension", "description": "Concepts classifying the person into a named category of humans sharing common history, traits, geographical origin or nationality. The race codes used to represent these concepts are based upon the [CDC Race and Ethnicity Code Set Version 1.0](http://www.cdc.gov/phin/resources/vocabulary/index.html) which includes over 900 concepts for representing race and ethnicity of which 921 reference race. The race concepts are grouped by and pre-mapped to the 5 OMB race categories: - American Indian or Alaska Native - Asian - Black or African American - Native Hawaiian or Other Pacific Islander - White.", "sourceReference": { "reference": "http://hl7.org/fhir/us/core/StructureDefinition/us-core-race" } }, { "name": "ValueSet : administrative-gender", "sourceUri": "ValueSet-administrative-gender.xml" }, { "name": "ValueSet : omb-ethnicity-category", "sourceUri": "ValueSet-omb-ethnicity-category.xml" }, { "name": "ValueSet : omb-race-category", "sourceUri": "ValueSet-omb-race-category.xml" }, { "name": "ValueSet : us-core-birthsex", "sourceUri": "ValueSet-us-core-birthsex.xml" } ] } ] }