| MolecularSequence: |
| _content | | Search on the entire content of the resource | |
| _filter | | This is the formal declaration for the _filter parameter, documented at [http://hl7.org/fhir/search_filter.html](http://hl7.org/fhir/search_filter.html) | |
| _id | | Logical id of this artifact | |
| _lastUpdated | | When the resource version last changed on given date (yyyy-mm-dd) | |
| (before) | | (before given date) | |
| (after) | | (after given date) | |
| _profile | | Profiles this resource claims to conform to | |
| _query | | A custom search profile that describes a specific defined query operation | |
| _security | | Security Labels applied to this resource | |
| _source | | Identifies where the resource comes from | |
| _tag | | Tags applied to this resource | |
| _text | | Search on the narrative of the resource | |
| chromosome | | Chromosome number of the reference sequence | |
| chromosome-variant-coordinate | | Search parameter by chromosome and variant coordinate. This will refer to part of a locus or part of a gene where search region will be represented in 1-based system. Since the coordinateSystem can either be 0-based or 1-based, this search query will include the result of both coordinateSystem that contains the equivalent segment of the gene or whole genome sequence. For example, a search for sequence can be represented as `chromosome-variant-coordinate=1$lt345$gt123`, this means it will search for the MolecularSequence resource with variants on chromosome 1 and with position >123 and <345, where in 1-based system resource, all strings within region 1:124-344 will be revealed, while in 0-based system resource, all strings within region 1:123-344 will be revealed. You may want to check detail about 0-based v.s. 1-based above. | |
| chromosome-window-coordinate | | Search parameter by chromosome and window. This will refer to part of a locus or part of a gene where search region will be represented in 1-based system. Since the coordinateSystem can either be 0-based or 1-based, this search query will include the result of both coordinateSystem that contains the equivalent segment of the gene or whole genome sequence. For example, a search for sequence can be represented as `chromosome-window-coordinate=1$lt345$gt123`, this means it will search for the MolecularSequence resource with a window on chromosome 1 and with position >123 and <345, where in 1-based system resource, all strings within region 1:124-344 will be revealed, while in 0-based system resource, all strings within region 1:123-344 will be revealed. You may want to check detail about 0-based v.s. 1-based above. | |
| identifier | | The unique identity for a particular sequence | |
| referenceseqid | | Reference Sequence of the sequence | |
| referenceseqid-variant-coordinate | | Search parameter by reference sequence and variant coordinate. This will refer to part of a locus or part of a gene where search region will be represented in 1-based system. Since the coordinateSystem can either be 0-based or 1-based, this search query will include the result of both coordinateSystem that contains the equivalent segment of the gene or whole genome sequence. For example, a search for sequence can be represented as `referenceSeqId-variant-coordinate=NC_000001.11$lt345$gt123`, this means it will search for the MolecularSequence resource with variants on NC_000001.11 and with position >123 and <345, where in 1-based system resource, all strings within region NC_000001.11:124-344 will be revealed, while in 0-based system resource, all strings within region NC_000001.11:123-344 will be revealed. You may want to check detail about 0-based v.s. 1-based above. | |
| referenceseqid-window-coordinate | | Search parameter by reference sequence and window. This will refer to part of a locus or part of a gene where search region will be represented in 1-based system. Since the coordinateSystem can either be 0-based or 1-based, this search query will include the result of both coordinateSystem that contains the equivalent segment of the gene or whole genome sequence. For example, a search for sequence can be represented as `referenceSeqId-window-coordinate=NC_000001.11$lt345$gt123`, this means it will search for the MolecularSequence resource with a window on NC_000001.11 and with position >123 and <345, where in 1-based system resource, all strings within region NC_000001.11:124-344 will be revealed, while in 0-based system resource, all strings within region NC_000001.11:123-344 will be revealed. You may want to check detail about 0-based v.s. 1-based above. | |
| type | | Amino Acid Sequence/ DNA Sequence / RNA Sequence | |
| variant-end | | End position (0-based exclusive, which menas the acid at this position will not be included, 1-based inclusive, which means the acid at this position will be included) of the variant. | |
| variant-start | | Start position (0-based inclusive, 1-based inclusive, that means the nucleic acid or amino acid at this position will be included) of the variant. | |
| window-end | | End position (0-based exclusive, which menas the acid at this position will not be included, 1-based inclusive, which means the acid at this position will be included) of the reference sequence. | |
| window-start | | Start position (0-based inclusive, 1-based inclusive, that means the nucleic acid or amino acid at this position will be included) of the reference sequence. | |
| patient (Patient): |
| _content | | Search on the entire content of the resource | |
| _filter | | This is the formal declaration for the _filter parameter, documented at [http://hl7.org/fhir/search_filter.html](http://hl7.org/fhir/search_filter.html) | |
| _id | | Logical id of this artifact | |
| _lastUpdated (exact) | | When the resource version last changed | |
| (before) | | (before given date) |
| (after) | | (after given date) |
| _profile | | Profiles this resource claims to conform to | |
| _query | | A custom search profile that describes a specific defined query operation | |
| _security | | Security Labels applied to this resource | |
| _source | | Identifies where the resource comes from | |
| _tag | | Tags applied to this resource | |
| _text | | Search on the narrative of the resource | |
| active | | Whether the patient record is active | |
| address | | A server defined search that may match any of the string fields in the Address, including line, city, district, state, country, postalCode, and/or text | |
| address-city | | A city specified in an address | |
| address-country | | A country specified in an address | |
| address-postalcode | | A postalCode specified in an address | |
| address-state | | A state specified in an address | |
| address-use | | A use code specified in an address | |
| age | | Searches for patients based on age as calculated based on current date and date of birth. Deceased patients are excluded from the search. | |
| birthOrderBoolean | | Search based on whether a patient was part of a multiple birth or not. | |
| birthdate (exact) | | The patient's date of birth | |
| (before) | | (before given date) |
| (after) | | (after given date) |
| death-date (exact) | | The date of death has been provided and satisfies this search value | |
| (before) | | (before given date) |
| (after) | | (after given date) |
| deceased | | This patient has been marked as deceased, or as a death date entered | |
| email | | A value in an email contact | |
| family | | A portion of the family name of the patient | |
| gender | | Gender of the patient | |
| general-practitioner | | Patient's nominated general practitioner, not the organization that manages the record | |
| given | | A portion of the given name of the patient | |
| identifier | | A patient identifier | |
| language | | Language code (irrespective of use value) | |
| link | | All patients linked to the given patient | |
| mothersMaidenName | | Search based on patient's mother's maiden name | |
| name | | A server defined search that may match any of the string fields in the HumanName, including family, give, prefix, suffix, suffix, and/or text | |
| organization | | The organization that is the custodian of the patient record | |
| part-agree | | Search by url for a participation agreement, which is stored in a DocumentReference | |
| phone | | A value in a phone contact | |
| phonetic | | A portion of either family or given name using some kind of phonetic matching algorithm | |
| telecom | | The value in any kind of telecom details of the patient | |
|
| Text | | Search for these words in the narrative. See [[http://technet.microsoft.com/en-us/library/ms142571.aspx]] for details |
| First Record | | (empty = start at the start) |
| # Records to return | | (default value, which is also max allowed, is 1000. Values of <2 not allowed) |
| Sort By | | |
| Summary: | | Return just a summary for each resource (if applicable) |
FHIR
© HL7.org
|
Server Home |
Health Intersections FHIR Server v1.0.330
|
FHIR Version 4.0.1
| User: ANONYMOUS (Unknown)